From 5b5321feedce5a6885c183ed79b489386d43f1ca Mon Sep 17 00:00:00 2001 From: gabrielbodard Date: Tue, 5 Mar 2024 17:30:44 +0000 Subject: [PATCH] Published development Guidelines. --- gl/dev/app-allidx.html | 2 +- gl/dev/app-allsupp-pt-br.html | 2 +- gl/dev/app-allsupp.html | 2 +- gl/dev/app-alltrans-pt-br.html | 2 +- gl/dev/app-alltrans.html | 2 +- gl/dev/app-bibliography.html | 2 +- gl/dev/app-elements.html | 2 +- gl/dev/app-epi-ceipac.html | 2 +- gl/dev/app-epi-egyptology.html | 2 +- gl/dev/app-epi-krummreypanciera.html | 2 +- gl/dev/app-epi-mycenaean.html | 2 +- gl/dev/app-epi-oracc.html | 2 +- gl/dev/app-epi-panciera.html | 2 +- gl/dev/app-epi-petrae.html | 2 +- gl/dev/app-geo.html | 4 ++-- gl/dev/app-glossary-bg.html | 2 +- gl/dev/app-glossary-es.html | 2 +- gl/dev/app-glossary-fi.html | 2 +- gl/dev/app-glossary-fr.html | 2 +- gl/dev/app-glossary-it.html | 2 +- gl/dev/app-glossary-pt-br.html | 2 +- gl/dev/app-glossary.html | 2 +- gl/dev/app-papy-apis.html | 2 +- gl/dev/app-papy-ddbdp.html | 2 +- gl/dev/app-papy-hgv.html | 2 +- gl/dev/encode-text-pt-br.html | 2 +- gl/dev/encode-text.html | 2 +- gl/dev/idx-datesage.html | 4 ++-- gl/dev/idx-events.html | 4 ++-- gl/dev/idx-geognames.html | 4 ++-- gl/dev/idx-keywords.html | 4 ++-- gl/dev/idx-nontei.html | 2 +- gl/dev/idx-other.html | 4 ++-- gl/dev/idx-persnames.html | 4 ++-- gl/dev/idx-persons.html | 4 ++-- gl/dev/idx-places.html | 4 ++-- gl/dev/idx-socialterms.html | 4 ++-- gl/dev/idx-titlesoffices.html | 4 ++-- gl/dev/idx-wordslemmata.html | 4 ++-- gl/dev/index-body.1_div.301.html | 2 +- gl/dev/index.html | 2 +- gl/dev/intro-eps-bg.html | 2 +- gl/dev/intro-eps-de.html | 2 +- gl/dev/intro-eps-es.html | 2 +- gl/dev/intro-eps-fi.html | 2 +- gl/dev/intro-eps-fr.html | 2 +- gl/dev/intro-eps-it.html | 2 +- gl/dev/intro-eps-pt-br.html | 2 +- gl/dev/intro-eps.html | 2 +- gl/dev/intro-intro-bg.html | 2 +- gl/dev/intro-intro-de.html | 2 +- gl/dev/intro-intro-es.html | 2 +- gl/dev/intro-intro-fi.html | 2 +- gl/dev/intro-intro-fr.html | 2 +- gl/dev/intro-intro-it.html | 2 +- gl/dev/intro-intro-pt-br.html | 2 +- gl/dev/intro-intro.html | 2 +- gl/dev/ref-TEI.html | 4 ++-- gl/dev/ref-ab.html | 4 ++-- gl/dev/ref-abbr.html | 4 ++-- gl/dev/ref-abstract.html | 4 ++-- gl/dev/ref-accMat.html | 4 ++-- gl/dev/ref-acquisition.html | 4 ++-- gl/dev/ref-add.html | 4 ++-- gl/dev/ref-addName.html | 4 ++-- gl/dev/ref-addSpan.html | 4 ++-- gl/dev/ref-additional.html | 4 ++-- gl/dev/ref-additions.html | 4 ++-- gl/dev/ref-addrLine.html | 4 ++-- gl/dev/ref-address.html | 4 ++-- gl/dev/ref-adminInfo.html | 4 ++-- gl/dev/ref-altIdentifier.html | 4 ++-- gl/dev/ref-am.html | 4 ++-- gl/dev/ref-analytic.html | 4 ++-- gl/dev/ref-anchor.html | 4 ++-- gl/dev/ref-annotation.html | 6 +++--- gl/dev/ref-annotationBlock.html | 4 ++-- gl/dev/ref-app.html | 4 ++-- gl/dev/ref-application.html | 4 ++-- gl/dev/ref-att.anchoring.html | 2 +- gl/dev/ref-att.ascribed.directed.html | 2 +- gl/dev/ref-att.ascribed.html | 2 +- gl/dev/ref-att.breaking.html | 2 +- gl/dev/ref-att.cReferencing.html | 2 +- gl/dev/ref-att.canonical.html | 2 +- gl/dev/ref-att.citeStructurePart.html | 2 +- gl/dev/ref-att.citing.html | 2 +- gl/dev/ref-att.coordinated.html | 2 +- gl/dev/ref-att.damaged.html | 2 +- gl/dev/ref-att.datable.custom.html | 2 +- gl/dev/ref-att.datable.html | 2 +- gl/dev/ref-att.datable.iso.html | 2 +- gl/dev/ref-att.datable.w3c.html | 2 +- gl/dev/ref-att.datcat.html | 2 +- gl/dev/ref-att.declarable.html | 2 +- gl/dev/ref-att.declaring.html | 2 +- gl/dev/ref-att.dimensions.html | 2 +- gl/dev/ref-att.divLike.html | 2 +- gl/dev/ref-att.docStatus.html | 2 +- gl/dev/ref-att.duration.html | 2 +- gl/dev/ref-att.duration.iso.html | 2 +- gl/dev/ref-att.duration.w3c.html | 2 +- gl/dev/ref-att.editLike.html | 2 +- gl/dev/ref-att.edition.html | 2 +- gl/dev/ref-att.enjamb.html | 2 +- gl/dev/ref-att.formula.html | 2 +- gl/dev/ref-att.fragmentable.html | 2 +- gl/dev/ref-att.gaijiProp.html | 2 +- gl/dev/ref-att.global.analytic.html | 2 +- gl/dev/ref-att.global.change.html | 2 +- gl/dev/ref-att.global.facs.html | 2 +- gl/dev/ref-att.global.html | 2 +- gl/dev/ref-att.global.linking.html | 2 +- gl/dev/ref-att.global.rendition.html | 2 +- gl/dev/ref-att.global.responsibility.html | 2 +- gl/dev/ref-att.global.source.html | 2 +- gl/dev/ref-att.handFeatures.html | 2 +- gl/dev/ref-att.internetMedia.html | 2 +- gl/dev/ref-att.interpLike.html | 2 +- gl/dev/ref-att.lexicographic.html | 2 +- gl/dev/ref-att.lexicographic.normalized.html | 2 +- gl/dev/ref-att.linguistic.html | 4 ++-- gl/dev/ref-att.locatable.html | 2 +- gl/dev/ref-att.measurement.html | 2 +- gl/dev/ref-att.media.html | 2 +- gl/dev/ref-att.metrical.html | 2 +- gl/dev/ref-att.milestoneUnit.html | 2 +- gl/dev/ref-att.msClass.html | 2 +- gl/dev/ref-att.msExcerpt.html | 2 +- gl/dev/ref-att.naming.html | 2 +- gl/dev/ref-att.notated.html | 2 +- gl/dev/ref-att.patternReplacement.html | 2 +- gl/dev/ref-att.personal.html | 2 +- gl/dev/ref-att.placement.html | 2 +- gl/dev/ref-att.pointing.group.html | 2 +- gl/dev/ref-att.pointing.html | 2 +- gl/dev/ref-att.ranging.html | 2 +- gl/dev/ref-att.rdgPart.html | 2 +- gl/dev/ref-att.resourced.html | 2 +- gl/dev/ref-att.scoping.html | 2 +- gl/dev/ref-att.segLike.html | 2 +- gl/dev/ref-att.sortable.html | 2 +- gl/dev/ref-att.spanning.html | 2 +- gl/dev/ref-att.styleDef.html | 2 +- gl/dev/ref-att.tableDecoration.html | 2 +- gl/dev/ref-att.textCritical.html | 2 +- gl/dev/ref-att.timed.html | 2 +- gl/dev/ref-att.transcriptional.html | 2 +- gl/dev/ref-att.typed.html | 2 +- gl/dev/ref-att.witnessed.html | 2 +- gl/dev/ref-att.written.html | 2 +- gl/dev/ref-author.html | 4 ++-- gl/dev/ref-authority.html | 4 ++-- gl/dev/ref-availability.html | 4 ++-- gl/dev/ref-back.html | 4 ++-- gl/dev/ref-bibl.html | 4 ++-- gl/dev/ref-biblFull.html | 4 ++-- gl/dev/ref-biblScope.html | 4 ++-- gl/dev/ref-biblStruct.html | 4 ++-- gl/dev/ref-binaryObject.html | 4 ++-- gl/dev/ref-binding.html | 4 ++-- gl/dev/ref-bindingDesc.html | 4 ++-- gl/dev/ref-birth.html | 4 ++-- gl/dev/ref-bloc.html | 4 ++-- gl/dev/ref-body.html | 4 ++-- gl/dev/ref-c.html | 4 ++-- gl/dev/ref-cRefPattern.html | 4 ++-- gl/dev/ref-calendar.html | 4 ++-- gl/dev/ref-calendarDesc.html | 4 ++-- gl/dev/ref-catDesc.html | 4 ++-- gl/dev/ref-catRef.html | 4 ++-- gl/dev/ref-catchwords.html | 4 ++-- gl/dev/ref-category.html | 4 ++-- gl/dev/ref-cb.html | 4 ++-- gl/dev/ref-cell.html | 4 ++-- gl/dev/ref-certainty.html | 4 ++-- gl/dev/ref-change.html | 4 ++-- gl/dev/ref-charDecl.html | 4 ++-- gl/dev/ref-choice.html | 4 ++-- gl/dev/ref-cit.html | 4 ++-- gl/dev/ref-citeData.html | 4 ++-- gl/dev/ref-citeStructure.html | 4 ++-- gl/dev/ref-citedRange.html | 4 ++-- gl/dev/ref-classCode.html | 4 ++-- gl/dev/ref-classDecl.html | 4 ++-- gl/dev/ref-collation.html | 4 ++-- gl/dev/ref-collection.html | 4 ++-- gl/dev/ref-colophon.html | 4 ++-- gl/dev/ref-condition.html | 4 ++-- gl/dev/ref-conversion.html | 4 ++-- gl/dev/ref-corr.html | 4 ++-- gl/dev/ref-correction.html | 4 ++-- gl/dev/ref-correspAction.html | 4 ++-- gl/dev/ref-correspContext.html | 4 ++-- gl/dev/ref-correspDesc.html | 4 ++-- gl/dev/ref-country.html | 4 ++-- gl/dev/ref-creation.html | 4 ++-- gl/dev/ref-custEvent.html | 4 ++-- gl/dev/ref-custodialHist.html | 4 ++-- gl/dev/ref-damage.html | 4 ++-- gl/dev/ref-date.html | 4 ++-- gl/dev/ref-dateline.html | 4 ++-- gl/dev/ref-death.html | 4 ++-- gl/dev/ref-decoDesc.html | 4 ++-- gl/dev/ref-decoNote.html | 4 ++-- gl/dev/ref-del.html | 4 ++-- gl/dev/ref-delSpan.html | 4 ++-- gl/dev/ref-depth.html | 4 ++-- gl/dev/ref-desc.html | 4 ++-- gl/dev/ref-dim.html | 4 ++-- gl/dev/ref-dimensions.html | 4 ++-- gl/dev/ref-distinct.html | 4 ++-- gl/dev/ref-distributor.html | 4 ++-- gl/dev/ref-district.html | 4 ++-- gl/dev/ref-div.html | 4 ++-- gl/dev/ref-divGen.html | 4 ++-- gl/dev/ref-docAuthor.html | 4 ++-- gl/dev/ref-docDate.html | 4 ++-- gl/dev/ref-docEdition.html | 4 ++-- gl/dev/ref-docImprint.html | 4 ++-- gl/dev/ref-docTitle.html | 4 ++-- gl/dev/ref-edition.html | 4 ++-- gl/dev/ref-editionStmt.html | 4 ++-- gl/dev/ref-editor.html | 4 ++-- gl/dev/ref-editorialDecl.html | 4 ++-- gl/dev/ref-ellipsis.html | 4 ++-- gl/dev/ref-email.html | 4 ++-- gl/dev/ref-emph.html | 4 ++-- gl/dev/ref-encodingDesc.html | 4 ++-- gl/dev/ref-epigraph.html | 4 ++-- gl/dev/ref-event.html | 4 ++-- gl/dev/ref-ex.html | 4 ++-- gl/dev/ref-expan.html | 4 ++-- gl/dev/ref-explicit.html | 4 ++-- gl/dev/ref-extent.html | 4 ++-- gl/dev/ref-facsimile.html | 4 ++-- gl/dev/ref-figDesc.html | 4 ++-- gl/dev/ref-figure.html | 4 ++-- gl/dev/ref-fileDesc.html | 4 ++-- gl/dev/ref-filiation.html | 4 ++-- gl/dev/ref-finalRubric.html | 4 ++-- gl/dev/ref-floatingText.html | 4 ++-- gl/dev/ref-floruit.html | 4 ++-- gl/dev/ref-foliation.html | 4 ++-- gl/dev/ref-foreign.html | 4 ++-- gl/dev/ref-forename.html | 4 ++-- gl/dev/ref-form.html | 4 ++-- gl/dev/ref-front.html | 4 ++-- gl/dev/ref-funder.html | 4 ++-- gl/dev/ref-fw.html | 4 ++-- gl/dev/ref-g.html | 4 ++-- gl/dev/ref-gap.html | 4 ++-- gl/dev/ref-gb.html | 4 ++-- gl/dev/ref-gen.html | 4 ++-- gl/dev/ref-genName.html | 4 ++-- gl/dev/ref-gender.html | 4 ++-- gl/dev/ref-geo.html | 4 ++-- gl/dev/ref-geoDecl.html | 4 ++-- gl/dev/ref-geogFeat.html | 4 ++-- gl/dev/ref-geogName.html | 4 ++-- gl/dev/ref-gloss.html | 4 ++-- gl/dev/ref-glyph.html | 4 ++-- gl/dev/ref-graphic.html | 4 ++-- gl/dev/ref-group.html | 4 ++-- gl/dev/ref-handDesc.html | 4 ++-- gl/dev/ref-handNote.html | 4 ++-- gl/dev/ref-handNotes.html | 4 ++-- gl/dev/ref-handShift.html | 4 ++-- gl/dev/ref-head.html | 4 ++-- gl/dev/ref-headItem.html | 4 ++-- gl/dev/ref-headLabel.html | 4 ++-- gl/dev/ref-height.html | 4 ++-- gl/dev/ref-heraldry.html | 4 ++-- gl/dev/ref-hi.html | 4 ++-- gl/dev/ref-history.html | 4 ++-- gl/dev/ref-hyphenation.html | 4 ++-- gl/dev/ref-idno.html | 4 ++-- gl/dev/ref-imprint.html | 4 ++-- gl/dev/ref-incipit.html | 4 ++-- gl/dev/ref-index.html | 4 ++-- gl/dev/ref-institution.html | 4 ++-- gl/dev/ref-interp.html | 4 ++-- gl/dev/ref-interpGrp.html | 4 ++-- gl/dev/ref-interpretation.html | 4 ++-- gl/dev/ref-item.html | 4 ++-- gl/dev/ref-join.html | 4 ++-- gl/dev/ref-keywords.html | 4 ++-- gl/dev/ref-l.html | 4 ++-- gl/dev/ref-label.html | 4 ++-- gl/dev/ref-lang.html | 4 ++-- gl/dev/ref-langUsage.html | 4 ++-- gl/dev/ref-language.html | 4 ++-- gl/dev/ref-layout.html | 4 ++-- gl/dev/ref-layoutDesc.html | 4 ++-- gl/dev/ref-lb.html | 4 ++-- gl/dev/ref-lem.html | 4 ++-- gl/dev/ref-lg.html | 4 ++-- gl/dev/ref-licence.html | 4 ++-- gl/dev/ref-line.html | 4 ++-- gl/dev/ref-link.html | 4 ++-- gl/dev/ref-linkGrp.html | 4 ++-- gl/dev/ref-list.html | 4 ++-- gl/dev/ref-listAnnotation.html | 4 ++-- gl/dev/ref-listApp.html | 4 ++-- gl/dev/ref-listBibl.html | 4 ++-- gl/dev/ref-listChange.html | 4 ++-- gl/dev/ref-listEvent.html | 4 ++-- gl/dev/ref-listNym.html | 4 ++-- gl/dev/ref-listObject.html | 4 ++-- gl/dev/ref-listOrg.html | 4 ++-- gl/dev/ref-listPerson.html | 4 ++-- gl/dev/ref-listPlace.html | 4 ++-- gl/dev/ref-listPrefixDef.html | 4 ++-- gl/dev/ref-listRelation.html | 4 ++-- gl/dev/ref-listTranspose.html | 4 ++-- gl/dev/ref-localProp.html | 4 ++-- gl/dev/ref-location.html | 4 ++-- gl/dev/ref-locus.html | 4 ++-- gl/dev/ref-locusGrp.html | 4 ++-- gl/dev/ref-m.html | 4 ++-- gl/dev/ref-macro.abContent.html | 2 +- gl/dev/ref-macro.limitedContent.html | 2 +- gl/dev/ref-macro.paraContent.html | 2 +- gl/dev/ref-macro.phraseSeq.html | 2 +- gl/dev/ref-macro.phraseSeq.limited.html | 2 +- gl/dev/ref-macro.specialPara.html | 2 +- gl/dev/ref-macro.xtext.html | 2 +- gl/dev/ref-mapping.html | 4 ++-- gl/dev/ref-material.html | 4 ++-- gl/dev/ref-measure.html | 4 ++-- gl/dev/ref-measureGrp.html | 4 ++-- gl/dev/ref-media.html | 4 ++-- gl/dev/ref-meeting.html | 4 ++-- gl/dev/ref-mentioned.html | 4 ++-- gl/dev/ref-metamark.html | 4 ++-- gl/dev/ref-milestone.html | 4 ++-- gl/dev/ref-mod.html | 4 ++-- gl/dev/ref-model.addrPart.html | 2 +- gl/dev/ref-model.addressLike.html | 2 +- gl/dev/ref-model.annotationLike.html | 2 +- gl/dev/ref-model.annotationPart.body.html | 2 +- gl/dev/ref-model.attributable.html | 2 +- gl/dev/ref-model.availabilityPart.html | 2 +- gl/dev/ref-model.biblLike.html | 2 +- gl/dev/ref-model.biblPart.html | 2 +- gl/dev/ref-model.certLike.html | 2 +- gl/dev/ref-model.choicePart.html | 2 +- gl/dev/ref-model.common.html | 2 +- gl/dev/ref-model.correspActionPart.html | 2 +- gl/dev/ref-model.correspContextPart.html | 2 +- gl/dev/ref-model.correspDescPart.html | 2 +- gl/dev/ref-model.dateLike.html | 2 +- gl/dev/ref-model.descLike.html | 2 +- gl/dev/ref-model.describedResource.html | 2 +- gl/dev/ref-model.dimLike.html | 2 +- gl/dev/ref-model.divBottom.html | 2 +- gl/dev/ref-model.divGenLike.html | 2 +- gl/dev/ref-model.divLike.html | 2 +- gl/dev/ref-model.divPart.html | 2 +- gl/dev/ref-model.divPart.spoken.html | 2 +- gl/dev/ref-model.divTop.html | 2 +- gl/dev/ref-model.divTopPart.html | 2 +- gl/dev/ref-model.divWrapper.html | 2 +- gl/dev/ref-model.editorialDeclPart.html | 2 +- gl/dev/ref-model.emphLike.html | 2 +- gl/dev/ref-model.encodingDescPart.html | 2 +- gl/dev/ref-model.entryPart.html | 2 +- gl/dev/ref-model.eventLike.html | 2 +- gl/dev/ref-model.formPart.html | 2 +- gl/dev/ref-model.frontPart.html | 2 +- gl/dev/ref-model.gLike.html | 2 +- gl/dev/ref-model.global.edit.html | 2 +- gl/dev/ref-model.global.html | 2 +- gl/dev/ref-model.global.meta.html | 2 +- gl/dev/ref-model.gramPart.html | 2 +- gl/dev/ref-model.graphicLike.html | 2 +- gl/dev/ref-model.headLike.html | 2 +- gl/dev/ref-model.hiLike.html | 2 +- gl/dev/ref-model.highlighted.html | 2 +- gl/dev/ref-model.imprintPart.html | 2 +- gl/dev/ref-model.inter.html | 2 +- gl/dev/ref-model.lLike.html | 2 +- gl/dev/ref-model.labelLike.html | 2 +- gl/dev/ref-model.limitedPhrase.html | 2 +- gl/dev/ref-model.linePart.html | 2 +- gl/dev/ref-model.listLike.html | 2 +- gl/dev/ref-model.measureLike.html | 2 +- gl/dev/ref-model.milestoneLike.html | 2 +- gl/dev/ref-model.morphLike.html | 2 +- gl/dev/ref-model.msItemPart.html | 2 +- gl/dev/ref-model.msQuoteLike.html | 2 +- gl/dev/ref-model.nameLike.agent.html | 2 +- gl/dev/ref-model.nameLike.html | 2 +- gl/dev/ref-model.noteLike.html | 2 +- gl/dev/ref-model.objectLike.html | 2 +- gl/dev/ref-model.offsetLike.html | 2 +- gl/dev/ref-model.orgPart.html | 2 +- gl/dev/ref-model.pLike.front.html | 2 +- gl/dev/ref-model.pLike.html | 2 +- gl/dev/ref-model.pPart.data.html | 2 +- gl/dev/ref-model.pPart.edit.html | 2 +- gl/dev/ref-model.pPart.editorial.html | 2 +- gl/dev/ref-model.pPart.msdesc.html | 2 +- gl/dev/ref-model.pPart.transcriptional.html | 2 +- gl/dev/ref-model.paraPart.html | 2 +- gl/dev/ref-model.persNamePart.html | 2 +- gl/dev/ref-model.persStateLike.html | 2 +- gl/dev/ref-model.personLike.html | 2 +- gl/dev/ref-model.personPart.html | 2 +- gl/dev/ref-model.phrase.html | 2 +- gl/dev/ref-model.physDescPart.html | 2 +- gl/dev/ref-model.placeLike.html | 2 +- gl/dev/ref-model.placeNamePart.html | 2 +- gl/dev/ref-model.placeStateLike.html | 2 +- gl/dev/ref-model.profileDescPart.html | 2 +- gl/dev/ref-model.ptrLike.html | 2 +- gl/dev/ref-model.publicationStmtPart.agency.html | 2 +- gl/dev/ref-model.publicationStmtPart.detail.html | 2 +- gl/dev/ref-model.quoteLike.html | 2 +- gl/dev/ref-model.rdgLike.html | 2 +- gl/dev/ref-model.rdgPart.html | 2 +- gl/dev/ref-model.resource.html | 2 +- gl/dev/ref-model.respLike.html | 2 +- gl/dev/ref-model.segLike.html | 2 +- gl/dev/ref-model.stageLike.html | 2 +- gl/dev/ref-model.standOffPart.html | 2 +- gl/dev/ref-model.teiHeaderPart.html | 2 +- gl/dev/ref-model.titlepagePart.html | 2 +- gl/dev/ref-monogr.html | 4 ++-- gl/dev/ref-msContents.html | 4 ++-- gl/dev/ref-msDesc.html | 4 ++-- gl/dev/ref-msFrag.html | 4 ++-- gl/dev/ref-msIdentifier.html | 4 ++-- gl/dev/ref-msItem.html | 4 ++-- gl/dev/ref-msItemStruct.html | 4 ++-- gl/dev/ref-msName.html | 4 ++-- gl/dev/ref-msPart.html | 4 ++-- gl/dev/ref-musicNotation.html | 4 ++-- gl/dev/ref-name.html | 4 ++-- gl/dev/ref-namespace.html | 4 ++-- gl/dev/ref-normalization.html | 4 ++-- gl/dev/ref-notatedMusic.html | 4 ++-- gl/dev/ref-note.html | 4 ++-- gl/dev/ref-noteGrp.html | 4 ++-- gl/dev/ref-notesStmt.html | 4 ++-- gl/dev/ref-num.html | 4 ++-- gl/dev/ref-nym.html | 4 ++-- gl/dev/ref-object.html | 4 ++-- gl/dev/ref-objectDesc.html | 4 ++-- gl/dev/ref-objectIdentifier.html | 4 ++-- gl/dev/ref-objectName.html | 4 ++-- gl/dev/ref-objectType.html | 4 ++-- gl/dev/ref-offset.html | 4 ++-- gl/dev/ref-org.html | 4 ++-- gl/dev/ref-orgName.html | 4 ++-- gl/dev/ref-orig.html | 4 ++-- gl/dev/ref-origDate.html | 4 ++-- gl/dev/ref-origPlace.html | 4 ++-- gl/dev/ref-origin.html | 4 ++-- gl/dev/ref-p.html | 4 ++-- gl/dev/ref-particDesc.html | 4 ++-- gl/dev/ref-path.html | 4 ++-- gl/dev/ref-pb.html | 4 ++-- gl/dev/ref-pc.html | 4 ++-- gl/dev/ref-persName.html | 4 ++-- gl/dev/ref-persPronouns.html | 4 ++-- gl/dev/ref-person.html | 4 ++-- gl/dev/ref-personGrp.html | 4 ++-- gl/dev/ref-persona.html | 4 ++-- gl/dev/ref-phr.html | 4 ++-- gl/dev/ref-physDesc.html | 4 ++-- gl/dev/ref-place.html | 4 ++-- gl/dev/ref-placeName.html | 4 ++-- gl/dev/ref-postBox.html | 4 ++-- gl/dev/ref-postCode.html | 4 ++-- gl/dev/ref-precision.html | 4 ++-- gl/dev/ref-prefixDef.html | 4 ++-- gl/dev/ref-principal.html | 4 ++-- gl/dev/ref-profileDesc.html | 4 ++-- gl/dev/ref-projectDesc.html | 4 ++-- gl/dev/ref-provenance.html | 4 ++-- gl/dev/ref-ptr.html | 4 ++-- gl/dev/ref-pubPlace.html | 4 ++-- gl/dev/ref-publicationStmt.html | 4 ++-- gl/dev/ref-publisher.html | 4 ++-- gl/dev/ref-punctuation.html | 4 ++-- gl/dev/ref-q.html | 4 ++-- gl/dev/ref-quotation.html | 4 ++-- gl/dev/ref-quote.html | 4 ++-- gl/dev/ref-rb.html | 4 ++-- gl/dev/ref-rdg.html | 4 ++-- gl/dev/ref-rdgGrp.html | 4 ++-- gl/dev/ref-recordHist.html | 4 ++-- gl/dev/ref-redo.html | 4 ++-- gl/dev/ref-ref.html | 4 ++-- gl/dev/ref-refState.html | 4 ++-- gl/dev/ref-refsDecl.html | 4 ++-- gl/dev/ref-reg.html | 4 ++-- gl/dev/ref-region.html | 4 ++-- gl/dev/ref-relatedItem.html | 4 ++-- gl/dev/ref-relation.html | 4 ++-- gl/dev/ref-rendition.html | 4 ++-- gl/dev/ref-repository.html | 4 ++-- gl/dev/ref-resp.html | 4 ++-- gl/dev/ref-respStmt.html | 4 ++-- gl/dev/ref-retrace.html | 2 +- gl/dev/ref-revisionDesc.html | 4 ++-- gl/dev/ref-roleName.html | 4 ++-- gl/dev/ref-row.html | 4 ++-- gl/dev/ref-rs.html | 4 ++-- gl/dev/ref-rt.html | 4 ++-- gl/dev/ref-rubric.html | 4 ++-- gl/dev/ref-ruby.html | 4 ++-- gl/dev/ref-s.html | 4 ++-- gl/dev/ref-said.html | 4 ++-- gl/dev/ref-samplingDecl.html | 4 ++-- gl/dev/ref-schemaRef.html | 4 ++-- gl/dev/ref-scriptDesc.html | 4 ++-- gl/dev/ref-scriptNote.html | 4 ++-- gl/dev/ref-seal.html | 4 ++-- gl/dev/ref-sealDesc.html | 4 ++-- gl/dev/ref-secFol.html | 4 ++-- gl/dev/ref-secl.html | 4 ++-- gl/dev/ref-seg.html | 4 ++-- gl/dev/ref-segmentation.html | 4 ++-- gl/dev/ref-series.html | 4 ++-- gl/dev/ref-seriesStmt.html | 4 ++-- gl/dev/ref-settingDesc.html | 4 ++-- gl/dev/ref-settlement.html | 4 ++-- gl/dev/ref-sic.html | 4 ++-- gl/dev/ref-signatures.html | 4 ++-- gl/dev/ref-soCalled.html | 4 ++-- gl/dev/ref-source.html | 4 ++-- gl/dev/ref-sourceDesc.html | 4 ++-- gl/dev/ref-sourceDoc.html | 4 ++-- gl/dev/ref-sp.html | 4 ++-- gl/dev/ref-space.html | 4 ++-- gl/dev/ref-speaker.html | 4 ++-- gl/dev/ref-sponsor.html | 4 ++-- gl/dev/ref-stage.html | 4 ++-- gl/dev/ref-stamp.html | 4 ++-- gl/dev/ref-standOff.html | 4 ++-- gl/dev/ref-state.html | 4 ++-- gl/dev/ref-stdVals.html | 4 ++-- gl/dev/ref-street.html | 4 ++-- gl/dev/ref-styleDefDecl.html | 4 ++-- gl/dev/ref-subst.html | 4 ++-- gl/dev/ref-substJoin.html | 4 ++-- gl/dev/ref-summary.html | 4 ++-- gl/dev/ref-supplied.html | 4 ++-- gl/dev/ref-support.html | 4 ++-- gl/dev/ref-supportDesc.html | 4 ++-- gl/dev/ref-surface.html | 4 ++-- gl/dev/ref-surfaceGrp.html | 4 ++-- gl/dev/ref-surname.html | 4 ++-- gl/dev/ref-surplus.html | 4 ++-- gl/dev/ref-surrogates.html | 4 ++-- gl/dev/ref-table.html | 4 ++-- gl/dev/ref-tagUsage.html | 4 ++-- gl/dev/ref-tagsDecl.html | 4 ++-- gl/dev/ref-taxonomy.html | 4 ++-- gl/dev/ref-teiCorpus.html | 4 ++-- gl/dev/ref-teiHeader.html | 4 ++-- gl/dev/ref-teidata.certainty.html | 2 +- gl/dev/ref-teidata.count.html | 2 +- gl/dev/ref-teidata.duration.iso.html | 10 +++++----- gl/dev/ref-teidata.duration.w3c.html | 10 +++++----- gl/dev/ref-teidata.enumerated.html | 2 +- gl/dev/ref-teidata.gender.html | 2 +- gl/dev/ref-teidata.language.html | 2 +- gl/dev/ref-teidata.name.html | 2 +- gl/dev/ref-teidata.namespace.html | 2 +- gl/dev/ref-teidata.numeric.html | 2 +- gl/dev/ref-teidata.outputMeasurement.html | 4 ++-- gl/dev/ref-teidata.pattern.html | 2 +- gl/dev/ref-teidata.point.html | 4 ++-- gl/dev/ref-teidata.pointer.html | 2 +- gl/dev/ref-teidata.prefix.html | 2 +- gl/dev/ref-teidata.probCert.html | 2 +- gl/dev/ref-teidata.probability.html | 2 +- gl/dev/ref-teidata.replacement.html | 2 +- gl/dev/ref-teidata.sex.html | 2 +- gl/dev/ref-teidata.temporal.iso.html | 2 +- gl/dev/ref-teidata.temporal.w3c.html | 2 +- gl/dev/ref-teidata.text.html | 2 +- gl/dev/ref-teidata.truthValue.html | 2 +- gl/dev/ref-teidata.version.html | 2 +- gl/dev/ref-teidata.versionNumber.html | 2 +- gl/dev/ref-teidata.word.html | 2 +- gl/dev/ref-teidata.xTruthValue.html | 2 +- gl/dev/ref-teidata.xmlName.html | 2 +- gl/dev/ref-teidata.xpath.html | 2 +- gl/dev/ref-term.html | 4 ++-- gl/dev/ref-text.html | 4 ++-- gl/dev/ref-textClass.html | 4 ++-- gl/dev/ref-textLang.html | 4 ++-- gl/dev/ref-time.html | 4 ++-- gl/dev/ref-title.html | 4 ++-- gl/dev/ref-titleStmt.html | 4 ++-- gl/dev/ref-transcriptionDesc.html | 4 ++-- gl/dev/ref-transpose.html | 4 ++-- gl/dev/ref-typeDesc.html | 4 ++-- gl/dev/ref-typeNote.html | 4 ++-- gl/dev/ref-unclear.html | 4 ++-- gl/dev/ref-undo.html | 4 ++-- gl/dev/ref-unicodeProp.html | 4 ++-- gl/dev/ref-unihanProp.html | 4 ++-- gl/dev/ref-unit.html | 4 ++-- gl/dev/ref-unitDecl.html | 4 ++-- gl/dev/ref-unitDef.html | 4 ++-- gl/dev/ref-variantEncoding.html | 4 ++-- gl/dev/ref-w.html | 4 ++-- gl/dev/ref-watermark.html | 4 ++-- gl/dev/ref-width.html | 4 ++-- gl/dev/ref-wit.html | 4 ++-- gl/dev/ref-xenoData.html | 4 ++-- gl/dev/ref-zone.html | 6 +++--- gl/dev/supp-app-external-pt-br.html | 4 ++-- gl/dev/supp-app-external.html | 4 ++-- gl/dev/supp-app-inline-pt-br.html | 4 ++-- gl/dev/supp-app-inline.html | 4 ++-- gl/dev/supp-app-stylesheets-pt-br.html | 4 ++-- gl/dev/supp-app-stylesheets.html | 4 ++-- gl/dev/supp-apparatus-pt-br.html | 4 ++-- gl/dev/supp-apparatus.html | 4 ++-- gl/dev/supp-bibliography-pt-br.html | 4 ++-- gl/dev/supp-bibliography.html | 4 ++-- gl/dev/supp-commentary-pt-br.html | 4 ++-- gl/dev/supp-commentary.html | 4 ++-- gl/dev/supp-descdecor-pt-br.html | 4 ++-- gl/dev/supp-descdecor.html | 4 ++-- gl/dev/supp-descdimensions-pt-br.html | 4 ++-- gl/dev/supp-descdimensions.html | 4 ++-- gl/dev/supp-descletters-pt-br.html | 4 ++-- gl/dev/supp-descletters.html | 4 ++-- gl/dev/supp-descobject-pt-br.html | 4 ++-- gl/dev/supp-descobject.html | 4 ++-- gl/dev/supp-description-pt-br.html | 4 ++-- gl/dev/supp-description.html | 4 ++-- gl/dev/supp-desctext-pt-br.html | 4 ++-- gl/dev/supp-desctext.html | 4 ++-- gl/dev/supp-desctexttype.html | 4 ++-- gl/dev/supp-histfound-pt-br.html | 10 +++++----- gl/dev/supp-histfound.html | 10 +++++----- gl/dev/supp-histinvno-pt-br.html | 4 ++-- gl/dev/supp-histinvno.html | 4 ++-- gl/dev/supp-histlocations-pt-br.html | 4 ++-- gl/dev/supp-histlocations.html | 4 ++-- gl/dev/supp-histmodern-pt-br.html | 6 +++--- gl/dev/supp-histmodern.html | 8 ++++---- gl/dev/supp-historigdate-pt-br.html | 10 +++++----- gl/dev/supp-historigdate.html | 10 +++++----- gl/dev/supp-historigin-pt-br.html | 6 +++--- gl/dev/supp-historigin.html | 6 +++--- gl/dev/supp-history-pt-br.html | 4 ++-- gl/dev/supp-history.html | 4 ++-- gl/dev/supp-images-pt-br.html | 4 ++-- gl/dev/supp-images.html | 4 ++-- gl/dev/supp-indexing-pt-br.html | 2 +- gl/dev/supp-indexing.html | 2 +- gl/dev/supp-language-pt-br.html | 4 ++-- gl/dev/supp-language.html | 6 +++--- gl/dev/supp-publication-pt-br.html | 4 ++-- gl/dev/supp-publication.html | 4 ++-- gl/dev/supp-structure-pt-br.html | 6 +++--- gl/dev/supp-structure.html | 6 +++--- gl/dev/supp-translation-pt-br.html | 2 +- gl/dev/supp-translation.html | 2 +- gl/dev/toc-bg.html | 2 +- gl/dev/toc-es.html | 2 +- gl/dev/toc-it.html | 2 +- gl/dev/toc-pt-br.html | 2 +- gl/dev/trans-abbrevfully-pt-br.html | 4 ++-- gl/dev/trans-abbrevfully.html | 4 ++-- gl/dev/trans-abbrevmark-pt-br.html | 4 ++-- gl/dev/trans-abbrevmark.html | 4 ++-- gl/dev/trans-abbrevnotex-pt-br.html | 4 ++-- gl/dev/trans-abbrevnotex.html | 4 ++-- gl/dev/trans-abbrevpartial-pt-br.html | 4 ++-- gl/dev/trans-abbrevpartial.html | 4 ++-- gl/dev/trans-abbrevsymbo-pt-br.html | 4 ++-- gl/dev/trans-abbrevsymbol.html | 4 ++-- gl/dev/trans-abbrevuncert-pt-br.html | 4 ++-- gl/dev/trans-abbrevuncert.html | 4 ++-- gl/dev/trans-addition-pt-br.html | 4 ++-- gl/dev/trans-addition.html | 4 ++-- gl/dev/trans-additionwithmark-pt-br.html | 4 ++-- gl/dev/trans-additionwithmark.html | 4 ++-- gl/dev/trans-alt-inline.html | 4 ++-- gl/dev/trans-ambiguous-pt-br.html | 4 ++-- gl/dev/trans-ambiguous.html | 4 ++-- gl/dev/trans-ambiguousalt-pt-br.html | 4 ++-- gl/dev/trans-ambiguousalt.html | 4 ++-- gl/dev/trans-ancientcorrection-pt-br.html | 4 ++-- gl/dev/trans-ancientcorrection.html | 4 ++-- gl/dev/trans-ancientcorrectionlost-pt-br.html | 4 ++-- gl/dev/trans-ancientcorrectionlost.html | 4 ++-- gl/dev/trans-apices-pt-br.html | 4 ++-- gl/dev/trans-apices.html | 4 ++-- gl/dev/trans-breviatio-pt-br.html | 4 ++-- gl/dev/trans-breviatio.html | 4 ++-- gl/dev/trans-charactershighlighted-pt-br.html | 4 ++-- gl/dev/trans-charactershighlighted.html | 4 ++-- gl/dev/trans-claudian-pt-br.html | 6 +++--- gl/dev/trans-claudian.html | 6 +++--- gl/dev/trans-cleartext-pt-br.html | 2 +- gl/dev/trans-cleartext.html | 4 ++-- gl/dev/trans-correction-pt-br.html | 4 ++-- gl/dev/trans-correction.html | 4 ++-- gl/dev/trans-damaged-pt-br.html | 4 ++-- gl/dev/trans-damaged.html | 4 ++-- gl/dev/trans-diplomatic-pt-br.html | 2 +- gl/dev/trans-diplomatic.html | 2 +- gl/dev/trans-editorsnote-pt-br.html | 4 ++-- gl/dev/trans-editorsnote.html | 4 ++-- gl/dev/trans-ellipsis-pt-br.html | 4 ++-- gl/dev/trans-ellipsis.html | 4 ++-- gl/dev/trans-erased-pt-br.html | 4 ++-- gl/dev/trans-erased.html | 4 ++-- gl/dev/trans-erasedillegible-pt-br.html | 4 ++-- gl/dev/trans-erasedillegible.html | 4 ++-- gl/dev/trans-erasedlost-pt-br.html | 4 ++-- gl/dev/trans-erasedlost.html | 4 ++-- gl/dev/trans-erroneoussubstitution-pt-br.html | 4 ++-- gl/dev/trans-erroneoussubstitution.html | 4 ++-- gl/dev/trans-foreignellipsis-pt-br.html | 4 ++-- gl/dev/trans-foreignellipsis.html | 4 ++-- gl/dev/trans-foreigntext-pt-br.html | 8 ++++---- gl/dev/trans-foreigntext.html | 10 +++++----- gl/dev/trans-fractionknown-pt-br.html | 4 ++-- gl/dev/trans-fractionknown.html | 4 ++-- gl/dev/trans-fractionunknown-pt-br.html | 4 ++-- gl/dev/trans-fractionunknown.html | 4 ++-- gl/dev/trans-handshift-pt-br.html | 4 ++-- gl/dev/trans-handshift.html | 4 ++-- gl/dev/trans-illegiblecharapprox-pt-br.html | 4 ++-- gl/dev/trans-illegiblecharapprox.html | 4 ++-- gl/dev/trans-illegiblecharknown-pt-br.html | 4 ++-- gl/dev/trans-illegiblecharknown.html | 4 ++-- gl/dev/trans-illegiblecharunknown-pt-br.html | 4 ++-- gl/dev/trans-illegiblecharunknown.html | 4 ++-- gl/dev/trans-illegiblelineapprox-pt-br.html | 4 ++-- gl/dev/trans-illegiblelineapprox.html | 4 ++-- gl/dev/trans-illegiblelineknown-pt-br.html | 4 ++-- gl/dev/trans-illegiblelineknown.html | 4 ++-- gl/dev/trans-illegiblelineunknown-pt-br.html | 4 ++-- gl/dev/trans-illegiblelineunknown.html | 4 ++-- gl/dev/trans-illegibleotherunits-pt-br.html | 4 ++-- gl/dev/trans-illegibleotherunits.html | 4 ++-- gl/dev/trans-lacunasegmented-pt-br.html | 4 ++-- gl/dev/trans-lacunasegmented.html | 4 ++-- gl/dev/trans-ligature-pt-br.html | 4 ++-- gl/dev/trans-ligature.html | 4 ++-- gl/dev/trans-linebreak-pt-br.html | 4 ++-- gl/dev/trans-linebreak.html | 4 ++-- gl/dev/trans-linebreakdirection-pt-br.html | 4 ++-- gl/dev/trans-linebreakdirection.html | 4 ++-- gl/dev/trans-linebreakinword-pt-br.html | 4 ++-- gl/dev/trans-linebreakinword.html | 4 ++-- gl/dev/trans-lostcharapprox-pt-br.html | 4 ++-- gl/dev/trans-lostcharapprox.html | 4 ++-- gl/dev/trans-lostcharknown-pt-br.html | 4 ++-- gl/dev/trans-lostcharknown.html | 4 ++-- gl/dev/trans-lostcharmetre-pt-br.html | 4 ++-- gl/dev/trans-lostcharmetre.html | 4 ++-- gl/dev/trans-lostcharnumeral-pt-br.html | 4 ++-- gl/dev/trans-lostcharnumeral.html | 4 ++-- gl/dev/trans-lostcharpraenomen-pt-br.html | 4 ++-- gl/dev/trans-lostcharpraenomen.html | 4 ++-- gl/dev/trans-lostcharunknown-pt-br.html | 4 ++-- gl/dev/trans-lostcharunknown.html | 4 ++-- gl/dev/trans-lostlineapprox-pt-br.html | 4 ++-- gl/dev/trans-lostlineapprox.html | 4 ++-- gl/dev/trans-lostlineknown-pt-br.html | 4 ++-- gl/dev/trans-lostlineknown.html | 4 ++-- gl/dev/trans-lostlineunknown-pt-br.html | 4 ++-- gl/dev/trans-lostlineunknown.html | 4 ++-- gl/dev/trans-lostotherunits-pt-br.html | 4 ++-- gl/dev/trans-lostotherunits.html | 4 ++-- gl/dev/trans-markeddeletion-pt-br.html | 2 +- gl/dev/trans-markeddeletion.html | 2 +- gl/dev/trans-metricalelements.html | 4 ++-- gl/dev/trans-metricaltypology.html | 4 ++-- gl/dev/trans-nonstructural-pt-br.html | 4 ++-- gl/dev/trans-nonstructural.html | 10 +++++----- gl/dev/trans-numacrophonic-pt-br.html | 4 ++-- gl/dev/trans-numacrophonic.html | 4 ++-- gl/dev/trans-numknown-pt-br.html | 4 ++-- gl/dev/trans-numknown.html | 4 ++-- gl/dev/trans-numnoncongruent-pt-br.html | 4 ++-- gl/dev/trans-numnoncongruent.html | 4 ++-- gl/dev/trans-numrange-pt-br.html | 4 ++-- gl/dev/trans-numrange.html | 4 ++-- gl/dev/trans-numtick-pt-br.html | 4 ++-- gl/dev/trans-numtick.html | 4 ++-- gl/dev/trans-numunknown-pt-br.html | 4 ++-- gl/dev/trans-numunknown.html | 4 ++-- gl/dev/trans-omitted-pt-br.html | 4 ++-- gl/dev/trans-omitted.html | 4 ++-- gl/dev/trans-paragraphos-pt-br.html | 2 +- gl/dev/trans-paragraphos.html | 2 +- gl/dev/trans-parallelcopy-pt-br.html | 4 ++-- gl/dev/trans-parallelcopy.html | 4 ++-- gl/dev/trans-possiblevacat-pt-br.html | 4 ++-- gl/dev/trans-possiblevacat.html | 4 ++-- gl/dev/trans-possiblyillegible-pt-br.html | 4 ++-- gl/dev/trans-possiblyillegible.html | 4 ++-- gl/dev/trans-possiblylost-pt-br.html | 4 ++-- gl/dev/trans-possiblylost.html | 4 ++-- gl/dev/trans-previouseditor-pt-br.html | 4 ++-- gl/dev/trans-previouseditor.html | 4 ++-- gl/dev/trans-quotation-pt-br.html | 4 ++-- gl/dev/trans-quotation.html | 4 ++-- gl/dev/trans-raisedlowered-pt-br.html | 4 ++-- gl/dev/trans-raisedlowered.html | 4 ++-- gl/dev/trans-regularization-pt-br.html | 4 ++-- gl/dev/trans-regularization.html | 4 ++-- gl/dev/trans-restored-pt-br.html | 4 ++-- gl/dev/trans-restored.html | 4 ++-- gl/dev/trans-restoredillustrative-pt-br.html | 4 ++-- gl/dev/trans-restoredillustrative.html | 4 ++-- gl/dev/trans-restoredincomplete-pt-br.html | 4 ++-- gl/dev/trans-restoredincomplete.html | 4 ++-- gl/dev/trans-restoreduncert-pt-br.html | 4 ++-- gl/dev/trans-restoreduncert.html | 4 ++-- gl/dev/trans-reversed-pt-br.html | 4 ++-- gl/dev/trans-reversed.html | 4 ++-- gl/dev/trans-struckovererasure-pt-br.html | 4 ++-- gl/dev/trans-struckovererasure.html | 4 ++-- gl/dev/trans-subaudible-pt-br.html | 4 ++-- gl/dev/trans-subaudible.html | 4 ++-- gl/dev/trans-superfluous-pt-br.html | 4 ++-- gl/dev/trans-superfluous.html | 4 ++-- gl/dev/trans-supralinearetc-pt-br.html | 4 ++-- gl/dev/trans-supralinearetc.html | 4 ++-- gl/dev/trans-symbol-pt-br.html | 4 ++-- gl/dev/trans-symbol.html | 4 ++-- gl/dev/trans-symbolchirho-pt-br.html | 4 ++-- gl/dev/trans-symbolchirho.html | 4 ++-- gl/dev/trans-symbolinterpunct-pt-br.html | 4 ++-- gl/dev/trans-symbolinterpunct.html | 4 ++-- gl/dev/trans-symbolmonogr-pt-br.html | 4 ++-- gl/dev/trans-symbolmonogr.html | 4 ++-- gl/dev/trans-tallorsmall-pt-br.html | 4 ++-- gl/dev/trans-tallorsmall.html | 4 ++-- gl/dev/trans-textnotcompleted-pt-br.html | 4 ++-- gl/dev/trans-textnotcompleted.html | 4 ++-- gl/dev/trans-textpart-pt-br.html | 4 ++-- gl/dev/trans-textpart.html | 4 ++-- gl/dev/trans-uninterpreted-pt-br.html | 4 ++-- gl/dev/trans-uninterpreted.html | 4 ++-- gl/dev/trans-vacatchar-pt-br.html | 4 ++-- gl/dev/trans-vacatchar.html | 4 ++-- gl/dev/trans-vacatline-pt-br.html | 4 ++-- gl/dev/trans-vacatline.html | 4 ++-- gl/dev/trans-vacatotherunits-pt-br.html | 4 ++-- gl/dev/trans-vacatotherunits.html | 4 ++-- gl/dev/trans-verseline-pt-br.html | 4 ++-- gl/dev/trans-verseline.html | 4 ++-- gl/dev/trans-whitespace-pt-br.html | 10 +++++----- gl/dev/trans-whitespace.html | 10 +++++----- 861 files changed, 1511 insertions(+), 1511 deletions(-) diff --git a/gl/dev/app-allidx.html b/gl/dev/app-allidx.html index 28fed400c..fe3354f7a 100644 --- a/gl/dev/app-allidx.html +++ b/gl/dev/app-allidx.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Vocabulary and Indexing Guidelines

2023-04-27

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Vocabulary and Indexing Guidelines

2024-03-05

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-allsupp-pt-br.html b/gl/dev/app-allsupp-pt-br.html index d7548d91e..3f69c2865 100644 --- a/gl/dev/app-allsupp-pt-br.html +++ b/gl/dev/app-allsupp-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Lista de todas as normas de dados do suporte

2023-04-27

Este índice das Normas EpiDoc agrupa os links para todas as seções que dizem respeito ao registro da materialidade e da história do(s) objeto(s) portadores de texto, e também elementos relativos às edições acadêmicas, como comentários, ilustrações, bibliografia e dados gerais de publicação. As Normas relativas à transcrição e representação editorial do texto em si estão agrupadas em um índice separado, entitulado Lista de todas as normas de transcrição.

Estrutura básica de um arquivo EpiDoc XML

As divisões principais do corpo de um arquivo EpiDoc são:

  • Edition
    • Textpart
  • Translation
  • Apparatus
  • Commentary
  • Bibliography

Para maiores detalhes sobre cada uma destas divisões, veja:

Estrutura de uma edição EpiDoc:

  • Esta é uma das páginas mais úteis destas Normas. Ela documenta o layout básico de um arquivo EpiDoc típico com mais detalhes que as normas gerais fornecidas pelo TEI para a estrutura de um documento, especificando um número de divisões, tanto do header quanto do body do documento, que tem objetivos específicos dentro de uma edição textual acadêmica.

As páginas linkadas abaixo dão instruções mais detalhadas para o preenchimento das várias subseções que foram citadas resumidamente nas normas estruturais básicas linkadas acima.

Responsabilidade por esta seção

  1. Gabriel Bodard, autor
  2. Simona Stoyanova, autor
  3. Tom Elliott, autor
  4. Charlotte Tupman, autor
  5. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Lista de todas as normas de dados do suporte

2024-03-05

Este índice das Normas EpiDoc agrupa os links para todas as seções que dizem respeito ao registro da materialidade e da história do(s) objeto(s) portadores de texto, e também elementos relativos às edições acadêmicas, como comentários, ilustrações, bibliografia e dados gerais de publicação. As Normas relativas à transcrição e representação editorial do texto em si estão agrupadas em um índice separado, entitulado Lista de todas as normas de transcrição.

Estrutura básica de um arquivo EpiDoc XML

As divisões principais do corpo de um arquivo EpiDoc são:

  • Edition
    • Textpart
  • Translation
  • Apparatus
  • Commentary
  • Bibliography

Para maiores detalhes sobre cada uma destas divisões, veja:

Estrutura de uma edição EpiDoc:

  • Esta é uma das páginas mais úteis destas Normas. Ela documenta o layout básico de um arquivo EpiDoc típico com mais detalhes que as normas gerais fornecidas pelo TEI para a estrutura de um documento, especificando um número de divisões, tanto do header quanto do body do documento, que tem objetivos específicos dentro de uma edição textual acadêmica.

As páginas linkadas abaixo dão instruções mais detalhadas para o preenchimento das várias subseções que foram citadas resumidamente nas normas estruturais básicas linkadas acima.

Responsabilidade por esta seção

  1. Gabriel Bodard, autor
  2. Simona Stoyanova, autor
  3. Tom Elliott, autor
  4. Charlotte Tupman, autor
  5. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-allsupp.html b/gl/dev/app-allsupp.html index 168a5eb44..c8455adc2 100644 --- a/gl/dev/app-allsupp.html +++ b/gl/dev/app-allsupp.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

List of All Supporting Data Guidelines

2023-04-27

This index to the EpiDoc Guidelines groups together links to all the sections that address recording of the materiality and history of text-bearing object(s), as well as such features of scholarly editions as extended commentary, illustrations, bibliography, and general publication data. Guidelines for the transcription and editorial representation of the texts themselves are grouped together in a separate index entitled List of All Transcription Guidelines.

Basic EpiDoc XML File Structure

The main divisions in the body of an EpiDoc file are:

  • Edition
    • Textpart
  • Translation
  • Apparatus
  • Commentary
  • Bibliography

For further detail on each of these divisions, see:

Structure of an EpiDoc edition:

  • one of the most useful pages in these Guidelines. It documents the basic layout of a typical EpiDoc file, going beyond the general guidance provided by the TEI for document structure in specifying a number of divisions of both the document header and the document body that serve particular purposes in the expression of a scholarly textual edition.

The pages linked below provide more detailed instructions for filling out the various subsections that are summarized in the basic structural guidance linked above.

Responsibility for this section

  1. Gabriel Bodard, Author
  2. Simona Stoyanova, Author
  3. Tom Elliott, Author
  4. Charlotte Tupman, Author
  5. Scott Vanderbilt, Author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

List of All Supporting Data Guidelines

2024-03-05

This index to the EpiDoc Guidelines groups together links to all the sections that address recording of the materiality and history of text-bearing object(s), as well as such features of scholarly editions as extended commentary, illustrations, bibliography, and general publication data. Guidelines for the transcription and editorial representation of the texts themselves are grouped together in a separate index entitled List of All Transcription Guidelines.

Basic EpiDoc XML File Structure

The main divisions in the body of an EpiDoc file are:

  • Edition
    • Textpart
  • Translation
  • Apparatus
  • Commentary
  • Bibliography

For further detail on each of these divisions, see:

Structure of an EpiDoc edition:

  • one of the most useful pages in these Guidelines. It documents the basic layout of a typical EpiDoc file, going beyond the general guidance provided by the TEI for document structure in specifying a number of divisions of both the document header and the document body that serve particular purposes in the expression of a scholarly textual edition.

The pages linked below provide more detailed instructions for filling out the various subsections that are summarized in the basic structural guidance linked above.

Responsibility for this section

  1. Gabriel Bodard, Author
  2. Simona Stoyanova, Author
  3. Tom Elliott, Author
  4. Charlotte Tupman, Author
  5. Scott Vanderbilt, Author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-alltrans-pt-br.html b/gl/dev/app-alltrans-pt-br.html index 3adbd9a2e..485ac0f75 100644 --- a/gl/dev/app-alltrans-pt-br.html +++ b/gl/dev/app-alltrans-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Lista de Todas as Normas de Transcrição

2023-04-27

Este índice das Normas EpiDoc agrupa links para todas as seções que fornecem orientação e exemplos para fazer a marcação de aspectos do texto em si (e não da materialidade e histórico dos objetos onde ele aparece, para isto veja a Lista de Todas as Normas de Dados de Suporte). Estas seções enfocam não apenas a transcrição, no senso técnico de se relatar leitura e representar o(s) sistema(s) de escrita, mas também a forma, aparência e layout do texto e de seus caracteres, bem como outras intervenções editoriais no texto, como sua suplementação, regularização, identificação de números e similares.

Uma observação sobre Transcrição Diplomática.

Uma observação sobre lidar com espaço em branco.

Transcrição

Responsabilidade por esta seção

  1. Gabriel Bodard, Autor
  2. Charlotte Tupman, Autor
  3. Tom Elliott, Autor
  4. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Lista de Todas as Normas de Transcrição

2024-03-05

Este índice das Normas EpiDoc agrupa links para todas as seções que fornecem orientação e exemplos para fazer a marcação de aspectos do texto em si (e não da materialidade e histórico dos objetos onde ele aparece, para isto veja a Lista de Todas as Normas de Dados de Suporte). Estas seções enfocam não apenas a transcrição, no senso técnico de se relatar leitura e representar o(s) sistema(s) de escrita, mas também a forma, aparência e layout do texto e de seus caracteres, bem como outras intervenções editoriais no texto, como sua suplementação, regularização, identificação de números e similares.

Uma observação sobre Transcrição Diplomática.

Uma observação sobre lidar com espaço em branco.

Transcrição

Responsabilidade por esta seção

  1. Gabriel Bodard, Autor
  2. Charlotte Tupman, Autor
  3. Tom Elliott, Autor
  4. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-alltrans.html b/gl/dev/app-alltrans.html index 1897673fd..c79210971 100644 --- a/gl/dev/app-alltrans.html +++ b/gl/dev/app-alltrans.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

List of All Transcription Guidelines

2023-04-27

This index to the EpiDoc Guidelines groups together links to all the sections that provide guidance and examples for marking up aspects of text itself (as opposed to the materiality and history of the objects upon which they appear, for which see the List of All Supporting Data Guidelines). These sections address not only transcription in the technical sense of reporting readings and representing the writing system(s), but also the form, appearance, and layout of the text and its characters, as well as other editorial interventions in the text such as supplementation, regularization, and identification of numerals and the like.

A note on Diplomatic Transcription.

A note on whitespace handling.

Responsibility for this section

  1. Gabriel Bodard, Author
  2. Charlotte Tupman, Author
  3. Tom Elliott, Author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

List of All Transcription Guidelines

2024-03-05

This index to the EpiDoc Guidelines groups together links to all the sections that provide guidance and examples for marking up aspects of text itself (as opposed to the materiality and history of the objects upon which they appear, for which see the List of All Supporting Data Guidelines). These sections address not only transcription in the technical sense of reporting readings and representing the writing system(s), but also the form, appearance, and layout of the text and its characters, as well as other editorial interventions in the text such as supplementation, regularization, and identification of numerals and the like.

A note on Diplomatic Transcription.

A note on whitespace handling.

Responsibility for this section

  1. Gabriel Bodard, Author
  2. Charlotte Tupman, Author
  3. Tom Elliott, Author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-bibliography.html b/gl/dev/app-bibliography.html index 12e26edcc..4b695a46c 100644 --- a/gl/dev/app-bibliography.html +++ b/gl/dev/app-bibliography.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Bibliography

2023-04-27

Epigraphic and papyrological conventions

These publications are the source for the Leiden-style conventions used in the Guidelines and the Example XSLT transformations.

  1. Joshua D. Sosin et al., 2011, Papyrological conventions used in Duke Databank texts, Available: http://papyri.info/conventions.html
  2. Francisca Feraudi-Gruénais, Andreas Dafferner & Brigitte Ruck, 2002, EDH: Handbuch zur Epigraphischen Datenbank Heidelberg, Available: http://www.rzuser.uni-heidelberg.de/~f56/misc/edh-handbuch.pdf
  3. Marcus Dohnicht, Zusammenstellung der diakritischen Zeichen zur Wiedergabe der lateinischen Inschrifttexte der Antike für den Unicode (Entwurft Juli 2000), http://www.csad.ox.ac.uk/varia/unicode/Dohnicht.pdf
  4. Sterling Dow, Conventions in editing: a suggested reformulation of the Leiden System, Greek, Roman and Byzantine Studies Scholarly Aids 2, Durham, 1969
  5. Hans Krummrey and Silvio Panciera, Criteri di edizione e segni diacritici in Tituli 2 (1980), 205-215
  6. Silvio Panciera, Struttura dei supplementi e segni diacritici dieci anni dopo in Supplementa Italica 8 (1991), 9-21
  7. POxy: Oxyrhynchus Papyri, Egypt Exploration Society, 1898-
  8. Louis Robert with Jeanne Robert, Fouilles d'Amyzon en Carie, Paris: De Boccard, 1983, pp. 9-11 on Signes critiques du corpus et édition
  9. SEG: Supplementum Epigraphicum Graecum, Lugduni Batavorum: Sijthoff, 1923-

Epigraphic and Papyrological Databases not primarily based on EpiDoc

  1. Electronic Archive of Greek and Latin Epigraphy (EAGLE), available: www.eagle-eagle.it/
  2. Epigraphische Datenbank Heidelberg (EDH), available: edh-www.adw.uni-heidelberg.de
  3. Epigraphic Database Roma (EDR), available: edr-edr.it
  4. Epigraphik Datenbank Clauss-Slaby (EDCS), available: manfredclauss.de/
  5. Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE), available: http://petrae.tge-adonis.fr/index.php

Bibliography on digital epigraphy and text encoding

Further reading:

  1. Fernando-Luis Álvarez, Elena García-Barriocanal and Joaquín-L. Gómez-Pantoja, 'Sharing Epigraphic Information as Linked Data', in (eds. Sanchez-Alonso & Athanasiadis), Metadata and semantic research (Springer 2010), pp. 222-234. Available: http://www.springerlink.com/content/j71267848rvj8522/
  2. Lisa Anderson & Heidi Wendt, 'Ancient Relationships, Modern Intellectual Horizons: The practical challenges and possibilities of encoding Greek and Latin inscriptions.' In ed. M.T. Rutz & M.M. Kersel, Archaeologies of Text: Archaeology, Technology, and Ethics. Oxbow Books, 2014 (Joukowsky Institute Publication 6). Pp. 164–175.
  3. Alison Babeu, 'Epigraphy', “Rome Wasn’t Digitized in a Day”: Building a Cyberinfrastructure for Digital Classicists Draft Version 1.3—11/18/10, pp. 73-89. CLIR, 2010. Online at: http://www.clir.org/pubs/archives/Babeu2010.pdf
  4. Roger S. Bagnall, 'Integrating Digital Papyrology', presented at Online Humanities Scholarship: The Shape of Things to Come, University of Virginia, March 26-28, 2010. Available: http://archive.nyu.edu/handle/2451/29592
  5. Gabriel Bodard, The Inscriptions of Aphrodisias as electronic publication: A user's perspective and a proposed paradigm, in Digital Medievalist 4 (2008), Available: http://digitalmedievalist.org/journal/4/bodard/
  6. Gabriel Bodard, 'EpiDoc: Epigraphic Documents in XML for Publication and Interchange', in (ed. F. Feraudi-Gruénais) Latin On Stone: epigraphic research and electronic archives (Lexington Books, 2010), pp. 101-118.
  7. Gabriel Bodard, 'Digital Epigraphy and Lexicographical and Onomastic Markup'. Pre-press available: http://blog.stoa.org/archives/1226
  8. Gabriel Bodard & Simona Stoyanova (2016). Epigraphers and Encoders: Strategies for Teaching and Learning Digital Epigraphy. In ed. Bodard/Romanello, Digital Classics Outside the Echo-Chamber: Teaching, Knowledge Exchange and Public Engagement. London: Ubiquity Press. Pp. 51–68. Available: http://dx.doi.org/10.5334/bat.d
  9. Gabriel Bodard & Polina Yordanova (2020), Publication, Testing and Visualization with EFES: A tool for all stages of the EpiDoc editing process. Studia Digitalia Universitatis Babeș-Bolyai 65.1, pp. 17–35. Available: https://doi.org/10.24193/subbdigitalia.2020.1.02
  10. Hugh Cayless, Charlotte Roueché et al., 'Epigraphy in 2017', Digital Humanities Quarterly 3.1 (2009), available: http://digitalhumanities.org/dhq/vol/3/1/000030/000030.html
  11. Tim Finney, Converting Leiden-style Editions to TEI Lite XML (2001), Available: http://www.tei-c.org/Sample_Manuals/leiden.html
  12. Marion Lamé, 'Pour une codification historique des inscriptions', Rivista Storica dell'Antiquità 38 (2008), pp. 213-225. Italian translation, 'Per una codifica storica delle iscrizioni', Griselda Online, 2008. Online at: http://www.griseldaonline.it/informatica/lame.htm
  13. Laura Löser (2014). Meeting the Needs of Today’s Audiences of Epigraphy with Digital Editions. In ed. Orlandi et al. Information Technologies for Epigraphy and Cultural Heritage, pp. 239–251.
  14. Anne Mahoney, 'Epigraphy', in (eds. Burnard, O'Brian & Unsworth) Electronic Textual Editing (2006), preview online at http://www.tei-c.org/Activities/ETE/Preview/mahoney.xml
  15. Silvia Orlandi, Raffaella Santucci, Vittore Casarosa & Pietro Maria Liuzzo, eds. (2014). Information Technologies for Epigraphy and Cultural Heritage. Proceedings of the First EAGLE International Conference. Rome: Sapienza Università Editrice. Available: http://www.eagle-network.eu/wp-content/uploads/2015/01/Paris-Conference-Proceedings.pdf
  16. Charlotte Roueché and Gabriel Bodard, 'The Epidoc Aphrodisias Pilot Project', Forum Archaeologiae 23/VI/2002, online at http://farch.net
  17. Charlotte Roueché, 'Digitizing Inscribed Texts', in Text Editing, Print and the Digital World (Ashgate, 2008) pp. 159-168.
  18. Joshua D. Sosin, 'Digital Papyrology', Congress of the International Association of Papyrologists, 19 August 2010, Geneva. Available: http://blog.stoa.org/archives/1263
  19. Text Encoding Initiative, P5: Guidelines for Electronic Text Encoding and Interchange, Available: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html
  20. Charlotte Tupman, 'Contextual epigraphy and XML: digital publication and its application to the study of inscribed funerary monuments', in (eds. Bodard & Mahony) Digital Research in the Study of Classical Antiquity (Ashgate, 2010), pp. 73-86.

Responsibility for this section

  1. Gabriel Bodard, author Hugh Cayless, author Wikipedia, source

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Bibliography

2024-03-05

Epigraphic and papyrological conventions

These publications are the source for the Leiden-style conventions used in the Guidelines and the Example XSLT transformations.

  1. Joshua D. Sosin et al., 2011, Papyrological conventions used in Duke Databank texts, Available: http://papyri.info/conventions.html
  2. Francisca Feraudi-Gruénais, Andreas Dafferner & Brigitte Ruck, 2002, EDH: Handbuch zur Epigraphischen Datenbank Heidelberg, Available: http://www.rzuser.uni-heidelberg.de/~f56/misc/edh-handbuch.pdf
  3. Marcus Dohnicht, Zusammenstellung der diakritischen Zeichen zur Wiedergabe der lateinischen Inschrifttexte der Antike für den Unicode (Entwurft Juli 2000), http://www.csad.ox.ac.uk/varia/unicode/Dohnicht.pdf
  4. Sterling Dow, Conventions in editing: a suggested reformulation of the Leiden System, Greek, Roman and Byzantine Studies Scholarly Aids 2, Durham, 1969
  5. Hans Krummrey and Silvio Panciera, Criteri di edizione e segni diacritici in Tituli 2 (1980), 205-215
  6. Silvio Panciera, Struttura dei supplementi e segni diacritici dieci anni dopo in Supplementa Italica 8 (1991), 9-21
  7. POxy: Oxyrhynchus Papyri, Egypt Exploration Society, 1898-
  8. Louis Robert with Jeanne Robert, Fouilles d'Amyzon en Carie, Paris: De Boccard, 1983, pp. 9-11 on Signes critiques du corpus et édition
  9. SEG: Supplementum Epigraphicum Graecum, Lugduni Batavorum: Sijthoff, 1923-

Epigraphic and Papyrological Databases not primarily based on EpiDoc

  1. Electronic Archive of Greek and Latin Epigraphy (EAGLE), available: www.eagle-eagle.it/
  2. Epigraphische Datenbank Heidelberg (EDH), available: edh-www.adw.uni-heidelberg.de
  3. Epigraphic Database Roma (EDR), available: edr-edr.it
  4. Epigraphik Datenbank Clauss-Slaby (EDCS), available: manfredclauss.de/
  5. Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE), available: http://petrae.tge-adonis.fr/index.php

Bibliography on digital epigraphy and text encoding

Further reading:

  1. Fernando-Luis Álvarez, Elena García-Barriocanal and Joaquín-L. Gómez-Pantoja, 'Sharing Epigraphic Information as Linked Data', in (eds. Sanchez-Alonso & Athanasiadis), Metadata and semantic research (Springer 2010), pp. 222-234. Available: http://www.springerlink.com/content/j71267848rvj8522/
  2. Lisa Anderson & Heidi Wendt, 'Ancient Relationships, Modern Intellectual Horizons: The practical challenges and possibilities of encoding Greek and Latin inscriptions.' In ed. M.T. Rutz & M.M. Kersel, Archaeologies of Text: Archaeology, Technology, and Ethics. Oxbow Books, 2014 (Joukowsky Institute Publication 6). Pp. 164–175.
  3. Alison Babeu, 'Epigraphy', “Rome Wasn’t Digitized in a Day”: Building a Cyberinfrastructure for Digital Classicists Draft Version 1.3—11/18/10, pp. 73-89. CLIR, 2010. Online at: http://www.clir.org/pubs/archives/Babeu2010.pdf
  4. Roger S. Bagnall, 'Integrating Digital Papyrology', presented at Online Humanities Scholarship: The Shape of Things to Come, University of Virginia, March 26-28, 2010. Available: http://archive.nyu.edu/handle/2451/29592
  5. Gabriel Bodard, The Inscriptions of Aphrodisias as electronic publication: A user's perspective and a proposed paradigm, in Digital Medievalist 4 (2008), Available: http://digitalmedievalist.org/journal/4/bodard/
  6. Gabriel Bodard, 'EpiDoc: Epigraphic Documents in XML for Publication and Interchange', in (ed. F. Feraudi-Gruénais) Latin On Stone: epigraphic research and electronic archives (Lexington Books, 2010), pp. 101-118.
  7. Gabriel Bodard, 'Digital Epigraphy and Lexicographical and Onomastic Markup'. Pre-press available: http://blog.stoa.org/archives/1226
  8. Gabriel Bodard & Simona Stoyanova (2016). Epigraphers and Encoders: Strategies for Teaching and Learning Digital Epigraphy. In ed. Bodard/Romanello, Digital Classics Outside the Echo-Chamber: Teaching, Knowledge Exchange and Public Engagement. London: Ubiquity Press. Pp. 51–68. Available: http://dx.doi.org/10.5334/bat.d
  9. Gabriel Bodard & Polina Yordanova (2020), Publication, Testing and Visualization with EFES: A tool for all stages of the EpiDoc editing process. Studia Digitalia Universitatis Babeș-Bolyai 65.1, pp. 17–35. Available: https://doi.org/10.24193/subbdigitalia.2020.1.02
  10. Hugh Cayless, Charlotte Roueché et al., 'Epigraphy in 2017', Digital Humanities Quarterly 3.1 (2009), available: http://digitalhumanities.org/dhq/vol/3/1/000030/000030.html
  11. Tim Finney, Converting Leiden-style Editions to TEI Lite XML (2001), Available: http://www.tei-c.org/Sample_Manuals/leiden.html
  12. Marion Lamé, 'Pour une codification historique des inscriptions', Rivista Storica dell'Antiquità 38 (2008), pp. 213-225. Italian translation, 'Per una codifica storica delle iscrizioni', Griselda Online, 2008. Online at: http://www.griseldaonline.it/informatica/lame.htm
  13. Laura Löser (2014). Meeting the Needs of Today’s Audiences of Epigraphy with Digital Editions. In ed. Orlandi et al. Information Technologies for Epigraphy and Cultural Heritage, pp. 239–251.
  14. Anne Mahoney, 'Epigraphy', in (eds. Burnard, O'Brian & Unsworth) Electronic Textual Editing (2006), preview online at http://www.tei-c.org/Activities/ETE/Preview/mahoney.xml
  15. Silvia Orlandi, Raffaella Santucci, Vittore Casarosa & Pietro Maria Liuzzo, eds. (2014). Information Technologies for Epigraphy and Cultural Heritage. Proceedings of the First EAGLE International Conference. Rome: Sapienza Università Editrice. Available: http://www.eagle-network.eu/wp-content/uploads/2015/01/Paris-Conference-Proceedings.pdf
  16. Charlotte Roueché and Gabriel Bodard, 'The Epidoc Aphrodisias Pilot Project', Forum Archaeologiae 23/VI/2002, online at http://farch.net
  17. Charlotte Roueché, 'Digitizing Inscribed Texts', in Text Editing, Print and the Digital World (Ashgate, 2008) pp. 159-168.
  18. Joshua D. Sosin, 'Digital Papyrology', Congress of the International Association of Papyrologists, 19 August 2010, Geneva. Available: http://blog.stoa.org/archives/1263
  19. Text Encoding Initiative, P5: Guidelines for Electronic Text Encoding and Interchange, Available: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html
  20. Charlotte Tupman, 'Contextual epigraphy and XML: digital publication and its application to the study of inscribed funerary monuments', in (eds. Bodard & Mahony) Digital Research in the Study of Classical Antiquity (Ashgate, 2010), pp. 73-86.

Responsibility for this section

  1. Gabriel Bodard, author Hugh Cayless, author Wikipedia, source

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-elements.html b/gl/dev/app-elements.html index 50e390c49..92249b8a4 100644 --- a/gl/dev/app-elements.html +++ b/gl/dev/app-elements.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Index of TEI elements

2023-04-27

...under construction...

ab
Multi-language texts
Textpart
Textos em vários idiomas
abbr
Abbreviation fully expanded
Expansion of abbreviation including symbol/characters
Abbreviation not expanded at all
Expansion of symbol
Abbreviation uncertainly expanded
Chi-Rho
Monograms
Abreviação completamente expandida
Expansão de abreviação com inclusão de símbolo/caracteres
Abreviação não expandida
Expansão de símbolo para palavra
Abreviação expandida de modo incerto
Chi-Rho
Monogramas
add
Text Addition by Ancient Hand
Addition With Mark
Ancient Corrections (Where Both Old and New Text Can Be Read)
Ancient Corrections (Old Text Lost)
Text Struck Over Erasure
Texto adicionado por mão na antiguidade
Aditção com Marca
Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)
Correção antiga (original ilegível ou perdido)
Texto Escrito Sobre Texto Apagado
altIdentifier
Inventory numbers and repository
Números de inventário de depósito
am
Expansion of abbreviation including symbol/characters
Expansion of symbol
Chi-Rho
Monograms
Expansão de abreviação com inclusão de símbolo/caracteres
Expansão de símbolo para palavra
Chi-Rho
Monogramas
app
External apparatus criticus
Apparatus criticus externo
Inline apparatus criticus
Apparatus criticus em linha
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Alternative readings: inline encoding and display
availability
Publication information
Informação sobre publicação
bibl
Encoding the Bibliography
Codificando a Bibliografia
Images, figures and facsimile
Imagens, figuras e fac-símile
biblScope
Encoding the Bibliography
biblStruct
Encoding the Bibliography
Codificando a Bibliografia
calendar
Dates, dating formulae, ages
cb
Non-Structural Text-Parts
certainty
Numbers with Non-sequential Values
Possible Vacat
Possible Illegible Characters/Lines
Lines Possibly Lost / Text Possibly Breaks
Números com Valores Não-Sequenciais
Possível Vacat
Caracteres/Linhas Possivelmente Ilegíveis
Linhas Possivelmente Perdidas / Quebra Possível de Texto
choice
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Ambiguous Characters with Alternatives Offered
Erroneous substitution
Regularization
Caracteres ambíguos com apresentação de alternativas
Correção de Caracteres Errôneos
Regularização
citedRange
Encoding the Bibliography
Codificando a Bibliografia
corr
Correction without Specification
Erroneous substitution
Correção sem Especificação
Correção de Caracteres Errôneos
custEvent
Provenance of the text-bearing object
custodialHist
Provenance of the text-bearing object
damage
Damaged characters
Caracteres Danificados
date
Images, figures and facsimile
Imagens, figuras e fac-símile
Dates, dating formulae, ages
decoDesc
Description of decoration or iconography
Descrição de decoração ou iconografia
decoNote
Description of decoration or iconography
Descrição de decoração ou iconografia
del
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Ancient Corrections (Where Both Old and New Text Can Be Read)
Erased But Legible Text
Erased and Illegible / Restored
Erased and Lost
Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)
Texto Apagado, mas Legível
Apagado e Ilegível / Restaurado
Apagado e Perdido
depth
Dimensions of object or campus
Dimensões do objeto ou campus
desc
Images, figures and facsimile
Imagens, figuras e fac-símile
Editorial restoration: example or illustrative supplement
Restauração Editorial: exemplo ou suplemento ilustrativo
dim
Dimensions of object or campus
Dimensões do objeto ou campus
dimensions
Description of object or support
Descrição de objeto ou suporte
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
Dimensions of object or campus
Dimensões do objeto ou campus
div
Apparatus criticus
Apparatus criticus
Commentary
Comentário
Images, figures and facsimile
Imagens, figuras e fac-símile
Multi-language texts
Textpart
Textos em vários idiomas
Textpart
editor
Publication information
Informação sobre publicação
elements
Marked for Deletion by Slashes/Cross Strokes
Paragraphos
Marcado para ser Apagado por Barras / Traços Cruzados
Paragraphos
event
Events
ex
Abbreviation fully expanded
Expansion of abbreviation including symbol/characters
Abbreviation partially expanded
Expansion of symbol
Abbreviation uncertainly expanded
Chi-Rho
Monograms
Abreviação completamente expandida
Expansão de abreviação com inclusão de símbolo/caracteres
Abreviação parcialmente expandida
Expansão de símbolo para palavra
Abreviação expandida de modo incerto
Chi-Rho
Monogramas
expan
Abbreviation fully expanded
Expansion of abbreviation including symbol/characters
Abbreviation partially expanded
Expansion of symbol
Abbreviation uncertainly expanded
Chi-Rho
Monograms
Managing Whitespace in Transcriptions
Abreviação completamente expandida
Expansão de abreviação com inclusão de símbolo/caracteres
Abreviação parcialmente expandida
Expansão de símbolo para palavra
Abreviação expandida de modo incerto
Chi-Rho
Monogramas
Gerenciando Espaço em Branco em Transcrições
facsimile
Images, figures and facsimile
Imagens, figuras e fac-símile
figDesc
Monograms
Monogramas
figure
Monograms
Monogramas
foreign
Languages and scripts
Línguas e escritas
Multi-language texts
Textos em vários idiomas
g
Expansion of abbreviation including symbol/characters
Expansion of symbol
Claudian letters
Symbol (non meaning-bearing)
Symbol: interpuncts
Chi-Rho
Monograms
Expansão de abreviação com inclusão de símbolo/caracteres
Expansão de símbolo para palavra
Letras Claudias
Símbolo (não carrega significado)
Símbolo: ponto mediano
Chi-Rho
Monogramas
gap
Words Omitted by Editor for Brevity
Erased and Lost
Foreign Ellipsis
Illegible Characters, Quantity Approximate (Circa or Range)
Illegible Characters, Quantity Known
Illegible Characters, Quantity Unknown
Illegible Lines, Quantity Approximate (Circa or Range)
Illegible Lines, Quantity Known
Illegible Lines, Quantity Unknown
Illegible text, other units (e.g. cm)
Editorial restoration: Segmented or adjacent lacunae
Lost characters, quantity approximate
Lost characters, quantity known
Lost Characters, Metre Known/Reconstructed
Lost Characters, Numeral
Lost characters, praenomen
Lost characters, quantity unknown
Lost Lines, Quantity Approximate (Circa or Range)
Lost lines, quantity known
Lost Lines, Quantity Unknown
Lacunas, Other Units
Possible Illegible Characters/Lines
Lines Possibly Lost / Text Possibly Breaks
Editorial restoration: Word incompletely restored
Editorial restoration: example or illustrative supplement
Text not completed (omission not restored)
Palavras Omitidas pelo Editor por Brevidade
Apagado e Perdido
Texto Estrangeiro Omitido da Edição
Caracteres Ilegíveis, Quantidade Aproximada (Circa ou Range)
Caracteres Ilegíveis, Quantidade Conhecida
Caracteres Ilegíveis, Quantidade Desconhecida
Linhas Ilegíveis, Quantidade Aproximada (Circa ou Range)
Illegible Lines, Quantity Known
Linhas Ilegíveis, Quantidade Desconhecida
Texto Ilegível, outras unidades (e.g. cm)
Restauração Editorial: Lacunas segmentadas ou adjacentes
Caracteres perdidos, quantidade aproximada
Caracteres perdidos, quantidade conhecida
Caracteres perdidos, Métrica Conhecida/Reconstruída
Caracteres Perdidos, Numeral
Caracteres perdidos, praenomen
Caracteres perdidos, quantidade desconhecida
Linhas Perdidas, Quantidade Aproximada (Cerca ou Estimativa)
Linhas perdidas, quantidade conhecida
Linhas Perdidas, Quantidade Desconhecida
Lacunas, Outras Unidades
Caracteres/Linhas Possivelmente Ilegíveis
Linhas Possivelmente Perdidas / Quebra Possível de Texto
Restauração Editorial: palavra com restauro incompleto
Restauração Editorial: exemplo ou suplemento ilustrativo
Texto incompleto (omissão não restaurada)
geogName
Encoding geographic names and locations
Place names and geographical terms mentioned in the text
Place authority lists/gazetteers
gloss
Other/generic authority lists
Multi-language texts
Textos em vários idiomas
glyph
Symbol (non meaning-bearing)
graphic
Images, figures and facsimile
Imagens, figuras e fac-símile
handDesc
Description of hands and letters
Descrição de mãos e de letras
handNote
Description of hands and letters
Descrição de mãos e de letras
handShift
Handshift
Mudança de escriba ou de mão
height
Description of hands and letters
Descrição de mãos e de letras
Dimensions of object or campus
Dimensões do objeto ou campus
hi
Description of hands and letters
Descrição de mãos e de letras
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Apices and other diacritics
Characters highlighted or set apart in some way
Ligatured letters
Raised/Lowered characters
Reversed letters; inverted (or rotated) letters
Supralinear line, underline or strikethrough
Chi-Rho
Tall or Small Characters
Ápices
Caracteres ressaltados ou destacados de alguma forma
Letras em ligadura
Caracteres Elevados ou Rebaixados
Letras reversas, rotacionadas ou invertidas
Linha Supralinear, sublinhado ou strikethrough
Chi-Rho
Caracteres Altos ou Pequenos
history
Provenance of the text-bearing object
Proveniência do objeto portador de texto
Dates and locations of modern observations
Datas e locais de observações modernas
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Modern or last known locations
Localização moderna ou última conhecida
idno
Inventory numbers and repository
Números de inventário de depósito
Publication information
Informação sobre publicação
Place authority lists/gazetteers
item
Other/generic authority lists
keywords
Description of the text type
Other taxonomies, general keywords
l
Verse Lines
Metrical typology
Metrical elements
Linhas de Verso
label
Events
langUsage
Languages and scripts
Línguas e escritas
language
Languages and scripts
Línguas e escritas
layout
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
layoutDesc
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
lb
Line breaks
Line Breaks: Direction of Text
Line Breaks In Words
Quebras de linhaLine breaks
Quebras de Linha: Direção do Texto
Quebras de Linha em Palavras
lem
External apparatus criticus
Apparatus criticus externo
Inline apparatus criticus
Apparatus criticus em linha
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Alternative readings: inline encoding and display
lg
Verse Lines
Metrical typology
Metrical elements
Linhas de Verso
licence
Publication information
Informação sobre publicação
list
Other/generic authority lists
listApp
External apparatus criticus
Apparatus criticus externo
listBibl
Encoding the Bibliography
Codificando a Bibliografia
listEvent
Events
listNym
Indexing and controlling persons and names
listPerson
Indexing and controlling persons and names
mapping
Symbol (non meaning-bearing)
material
Description of object or support
Descrição de objeto ou suporte
metDecl
Verse Lines
Metrical typology
Metrical elements
milestone
Non-Structural Text-Parts
Textpart
Partes de Texto Não-Estrutural
Textpart
msContents
Other taxonomies, general keywords
msDesc
Structure of an EpiDoc edition
Estrutura de uma edição EpiDoc
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Localização moderna ou última conhecida
msIdentifier
Inventory numbers and repository
Números de inventário de depósito
msName
Inventory numbers and repository
Números de inventário de depósito
name
Personal names and prosopographical links
Lost characters, praenomen
Caracteres perdidos, praenomen
note
External apparatus criticus
Apparatus criticus externo
Editor's Note
Editorial restoration: example or illustrative supplement
Nota do Editor
Restauração Editorial: exemplo ou suplemento ilustrativo
num
Fractions of Known Value
Fractions of Unknown Value
Lost Characters, Numeral
Acrophonic Numbers
Numbers/numerals of Known Value
Numbers with Non-sequential Values
Numbers With a Range of Values
Numbers with a tick symbol/diacritic
Numbers/numerals of Unknown Value
Frações de Valor Conhecido
Frações de Valor Desconhecido
Caracteres Perdidos, Numeral
Números Acrofônicos
Números/Numerais de Valor Conhecido
Números com Valores Não-Sequenciais
Números com uma Gama de Valores Possíveis
Números com um sinal de visto/diacríticos
Números/Numerais de Valor Desconhecido
nym
Indexing and controlling persons and names
objectType
Description of object or support
Descrição de objeto ou suporte
orgName
Place names and geographical terms mentioned in the text
orig
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Erased But Legible Text
Regularization
Uninterpreted characters
Texto Apagado, mas Legível
Regularização
Caracteres não-interpretados
origDate
Original date of text and/or object
Data original do texto e/ou objeto
Original location of the text-bearing object
Local original do objeto portador de texto
origPlace
Original location of the text-bearing object
Local original do objeto portador de texto
origin
Provenance of the text-bearing object
Proveniência do objeto portador de texto
Original location of the text-bearing object
Local original do objeto portador de texto
Modern or last known locations
p
Original location of the text-bearing object
Local original do objeto portador de texto
pb
Non-Structural Text-Parts
persName
Findspot and find context
Contexto de descoberta (Findspot)
Personal names and prosopographical links
Indexing and controlling persons and names
person
Indexing and controlling persons and names
physDesc
Physical description
Descrição física
place
Encoding geographic names and locations
Place names and geographical terms mentioned in the text
Place authority lists/gazetteers
placeName
Encoding geographic names and locations
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Place names and geographical terms mentioned in the text
Place authority lists/gazetteers
precision
Original date of text and/or object
Data original do texto e/ou objeto
prefixDef
Symbol (non meaning-bearing)
provenance
Provenance of the text-bearing object
Proveniência do objeto portador de texto
Dates and locations of modern observations
Datas e locais de observações modernas
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Modern or last known locations
Localização moderna ou última conhecida
ptr
Images, figures and facsimile
Imagens, figuras e fac-símile
publicationStmt
Publication information
Informação sobre publicação
q
Quotation Marks
Aspas
rdg
External apparatus criticus
Apparatus criticus externo
Inline apparatus criticus
Apparatus criticus em linha
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Alternative readings: inline encoding and display
ref
Images, figures and facsimile
Imagens, figuras e fac-símile
reg
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Regularization
Regularização
repository
Inventory numbers and repository
Números de inventário de depósito
rs
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
Description of decoration or iconography
Descrição de decoração ou iconografia
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Titles, offices, political posts, honorifics, occupations
Military, religious, socio-economic terminology
Dates, dating formulae, ages
Other taxonomies, general keywords
seg
Original location of the text-bearing object
Local original do objeto portador de texto
Multi-language texts
Lost Characters, Metre Known/Reconstructed
Editorial restoration: Word incompletely restored
Textos em vários idiomas
Caracteres perdidos, Métrica Conhecida/Reconstruída
Restauração Editorial: palavra com restauro incompleto
sic
Erroneous substitution
Correção de Caracteres Errôneos
space
Possible Vacat
Vacat Measured in Characters
Vacat Measured in Lines
Vacat Measured in Other Units
Possível Vacat
Vacat Medido em Caracteres
Vacat Medido em Linhas
Vacat Medido em Outras Unidades
subst
Ancient Corrections (Where Both Old and New Text Can Be Read)
Text Struck Over Erasure
Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)
Texto Escrito Sobre Texto Apagado
summary
Other taxonomies, general keywords
supplied
Abbreviation fully expanded
Breviatio
Erased and Illegible / Restored
Editorial restoration: Segmented or adjacent lacunae
Omitted letters
Parallel Text
Previous Editor
Editorial restoration: Characters lost but restored by modern editor
Editorial restoration: Word incompletely restored
Editorial restoration: Characters lost and restored tentatively
Editorial restoration: example or illustrative supplement
Subaudible Word
Abreviação completamente expandida
Breviatio
Apagado e Ilegível / Restaurado
Restauração Editorial: Lacunas segmentadas ou adjacentes
Letras Omitidas
Texto Paralelo
Editor Anterior
Restauração Editorial: Caracteres perdidos mas restaurados por um editor moderno
Restauração Editorial: palavra com restauro incompleto
Restauração Editorial: Caracteres perdidos e restaurados de modo incerto
Restauração Editorial: exemplo ou suplemento ilustrativo
Palavra Subaudível
support
Description of object or support
Descrição de objeto ou suporte
supportDesc
Description of object or support
Descrição de objeto ou suporte
surface
Images, figures and facsimile
Imagens, figuras e fac-símile
surplus
Superfluous Text
Texto Supérfluo
teiHeader
Dates and locations of modern observations
Datas e locais de observações modernas
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Localização moderna ou última conhecida
term
Description of the text type
Other taxonomies, general keywords
Other/generic authority lists
Multi-language texts
Textos em vários idiomas
textClass
Description of the text type
Other taxonomies, general keywords
textLang
Languages and scripts
Línguas e escritas
title
Publication information
Informação sobre publicação
titleStmt
Publication information
Informação sobre publicação
unclear
Ambiguous Characters (Leiden underdotted)
Ambiguous Characters with Alternatives Offered
Erased But Legible Text
Caracteres ambíguos (ponto subescrito do Leiden)
Caracteres ambíguos com apresentação de alternativas
Texto Apagado, mas Legível
w
Words and Lemmatization
Titles, offices, political posts, honorifics, occupations
Military, religious, socio-economic terminology
Editorial restoration: Word incompletely restored
Restauração Editorial: palavra com restauro incompleto
width
Dimensions of object or campus
Dimensões do objeto ou campus

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Index of TEI elements

2024-03-05

...under construction...

ab
Multi-language texts
Textpart
Textos em vários idiomas
abbr
Abbreviation fully expanded
Expansion of abbreviation including symbol/characters
Abbreviation not expanded at all
Expansion of symbol
Abbreviation uncertainly expanded
Chi-Rho
Monograms
Abreviação completamente expandida
Expansão de abreviação com inclusão de símbolo/caracteres
Abreviação não expandida
Expansão de símbolo para palavra
Abreviação expandida de modo incerto
Chi-Rho
Monogramas
add
Text Addition by Ancient Hand
Addition With Mark
Ancient Corrections (Where Both Old and New Text Can Be Read)
Ancient Corrections (Old Text Lost)
Text Struck Over Erasure
Texto adicionado por mão na antiguidade
Aditção com Marca
Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)
Correção antiga (original ilegível ou perdido)
Texto Escrito Sobre Texto Apagado
altIdentifier
Inventory numbers and repository
Números de inventário de depósito
am
Expansion of abbreviation including symbol/characters
Expansion of symbol
Chi-Rho
Monograms
Expansão de abreviação com inclusão de símbolo/caracteres
Expansão de símbolo para palavra
Chi-Rho
Monogramas
app
External apparatus criticus
Apparatus criticus externo
Inline apparatus criticus
Apparatus criticus em linha
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Alternative readings: inline encoding and display
availability
Publication information
Informação sobre publicação
bibl
Encoding the Bibliography
Codificando a Bibliografia
Images, figures and facsimile
Imagens, figuras e fac-símile
biblScope
Encoding the Bibliography
biblStruct
Encoding the Bibliography
Codificando a Bibliografia
calendar
Dates, dating formulae, ages
cb
Non-Structural Text-Parts
certainty
Numbers with Non-sequential Values
Possible Vacat
Possible Illegible Characters/Lines
Lines Possibly Lost / Text Possibly Breaks
Números com Valores Não-Sequenciais
Possível Vacat
Caracteres/Linhas Possivelmente Ilegíveis
Linhas Possivelmente Perdidas / Quebra Possível de Texto
choice
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Ambiguous Characters with Alternatives Offered
Erroneous substitution
Regularization
Caracteres ambíguos com apresentação de alternativas
Correção de Caracteres Errôneos
Regularização
citedRange
Encoding the Bibliography
Codificando a Bibliografia
corr
Correction without Specification
Erroneous substitution
Correção sem Especificação
Correção de Caracteres Errôneos
custEvent
Provenance of the text-bearing object
custodialHist
Provenance of the text-bearing object
damage
Damaged characters
Caracteres Danificados
date
Images, figures and facsimile
Imagens, figuras e fac-símile
Dates, dating formulae, ages
decoDesc
Description of decoration or iconography
Descrição de decoração ou iconografia
decoNote
Description of decoration or iconography
Descrição de decoração ou iconografia
del
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Ancient Corrections (Where Both Old and New Text Can Be Read)
Erased But Legible Text
Erased and Illegible / Restored
Erased and Lost
Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)
Texto Apagado, mas Legível
Apagado e Ilegível / Restaurado
Apagado e Perdido
depth
Dimensions of object or campus
Dimensões do objeto ou campus
desc
Images, figures and facsimile
Imagens, figuras e fac-símile
Editorial restoration: example or illustrative supplement
Restauração Editorial: exemplo ou suplemento ilustrativo
dim
Dimensions of object or campus
Dimensões do objeto ou campus
dimensions
Description of object or support
Descrição de objeto ou suporte
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
Dimensions of object or campus
Dimensões do objeto ou campus
div
Apparatus criticus
Apparatus criticus
Commentary
Comentário
Images, figures and facsimile
Imagens, figuras e fac-símile
Multi-language texts
Textpart
Textos em vários idiomas
Textpart
editor
Publication information
Informação sobre publicação
elements
Marked for Deletion by Slashes/Cross Strokes
Paragraphos
Marcado para ser Apagado por Barras / Traços Cruzados
Paragraphos
event
Events
ex
Abbreviation fully expanded
Expansion of abbreviation including symbol/characters
Abbreviation partially expanded
Expansion of symbol
Abbreviation uncertainly expanded
Chi-Rho
Monograms
Abreviação completamente expandida
Expansão de abreviação com inclusão de símbolo/caracteres
Abreviação parcialmente expandida
Expansão de símbolo para palavra
Abreviação expandida de modo incerto
Chi-Rho
Monogramas
expan
Abbreviation fully expanded
Expansion of abbreviation including symbol/characters
Abbreviation partially expanded
Expansion of symbol
Abbreviation uncertainly expanded
Chi-Rho
Monograms
Managing Whitespace in Transcriptions
Abreviação completamente expandida
Expansão de abreviação com inclusão de símbolo/caracteres
Abreviação parcialmente expandida
Expansão de símbolo para palavra
Abreviação expandida de modo incerto
Chi-Rho
Monogramas
Gerenciando Espaço em Branco em Transcrições
facsimile
Images, figures and facsimile
Imagens, figuras e fac-símile
figDesc
Monograms
Monogramas
figure
Monograms
Monogramas
foreign
Languages and scripts
Línguas e escritas
Multi-language texts
Textos em vários idiomas
g
Expansion of abbreviation including symbol/characters
Expansion of symbol
Claudian letters
Symbol (non meaning-bearing)
Symbol: interpuncts
Chi-Rho
Monograms
Expansão de abreviação com inclusão de símbolo/caracteres
Expansão de símbolo para palavra
Letras Claudias
Símbolo (não carrega significado)
Símbolo: ponto mediano
Chi-Rho
Monogramas
gap
Words Omitted by Editor for Brevity
Erased and Lost
Foreign Ellipsis
Illegible Characters, Quantity Approximate (Circa or Range)
Illegible Characters, Quantity Known
Illegible Characters, Quantity Unknown
Illegible Lines, Quantity Approximate (Circa or Range)
Illegible Lines, Quantity Known
Illegible Lines, Quantity Unknown
Illegible text, other units (e.g. cm)
Editorial restoration: Segmented or adjacent lacunae
Lost characters, quantity approximate
Lost characters, quantity known
Lost Characters, Metre Known/Reconstructed
Lost Characters, Numeral
Lost characters, praenomen
Lost characters, quantity unknown
Lost Lines, Quantity Approximate (Circa or Range)
Lost lines, quantity known
Lost Lines, Quantity Unknown
Lacunas, Other Units
Possible Illegible Characters/Lines
Lines Possibly Lost / Text Possibly Breaks
Editorial restoration: Word incompletely restored
Editorial restoration: example or illustrative supplement
Text not completed (omission not restored)
Palavras Omitidas pelo Editor por Brevidade
Apagado e Perdido
Texto Estrangeiro Omitido da Edição
Caracteres Ilegíveis, Quantidade Aproximada (Circa ou Range)
Caracteres Ilegíveis, Quantidade Conhecida
Caracteres Ilegíveis, Quantidade Desconhecida
Linhas Ilegíveis, Quantidade Aproximada (Circa ou Range)
Illegible Lines, Quantity Known
Linhas Ilegíveis, Quantidade Desconhecida
Texto Ilegível, outras unidades (e.g. cm)
Restauração Editorial: Lacunas segmentadas ou adjacentes
Caracteres perdidos, quantidade aproximada
Caracteres perdidos, quantidade conhecida
Caracteres perdidos, Métrica Conhecida/Reconstruída
Caracteres Perdidos, Numeral
Caracteres perdidos, praenomen
Caracteres perdidos, quantidade desconhecida
Linhas Perdidas, Quantidade Aproximada (Cerca ou Estimativa)
Linhas perdidas, quantidade conhecida
Linhas Perdidas, Quantidade Desconhecida
Lacunas, Outras Unidades
Caracteres/Linhas Possivelmente Ilegíveis
Linhas Possivelmente Perdidas / Quebra Possível de Texto
Restauração Editorial: palavra com restauro incompleto
Restauração Editorial: exemplo ou suplemento ilustrativo
Texto incompleto (omissão não restaurada)
geogName
Encoding geographic names and locations
Place names and geographical terms mentioned in the text
Place authority lists/gazetteers
gloss
Other/generic authority lists
Multi-language texts
Textos em vários idiomas
glyph
Symbol (non meaning-bearing)
graphic
Images, figures and facsimile
Imagens, figuras e fac-símile
handDesc
Description of hands and letters
Descrição de mãos e de letras
handNote
Description of hands and letters
Descrição de mãos e de letras
handShift
Handshift
Mudança de escriba ou de mão
height
Description of hands and letters
Descrição de mãos e de letras
Dimensions of object or campus
Dimensões do objeto ou campus
hi
Description of hands and letters
Descrição de mãos e de letras
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Apices and other diacritics
Characters highlighted or set apart in some way
Ligatured letters
Raised/Lowered characters
Reversed letters; inverted (or rotated) letters
Supralinear line, underline or strikethrough
Chi-Rho
Tall or Small Characters
Ápices
Caracteres ressaltados ou destacados de alguma forma
Letras em ligadura
Caracteres Elevados ou Rebaixados
Letras reversas, rotacionadas ou invertidas
Linha Supralinear, sublinhado ou strikethrough
Chi-Rho
Caracteres Altos ou Pequenos
history
Provenance of the text-bearing object
Proveniência do objeto portador de texto
Dates and locations of modern observations
Datas e locais de observações modernas
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Modern or last known locations
Localização moderna ou última conhecida
idno
Inventory numbers and repository
Números de inventário de depósito
Publication information
Informação sobre publicação
Place authority lists/gazetteers
item
Other/generic authority lists
keywords
Description of the text type
Other taxonomies, general keywords
l
Verse Lines
Metrical typology
Metrical elements
Linhas de Verso
label
Events
langUsage
Languages and scripts
Línguas e escritas
language
Languages and scripts
Línguas e escritas
layout
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
layoutDesc
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
lb
Line breaks
Line Breaks: Direction of Text
Line Breaks In Words
Quebras de linhaLine breaks
Quebras de Linha: Direção do Texto
Quebras de Linha em Palavras
lem
External apparatus criticus
Apparatus criticus externo
Inline apparatus criticus
Apparatus criticus em linha
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Alternative readings: inline encoding and display
lg
Verse Lines
Metrical typology
Metrical elements
Linhas de Verso
licence
Publication information
Informação sobre publicação
list
Other/generic authority lists
listApp
External apparatus criticus
Apparatus criticus externo
listBibl
Encoding the Bibliography
Codificando a Bibliografia
listEvent
Events
listNym
Indexing and controlling persons and names
listPerson
Indexing and controlling persons and names
mapping
Symbol (non meaning-bearing)
material
Description of object or support
Descrição de objeto ou suporte
metDecl
Verse Lines
Metrical typology
Metrical elements
milestone
Non-Structural Text-Parts
Textpart
Partes de Texto Não-Estrutural
Textpart
msContents
Other taxonomies, general keywords
msDesc
Structure of an EpiDoc edition
Estrutura de uma edição EpiDoc
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Localização moderna ou última conhecida
msIdentifier
Inventory numbers and repository
Números de inventário de depósito
msName
Inventory numbers and repository
Números de inventário de depósito
name
Personal names and prosopographical links
Lost characters, praenomen
Caracteres perdidos, praenomen
note
External apparatus criticus
Apparatus criticus externo
Editor's Note
Editorial restoration: example or illustrative supplement
Nota do Editor
Restauração Editorial: exemplo ou suplemento ilustrativo
num
Fractions of Known Value
Fractions of Unknown Value
Lost Characters, Numeral
Acrophonic Numbers
Numbers/numerals of Known Value
Numbers with Non-sequential Values
Numbers With a Range of Values
Numbers with a tick symbol/diacritic
Numbers/numerals of Unknown Value
Frações de Valor Conhecido
Frações de Valor Desconhecido
Caracteres Perdidos, Numeral
Números Acrofônicos
Números/Numerais de Valor Conhecido
Números com Valores Não-Sequenciais
Números com uma Gama de Valores Possíveis
Números com um sinal de visto/diacríticos
Números/Numerais de Valor Desconhecido
nym
Indexing and controlling persons and names
objectType
Description of object or support
Descrição de objeto ou suporte
orgName
Place names and geographical terms mentioned in the text
orig
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Erased But Legible Text
Regularization
Uninterpreted characters
Texto Apagado, mas Legível
Regularização
Caracteres não-interpretados
origDate
Original date of text and/or object
Data original do texto e/ou objeto
Original location of the text-bearing object
Local original do objeto portador de texto
origPlace
Original location of the text-bearing object
Local original do objeto portador de texto
origin
Provenance of the text-bearing object
Proveniência do objeto portador de texto
Original location of the text-bearing object
Local original do objeto portador de texto
Modern or last known locations
p
Original location of the text-bearing object
Local original do objeto portador de texto
pb
Non-Structural Text-Parts
persName
Findspot and find context
Contexto de descoberta (Findspot)
Personal names and prosopographical links
Indexing and controlling persons and names
person
Indexing and controlling persons and names
physDesc
Physical description
Descrição física
place
Encoding geographic names and locations
Place names and geographical terms mentioned in the text
Place authority lists/gazetteers
placeName
Encoding geographic names and locations
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Place names and geographical terms mentioned in the text
Place authority lists/gazetteers
precision
Original date of text and/or object
Data original do texto e/ou objeto
prefixDef
Symbol (non meaning-bearing)
provenance
Provenance of the text-bearing object
Proveniência do objeto portador de texto
Dates and locations of modern observations
Datas e locais de observações modernas
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Modern or last known locations
Localização moderna ou última conhecida
ptr
Images, figures and facsimile
Imagens, figuras e fac-símile
publicationStmt
Publication information
Informação sobre publicação
q
Quotation Marks
Aspas
rdg
External apparatus criticus
Apparatus criticus externo
Inline apparatus criticus
Apparatus criticus em linha
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Alternative readings: inline encoding and display
ref
Images, figures and facsimile
Imagens, figuras e fac-símile
reg
What the EpiDoc Example Stylesheet can do for your apparatus
O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus
Regularization
Regularização
repository
Inventory numbers and repository
Números de inventário de depósito
rs
Description and layout of text field or campus
Descrição e layout de campo de texto ou campus
Description of decoration or iconography
Descrição de decoração ou iconografia
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Titles, offices, political posts, honorifics, occupations
Military, religious, socio-economic terminology
Dates, dating formulae, ages
Other taxonomies, general keywords
seg
Original location of the text-bearing object
Local original do objeto portador de texto
Multi-language texts
Lost Characters, Metre Known/Reconstructed
Editorial restoration: Word incompletely restored
Textos em vários idiomas
Caracteres perdidos, Métrica Conhecida/Reconstruída
Restauração Editorial: palavra com restauro incompleto
sic
Erroneous substitution
Correção de Caracteres Errôneos
space
Possible Vacat
Vacat Measured in Characters
Vacat Measured in Lines
Vacat Measured in Other Units
Possível Vacat
Vacat Medido em Caracteres
Vacat Medido em Linhas
Vacat Medido em Outras Unidades
subst
Ancient Corrections (Where Both Old and New Text Can Be Read)
Text Struck Over Erasure
Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)
Texto Escrito Sobre Texto Apagado
summary
Other taxonomies, general keywords
supplied
Abbreviation fully expanded
Breviatio
Erased and Illegible / Restored
Editorial restoration: Segmented or adjacent lacunae
Omitted letters
Parallel Text
Previous Editor
Editorial restoration: Characters lost but restored by modern editor
Editorial restoration: Word incompletely restored
Editorial restoration: Characters lost and restored tentatively
Editorial restoration: example or illustrative supplement
Subaudible Word
Abreviação completamente expandida
Breviatio
Apagado e Ilegível / Restaurado
Restauração Editorial: Lacunas segmentadas ou adjacentes
Letras Omitidas
Texto Paralelo
Editor Anterior
Restauração Editorial: Caracteres perdidos mas restaurados por um editor moderno
Restauração Editorial: palavra com restauro incompleto
Restauração Editorial: Caracteres perdidos e restaurados de modo incerto
Restauração Editorial: exemplo ou suplemento ilustrativo
Palavra Subaudível
support
Description of object or support
Descrição de objeto ou suporte
supportDesc
Description of object or support
Descrição de objeto ou suporte
surface
Images, figures and facsimile
Imagens, figuras e fac-símile
surplus
Superfluous Text
Texto Supérfluo
teiHeader
Dates and locations of modern observations
Datas e locais de observações modernas
Original location of the text-bearing object
Local original do objeto portador de texto
Findspot and find context
Contexto de descoberta (Findspot)
Localização moderna ou última conhecida
term
Description of the text type
Other taxonomies, general keywords
Other/generic authority lists
Multi-language texts
Textos em vários idiomas
textClass
Description of the text type
Other taxonomies, general keywords
textLang
Languages and scripts
Línguas e escritas
title
Publication information
Informação sobre publicação
titleStmt
Publication information
Informação sobre publicação
unclear
Ambiguous Characters (Leiden underdotted)
Ambiguous Characters with Alternatives Offered
Erased But Legible Text
Caracteres ambíguos (ponto subescrito do Leiden)
Caracteres ambíguos com apresentação de alternativas
Texto Apagado, mas Legível
w
Words and Lemmatization
Titles, offices, political posts, honorifics, occupations
Military, religious, socio-economic terminology
Editorial restoration: Word incompletely restored
Restauração Editorial: palavra com restauro incompleto
width
Dimensions of object or campus
Dimensões do objeto ou campus

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-ceipac.html b/gl/dev/app-epi-ceipac.html index 963c75ba6..a67268630 100644 --- a/gl/dev/app-epi-ceipac.html +++ b/gl/dev/app-epi-ceipac.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with CEIPAC (Corpus de epigrafía anfórica)

2023-04-27

LeidenDescriptionEpiDoc page(s)
ABCNormal letters. Generally letters are transcribed in upper case when they are oriented towards the direction of reading of the text, regardless of the fact that the seal is retrograde or to be read left to right.
abcReflected characters. In lower case are those letters that are visible but are written in the direction opposite to that of the text. Reversed Letters, Inverted (Or Rotated) Letters
A!BC, a!bcCharacters inverted or turned around. Exclamation mark is used after a character when this is inverted or turned around, which is not the same thing as reflected. Reversed Letters, Inverted (Or Rotated) Letters
A<BC, >ABC, A<<BC, >>ABCCharacters dimensions. Single characters with a smaller or grater dimension than other characters are marked with < or > between the characters beeing compared. The sign can be repeated twice to emphasize much smaller or bigger than the other. Description Of Hands And Letters
$A$BC, $AB$CGreek Letters. Dollar signs are used to surround greek letters. The greek charachter Φ which is the same as the digraphic PH in latin is converted in $PH$. Use Unicode letters or Multi-Language Texts
|ABC|, |ABC, ABC|, ABCEnd of inscribed field. End of lines indicate the end of the cartiglio. They are marked with a vertical bar if clearly visible in the inscription. The limits of the inscribed field are left open when the closure is not preserved Non-structural text-parts
|ABC|/|ABC|Line Break. The Obliquous bar marks the change of line and always follow the mark for a end of inscribed field. Line Breaks
A~B~C, A~BC, AB~CLigatures. The tildes is used between two characters to mark that some of the strikes are common. Ligatured Letters
A^B^C, A^BC, AB^CNexi between characters by fusion. The circumflex accent is the sign used to mark nexi between characters by fusion. Ligatured Letters
{AB}Nexi between characters by inclusion. Braces are used to mark the union of characters by inclusion. Ligatured Letters
{A/BC} Nexi between characters by inclusion on two lines. When letters of the same dimension are written in a place of equale size of that of the bigger letter. Ligatured Letters
{A^BC}, {AB^C}Hybrid Nexi. This type of nexi is marked combining the circumflex accent and braces. Ligatured Letters
A·B·C, A·BC, AB·CInterpunction. Different classes of interpunction are marked with a high dot. Interpuncts
{A·}BCPunctuation mark into the place of a letter. Interpuncts and Non-structural text-parts
((signum))Symbols and decorations. Between brackets the latin word describing the symbol. Symbol (Non Meaning-Bearing)
A'B'C', A'BC, AB'C, ABC', A''B''C''Ambiguous characters. These are represented with an apostrophe appended to the characters for which some traces are visible, but whose identification is impossible from the context. the repetition of the apostrophe is used to emphasize the degree of dubt. Ambiguous Characters
<ABC>, A<B>CCharacters omitted by mistake or by abbreviation of a word. The editor adds between two angle parathesis the characters omitted by mistake or to further shorten the abbreviated word (e.g. when the character has double value, as in geminated consonants.) Omitted Letters
[ABC], [ABC?]Restored characters.Within square brackets are those characters which were lost because of damage to the support or erosion of the original text, and can be restored by the editor. The certainty about these values is signed out by question marks. Restored text
[[ABC]]Characters intentionally deleted. Those characters intentionally deleted are marked within double parenthesis, e.g. with severian stamps. Erased but legible text and Erased and lost
[-],[---]Empty spaces for charcters. Between square brackets are places as many hyphens as the number of possibly lost characters Lost characters, quantity known, Lost characters, quantity approximate and Lost characters, quantity unknown
(-), (---), (?)Empty spaces. Between brackets are as many hyphens as the spaces which can be calculated to mark a space intentionally left blank. The question mark means that the number of spaces cannot be quantified. Vacat measured in charactrers
ABC+, AB+CLacuna of one or more letters. The plus sign indicates that the following character might have lost one or more intermediate letters. Possible Illegible Characters
ABC*, AB*CUncertain lacuna. The star sign indicates that after the character there might be one or more characters. Gap of unknown extent and certainty as in Text Possibly Breaks
A&BC, A^B&C^B, ((signum))& ((signum))Ambiguity. When a character or a nexus or a symbol might be interepreted in various ways the & sign is used to combine the possible solutions. Apparatus Criticus, Ambiguous characters (Leiden underdot) and Ambiguous characters multiple alternatives
ABC, sine imagineWe write sine imagine after the transcription if in the publication there is no image of the stamp. This would be encoded in the teiHeader.
ABC, bis impressum estWe write bit impressum est after the trancription if the stamp appears struk again. Text Struck Over Erasure

Table above taken from Corpus Conservation Labelling PDF Document for support of epigraphic filling out.

Responsibility for this section

  1. Pietro Liuzzo, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with CEIPAC (Corpus de epigrafía anfórica)

2024-03-05

LeidenDescriptionEpiDoc page(s)
ABCNormal letters. Generally letters are transcribed in upper case when they are oriented towards the direction of reading of the text, regardless of the fact that the seal is retrograde or to be read left to right.
abcReflected characters. In lower case are those letters that are visible but are written in the direction opposite to that of the text. Reversed Letters, Inverted (Or Rotated) Letters
A!BC, a!bcCharacters inverted or turned around. Exclamation mark is used after a character when this is inverted or turned around, which is not the same thing as reflected. Reversed Letters, Inverted (Or Rotated) Letters
A<BC, >ABC, A<<BC, >>ABCCharacters dimensions. Single characters with a smaller or grater dimension than other characters are marked with < or > between the characters beeing compared. The sign can be repeated twice to emphasize much smaller or bigger than the other. Description Of Hands And Letters
$A$BC, $AB$CGreek Letters. Dollar signs are used to surround greek letters. The greek charachter Φ which is the same as the digraphic PH in latin is converted in $PH$. Use Unicode letters or Multi-Language Texts
|ABC|, |ABC, ABC|, ABCEnd of inscribed field. End of lines indicate the end of the cartiglio. They are marked with a vertical bar if clearly visible in the inscription. The limits of the inscribed field are left open when the closure is not preserved Non-structural text-parts
|ABC|/|ABC|Line Break. The Obliquous bar marks the change of line and always follow the mark for a end of inscribed field. Line Breaks
A~B~C, A~BC, AB~CLigatures. The tildes is used between two characters to mark that some of the strikes are common. Ligatured Letters
A^B^C, A^BC, AB^CNexi between characters by fusion. The circumflex accent is the sign used to mark nexi between characters by fusion. Ligatured Letters
{AB}Nexi between characters by inclusion. Braces are used to mark the union of characters by inclusion. Ligatured Letters
{A/BC} Nexi between characters by inclusion on two lines. When letters of the same dimension are written in a place of equale size of that of the bigger letter. Ligatured Letters
{A^BC}, {AB^C}Hybrid Nexi. This type of nexi is marked combining the circumflex accent and braces. Ligatured Letters
A·B·C, A·BC, AB·CInterpunction. Different classes of interpunction are marked with a high dot. Interpuncts
{A·}BCPunctuation mark into the place of a letter. Interpuncts and Non-structural text-parts
((signum))Symbols and decorations. Between brackets the latin word describing the symbol. Symbol (Non Meaning-Bearing)
A'B'C', A'BC, AB'C, ABC', A''B''C''Ambiguous characters. These are represented with an apostrophe appended to the characters for which some traces are visible, but whose identification is impossible from the context. the repetition of the apostrophe is used to emphasize the degree of dubt. Ambiguous Characters
<ABC>, A<B>CCharacters omitted by mistake or by abbreviation of a word. The editor adds between two angle parathesis the characters omitted by mistake or to further shorten the abbreviated word (e.g. when the character has double value, as in geminated consonants.) Omitted Letters
[ABC], [ABC?]Restored characters.Within square brackets are those characters which were lost because of damage to the support or erosion of the original text, and can be restored by the editor. The certainty about these values is signed out by question marks. Restored text
[[ABC]]Characters intentionally deleted. Those characters intentionally deleted are marked within double parenthesis, e.g. with severian stamps. Erased but legible text and Erased and lost
[-],[---]Empty spaces for charcters. Between square brackets are places as many hyphens as the number of possibly lost characters Lost characters, quantity known, Lost characters, quantity approximate and Lost characters, quantity unknown
(-), (---), (?)Empty spaces. Between brackets are as many hyphens as the spaces which can be calculated to mark a space intentionally left blank. The question mark means that the number of spaces cannot be quantified. Vacat measured in charactrers
ABC+, AB+CLacuna of one or more letters. The plus sign indicates that the following character might have lost one or more intermediate letters. Possible Illegible Characters
ABC*, AB*CUncertain lacuna. The star sign indicates that after the character there might be one or more characters. Gap of unknown extent and certainty as in Text Possibly Breaks
A&BC, A^B&C^B, ((signum))& ((signum))Ambiguity. When a character or a nexus or a symbol might be interepreted in various ways the & sign is used to combine the possible solutions. Apparatus Criticus, Ambiguous characters (Leiden underdot) and Ambiguous characters multiple alternatives
ABC, sine imagineWe write sine imagine after the transcription if in the publication there is no image of the stamp. This would be encoded in the teiHeader.
ABC, bis impressum estWe write bit impressum est after the trancription if the stamp appears struk again. Text Struck Over Erasure

Table above taken from Corpus Conservation Labelling PDF Document for support of epigraphic filling out.

Responsibility for this section

  1. Pietro Liuzzo, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-egyptology.html b/gl/dev/app-epi-egyptology.html index 2135369fe..5e93c0475 100644 --- a/gl/dev/app-epi-egyptology.html +++ b/gl/dev/app-epi-egyptology.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with Egyptological philological markup

2023-04-27

Traditional philological markupPhenomenonEpiDoc Guidelines
Line breaks, layout
jmn.t (2) pw
jmn.t |² pw
Line or column(!) with indication of direction (no matter whether the primary writing direction is in lines or in columns)Line break
and Line break with indication of direction
j(2)mn.t
j|²mn.t
Line or column(!) column break inside a word Line break, inside word
jmn.t pw
ḥsb.t 10
Highlighted characters (e.g., rubrum, tall characters in Demotic) Highlighted characters
sꜣ (space left free) ꞽrm ꜣrsn Free space on the text support in a line Vacat (measured in quadrats)
Text destruction
sꜣ [...] ꜣrsn Gap of unknown length, completely destroyed Lost characters, quantity not known
sꜣ ⸢...⸣ ꜣrsn Gap of unknown length, barely legible Lost characters, quantity not known
sꜣ [--ca. 3 Q.--] ꞽrm Gap of certain or approximate length, completely destroyed Lost characters, quantity known
or Lost characters, quantity approximate
sꜣ ⸢--ca. 3 Q.--⸣ ꞽrm Gap of certain or approximate length, barely legible Lost characters, quantity known
and Lost characters, quantity approximate
j[mn].tModern reconstruction in gap Restored text
and Restored text, uncertain
or Text restored from parallel copy
Characters now lost, but recorded by earlier scholarsText visible to previous editor
j⸢mn⸣.t Partial destruction, but perfectly or unambiguously legible Damaged text
or Ambiguous characters
Modern editorial marks
jmn{.t}-rꜥ Erroneous ancient addition Superfluous text
zw{r}j Traditional ‘superfluous’ double spelling Superfluous text
jmn⟨.w⟩ Erroneous ancient omission Supplement of omitted characters
jmn.{t}⟨w⟩ Erroneous ancient substitution Erroneous substitution
w{d}⟨ḏ⟩=fRegularization of transcription, according to Old Egyptian spelling Regularization
sḏm.t(w)=f
pr(j)=f
ꞽw=f (ḥr) sdm
Regularization of transcription (towards plene spelling or reconstruction according to grammatical theory)Regularization
Ancient editorial work
⟦jmn-rꜥ nb⟧-nṯr.(w)Characters deleted in antiquityErased but legible text
and Erased and illegible
and Erased and lost
((no specific mark))Addition above/below the line Text added by ancient hand
Varia
jmn.t (unfinished) Text not completed Text not completed

See also: TEI-XML in Eyptology and Coptic Studies.

Unicode codes of specific Egyptological transliteration letters

CharUnicodeCharUnicodeName
U+A723 U+A722Egyptological Alif
U+A725 U+A724Egyptological Ain
U+A7BDU+A7BCEgyptological Yod
U+0069&U+032F Egyptological ult.inf.-i
ïU+00EF
U+0075&U+032F Egyptological ult.inf.-u
ʾU+02BE Egyptological Secondary Alif
U+1E25 U+1E24
U+1E2B U+1E2A
U+1E96 U+0048&U+0331
U+0068&U+032D U+0048&U+032D
śU+015B ŚU+015A
šU+0161 ŠU+0160
U+1E33 U+1E32
U+1E6D U+1E6C
U+1E71 U+1E70
U+1E6F U+1E6E
čU+010D ČU+010C
U+1E0F U+1E0E
č̣U+010D&U+0323 Č̣U+010C&U+0323
U+27E8 U+27E9
U+2E22 U+2E23
U+2E17

See also: Egyptological transliteration systems in Unicode [external PDF].

Responsibility for this section

  1. Daniel A. Werning, author
  2. Gabriel Bodard, created template

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with Egyptological philological markup

2024-03-05

Traditional philological markupPhenomenonEpiDoc Guidelines
Line breaks, layout
jmn.t (2) pw
jmn.t |² pw
Line or column(!) with indication of direction (no matter whether the primary writing direction is in lines or in columns)Line break
and Line break with indication of direction
j(2)mn.t
j|²mn.t
Line or column(!) column break inside a word Line break, inside word
jmn.t pw
ḥsb.t 10
Highlighted characters (e.g., rubrum, tall characters in Demotic) Highlighted characters
sꜣ (space left free) ꞽrm ꜣrsn Free space on the text support in a line Vacat (measured in quadrats)
Text destruction
sꜣ [...] ꜣrsn Gap of unknown length, completely destroyed Lost characters, quantity not known
sꜣ ⸢...⸣ ꜣrsn Gap of unknown length, barely legible Lost characters, quantity not known
sꜣ [--ca. 3 Q.--] ꞽrm Gap of certain or approximate length, completely destroyed Lost characters, quantity known
or Lost characters, quantity approximate
sꜣ ⸢--ca. 3 Q.--⸣ ꞽrm Gap of certain or approximate length, barely legible Lost characters, quantity known
and Lost characters, quantity approximate
j[mn].tModern reconstruction in gap Restored text
and Restored text, uncertain
or Text restored from parallel copy
Characters now lost, but recorded by earlier scholarsText visible to previous editor
j⸢mn⸣.t Partial destruction, but perfectly or unambiguously legible Damaged text
or Ambiguous characters
Modern editorial marks
jmn{.t}-rꜥ Erroneous ancient addition Superfluous text
zw{r}j Traditional ‘superfluous’ double spelling Superfluous text
jmn⟨.w⟩ Erroneous ancient omission Supplement of omitted characters
jmn.{t}⟨w⟩ Erroneous ancient substitution Erroneous substitution
w{d}⟨ḏ⟩=fRegularization of transcription, according to Old Egyptian spelling Regularization
sḏm.t(w)=f
pr(j)=f
ꞽw=f (ḥr) sdm
Regularization of transcription (towards plene spelling or reconstruction according to grammatical theory)Regularization
Ancient editorial work
⟦jmn-rꜥ nb⟧-nṯr.(w)Characters deleted in antiquityErased but legible text
and Erased and illegible
and Erased and lost
((no specific mark))Addition above/below the line Text added by ancient hand
Varia
jmn.t (unfinished) Text not completed Text not completed

See also: TEI-XML in Eyptology and Coptic Studies.

Unicode codes of specific Egyptological transliteration letters

CharUnicodeCharUnicodeName
U+A723 U+A722Egyptological Alif
U+A725 U+A724Egyptological Ain
U+A7BDU+A7BCEgyptological Yod
U+0069&U+032F Egyptological ult.inf.-i
ïU+00EF
U+0075&U+032F Egyptological ult.inf.-u
ʾU+02BE Egyptological Secondary Alif
U+1E25 U+1E24
U+1E2B U+1E2A
U+1E96 U+0048&U+0331
U+0068&U+032D U+0048&U+032D
śU+015B ŚU+015A
šU+0161 ŠU+0160
U+1E33 U+1E32
U+1E6D U+1E6C
U+1E71 U+1E70
U+1E6F U+1E6E
čU+010D ČU+010C
U+1E0F U+1E0E
č̣U+010D&U+0323 Č̣U+010C&U+0323
U+27E8 U+27E9
U+2E22 U+2E23
U+2E17

See also: Egyptological transliteration systems in Unicode [external PDF].

Responsibility for this section

  1. Daniel A. Werning, author
  2. Gabriel Bodard, created template

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-krummreypanciera.html b/gl/dev/app-epi-krummreypanciera.html index 2dfc51b72..add589199 100644 --- a/gl/dev/app-epi-krummreypanciera.html +++ b/gl/dev/app-epi-krummreypanciera.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with Krummrey-Panciera 1980

2023-04-27

The diacritical signs as enumerated in Krummrey Panciera 1980, with links to EpiDoc guidance for encoding each semantic distinction expressed thereby in TEI XML.

I. Praemonenda

1. (print diplomatic transcription if no photograph available)
Not applicable. A single EpIDoc-encoded edition can be used to generate both interpretive and diplomatic views via different stylesheet transformations. (No reference to diplomatic transcription in Gudielines?)
2. (close square brackets at beginning and end of lines, unless in linear presentation)
Same recommendation applies to supplied elements in EpiDoc. (Not in Guidelines?)
3. (don't use italics or underline for notes in text)
Not applicable.
4. (don't add spacing between or around diacritical signs when within a word)
Same recommendation applies to EpiDoc. (Not in Guidelines?)
5. (not all combinations of diacritical notes have been given; just nest them)
Same applies to EpiDoc, but no specific guidance required.

II. Versuum paginarumque diuisio

1. abc /5 abc
Lines and line breaks
2. abc // abc
Columns, fragments, sections, pages and other breaks

IV. Litterarum formae notabiliores

1. á, é, í, ó, ú
Apices
2. abc, V
Supralinear line, etc.
3, ((y)), ((bs)), ((ps)), ((v))
Claudian letters
4. a͡b, a͡bc
Ligatures

V. Litterae erasae

1. 〚abc〛 aut 〚ABC〛 aut 〚ạḅc̣〛
Erased but legible text
2. 〚[abc]〛
Erased and illegible but restored
3. 〚[...]〛aut 〚[c. 5 ]〛 aut 〚[- - -]〛
Erased and lost

VI. Literae in litura scriptae

1. «abc» aut «ABC» aut «ạḅc̣»
Text struck over erasure and Erased but legible text
2. «[abc]»
Text struck over erasure and Erased and illegible but restored
3. «[...]»aut «[c. 5 ]» aut «[- - -]»
Text struck over erasure and Erased and lost

VII. Additamenta antiqua

1. `abc´
Text added by ancient hand

IX. Litterae ab editore expunctae adiectae correctae

1. {abc}
Superfluous characters
2. <abc>
Supplement of omitted characters
3. ⸢abc⸣
Erroneous substitution

X. Verba breviata notae verba subaudita inscriptiones non finitae

1. a(bc)
Abbreviation fully expanded
2. a(- - -)
Abbreviation not expanded at all
3. (abc)
Expansion of symbol to word
4. (scil. abc)
Editor makes subaudible word manifest
5. (- - -)
Text not completed (omission not restored)

XI. Aliae notae editoris

1. (!)
Editor's note
2. vac.3 aut vac.c.3 aut vac.
vacat measured in characters (horizontal space)
3. vac.?
Possible vacat
4. ... , [...]
Words omitted by editor

Responsibility for this section

  1. Gabriel Bodard, author
  2. Hugh Cayless, help deciphering Hans Krummrey's Latin

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with Krummrey-Panciera 1980

2024-03-05

The diacritical signs as enumerated in Krummrey Panciera 1980, with links to EpiDoc guidance for encoding each semantic distinction expressed thereby in TEI XML.

I. Praemonenda

1. (print diplomatic transcription if no photograph available)
Not applicable. A single EpIDoc-encoded edition can be used to generate both interpretive and diplomatic views via different stylesheet transformations. (No reference to diplomatic transcription in Gudielines?)
2. (close square brackets at beginning and end of lines, unless in linear presentation)
Same recommendation applies to supplied elements in EpiDoc. (Not in Guidelines?)
3. (don't use italics or underline for notes in text)
Not applicable.
4. (don't add spacing between or around diacritical signs when within a word)
Same recommendation applies to EpiDoc. (Not in Guidelines?)
5. (not all combinations of diacritical notes have been given; just nest them)
Same applies to EpiDoc, but no specific guidance required.

II. Versuum paginarumque diuisio

1. abc /5 abc
Lines and line breaks
2. abc // abc
Columns, fragments, sections, pages and other breaks

IV. Litterarum formae notabiliores

1. á, é, í, ó, ú
Apices
2. abc, V
Supralinear line, etc.
3, ((y)), ((bs)), ((ps)), ((v))
Claudian letters
4. a͡b, a͡bc
Ligatures

V. Litterae erasae

1. 〚abc〛 aut 〚ABC〛 aut 〚ạḅc̣〛
Erased but legible text
2. 〚[abc]〛
Erased and illegible but restored
3. 〚[...]〛aut 〚[c. 5 ]〛 aut 〚[- - -]〛
Erased and lost

VI. Literae in litura scriptae

1. «abc» aut «ABC» aut «ạḅc̣»
Text struck over erasure and Erased but legible text
2. «[abc]»
Text struck over erasure and Erased and illegible but restored
3. «[...]»aut «[c. 5 ]» aut «[- - -]»
Text struck over erasure and Erased and lost

VII. Additamenta antiqua

1. `abc´
Text added by ancient hand

IX. Litterae ab editore expunctae adiectae correctae

1. {abc}
Superfluous characters
2. <abc>
Supplement of omitted characters
3. ⸢abc⸣
Erroneous substitution

X. Verba breviata notae verba subaudita inscriptiones non finitae

1. a(bc)
Abbreviation fully expanded
2. a(- - -)
Abbreviation not expanded at all
3. (abc)
Expansion of symbol to word
4. (scil. abc)
Editor makes subaudible word manifest
5. (- - -)
Text not completed (omission not restored)

XI. Aliae notae editoris

1. (!)
Editor's note
2. vac.3 aut vac.c.3 aut vac.
vacat measured in characters (horizontal space)
3. vac.?
Possible vacat
4. ... , [...]
Words omitted by editor

Responsibility for this section

  1. Gabriel Bodard, author
  2. Hugh Cayless, help deciphering Hans Krummrey's Latin

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-mycenaean.html b/gl/dev/app-epi-mycenaean.html index 012fa2eaf..b23e83b5f 100644 --- a/gl/dev/app-epi-mycenaean.html +++ b/gl/dev/app-epi-mycenaean.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with Mycenaean usage (Wingspread Conventions)

2023-04-27

DescriptionWingspreadDAMOSEpiDoc exampleEpiDoc Guidelines
Characters and glyphs
syllabogrampa or ro2pa or ro2<c type="syllabogram">pa</c>
<c type="syllabogram">ro2</c>
Not covered.
logogramOLEOLE<c type="logogram">OLE</c>Not covered.
syllabogram used as logogramPAPA<c type="syllabogram-as-logogram">PA</c>Not covered.
Monogram (i.e. ligatured syllabograms)MERIME±RI<hi rend="monogram">MERI</hi>Not covered.
Ligatured logogramsTELA+POTELA+PO<hi rend="ligature">TELA+PO</hi>Ligatured Letters
MetrogramSS<c type="metrogram">S</c>Not covered.
Arithmogram11<num>1</num>Numbers/Numerals Of Known Value
Syllabogram as abbreviationoo<abbr>o</abbr>Abbreviation not Expanded at All
Word divider,,<pc><g ref="#div"/></pc>Not covered.
Undeciphered glyph (syllabogram)*47*47<g ref="#s47"/>Not covered.
Undeciphered glyph (logogram)*123*123<g ref="#l123"/>Not covered.
Undeciphered glyph (vase logogram)*155VAS*155VAS<g ref="#l155vas"/>Not covered.
Gender specifierm or f:m or :f<c type="specifier">m</c>Not covered.
Other specifier1;1<c type="specifier">1</c>Not covered.
Editorial interventions and observations
to be added

Responsibility for this section

  1. Gabriel Bodard, author
  2. Federico Aurora, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with Mycenaean usage (Wingspread Conventions)

2024-03-05

DescriptionWingspreadDAMOSEpiDoc exampleDAMOS exampleEpiDoc Guidelines
Characters and glyphs
syllabogram (in a syllabic word)pa- or -ro2pa- or -ro2pa-
-ro2
4327 (PY An(6) 35); 4471; 4626Clear text
syllabic wordda-mo-deda-mo-de<w xml:id="">da-mo-de</w>4579Words and lemmata
logogramOLEOLE<w type="logogram" xml:id="">OLE</w>4560Not yet covered.
syllabogram used as logogram (i.e. adjectival logogram)PAPA<w type="syllabogram-as-logogram" xml:id="">PA</w>4960Not yet covered.
Monogram (i.e. ligatured syllabograms used as logogram)MERIME±RI<w type="monogram" xml:id="">MERI</w>2Not covered.
Ligatured logogramsTELA+POTELA+PO<w type="ligature" xml:id="">TELA+PO</w>681cf. Ligatured Letters
MetrogramSS<w type="metrogram" xml:id="">S</w>4214Not yet covered.
Arithmogram11<num xml:id="">1</num>4170Numbers/Numerals Of Known Value
Syllabogram as abbreviationoo<w xml:id=""><abbr>o</abbr></w>380Abbreviation not Expanded at All
Word divider,,<pc xml:id=""><g ref="#div"/></pc>4421cf. Symbol: interpuncts
Undeciphered glyph (syllabogram)*47*47<g ref="#s47"/>Not covered.
Undeciphered glyph (logogram)*123*123<g ref="#l123"/>Not covered.
Undeciphered glyph (vase logogram)*155VAS*155VAS<g ref="#l155vas"/>Not covered.
Gender specifierm or f:m or :f<c type="specifier">m</c>Not covered.
Other specifier1;1<c type="specifier">1</c>Not covered.
Editorial interventions and observations
to be added

Note: for the purposes of the DAMOS database, all words and other units of text should be identified with a unique xml:id (which will be assigned by DAMOS). This may not be required for all Mycenaean EpiDoc projects.

Responsibility for this section

  1. Gabriel Bodard, author
  2. Federico Aurora, author
  3. Nora White, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-oracc.html b/gl/dev/app-epi-oracc.html index 3d242031c..5bb67ddde 100644 --- a/gl/dev/app-epi-oracc.html +++ b/gl/dev/app-epi-oracc.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with ORACC

2023-04-27

DescriptionConventional displayATFEpiDoc page(s)
Correction of signAB!AB!Correction (without specification)
Correction of sign (original shown)AB!(BA)AB!(BA)Erroneous substitution
Damage to signbi-it-subi-it#-su#Ambiguous characters (Leiden underdot)
Unknown number of characters lost[...][...]Lost characters, quantity unknown
One character lost[x][x]Lost characters, quantity known
Six characters lost[x x x x x x][x x x x x x]Lost characters, quantity known
Three to six characters lost[x x x (x x x)][x x x (x x x)](tba)
Restored lost characters[AB][AB]Editorial restoration
Uncertainly restored lost characters[AB?][AB?]Editorial restoration, uncertain
Restoration of accidental omission<ab><ab>Supplement of omitted characters
Restoration of intentional omissionbi-it-<(su)>bi-it-<(su)>Abbreviation fully expanded
Characters rejected by editor<<ab>><<ab>>Superfluous characters
Unclear signxxIllegible characters, quantity known
Clear but uninterpreted signAB$ABUninterpreted characters (Leiden uppercase)
Ligature or compound graphemea+naa+naLigatures

Cf. also Steve Tinney and Eleanor Robson, ATF Quick Reference, Oracc: The Open Richly Annotated Cuneiform Corpus, Oracc, 2014.

Responsibility for this section

  1. Gabriel Bodard, author
  2. Eleanor Robson, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with ORACC

2024-03-05

DescriptionConventional displayATFEpiDoc page(s)
Correction of signAB!AB!Correction (without specification)
Correction of sign (original shown)AB!(BA)AB!(BA)Erroneous substitution
Damage to signbi-it-subi-it#-su#Ambiguous characters (Leiden underdot)
Unknown number of characters lost[...][...]Lost characters, quantity unknown
One character lost[x][x]Lost characters, quantity known
Six characters lost[x x x x x x][x x x x x x]Lost characters, quantity known
Three to six characters lost[x x x (x x x)][x x x (x x x)](tba)
Restored lost characters[AB][AB]Editorial restoration
Uncertainly restored lost characters[AB?][AB?]Editorial restoration, uncertain
Restoration of accidental omission<ab><ab>Supplement of omitted characters
Restoration of intentional omissionbi-it-<(su)>bi-it-<(su)>Abbreviation fully expanded
Characters rejected by editor<<ab>><<ab>>Superfluous characters
Unclear signxxIllegible characters, quantity known
Clear but uninterpreted signAB$ABUninterpreted characters (Leiden uppercase)
Ligature or compound graphemea+naa+naLigatures

Cf. also Steve Tinney and Eleanor Robson, ATF Quick Reference, Oracc: The Open Richly Annotated Cuneiform Corpus, Oracc, 2014.

Responsibility for this section

  1. Gabriel Bodard, author
  2. Eleanor Robson, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-panciera.html b/gl/dev/app-epi-panciera.html index 808720a0f..471c6afa0 100644 --- a/gl/dev/app-epi-panciera.html +++ b/gl/dev/app-epi-panciera.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with Panciera 1991

2023-04-27

The diacritical signs as enumerated in Panciera 1991, with links to EpiDoc guidance for encoding each semantic distinction expressed thereby in TEI XML.

A. Litterae in lapide exstantes

I. Litterae ita laesae ut certius extra tituli contextum agnosci non possunt
Ambiguous characters
II. Litterae errore substitutae quas editor correxit
Erroneous substitution
III. Litterae errore adiectae quas editor expunxit
Superfluous characters
IV. Additamentum antiquum ad textum corrigendum aut supplendum
Text added by ancient hand
V. Litterae antiquitus erasae quae tamen legentur
Erased but legible text
VI. Litterae loco erasarum insculptae
Text struck over erasure
VII. Vestigia litterarum ita corruptarum ut nullo modo agnosci possint
Illegible characters, quantity known and quantity unknown
VIII. Litterae planae lectionis quae tamen in incerto est utrum ad initium verbi an ad medium an ad finem pertineant an ad verbum plus quam unum
Uninterpreted characters

B. Litterae omissae vel deperditae

I. Litterae errore omissae quas editor adiecit
Supplement of omitted characters
II. Litterae omissae quod lapicida inscriptionem ad finem non perduxit
Text not completed (omission not restored)
III. Litterae omissae compendii causa quas editor explevit
Abbreviation fully expanded
IV. Litterae quae a prioribus descriptae postea perierunt
Text visible to previous editor
V. Litterae fortuito superficiei damno vel fractura omnino deperditae quarum numerus sive computari potest sive non potest
Lost characters, quantity known, quantity approximate and quantity unknown
VI. Lacuna sive unius integri versus sive integrorum versuum quorum numerus incertus est
Lost lines, quantity known and quantity unknown
VII. Litterae omnino deperditae quas editor supplevit
Restored text
VIII. Litterae antiquitus omnino erasae quarum numerus sive computari potest sive non potest
Erased and lost

C. Varia

I. Litterae conexae
Ligatures
II. Litterae quae dicuntur Claudianae
Claudian letters
III. I longa
Tall or small characters
IV. Vocales apicibus notatae
Apices
V. Litterae et notae numerorum lineis notatae
Supralinear line, etc.
VI. Puncta hederae
Symbols and Interpuncts
VII. Verbum ab editore loco litterae inversae positum
Reversed or inverted letters
VIII. Verbum ab editore loco notae positum
Symbols and Expansion of symbol to word
IX. Verbum subauditum quod editor menifestum facit
Editor makes subaudible word manifest
X. Verbum ab loco anaglyphi positum
Symbols
XI. Nota editoris ut lector attento animo aliquid perpendat
Editor's note
XII. Nota editoris quae ponitur post aliquid de quo quaeritur
e.g. Uncertainly restored text or Abbreviation uncertainly expanded
XIII. Partes versus quae non inscriptae fuisse videntur
vacat measured in characters (horizontal space)
XIV. Verba praetermissa in textum laudando
Words omitted by editor
XV. Linearum diviso
Lines and line breaks
XVI. Versuum diviso
Verse lines
XVII. Paginarum diviso
Columns, fragments, sections, pages and other breaks

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with Panciera 1991

2024-03-05

The diacritical signs as enumerated in Panciera 1991, with links to EpiDoc guidance for encoding each semantic distinction expressed thereby in TEI XML.

A. Litterae in lapide exstantes

I. Litterae ita laesae ut certius extra tituli contextum agnosci non possunt
Ambiguous characters
II. Litterae errore substitutae quas editor correxit
Erroneous substitution
III. Litterae errore adiectae quas editor expunxit
Superfluous characters
IV. Additamentum antiquum ad textum corrigendum aut supplendum
Text added by ancient hand
V. Litterae antiquitus erasae quae tamen legentur
Erased but legible text
VI. Litterae loco erasarum insculptae
Text struck over erasure
VII. Vestigia litterarum ita corruptarum ut nullo modo agnosci possint
Illegible characters, quantity known and quantity unknown
VIII. Litterae planae lectionis quae tamen in incerto est utrum ad initium verbi an ad medium an ad finem pertineant an ad verbum plus quam unum
Uninterpreted characters

B. Litterae omissae vel deperditae

I. Litterae errore omissae quas editor adiecit
Supplement of omitted characters
II. Litterae omissae quod lapicida inscriptionem ad finem non perduxit
Text not completed (omission not restored)
III. Litterae omissae compendii causa quas editor explevit
Abbreviation fully expanded
IV. Litterae quae a prioribus descriptae postea perierunt
Text visible to previous editor
V. Litterae fortuito superficiei damno vel fractura omnino deperditae quarum numerus sive computari potest sive non potest
Lost characters, quantity known, quantity approximate and quantity unknown
VI. Lacuna sive unius integri versus sive integrorum versuum quorum numerus incertus est
Lost lines, quantity known and quantity unknown
VII. Litterae omnino deperditae quas editor supplevit
Restored text
VIII. Litterae antiquitus omnino erasae quarum numerus sive computari potest sive non potest
Erased and lost

C. Varia

I. Litterae conexae
Ligatures
II. Litterae quae dicuntur Claudianae
Claudian letters
III. I longa
Tall or small characters
IV. Vocales apicibus notatae
Apices
V. Litterae et notae numerorum lineis notatae
Supralinear line, etc.
VI. Puncta hederae
Symbols and Interpuncts
VII. Verbum ab editore loco litterae inversae positum
Reversed or inverted letters
VIII. Verbum ab editore loco notae positum
Symbols and Expansion of symbol to word
IX. Verbum subauditum quod editor menifestum facit
Editor makes subaudible word manifest
X. Verbum ab loco anaglyphi positum
Symbols
XI. Nota editoris ut lector attento animo aliquid perpendat
Editor's note
XII. Nota editoris quae ponitur post aliquid de quo quaeritur
e.g. Uncertainly restored text or Abbreviation uncertainly expanded
XIII. Partes versus quae non inscriptae fuisse videntur
vacat measured in characters (horizontal space)
XIV. Verba praetermissa in textum laudando
Words omitted by editor
XV. Linearum diviso
Lines and line breaks
XVI. Versuum diviso
Verse lines
XVII. Paginarum diviso
Columns, fragments, sections, pages and other breaks

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-epi-petrae.html b/gl/dev/app-epi-petrae.html index 8e4c4e208..08a481937 100644 --- a/gl/dev/app-epi-petrae.html +++ b/gl/dev/app-epi-petrae.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with PETRAE

2023-04-27

See PETRAE conventions at http://petrae.tge-adonis.fr/index.php/inscriptions/aide.

Conventions for epigraphic transcription

[ ]Restitution des lettres disparuesEditorial restoration: Characters lost but restored by modern editor
( )Résolution d'abbréviationAbbreviation fully expanded
〚 〛ÉrasureErased but legible text and Erased and illegible but restored
`Aug´Lettres ligaturéesLigatured letters
{ }Suppression de lettres gravées par erreurSuperfluous characters
< >Inclusion de lettres qui n'étaient pas présentes dans la pierreSupplement of omitted characters
˹ ˺Lettres corrigées d'après une copie ou un manuscrit peu fiable???
+Lettre non identifiableIllegible characters, quantity known and Illegible characters, quantity unknown
[...]Lacune non restituable de longueur déterminée : chaque point indique une lettre manquanteLost characters, quantity known
[ - - - ]Lacune de longueur indéterminée dans une ligne ou, ligne manquante, mais certaineLost characters, quantity unknown and Lost lines, quantity known
- - -Ligne(s) manquante(s) non restituable(s) en nombre indéterminéLost lines, quantity unknown
Point de séparationSymbols: interpuncts
HederaSymbols
ẹṭ Lettre pointée : lettre qui ne se lit pas entièrement sur la pierreAmbiguous characters
uac.uacatVacat, characters and Vacat, lines

Supporting and descriptive fields

Numéro PETRAE (numéro absolu) : par ex. 16/1/14/xxx où 16 désigne les Gaules, 1 la province d'Aquitaine, 14 la cité de Périgueux
Title and publication information and Inventory numbers and repository
Lieu de découverte (nom antique et nom moderne) et une présentation succinte qui tient lieu de titre.
Place and context of finding
Description de la pierre : indication de la nature du support et du matériau, état de conservation du monument, élément de décoration
Description and dimensions of monument or object
Date, circonstances, lieu et contexte local de découverte
Place and context of finding
Lieu et institution de conservation avec indication du n° d'inventaire dans le musée ou la collection
Modern locations and Inventory numbers and repository
Dimension du monument (longueur/largeur/hauteur)
Dimensions
Description du champ épigraphique, avec la (ou les) face(s) du support où se trouve le champ, les dimensions (éventuellement)
Description and layout of text field or campus
Datation du texte
Date of origin
Commentaires sur la mise en page, définition de l'écriture et commentaire sur la forme et la qualité des lettres (s'il y a lieu)
Description of letters or hands
Bibliographie: sauf exception, on ne donne pas la bibliographie antérieure au CIL.
Bibliography
Texte : on donne d'abord ligne par ligne, avec alignement à gauche, le texte en capitales avec les signes séparatifs. Il permet de se faire clairement une idée de ce qui a été lu et doit être considéré comme un état de l'information scientifique. On transcrit ensuite, ligne par ligne, avec alignement à gauche, l'inscription en minuscules, sans redonner les signes séparatifs, mais avec la ponctuation ordinaire d'un texte littéraire latin.
Transcription guidelines
Apparat critique : on ne donne ordinairement pas les lectures antérieures au CIL, sauf lorqu'elles mérite quelques considérations, notamment pour les inscriptions aujourd'hui perdues
External apparatus criticus
Traduction
Translation
Photos
Figures or facsimile

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with PETRAE

2024-03-05

See PETRAE conventions at http://petrae.tge-adonis.fr/index.php/inscriptions/aide.

Conventions for epigraphic transcription

[ ]Restitution des lettres disparuesEditorial restoration: Characters lost but restored by modern editor
( )Résolution d'abbréviationAbbreviation fully expanded
〚 〛ÉrasureErased but legible text and Erased and illegible but restored
`Aug´Lettres ligaturéesLigatured letters
{ }Suppression de lettres gravées par erreurSuperfluous characters
< >Inclusion de lettres qui n'étaient pas présentes dans la pierreSupplement of omitted characters
˹ ˺Lettres corrigées d'après une copie ou un manuscrit peu fiable???
+Lettre non identifiableIllegible characters, quantity known and Illegible characters, quantity unknown
[...]Lacune non restituable de longueur déterminée : chaque point indique une lettre manquanteLost characters, quantity known
[ - - - ]Lacune de longueur indéterminée dans une ligne ou, ligne manquante, mais certaineLost characters, quantity unknown and Lost lines, quantity known
- - -Ligne(s) manquante(s) non restituable(s) en nombre indéterminéLost lines, quantity unknown
Point de séparationSymbols: interpuncts
HederaSymbols
ẹṭ Lettre pointée : lettre qui ne se lit pas entièrement sur la pierreAmbiguous characters
uac.uacatVacat, characters and Vacat, lines

Supporting and descriptive fields

Numéro PETRAE (numéro absolu) : par ex. 16/1/14/xxx où 16 désigne les Gaules, 1 la province d'Aquitaine, 14 la cité de Périgueux
Title and publication information and Inventory numbers and repository
Lieu de découverte (nom antique et nom moderne) et une présentation succinte qui tient lieu de titre.
Place and context of finding
Description de la pierre : indication de la nature du support et du matériau, état de conservation du monument, élément de décoration
Description and dimensions of monument or object
Date, circonstances, lieu et contexte local de découverte
Place and context of finding
Lieu et institution de conservation avec indication du n° d'inventaire dans le musée ou la collection
Modern locations and Inventory numbers and repository
Dimension du monument (longueur/largeur/hauteur)
Dimensions
Description du champ épigraphique, avec la (ou les) face(s) du support où se trouve le champ, les dimensions (éventuellement)
Description and layout of text field or campus
Datation du texte
Date of origin
Commentaires sur la mise en page, définition de l'écriture et commentaire sur la forme et la qualité des lettres (s'il y a lieu)
Description of letters or hands
Bibliographie: sauf exception, on ne donne pas la bibliographie antérieure au CIL.
Bibliography
Texte : on donne d'abord ligne par ligne, avec alignement à gauche, le texte en capitales avec les signes séparatifs. Il permet de se faire clairement une idée de ce qui a été lu et doit être considéré comme un état de l'information scientifique. On transcrit ensuite, ligne par ligne, avec alignement à gauche, l'inscription en minuscules, sans redonner les signes séparatifs, mais avec la ponctuation ordinaire d'un texte littéraire latin.
Transcription guidelines
Apparat critique : on ne donne ordinairement pas les lectures antérieures au CIL, sauf lorqu'elles mérite quelques considérations, notamment pour les inscriptions aujourd'hui perdues
External apparatus criticus
Traduction
Translation
Photos
Figures or facsimile

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-geo.html b/gl/dev/app-geo.html index d96ae8f38..ca28313df 100644 --- a/gl/dev/app-geo.html +++ b/gl/dev/app-geo.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Encoding geographic names and locations

2023-04-27

NB: Guidance for encoding information about the original and historical disposition of the text-bearing object is provided in the sections on Original location of the text-bearing object and Original date of text and/or object.

It is customary in producing an edition of a pre-modern manuscript, papyrus, inscription, and the like to enumerate the occasions on which modern persons encountered and reported seminal information about the text-bearing object, its condition and disposition, etc., together with associated bibliographic reference. The initial such observation is often the occasion of finding, sometimes in situ, sometimes in circumstances or reuse, sometimes already in the context of a modern collection. There follow other observations, culminating in the "last observed location" or "current location."

Following general TEI guidance, EpiDoc treats each such observation as a discrete event in space and time, and encodes each in a separate provenance element in the history section of the header. The type attribute is used with the following standard values to distinguish the major types of events:

  • <provenance type="found"> is used to encode information about the initial modern observation of a text-bearing object
  • <provenance type="observed"> is used to encode information about subsequent modern observations
  • <provenance type="autopsy"> is a special case of <provenance type="observed"> that is used to encode a modern observation event during which the editor (i.e., the person creating the present edition) personally examined the object

Locations may be tagged in various contexts in the description of the text-bearing object: in origPlace, provenance (for find-place or modern locations). This page describes the issues that all of these locations share, rather than duplicating them in each section.

  • TEI definition: place ; EpiDoc-specific +

    Encoding geographic names and locations

    2024-03-05

    NB: Guidance for encoding information about the original and historical disposition of the text-bearing object is provided in the sections on Original location of the text-bearing object and Original date of text and/or object.

    It is customary in producing an edition of a pre-modern manuscript, papyrus, inscription, and the like to enumerate the occasions on which modern persons encountered and reported seminal information about the text-bearing object, its condition and disposition, etc., together with associated bibliographic reference. The initial such observation is often the occasion of finding, sometimes in situ, sometimes in circumstances or reuse, sometimes already in the context of a modern collection. There follow other observations, culminating in the "last observed location" or "current location."

    Following general TEI guidance, EpiDoc treats each such observation as a discrete event in space and time, and encodes each in a separate provenance element in the history section of the header. The type attribute is used with the following standard values to distinguish the major types of events:

    • <provenance type="found"> is used to encode information about the initial modern observation of a text-bearing object
    • <provenance type="observed"> is used to encode information about subsequent modern observations
    • <provenance type="autopsy"> is a special case of <provenance type="observed"> that is used to encode a modern observation event during which the editor (i.e., the person creating the present edition) personally examined the object

    Locations may be tagged in various contexts in the description of the text-bearing object: in origPlace, provenance (for find-place or modern locations). This page describes the issues that all of these locations share, rather than duplicating them in each section.

    Placenames and geognames can be identified in several different ways. One way is with a ref which points to the an internal gazetteer. Another option is to link to an external database (Pleiades, Geonames).

    For specific types of placenames see the following subsections:

    <origPlace ref="origPlace.xml#p003">
     <seg xml:lang="ru">Херсон</seg>
     <seg xml:lang="en">Chersonesos</seg>
    </origPlace>
    <geogName type="modernCountrykey="LY">Libya</geogName>
    <placeName type="ancientFindspot"
     ref="http://pleiades.stoa.org/places/373732key="db911">
    Apollonia</placeName>
    <placeName type="modernFindspot"
     ref="http://sws.geonames.org/81584">
    Marsa Suza</placeName>

    Responsibility for this section

    1. Gabriel Bodard, author
    2. Simona Stoyanova, author

    EpiDoc version: post-9.5

    Date: 2023-04-27

    \ No newline at end of file + customization: geogName

Placenames and geognames can be identified in several different ways. One way is with a ref which points to the an internal gazetteer. Another option is to link to an external database (Pleiades, Geonames).

For specific types of placenames see the following subsections:

<origPlace ref="origPlace.xml#p003">
 <seg xml:lang="ru">Херсон</seg>
 <seg xml:lang="en">Chersonesos</seg>
</origPlace>
<geogName type="modernCountrykey="LY">Libya</geogName>
<placeName type="ancientFindspot"
 ref="http://pleiades.stoa.org/places/373732key="db911">
Apollonia</placeName>
<placeName type="modernFindspot"
 ref="http://sws.geonames.org/81584">
Marsa Suza</placeName>

Responsibility for this section

  1. Gabriel Bodard, author
  2. Simona Stoyanova, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary-bg.html b/gl/dev/app-glossary-bg.html index 7939736b6..e8fdac3a4 100644 --- a/gl/dev/app-glossary-bg.html +++ b/gl/dev/app-glossary-bg.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

ПРИЛОЖЕНИЕ: РЕЧНИК

2023-04-27

Crosswalk, crosswalking
Основно понятие за преобразуване на данни от формата на една схема за кодиране или база данни в друга. Що се касае до EpiDoc понятията, този термин често се отнася до динамичното преобразуване на семантични различия на епиграфски и папироложки издания между EpiDoc XML и една или повече база данни от текстове или каталогови регистри. Тези "crosswalks" могат да се осъществят в която и да е посока, или в някои случаи в двете посоки и обратно без загуба на информация. Известни "crosswalks" на EpiDoc общността включват: преобразуването на IRT от EpiDoc във формата на база данните EDH; прехвърлянето на съдържания от Duke Databank, HGV и APIS в EpiDoc като част от проекта Papyri.info (процесът от HGV в EpiDoc е двупосочен и без загуби); текущото преобразуване на базата данни на EAGLE в EpiDoc XML като част от проекта EAGLE Europeana.
Encoding
В настоящия контекст терминът „кодиране“ означава преобразуване на информация четима от човешки същества в машинно четима информация, например под формата на XML.
EpiDoc Example Stylesheets
Софтуерен код, написан на Extensible Stylesheet Language (XSL or XSLT), чиято цел е трансформиране на файлове в EpiDoc XML в други формати (главно текстови и HTML). За тази цел се използват редица стандартни типографски практики (например Leiden). Документация и допълнителна информация може да намерите на Stylesheets page in the EpiDoc Wiki.
EpiDoc Schema
Набор от правила с формална структура, който показва на редактора или обработващия базата данни в XML кои елементи, атрибути и друго съдържание са достъпни в EpiDoc файл и как те да бъдат структурирани. Документация и допълнителна информация може да бъде намерена на Schema page in the EpiDoc Wiki.
Leiden, Leiden Conventions
Набор от правила за кодиране на класически епиграфски и папироложки текстове. Използват се опростени, произволни и недвусмислени символи, които пресъздават редакторските наблюдения и интервенции, например квадратните скоби '[' и ']' се използват да обозначат изгубен текст (който е възстановен или е налице празно място „lacuna“). Има няколко леки вариации на Leiden, които понастоящем са в употреба (може би най-известните сред тях са (Krummrey-Panciera и PETRAE). Обобщена информация за това какво представлява Leiden може да намерите на en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ е система за текстово маркиране, която се основава предимно на Leiden но в същото време включва нови знаци и комбинации за маркиране на сложни апарати, например специално разработената за средата за редакторство „без етикети“ "tags-free" на Papyrological Editor. Пълно описание и документацията, касаеща Leiden+, е на адрес: papyri.info/editor/help.
Markup
Езикът за маркиране е начин за кодиране на текстове, с цел създаване на различни подходи за представяне и извличане на информация за изготвяне на индекси или инструменти за търсене (срав. Encoding).
"Markup" понякога се използва като съкращение на Markup List, списък, в който се дискутират по електронен път теми, касаещи EpiDoc и други въпроси около маркирането на антични текстове.
Morpheus
Морфологичният анализ на Morpheus е инструмент, първоначално разработен от Perseus. Неговите версии се използват от Papyri.info и TLG за лематизиране на гръцки текстове. Perseus версията на този инструмент също спомага за лематизиране на латински и арабски текстове. (За повече информация: Bamboo и Perseus.)
Papyrological Navigator (PN)
Интерфейс за търсене в платформата Papyri.info, която включва DDbDP, HGV, APIS и други папироложки бази данни.
Papyrological editor (PE)
Инструмент за редактиране и управление на текст на платформата Papyri.info, който позволява отразяване на общностния принос и внасяне на корекции в корпуса от документална папирология, особено чрез редакторския интерфейс без етикети „tags-free“ на Leiden+.
Perseus
Проектът Perseus Digital Library изучава напредъка на библиотеките от физически към дигитални и предлага нарастващ брой текстове в тяхна подкрепа. Могат да се приложат търсения директно в уеб страницата, а също така и редица инструменти докато трае процесът на четене, като например инструментът Речник за гръцки и латински текстове Morpheus.
Pleiades
Справочник с места и топоними от античния свят, съставен въз основа на проекта, чийто продукт е Barrington Atlas of the Greek and Roman World. Pleiades задава уникални идентификатори на всички места, като по този начин опосредства съществуването на мрежа от свързани данни по подобие на тази, която е поддържана от Pelagios project. Може да намерите Pleiades на pleiades.stoa.org.
TEI
Text Encoding Initiative (Инициатива за Кодиране на Текстове). Съставлява насоки и инструменти за кодиране на литературни и исторически текстове в XML. Това е форматът, върху който се основава EpiDoc. Последните Насоки за TEI могат да се намерят онлайн на адрес: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
The World Wide Web Consortium (W3C) е международна общност, която разработва стандарти, приложими в Интернет. Общността е отворена, но също така разполага с персонал на пълно работно време и цели организации, които членуват в тази общност. За допълнителна информация: www.w3.org.
XML
Абревиатура на Extensible Markup Language. Формат за текстово кодиране, позволяващ структурирано кодиране на текст или данни във формат, четим както от хора, така и от машини. Това е техническата основа на TEI и EpiDoc, и е стандарт, поддържан от World-wide Web Consortium. Виж www.w3.org/XML за по-детайлно описание.
XSLT
Абревиатура на Extensible Stylesheet Language Transformations. XSLT е език, който конвертира XML документи в различен XML или други формати, като например HTML, който се използва за уебсайтове, форматът за импортиране за база данни или форматът Open Document, който стои зад обработването на текстови файлове.EpiDoc Stylesheets са пример за XSLT, използван за трансформиране на EpiDoc XML в общоприети формати за визуализация. W3 Schools предлагат полезно въведение в XSLT.

Отговорни лица за този раздел

  1. Габриел Бодар, автор
  2. Лаура Льосер, автор
  3. Том Елиът, автор
  4. Мария Дончева, преведе на български език
  5. Полина Йорданова, редактор на превода

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

ПРИЛОЖЕНИЕ: РЕЧНИК

2024-03-05

Crosswalk, crosswalking
Основно понятие за преобразуване на данни от формата на една схема за кодиране или база данни в друга. Що се касае до EpiDoc понятията, този термин често се отнася до динамичното преобразуване на семантични различия на епиграфски и папироложки издания между EpiDoc XML и една или повече база данни от текстове или каталогови регистри. Тези "crosswalks" могат да се осъществят в която и да е посока, или в някои случаи в двете посоки и обратно без загуба на информация. Известни "crosswalks" на EpiDoc общността включват: преобразуването на IRT от EpiDoc във формата на база данните EDH; прехвърлянето на съдържания от Duke Databank, HGV и APIS в EpiDoc като част от проекта Papyri.info (процесът от HGV в EpiDoc е двупосочен и без загуби); текущото преобразуване на базата данни на EAGLE в EpiDoc XML като част от проекта EAGLE Europeana.
Encoding
В настоящия контекст терминът „кодиране“ означава преобразуване на информация четима от човешки същества в машинно четима информация, например под формата на XML.
EpiDoc Example Stylesheets
Софтуерен код, написан на Extensible Stylesheet Language (XSL or XSLT), чиято цел е трансформиране на файлове в EpiDoc XML в други формати (главно текстови и HTML). За тази цел се използват редица стандартни типографски практики (например Leiden). Документация и допълнителна информация може да намерите на Stylesheets page in the EpiDoc Wiki.
EpiDoc Schema
Набор от правила с формална структура, който показва на редактора или обработващия базата данни в XML кои елементи, атрибути и друго съдържание са достъпни в EpiDoc файл и как те да бъдат структурирани. Документация и допълнителна информация може да бъде намерена на Schema page in the EpiDoc Wiki.
Leiden, Leiden Conventions
Набор от правила за кодиране на класически епиграфски и папироложки текстове. Използват се опростени, произволни и недвусмислени символи, които пресъздават редакторските наблюдения и интервенции, например квадратните скоби '[' и ']' се използват да обозначат изгубен текст (който е възстановен или е налице празно място „lacuna“). Има няколко леки вариации на Leiden, които понастоящем са в употреба (може би най-известните сред тях са (Krummrey-Panciera и PETRAE). Обобщена информация за това какво представлява Leiden може да намерите на en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ е система за текстово маркиране, която се основава предимно на Leiden но в същото време включва нови знаци и комбинации за маркиране на сложни апарати, например специално разработената за средата за редакторство „без етикети“ "tags-free" на Papyrological Editor. Пълно описание и документацията, касаеща Leiden+, е на адрес: papyri.info/editor/help.
Markup
Езикът за маркиране е начин за кодиране на текстове, с цел създаване на различни подходи за представяне и извличане на информация за изготвяне на индекси или инструменти за търсене (срав. Encoding).
"Markup" понякога се използва като съкращение на Markup List, списък, в който се дискутират по електронен път теми, касаещи EpiDoc и други въпроси около маркирането на антични текстове.
Morpheus
Морфологичният анализ на Morpheus е инструмент, първоначално разработен от Perseus. Неговите версии се използват от Papyri.info и TLG за лематизиране на гръцки текстове. Perseus версията на този инструмент също спомага за лематизиране на латински и арабски текстове. (За повече информация: Bamboo и Perseus.)
Papyrological Navigator (PN)
Интерфейс за търсене в платформата Papyri.info, която включва DDbDP, HGV, APIS и други папироложки бази данни.
Papyrological editor (PE)
Инструмент за редактиране и управление на текст на платформата Papyri.info, който позволява отразяване на общностния принос и внасяне на корекции в корпуса от документална папирология, особено чрез редакторския интерфейс без етикети „tags-free“ на Leiden+.
Perseus
Проектът Perseus Digital Library изучава напредъка на библиотеките от физически към дигитални и предлага нарастващ брой текстове в тяхна подкрепа. Могат да се приложат търсения директно в уеб страницата, а също така и редица инструменти докато трае процесът на четене, като например инструментът Речник за гръцки и латински текстове Morpheus.
Pleiades
Справочник с места и топоними от античния свят, съставен въз основа на проекта, чийто продукт е Barrington Atlas of the Greek and Roman World. Pleiades задава уникални идентификатори на всички места, като по този начин опосредства съществуването на мрежа от свързани данни по подобие на тази, която е поддържана от Pelagios project. Може да намерите Pleiades на pleiades.stoa.org.
TEI
Text Encoding Initiative (Инициатива за Кодиране на Текстове). Съставлява насоки и инструменти за кодиране на литературни и исторически текстове в XML. Това е форматът, върху който се основава EpiDoc. Последните Насоки за TEI могат да се намерят онлайн на адрес: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
The World Wide Web Consortium (W3C) е международна общност, която разработва стандарти, приложими в Интернет. Общността е отворена, но също така разполага с персонал на пълно работно време и цели организации, които членуват в тази общност. За допълнителна информация: www.w3.org.
XML
Абревиатура на Extensible Markup Language. Формат за текстово кодиране, позволяващ структурирано кодиране на текст или данни във формат, четим както от хора, така и от машини. Това е техническата основа на TEI и EpiDoc, и е стандарт, поддържан от World-wide Web Consortium. Виж www.w3.org/XML за по-детайлно описание.
XSLT
Абревиатура на Extensible Stylesheet Language Transformations. XSLT е език, който конвертира XML документи в различен XML или други формати, като например HTML, който се използва за уебсайтове, форматът за импортиране за база данни или форматът Open Document, който стои зад обработването на текстови файлове.EpiDoc Stylesheets са пример за XSLT, използван за трансформиране на EpiDoc XML в общоприети формати за визуализация. W3 Schools предлагат полезно въведение в XSLT.

Отговорни лица за този раздел

  1. Габриел Бодар, автор
  2. Лаура Льосер, автор
  3. Том Елиът, автор
  4. Мария Дончева, преведе на български език
  5. Полина Йорданова, редактор на превода

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary-es.html b/gl/dev/app-glossary-es.html index c6c03e58c..7e618e465 100644 --- a/gl/dev/app-glossary-es.html +++ b/gl/dev/app-glossary-es.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Apéndice: Glosario

2023-04-27

Crosswalk, crosswalking
Éste es un término general para designar el hecho de traspasar datos del formato de un patrón de codificación a otro o de una base de datos a otra. En lo concerniente a EpiDoc, la mayoría de las veces se refiere a la conversión dinámica de las distinciones semánticas de las ediciones epigráficas y papirológicas entre el patrón XML de EpiDoc y una o varias bases de datos de textos o registros de catálogos. Estos traspasos pueden darse en las dos direcciones (EpiDoc a base de datos o base de datos a EpiDoc), e incluso en algunos casos en ambas direcciones de modo reversible sin que ello ocasione pérdida alguna de información. Algunos traspasos destacados que ha llevado a cabo la comunidad EpiDoc incluyen: la conversión de IRT desde el patrón de EpiDoc al formato de la base de datos EDH; la migración de contenidos del Duke Databank, HGV y APIS a EpiDoc como parte del proyecto Papyri.info (HGV a EpiDoc no conlleva pérdidas y es bidireccional); además de la conversión, actualmente en desarrollo, de las bases de datos EAGLE al XML de EpiDoc, como parte del proyecto EAGLE Europeana
Encoding, codificación
En este contexto, la codificación se refiere a la conversión de información inteligible para las personas a información que pueda ser interpretada por una máquina, por ejemplo en forma de lenguaje XML.
EpiDoc Example Stylesheets
Se trata de un código de software escrito en Extensible Stylesheet Language (lenguaje extensible de hojas de estilo, designado habitualmente por las siglas XSL o XSLT), cuyo objetivo es la transformación de los ficheros EpiDoc en XML a otros formatos (principalmente texto y HTML). Para ello se emplea un gran abanico de convenciones tipográficas estándar (por ejemplo, Leiden). Se puede encontrar documentación y más información en la página de las hojas de estilo en la wiki de EpiDoc.
EpiDoc Schema, patrón de EpiDoc
Conjunto de normas que se rigen por una estructura formal con el objetivo de ordenar a un editor o procesador de XML qué elementos, atributos u otro contenido está disponible en un fichero EpiDoc y cómo estructurarlos. Para documentación y más información, véase la página sobre el patrón en la wiki de EpiDoc.
Leiden, Convenciones de Leiden
Conjunto de normas para la codificación de textos clásicos en soporte epigráfico y papirológico. Se emplean símbolos sencillos, arbitrarios y exentos de ambigüedad con el fin de representar observaciones de los editores así como sus intervenciones. Por ejemplo, se escribe entre ‘[’ y ‘]’ el texto perdido ya sea porque se haya restituido o simplemente para indicar la laguna. Existen algunas variaciones menores en el sistema de Leiden usado hoy en día, quizás las más destacadas sean Krummrey-Panciera y PETRAE. Un breve resumen sobre las Convenciones de Leiden se puede encontrar en Wikipedia.
Leiden+ (Leiden-plus)
Leiden+ es un sistema de marcaje de texto que se basa principalmente en las Convenciones de Leiden pero que incluye nuevos signos y combinaciones para el marcaje de aparatos complejos, por ejemplo las inventadas para el medio de edición sin etiquetas (tags-free) del Papyrological Editor . Se puede encontrar una descripción completa además de documentación sobre Leiden+ en: papyri.info/editor/help.
Markup, marcaje
El lenguaje de marcaje es un modo de codificar los contenidos de un texto con el objetivo de posibilitar distintos modelos de presentación además de, por ejemplo, facilitar la extracción de informaciones concretas para elaborar índices o para herramientas de búsqueda. (Véase también: Encoding, codificación).
Markup también se usa a veces como abreviación de Markup List, es decir, una lista de discusión vía correo electrónico sobre temas referentes a EpiDoc y otros asuntos de marcaje de textos antiguos.
Morpheus
El servicio de análisis morfológico Morpheus es una herramienta desarrollada originariamente por Perseus. Papyri.info y el TLG emplean algunas versiones del mismo para la lematización de sus textos griegos. La herramienta disponible en Perseus también ofrece lematización en latín y en árabe. Para más información: Bamboo y Perseus.
Papyrological Navigator (PN)
Es la interfaz de búsqueda de la plataforma Papyri.info. Incluye las bases de datos DDbDP, HGV y APIS entre otras.
Papyrological editor (PE)
Se trata de la herramienta de edición y administración de texto de la plataforma Papyri.info. Permite las contribuciones y enmiendas en comunidad al corpus de papirología documental, especialmente a través de la interfaz de edición sin etiquetas (tags-free) de Leiden+.
Perseus
El proyecto Perseus Digital Library estudia la progresión de las bibliotecas de físicas a digitales y ofrece un gran número de textos que va en aumento. Se pueden realizar búsquedas directamente en su web, además de usar una serie de herramientas mientras se leen los textos, como por ejemplo la herramienta diccionario para latín y griego Morpheus.
Pleiades
Se trata de un diccionario geográfico de lugares y topónimos del mundo antiguo, continuador del proyecto que creó el Barrington Atlas of the Greek and Roman World. Pleiades asigna identificadores específicos a todos los lugares, produciendo así una web de datos linkados como la desarrollada por el Pelagios project. Pleiades se puede consultar en: pleiades.stoa.org.
TEI
Text Encoding Initiative, o Iniciativa para la Codificación de Textos. Consiste en una serie de guías y herramientas para la codificación de textos literarios e históricos en XML. Éste es el formato en el que se basa EpiDoc. La versión más reciente de las guías de TEI se puede encontrar en http://www.tei-c.org/release/doc/tei-p5-doc/es/html/index-toc.html.
World Wide Web Consortium
El World Wide Web Consortium (W3C) es una comunidad internacional que desarrolla estándares para ser usados en Internet. El público general puede participar en él, aunque también hay personal a tiempo completo, así como organizaciones enteras que dedican sus esfuerzos a este consorcio. Para más información, véase: www.w3.org.
XML
Extensible Markup Language, o lenguaje de marcaje extensible. Se trata de un formato para la codificación basado en el texto que permite la codificación estructurada de textos o datos en un formato legible tanto para las personas como para las máquinas. Conforma la base técnica de las TEI y, por consiguiente, de EpiDoc. Es también uno de los estándares mantenidos por el World Wide Web Consortium. Véase www.w3.org/XML para la descripción detallada y mayores informaciones.
XSLT
Siglas en inglés de Extensible Stylesheet Language Transformations. XSLT es un lenguaje que convierte documentos XML en, o bien XML distintos, o bien a otros formatos como el HTML (usado para páginas web), el formato de importación para bases de datos o el formato Open Document que está detrás de un procesador de textos. Las hojas de estilo (Stylesheets) de EpiDoc son un ejemplo de XSLT empleado para la transformación de documentos EpiDoc en XML a formatos de presentación comunes. W3 Schools ofrece una útil introducción al XSLT.

Responsables de esta sección

  1. Gabriel Bodard, autor
  2. Laura Löser, autora
  3. Tom Elliott, autor
  4. Núria Garcia Casacuberta, traducido al español
  5. María José Estarán, traducido al español

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Apéndice: Glosario

2024-03-05

Crosswalk, crosswalking
Éste es un término general para designar el hecho de traspasar datos del formato de un patrón de codificación a otro o de una base de datos a otra. En lo concerniente a EpiDoc, la mayoría de las veces se refiere a la conversión dinámica de las distinciones semánticas de las ediciones epigráficas y papirológicas entre el patrón XML de EpiDoc y una o varias bases de datos de textos o registros de catálogos. Estos traspasos pueden darse en las dos direcciones (EpiDoc a base de datos o base de datos a EpiDoc), e incluso en algunos casos en ambas direcciones de modo reversible sin que ello ocasione pérdida alguna de información. Algunos traspasos destacados que ha llevado a cabo la comunidad EpiDoc incluyen: la conversión de IRT desde el patrón de EpiDoc al formato de la base de datos EDH; la migración de contenidos del Duke Databank, HGV y APIS a EpiDoc como parte del proyecto Papyri.info (HGV a EpiDoc no conlleva pérdidas y es bidireccional); además de la conversión, actualmente en desarrollo, de las bases de datos EAGLE al XML de EpiDoc, como parte del proyecto EAGLE Europeana
Encoding, codificación
En este contexto, la codificación se refiere a la conversión de información inteligible para las personas a información que pueda ser interpretada por una máquina, por ejemplo en forma de lenguaje XML.
EpiDoc Example Stylesheets
Se trata de un código de software escrito en Extensible Stylesheet Language (lenguaje extensible de hojas de estilo, designado habitualmente por las siglas XSL o XSLT), cuyo objetivo es la transformación de los ficheros EpiDoc en XML a otros formatos (principalmente texto y HTML). Para ello se emplea un gran abanico de convenciones tipográficas estándar (por ejemplo, Leiden). Se puede encontrar documentación y más información en la página de las hojas de estilo en la wiki de EpiDoc.
EpiDoc Schema, patrón de EpiDoc
Conjunto de normas que se rigen por una estructura formal con el objetivo de ordenar a un editor o procesador de XML qué elementos, atributos u otro contenido está disponible en un fichero EpiDoc y cómo estructurarlos. Para documentación y más información, véase la página sobre el patrón en la wiki de EpiDoc.
Leiden, Convenciones de Leiden
Conjunto de normas para la codificación de textos clásicos en soporte epigráfico y papirológico. Se emplean símbolos sencillos, arbitrarios y exentos de ambigüedad con el fin de representar observaciones de los editores así como sus intervenciones. Por ejemplo, se escribe entre ‘[’ y ‘]’ el texto perdido ya sea porque se haya restituido o simplemente para indicar la laguna. Existen algunas variaciones menores en el sistema de Leiden usado hoy en día, quizás las más destacadas sean Krummrey-Panciera y PETRAE. Un breve resumen sobre las Convenciones de Leiden se puede encontrar en Wikipedia.
Leiden+ (Leiden-plus)
Leiden+ es un sistema de marcaje de texto que se basa principalmente en las Convenciones de Leiden pero que incluye nuevos signos y combinaciones para el marcaje de aparatos complejos, por ejemplo las inventadas para el medio de edición sin etiquetas (tags-free) del Papyrological Editor . Se puede encontrar una descripción completa además de documentación sobre Leiden+ en: papyri.info/editor/help.
Markup, marcaje
El lenguaje de marcaje es un modo de codificar los contenidos de un texto con el objetivo de posibilitar distintos modelos de presentación además de, por ejemplo, facilitar la extracción de informaciones concretas para elaborar índices o para herramientas de búsqueda. (Véase también: Encoding, codificación).
Markup también se usa a veces como abreviación de Markup List, es decir, una lista de discusión vía correo electrónico sobre temas referentes a EpiDoc y otros asuntos de marcaje de textos antiguos.
Morpheus
El servicio de análisis morfológico Morpheus es una herramienta desarrollada originariamente por Perseus. Papyri.info y el TLG emplean algunas versiones del mismo para la lematización de sus textos griegos. La herramienta disponible en Perseus también ofrece lematización en latín y en árabe. Para más información: Bamboo y Perseus.
Papyrological Navigator (PN)
Es la interfaz de búsqueda de la plataforma Papyri.info. Incluye las bases de datos DDbDP, HGV y APIS entre otras.
Papyrological editor (PE)
Se trata de la herramienta de edición y administración de texto de la plataforma Papyri.info. Permite las contribuciones y enmiendas en comunidad al corpus de papirología documental, especialmente a través de la interfaz de edición sin etiquetas (tags-free) de Leiden+.
Perseus
El proyecto Perseus Digital Library estudia la progresión de las bibliotecas de físicas a digitales y ofrece un gran número de textos que va en aumento. Se pueden realizar búsquedas directamente en su web, además de usar una serie de herramientas mientras se leen los textos, como por ejemplo la herramienta diccionario para latín y griego Morpheus.
Pleiades
Se trata de un diccionario geográfico de lugares y topónimos del mundo antiguo, continuador del proyecto que creó el Barrington Atlas of the Greek and Roman World. Pleiades asigna identificadores específicos a todos los lugares, produciendo así una web de datos linkados como la desarrollada por el Pelagios project. Pleiades se puede consultar en: pleiades.stoa.org.
TEI
Text Encoding Initiative, o Iniciativa para la Codificación de Textos. Consiste en una serie de guías y herramientas para la codificación de textos literarios e históricos en XML. Éste es el formato en el que se basa EpiDoc. La versión más reciente de las guías de TEI se puede encontrar en http://www.tei-c.org/release/doc/tei-p5-doc/es/html/index-toc.html.
World Wide Web Consortium
El World Wide Web Consortium (W3C) es una comunidad internacional que desarrolla estándares para ser usados en Internet. El público general puede participar en él, aunque también hay personal a tiempo completo, así como organizaciones enteras que dedican sus esfuerzos a este consorcio. Para más información, véase: www.w3.org.
XML
Extensible Markup Language, o lenguaje de marcaje extensible. Se trata de un formato para la codificación basado en el texto que permite la codificación estructurada de textos o datos en un formato legible tanto para las personas como para las máquinas. Conforma la base técnica de las TEI y, por consiguiente, de EpiDoc. Es también uno de los estándares mantenidos por el World Wide Web Consortium. Véase www.w3.org/XML para la descripción detallada y mayores informaciones.
XSLT
Siglas en inglés de Extensible Stylesheet Language Transformations. XSLT es un lenguaje que convierte documentos XML en, o bien XML distintos, o bien a otros formatos como el HTML (usado para páginas web), el formato de importación para bases de datos o el formato Open Document que está detrás de un procesador de textos. Las hojas de estilo (Stylesheets) de EpiDoc son un ejemplo de XSLT empleado para la transformación de documentos EpiDoc en XML a formatos de presentación comunes. W3 Schools ofrece una útil introducción al XSLT.

Responsables de esta sección

  1. Gabriel Bodard, autor
  2. Laura Löser, autora
  3. Tom Elliott, autor
  4. Núria Garcia Casacuberta, traducido al español
  5. María José Estarán, traducido al español

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary-fi.html b/gl/dev/app-glossary-fi.html index 396587e29..428b94ea3 100644 --- a/gl/dev/app-glossary-fi.html +++ b/gl/dev/app-glossary-fi.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Liite: Sanasto

2023-04-27

Crosswalk, crosswalking
Yleisluontoinen termi, jolla kuvataan tiedon siirtämistä ja muuntamista yhdestä skeemasta tai tietokannasta toiseen. EpiDocin puitteissa se usein viittaa epigrafisten ja papyrologisten editioiden semanttisten erojen dynaamiseen muuntamiseen EpiDoc XML:n ja yhden tai useamman tekstitietokannan tai luettelotietueen välillä. Muuntaminen voi tapahtua kumpaan suuntaan tahansa tai joissakin tapauksissa molempiin suuntiin, ja se on käännettävissä takaisin alkuperäiseen tiedon katoamatta. EpiDoc yhteisön suorittamista ristimuunnoksista huomattavimpia ovat: IRT:n muuntaminen EpiDocista EDH tietokantaformaattiin; Duke Databankin, HGV:n ja APIS:in sisältöjen siirto EpiDociin osana Papyri.info -projektia (HGV-EpiDoc -muunnos on häviötön ja kaksisuuntainen); meneillään oleva EAGLE:n sisältämien tietokantojen muuntaminen EpiDoc XML:ksi osana EAGLE Europeana projektia.
Koodaaminen (Encoding)
Tässä yhteydessä koodaaminen tarkoittaa ihmisen luettavissa olevan tiedon muuntamista koneluettavaan muotoon, esim. XML-muodossa.
EpiDoc tyyliarkkimallit (EpiDoc Example Stylesheets)
Ohjelmakoodi, joka on kirjoitettu Extensible Stylesheet Language:lla (XSL or XSLT), ja joka on tarkoitettu käytettäväksi muunnettaessa EpiDoc XML -tiedostoja muihin formaatteihin (pääasiassa tekstiksi ja HTML:ksi) käyttäen tavanomaisten typografisten merkintätapojen valikoimaa (esim. Leidenin merkintätapaa). Kuvaus ja lisätietoa löytyy Stylesheet-sivulta EpiDocin wikissä.
EpiDoc-skeema (EpiDoc Schema)
Muodollisesti jäsennetty sarja sääntöjä, jotka kertovat XML-editorille tai prosessorille, mitkä elementit, attribuutit ja muut sisällöt ovat sallittuja EpiDoc-tiedostossa ja miten niiden tulee olla järjestettyjä. Kuvaus ja lisätiedot Schema-sivulta EpiDocin wikissä.
Leidenin merkintätapa (Leiden, Leiden Conventions)
Piirtokirjoitusten ja papyrustekstien transkribointia varten luotu sääntökokoelma, jossa käytetään selkeitä, yksiselitteisiä ja sopimuksenvaraisia symboleita kuvaamaan editoijan havaintoja ja tulkintoja. Esim. hakasulkeet ”[” ja ”]” kuvaavat kadonnutta tekstin osaa sisältäen joko editorin tekemän täydennyksen tai aukon tekstissä. Käytössä on useita Leidenin merkintätavan variaatioita (tunnetuimpia näistä lienevät Krummrey-Panciera ja PETRAE). Hyvä yhteenveto Leidenin merkintätavasta löytyy sivulta en.wikipedia.org/wiki/Leiden_Conventions.
Leiden+ (Leiden-plus)
Leiden+ on merkintäkieli, joka perustuu hyvin vahvastiLeidenin merkintätapaan, mutta sisältää uusia merkkejä ja merkintäyhdistelmiä, jotka mahdollistavat esimerkiksi monimutkaisten apparaattimerkintöjen tekemisen. Leiden+ on kehitetty Papyrologisen editorin ”tagitonta” editointiympäristöä varten. Yksityiskohtainen kuvaus ja tapausesimerkkejä löytyy osoitteesta papyri.info/editor/help.
Merkintäkieli (Markup)
Merkintäkieltä käytetään tekstin ominaisuuksien ja piirteiden kuvaamiseen koodauskielellä. Tällä tavoin koodattu aineisto voidaan esittää monilla eri tavoilla ja siitä voidaan poimia yksityiskohtaisia tietoja esim. indeksien laatimista varten tai siihen voidaan soveltaa erilaisia hakutyökaluja (ks. Encoding).
"Markup" -sanaa käytetään toisinaan myös lyhenteenä viittaamassa sanoihin Markup List, joka on sähköpostilista, jonka kautta keskustellaan EpiDocista ja muista vanhojen tekstien merkintätapoihin liittyvistä seikoista.
Morpheus
Morpheus, morfologinen analyysipalvelu, on työkalu, jonka alun perin kehitti Perseus. Papyri.info ja TLG käyttävät sen eri versioita sisältämiensä kreikankielisten tekstien lemmatisoinnissa. Perseuksen versio soveltuu myös latinan- ja arabiankielisten tekstien lemmatisointiin. (Lisätietoja Bamboo ja Perseus.)
Papyrologinen navigaattori (PN)
Papyri.info -alustan haku- ja selausliittymä, joka sisältää DDbDP-, HGV- ja APIS-tietokannat sekä joitakin muita papyrologisia tietokantoja.
Papyrologinen editori (PE)
Papyri.info -alustan työkalu tekstien editointia ja hallintaa sekä toimitustyön eri vaiheiden hallintaa varten. PE on yhteisöllinen editointityöskentelyn väline ja sitä kautta kenen tahansa on mahdollista osallistua tekstien tallentamiseen dokumentaaristen papyrusten tietokantaan samoin kuin siellä jo olevien editioiden parantamiseen. Papyrologisessa editorissa käytetään tagitonta Leiden+ editointiliittymää.
Perseus
Perseus Digital Library -projekti tutkii kirjaston kehityskulkua materiaalisesta digitaaliseen muotoon ja tarjoaa luettavaksi jatkuvasti kasvavan kokoelman tekstejä. Sivustolla voi paitsi lukea myös tehdä erilaisia hakuja ja käyttää myös joitakin muita sen sisältämiä työkaluja kuten esim. Morpheuksen sanakirjatyökalua kreikan- ja latinankielisiin teksteihin.
Pleiades
Vanhan ja keskiajan maailman paikkojen ja paikannimien hakemisto, joka perustuu teoksen the Barrington Atlas of the Greek and Roman World tuottaneeseen projektiin. Pleiades antaa kaikille paikoille yksilölliset tunnisteet ja luo sitä kautta edellytyksiä sellaisen toisiinsa linkitetyn tiedon verkoston rakentumiseen, jollaista mm. Pelagios-projekti organisoi ja kehittää. Pleiades löytyy osoitteesta pleiades.stoa.org.
TEI
Lyhennys sanoista Text Encoding Initiative. Ohjeisto ja työkalut kirjallisten ja historiallisten tekstien koodaamiseen XML-kielellä. EpiDoc perustuu tähän formaattiin. Viimeisin TEI ohjeisto löytyy verkosta http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
World Wide Web konsortio (W3C) on kansainvälinen yhteisö, joka kehittää standardeja käytettäväksi eri puolilla internetiä. Kuka tahansa voi osallistua kehitystyöhön, mutta hankkeessa työskentelee myös palkattuja työntekijöitä ja sen jäsenistöön kuuluu kokonaisia organisaatioitakin. Lisätietoja, ks. www.w3.org.
XML
Lyhennys sanoista Extensible Markup Language. Tekstimuotoinen rakenteellinen kuvauskieli, jolla voi koodata tekstiä tai tietoa ihmisen ja koneen luettavissa olevaan muotoon. Sekä TEI että EpiDoc perustuvat tähän teknologiaan. XML on standardi, jota ylläpitää World Wide Web Consortium. Tarkempi kuvaus ja lisätiedot, ks. www.w3.org/XML.
XSLT
Lyhennys sanoista Extensible Stylesheet Language Transformations. XSLT on merkintäkieli, jolla voi muuntaa XML-tiedostoja joko toisenlaiseen XML-merkintäkieleen tai johonkin muuhun muotoon kuten esim. HTML-formaattiin, jota käytetään verkkosivujen koodaamisessa, tai johonkin tuontiformaattiin tietokantaa rakennettaessa tai Open Document formaattiin, jota käytetään tekstinkäsittelyohjelmissa. EpiDoc-tyyliarkit ovat esimerkki XSLT:stä, jolla muunnetaan EpiDoc XML -tiedostot yleisiin esitysformaatteihin. Hyödyllinen johdatus XSLT-merkintäkieleen löytyy W3 Schools sivustolta.

Vastuussa tästä osiosta

  1. Gabriel Bodard, kirjoittaja
  2. Laura Löser, kirjoittaja
  3. Tom Elliott, kirjoittaja
  4. Katariina Kankaanpää, suomentaja
  5. Marja Vierros, suomentaja

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Liite: Sanasto

2024-03-05

Crosswalk, crosswalking
Yleisluontoinen termi, jolla kuvataan tiedon siirtämistä ja muuntamista yhdestä skeemasta tai tietokannasta toiseen. EpiDocin puitteissa se usein viittaa epigrafisten ja papyrologisten editioiden semanttisten erojen dynaamiseen muuntamiseen EpiDoc XML:n ja yhden tai useamman tekstitietokannan tai luettelotietueen välillä. Muuntaminen voi tapahtua kumpaan suuntaan tahansa tai joissakin tapauksissa molempiin suuntiin, ja se on käännettävissä takaisin alkuperäiseen tiedon katoamatta. EpiDoc yhteisön suorittamista ristimuunnoksista huomattavimpia ovat: IRT:n muuntaminen EpiDocista EDH tietokantaformaattiin; Duke Databankin, HGV:n ja APIS:in sisältöjen siirto EpiDociin osana Papyri.info -projektia (HGV-EpiDoc -muunnos on häviötön ja kaksisuuntainen); meneillään oleva EAGLE:n sisältämien tietokantojen muuntaminen EpiDoc XML:ksi osana EAGLE Europeana projektia.
Koodaaminen (Encoding)
Tässä yhteydessä koodaaminen tarkoittaa ihmisen luettavissa olevan tiedon muuntamista koneluettavaan muotoon, esim. XML-muodossa.
EpiDoc tyyliarkkimallit (EpiDoc Example Stylesheets)
Ohjelmakoodi, joka on kirjoitettu Extensible Stylesheet Language:lla (XSL or XSLT), ja joka on tarkoitettu käytettäväksi muunnettaessa EpiDoc XML -tiedostoja muihin formaatteihin (pääasiassa tekstiksi ja HTML:ksi) käyttäen tavanomaisten typografisten merkintätapojen valikoimaa (esim. Leidenin merkintätapaa). Kuvaus ja lisätietoa löytyy Stylesheet-sivulta EpiDocin wikissä.
EpiDoc-skeema (EpiDoc Schema)
Muodollisesti jäsennetty sarja sääntöjä, jotka kertovat XML-editorille tai prosessorille, mitkä elementit, attribuutit ja muut sisällöt ovat sallittuja EpiDoc-tiedostossa ja miten niiden tulee olla järjestettyjä. Kuvaus ja lisätiedot Schema-sivulta EpiDocin wikissä.
Leidenin merkintätapa (Leiden, Leiden Conventions)
Piirtokirjoitusten ja papyrustekstien transkribointia varten luotu sääntökokoelma, jossa käytetään selkeitä, yksiselitteisiä ja sopimuksenvaraisia symboleita kuvaamaan editoijan havaintoja ja tulkintoja. Esim. hakasulkeet ”[” ja ”]” kuvaavat kadonnutta tekstin osaa sisältäen joko editorin tekemän täydennyksen tai aukon tekstissä. Käytössä on useita Leidenin merkintätavan variaatioita (tunnetuimpia näistä lienevät Krummrey-Panciera ja PETRAE). Hyvä yhteenveto Leidenin merkintätavasta löytyy sivulta en.wikipedia.org/wiki/Leiden_Conventions.
Leiden+ (Leiden-plus)
Leiden+ on merkintäkieli, joka perustuu hyvin vahvastiLeidenin merkintätapaan, mutta sisältää uusia merkkejä ja merkintäyhdistelmiä, jotka mahdollistavat esimerkiksi monimutkaisten apparaattimerkintöjen tekemisen. Leiden+ on kehitetty Papyrologisen editorin ”tagitonta” editointiympäristöä varten. Yksityiskohtainen kuvaus ja tapausesimerkkejä löytyy osoitteesta papyri.info/editor/help.
Merkintäkieli (Markup)
Merkintäkieltä käytetään tekstin ominaisuuksien ja piirteiden kuvaamiseen koodauskielellä. Tällä tavoin koodattu aineisto voidaan esittää monilla eri tavoilla ja siitä voidaan poimia yksityiskohtaisia tietoja esim. indeksien laatimista varten tai siihen voidaan soveltaa erilaisia hakutyökaluja (ks. Encoding).
"Markup" -sanaa käytetään toisinaan myös lyhenteenä viittaamassa sanoihin Markup List, joka on sähköpostilista, jonka kautta keskustellaan EpiDocista ja muista vanhojen tekstien merkintätapoihin liittyvistä seikoista.
Morpheus
Morpheus, morfologinen analyysipalvelu, on työkalu, jonka alun perin kehitti Perseus. Papyri.info ja TLG käyttävät sen eri versioita sisältämiensä kreikankielisten tekstien lemmatisoinnissa. Perseuksen versio soveltuu myös latinan- ja arabiankielisten tekstien lemmatisointiin. (Lisätietoja Bamboo ja Perseus.)
Papyrologinen navigaattori (PN)
Papyri.info -alustan haku- ja selausliittymä, joka sisältää DDbDP-, HGV- ja APIS-tietokannat sekä joitakin muita papyrologisia tietokantoja.
Papyrologinen editori (PE)
Papyri.info -alustan työkalu tekstien editointia ja hallintaa sekä toimitustyön eri vaiheiden hallintaa varten. PE on yhteisöllinen editointityöskentelyn väline ja sitä kautta kenen tahansa on mahdollista osallistua tekstien tallentamiseen dokumentaaristen papyrusten tietokantaan samoin kuin siellä jo olevien editioiden parantamiseen. Papyrologisessa editorissa käytetään tagitonta Leiden+ editointiliittymää.
Perseus
Perseus Digital Library -projekti tutkii kirjaston kehityskulkua materiaalisesta digitaaliseen muotoon ja tarjoaa luettavaksi jatkuvasti kasvavan kokoelman tekstejä. Sivustolla voi paitsi lukea myös tehdä erilaisia hakuja ja käyttää myös joitakin muita sen sisältämiä työkaluja kuten esim. Morpheuksen sanakirjatyökalua kreikan- ja latinankielisiin teksteihin.
Pleiades
Vanhan ja keskiajan maailman paikkojen ja paikannimien hakemisto, joka perustuu teoksen the Barrington Atlas of the Greek and Roman World tuottaneeseen projektiin. Pleiades antaa kaikille paikoille yksilölliset tunnisteet ja luo sitä kautta edellytyksiä sellaisen toisiinsa linkitetyn tiedon verkoston rakentumiseen, jollaista mm. Pelagios-projekti organisoi ja kehittää. Pleiades löytyy osoitteesta pleiades.stoa.org.
TEI
Lyhennys sanoista Text Encoding Initiative. Ohjeisto ja työkalut kirjallisten ja historiallisten tekstien koodaamiseen XML-kielellä. EpiDoc perustuu tähän formaattiin. Viimeisin TEI ohjeisto löytyy verkosta http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
World Wide Web konsortio (W3C) on kansainvälinen yhteisö, joka kehittää standardeja käytettäväksi eri puolilla internetiä. Kuka tahansa voi osallistua kehitystyöhön, mutta hankkeessa työskentelee myös palkattuja työntekijöitä ja sen jäsenistöön kuuluu kokonaisia organisaatioitakin. Lisätietoja, ks. www.w3.org.
XML
Lyhennys sanoista Extensible Markup Language. Tekstimuotoinen rakenteellinen kuvauskieli, jolla voi koodata tekstiä tai tietoa ihmisen ja koneen luettavissa olevaan muotoon. Sekä TEI että EpiDoc perustuvat tähän teknologiaan. XML on standardi, jota ylläpitää World Wide Web Consortium. Tarkempi kuvaus ja lisätiedot, ks. www.w3.org/XML.
XSLT
Lyhennys sanoista Extensible Stylesheet Language Transformations. XSLT on merkintäkieli, jolla voi muuntaa XML-tiedostoja joko toisenlaiseen XML-merkintäkieleen tai johonkin muuhun muotoon kuten esim. HTML-formaattiin, jota käytetään verkkosivujen koodaamisessa, tai johonkin tuontiformaattiin tietokantaa rakennettaessa tai Open Document formaattiin, jota käytetään tekstinkäsittelyohjelmissa. EpiDoc-tyyliarkit ovat esimerkki XSLT:stä, jolla muunnetaan EpiDoc XML -tiedostot yleisiin esitysformaatteihin. Hyödyllinen johdatus XSLT-merkintäkieleen löytyy W3 Schools sivustolta.

Vastuussa tästä osiosta

  1. Gabriel Bodard, kirjoittaja
  2. Laura Löser, kirjoittaja
  3. Tom Elliott, kirjoittaja
  4. Katariina Kankaanpää, suomentaja
  5. Marja Vierros, suomentaja

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary-fr.html b/gl/dev/app-glossary-fr.html index c369a7511..3756a05f4 100644 --- a/gl/dev/app-glossary-fr.html +++ b/gl/dev/app-glossary-fr.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Glossaire

2023-04-27

Crosswalk, crosswalking - Conversion
Terme générique décrivant l’acte de convertir des données depuis un modèle d’information ou de base de donnée vers un autre. Dans le cadre spécifique d’EpiDoc, le terme fait référence à la conversion des distinctions sémantiques propres à l’épigraphie ou à la papyrologie entre la définition XML EpiDoc et un ou plusieurs systèmes d’enregistrement ou de catalogage. Ces conversions peuvent se faire dans l’une ou l’autre direction, voir même, dans certains cas, dans les deux sens en parallèle de manière transparente et sans perte d’informations. Parmi les conversions les plus notables réalisées par la communauté EpiDoc on notera :
- La conversion des IRT du format XML EpiDoc au format de base de donnée de l’EDH
- La conversion du contenu de la DDbDP, de l'HGV et de l'APIS vers EpiDoc dans le cadre du projet Papiry.info (la conversion HGV-EpiDoc étant bidirectionnelle et sans perte d’informations)
- La conversion actuellement en cours des bases de donnée sous-jacentes à EAGLE vers le format XML EpiDoc dans le cadre du projet EAGLE Europeana
Encodage
Encoder signifie, dans le contexte spécifique d’EpiDoc, la transcription d’informations textuelles classiques vers un format adapté à la lecture par des systèmes informatiques, par exemple selon un standard XML.
EpiDoc Example Stylesheets (feuilles de style d’exemple EpiDoc)
Code informatique écrit en XSL ou XSLT (Extensible Stylesheet Language), et destiné à être utilisé pour convertir un fichier XML EpiDoc vers un autre format (essentiellement du texte normal ou un fichier HTML) en appliquant un certain nombre de conventions typographiques (par exemple les conventions de Leyde). La documentation et un complément d’information sont disponibles sur la page Stylesheets du Wiki EpiDoc
Schéma EpiDoc
Ensemble de règles définies de manière formelle permettant d’indiquer à un programme d’édition ou de traitement de l’XML les éléments, attributs et autres informations disponibles au sein d’un fichier EpiDoc et la manière dont ils doivent être structurés. La documentation et des informations complémentaires sont disponibles sur la page Schéma du Wiki EpiDoc
Leyde, Conventions de Leyde (Leiden)
Ensemble de règles pour la transcription de textes épigraphiques ou papyrologiques utilisant de manière simple, arbitraire et claire des symboles pour représenter les constatations et interventions éditoriales, à l’instar de ‘[‘ et ‘]’ pour indiquer un fragment perdu (restauré ou lacunaire). Il existe diverses variantes mineures de ces conventions, Krummrey-Panciera et PETRAE étant probablement les plus communes à l’heure actuelle. Un bon résumé des conventions de Leyde est disponible sur la page en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leyde plus)
Leiden+ est un système de balisage de texte dérivé des règles de la convention de Leyde mais incluant de nouveaux symboles et combinaisons pour, notamment, l’annotation d’apparatus complexes. Il a été initialement conçu pour l’environnement “sans balises” développé dans le cadre de l’Editeur Papyrologique. La documentation et des informations complémentaires sont disponibles sur la page papyri.info/editor/help.
Markup (Balisage - Annotation)
Les langages de balisage sont une manière de transcrire le contenu d’un texte de manière à permettre sa représentations de différentes manières et à, par exemple, rendre possible l’indexation des informations qu’il contient afin de la rendre disponible dans des index ou via des moteurs de recherche. (cf. Encodage)
Le mot “Markup” est également utilisé à l’occasion comme abréviation pour décrire la liste de diffusion Markup, système d’échanges par email destiné à communiquer au sujet d’EpiDoc et d’autres problématiques liées au balisage de textes anciens.
Morpheus
Le service d’analyse morphologique Morpheus est un outil originellement développé par le projet Perseus dont des versions sont utilisées par les projets Papyri.info et TLG pour la lemmatisation des textes grecs. La version Perseus de l’outil permet également de fournir ce service pour l’arabe et le latin. Des informations complémentaires sont disponibles sur les pages Bamboo et Perseus.
Perseus
Le projet Perseus Digital Library étudie le passage des bibliothèque physiques traditionnelles aux bibliothèques digitales et offre un nombre croissant de textes. Divers outils peuvent être utilisés directement sur le site web du projet durant la lecture, à l’instar d’un moteur de recherche, de dictionnaires ou de l’outil d’analyse morphologique Morpheus.
Pleiades
Index géographique reprenant la localisation et la toponymie de sites anciens, partant des fondations mises en place par le Barrington Atlas of the Greek and Roman World. Pleiades assigne un identifiant unique à chaque lieu, permettant de mettre en place un Web des Données (Linked Data) tel que celui maintenu par le projet Pelagios. Le projet Pleiades est accessible à l’adresse pleiades.stoa.org
TEI
Text Encoding Initiative. Ensemble de recommandations et d’outils pour l’encodage de textes littéraires et historiques en XML. C’est le format sur lequel EpiDoc se base. Les dernières recommandations sont accessibles en ligne à l’adresse http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html
World Wide Web Consortium
Le World Wide Web Consortium (W3C) est une communauté internationale développant les standards destinés à être utilisés pour Internet. Le public peut contribuer mais il existe également un personnel permanent et diverses organisations qui font partie de l’entreprise. Des informations complémentaires sont disponibles sur la page www.w3.org
XML
Extensible Markup Language. Format d’encodage textuel permettant l’encodage structuré de données ou de textes dans un format lisible tant par les machines que par l’homme. C’est la base technologique sur laquelle sont fondés tant les formats TEI et EpiDoc et forme un standard maintenu par le World Wide Web Consortium. Des informations complémentaires sont disponibles sur www.w3.org/XML.
XSLT
Extensible Stylesheet Language Transformations. XSLT est le langage informatique permettant de convertir des documents XML dans d’autres formats XML ou d’autres langages informatiques, par exemple du HTML utilisé pour créer des sites web, un format d’import d’information pour une base de données ou le format Open Document utilisé par une application de traitement de texte. Les EpiDoc Stylesheets (feuilles de style EpiDoc) sont un exemple d’XSLT utilisé pour convertir des documents XML EpiDoc vers des formats d’affichage courants. Une intéressante introduction au format XSLT est proposée par la W3 Schools

Responsables de cette section

  1. Gabriel Bodard, Auteur
  2. Laura Löser, Auteur
  3. Tom Elliott, Auteur
  4. Pascal Lemaire, Traduction française

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Glossaire

2024-03-05

Crosswalk, crosswalking - Conversion
Terme générique décrivant l’acte de convertir des données depuis un modèle d’information ou de base de donnée vers un autre. Dans le cadre spécifique d’EpiDoc, le terme fait référence à la conversion des distinctions sémantiques propres à l’épigraphie ou à la papyrologie entre la définition XML EpiDoc et un ou plusieurs systèmes d’enregistrement ou de catalogage. Ces conversions peuvent se faire dans l’une ou l’autre direction, voir même, dans certains cas, dans les deux sens en parallèle de manière transparente et sans perte d’informations. Parmi les conversions les plus notables réalisées par la communauté EpiDoc on notera :
- La conversion des IRT du format XML EpiDoc au format de base de donnée de l’EDH
- La conversion du contenu de la DDbDP, de l'HGV et de l'APIS vers EpiDoc dans le cadre du projet Papiry.info (la conversion HGV-EpiDoc étant bidirectionnelle et sans perte d’informations)
- La conversion actuellement en cours des bases de donnée sous-jacentes à EAGLE vers le format XML EpiDoc dans le cadre du projet EAGLE Europeana
Encodage
Encoder signifie, dans le contexte spécifique d’EpiDoc, la transcription d’informations textuelles classiques vers un format adapté à la lecture par des systèmes informatiques, par exemple selon un standard XML.
EpiDoc Example Stylesheets (feuilles de style d’exemple EpiDoc)
Code informatique écrit en XSL ou XSLT (Extensible Stylesheet Language), et destiné à être utilisé pour convertir un fichier XML EpiDoc vers un autre format (essentiellement du texte normal ou un fichier HTML) en appliquant un certain nombre de conventions typographiques (par exemple les conventions de Leyde). La documentation et un complément d’information sont disponibles sur la page Stylesheets du Wiki EpiDoc
Schéma EpiDoc
Ensemble de règles définies de manière formelle permettant d’indiquer à un programme d’édition ou de traitement de l’XML les éléments, attributs et autres informations disponibles au sein d’un fichier EpiDoc et la manière dont ils doivent être structurés. La documentation et des informations complémentaires sont disponibles sur la page Schéma du Wiki EpiDoc
Leyde, Conventions de Leyde (Leiden)
Ensemble de règles pour la transcription de textes épigraphiques ou papyrologiques utilisant de manière simple, arbitraire et claire des symboles pour représenter les constatations et interventions éditoriales, à l’instar de ‘[‘ et ‘]’ pour indiquer un fragment perdu (restauré ou lacunaire). Il existe diverses variantes mineures de ces conventions, Krummrey-Panciera et PETRAE étant probablement les plus communes à l’heure actuelle. Un bon résumé des conventions de Leyde est disponible sur la page en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leyde plus)
Leiden+ est un système de balisage de texte dérivé des règles de la convention de Leyde mais incluant de nouveaux symboles et combinaisons pour, notamment, l’annotation d’apparatus complexes. Il a été initialement conçu pour l’environnement “sans balises” développé dans le cadre de l’Editeur Papyrologique. La documentation et des informations complémentaires sont disponibles sur la page papyri.info/editor/help.
Markup (Balisage - Annotation)
Les langages de balisage sont une manière de transcrire le contenu d’un texte de manière à permettre sa représentations de différentes manières et à, par exemple, rendre possible l’indexation des informations qu’il contient afin de la rendre disponible dans des index ou via des moteurs de recherche. (cf. Encodage)
Le mot “Markup” est également utilisé à l’occasion comme abréviation pour décrire la liste de diffusion Markup, système d’échanges par email destiné à communiquer au sujet d’EpiDoc et d’autres problématiques liées au balisage de textes anciens.
Morpheus
Le service d’analyse morphologique Morpheus est un outil originellement développé par le projet Perseus dont des versions sont utilisées par les projets Papyri.info et TLG pour la lemmatisation des textes grecs. La version Perseus de l’outil permet également de fournir ce service pour l’arabe et le latin. Des informations complémentaires sont disponibles sur les pages Bamboo et Perseus.
Perseus
Le projet Perseus Digital Library étudie le passage des bibliothèque physiques traditionnelles aux bibliothèques digitales et offre un nombre croissant de textes. Divers outils peuvent être utilisés directement sur le site web du projet durant la lecture, à l’instar d’un moteur de recherche, de dictionnaires ou de l’outil d’analyse morphologique Morpheus.
Pleiades
Index géographique reprenant la localisation et la toponymie de sites anciens, partant des fondations mises en place par le Barrington Atlas of the Greek and Roman World. Pleiades assigne un identifiant unique à chaque lieu, permettant de mettre en place un Web des Données (Linked Data) tel que celui maintenu par le projet Pelagios. Le projet Pleiades est accessible à l’adresse pleiades.stoa.org
TEI
Text Encoding Initiative. Ensemble de recommandations et d’outils pour l’encodage de textes littéraires et historiques en XML. C’est le format sur lequel EpiDoc se base. Les dernières recommandations sont accessibles en ligne à l’adresse http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html
World Wide Web Consortium
Le World Wide Web Consortium (W3C) est une communauté internationale développant les standards destinés à être utilisés pour Internet. Le public peut contribuer mais il existe également un personnel permanent et diverses organisations qui font partie de l’entreprise. Des informations complémentaires sont disponibles sur la page www.w3.org
XML
Extensible Markup Language. Format d’encodage textuel permettant l’encodage structuré de données ou de textes dans un format lisible tant par les machines que par l’homme. C’est la base technologique sur laquelle sont fondés tant les formats TEI et EpiDoc et forme un standard maintenu par le World Wide Web Consortium. Des informations complémentaires sont disponibles sur www.w3.org/XML.
XSLT
Extensible Stylesheet Language Transformations. XSLT est le langage informatique permettant de convertir des documents XML dans d’autres formats XML ou d’autres langages informatiques, par exemple du HTML utilisé pour créer des sites web, un format d’import d’information pour une base de données ou le format Open Document utilisé par une application de traitement de texte. Les EpiDoc Stylesheets (feuilles de style EpiDoc) sont un exemple d’XSLT utilisé pour convertir des documents XML EpiDoc vers des formats d’affichage courants. Une intéressante introduction au format XSLT est proposée par la W3 Schools

Responsables de cette section

  1. Gabriel Bodard, Auteur
  2. Laura Löser, Auteur
  3. Tom Elliott, Auteur
  4. Pascal Lemaire, Traduction française

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary-it.html b/gl/dev/app-glossary-it.html index 5822ca265..5d1951904 100644 --- a/gl/dev/app-glossary-it.html +++ b/gl/dev/app-glossary-it.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendice: Glossario

2023-04-27

Crosswalk, crosswalking
Un termine generico per lo spostamento di dati dal formato di uno schema di codifica o database all'altro. Per quanto riguarda EpiDoc, si riferisce spesso alla trasformazione dinamica delle distinzioni semantiche delle edizioni epigrafiche e papirologiche tra XML EpiDoc e uno o più dati di testi o documenti di catalogo. Questi "crosswalk" possono avvenire in entrambe le direzioni, o in alcuni casi in entrambe le direzioni e al contrario, senza perdita di informazioni. Crosswalk di spicco svolte dalla comunità EpiDoc includono: la conversione di IRT da EpiDoc al formato database di EDH; la migrazione del contenuto di Duke Databank, HGV e APIS a EpiDoc come parte del progetto Papyri.info (la migrazione HGV-a-EpiDoc è senza perdite e bidirezionale); l'attuale conversione delle banche dati costitutivi EAGLE in XML EpiDoc nell'ambito del progetto EAGLE Europeana.
Codifica
Codifica in questo contesto significa la conversione di informazioni leggibili in informazioni leggibili a macchina, ad esempio, in formato XML.
Fogli di stile EpiDoc (esempio)
Codice software, scritto in Extensible Stylesheet Language (XSL o XSLT), e destinato ad essere utilizzato nella trasformazione di file da XML EpiDoc ad altri formati (principalmente di testo e HTML) utilizzando una serie di convenzioni tipografiche standard (ad esempio, Leiden). Documentazione e ulteriori informazioni si trovano nella pagina "Stylesheets" (Fogli di stile) nella Wiki EpiDoc.
Schema EpiDoc
Un insieme di regole formalmente strutturato che indica ad un editor XML o a un processore quali elementi, attributi e altri contenuti sono disponibili in un file Wiki EpiDoc e come questi devono essere strutturati. Documentazione e ulteriori informazioni si trovano sulla pagina Schema nella Wiki EpiDoc.
Leiden, Convenzioni Leiden
Un insieme di regole per la codifica di testi epigrafici e papirologici classici che utilizza simboli semplici, arbitrari e inequivocabili per rappresentare osservazioni editoriali e interventi, ad esempio '[' e ']' per testo perduto (ripristinato o in lacune). Ci sono diverse variazioni minori di Leiden ora in uso (Krummrey-Panciera e Petrae forse le più importanti). Una buona sintesi di Leiden può essere trovata all'indirizzo en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ è un sistema di codifica del testo, basato strettamente su Leiden, che però include nuovi segni e combinazioni per la codifica di apparati critici complessi, creato ad esempio, per l'ambiente editoriale "tags-free" del Papyrological Editor. Descrizione e documentazione completa di Leiden+ si trova presso papyri.info/editor/help.
Markup (Codifica)
Il Markup, Linguaggio di marcatura, è un modo per codificare il contenuto di un testo al fine di consentire diversi modi di rappresentazione e, ad esempio, per estrarre informazioni da raccogliere per indici, o strumenti di ricerca (cfr. Codifica ).
"Markup" a volte è anche usato come nome breve per la Markup List, una mailing list per la discussione di Wiki EpiDoc e di altre questioni di codifica dei testi antichi.
Morpheus
Il servizio di analisi morfologica Morpheus è uno strumento sviluppato originariamente da Perseus , le cui versioni sono in uso da Papyri.info e da TLG per la lemmatizzazione dei testi greci. La versione Perseus dello strumento si utilizza anche per la lemmatizzazione del latino e dell'arabo. (Maggiori informazioni su Bamboo e Perseus.)
Papyrological Navigator (PN) (Navigatore Papirologico)
L'interfaccia di "ricerca e sfoglia" della piattaforma Papyri.info, che incorpora i DDbDP, HGV, APIS e altri database papirologici.
Papyrological editor (PE) (Editor Papirologico)
Lo strumento per l'elaborazione e la gestione dei testi e del flusso di lavoro editoriale della piattaforma Papyri.info che permette il contributo della comunità e l'emendazione del corpus documentario papirologico, in particolare attraverso l'interfaccia editoriale "tags-free" Leiden + .
Perseus
Il Perseus Digital Library Project studia la progressione da fisico a biblioteche digitali ed offre un crescente numero di testi. Ricerche e una serie di altri strumenti possono essere utilizzati direttamente sul sito durante la lettura, come ad esempio il dizionario di Morpheus per i testi greci e latini.
Pleiades
Un dizionario geografico di toponimi del mondo antico basato sul progetto che ha prodotto il Barrington Atlas of the Greek and Roman World. Pleiades attribuisce IDs univoci a ciascun toponimo, creando un web di Linked Data come quello curato dal Pelagios project. Pleiades è accessible tramite pleiades.stoa.org.
TEI
Text Encoding Initiative. Linee guida e strumenti per la codifica di testi letterari e storici in XML . È il formato su cui è basata la Wiki EpiDoc. Le più recenti linee guida TEI si possono trovare online all'indirizzo http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
Il World Wide Web Consortium (W3C) è una comunità internazionale per lo sviluppo di standards utilizzati ovunque l'Internet. Il pubblico può partecipare, ma vi è anche personale a tempo pieno e intere organizzazioni membri dell'impresa. Per maggiori informazioni, vedere: www.w3.org.
XML
Extensible Markup Language. Un formato di codifica basato su testo che consente la codifica di testo strutturato o di dati in formato leggibile dall'uomo e dalla macchina. È la base tecnica di entrambe TEI e Wiki EpiDoc, ed è uno standard gestito da il World-wide Web Consortium. Vedere www.w3.org/XML per le specifiche e ulteriori informazioni.
XSLT
Extensible Stylesheet Language Transformations. XSLT è un linguaggio che può convertire documenti in XML verso un diverso formato XML o in altri formati, ad esempio il formato HTML utilizzato per i siti web, il formato di importazione per un database, o l'Open Document Format che sta dietro un documento di elaborazione testi. Gli EpiDoc Stylesheets (Fogli di Stile EpiDoc) sono un esempio di XSLT utilizzato per trasformare XML EpiDoc in formati di visualizzazione comuni. Un'introduzione utile per XSLT è offerta da W3 Schools.

Responsabilità per questa sezione

  1. Gabriel Bodard, autore
  2. Laura Löser, autore
  3. Tom Elliott, autore
  4. Eleonora Litta, traduzione italiana
  5. Pietro Liuzzo, correzione traduzione italiana
  6. Greta Franzini, correzione traduzione italiana

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendice: Glossario

2024-03-05

Crosswalk, crosswalking
Un termine generico per lo spostamento di dati dal formato di uno schema di codifica o database all'altro. Per quanto riguarda EpiDoc, si riferisce spesso alla trasformazione dinamica delle distinzioni semantiche delle edizioni epigrafiche e papirologiche tra XML EpiDoc e uno o più dati di testi o documenti di catalogo. Questi "crosswalk" possono avvenire in entrambe le direzioni, o in alcuni casi in entrambe le direzioni e al contrario, senza perdita di informazioni. Crosswalk di spicco svolte dalla comunità EpiDoc includono: la conversione di IRT da EpiDoc al formato database di EDH; la migrazione del contenuto di Duke Databank, HGV e APIS a EpiDoc come parte del progetto Papyri.info (la migrazione HGV-a-EpiDoc è senza perdite e bidirezionale); l'attuale conversione delle banche dati costitutivi EAGLE in XML EpiDoc nell'ambito del progetto EAGLE Europeana.
Codifica
Codifica in questo contesto significa la conversione di informazioni leggibili in informazioni leggibili a macchina, ad esempio, in formato XML.
Fogli di stile EpiDoc (esempio)
Codice software, scritto in Extensible Stylesheet Language (XSL o XSLT), e destinato ad essere utilizzato nella trasformazione di file da XML EpiDoc ad altri formati (principalmente di testo e HTML) utilizzando una serie di convenzioni tipografiche standard (ad esempio, Leiden). Documentazione e ulteriori informazioni si trovano nella pagina "Stylesheets" (Fogli di stile) nella Wiki EpiDoc.
Schema EpiDoc
Un insieme di regole formalmente strutturato che indica ad un editor XML o a un processore quali elementi, attributi e altri contenuti sono disponibili in un file Wiki EpiDoc e come questi devono essere strutturati. Documentazione e ulteriori informazioni si trovano sulla pagina Schema nella Wiki EpiDoc.
Leiden, Convenzioni Leiden
Un insieme di regole per la codifica di testi epigrafici e papirologici classici che utilizza simboli semplici, arbitrari e inequivocabili per rappresentare osservazioni editoriali e interventi, ad esempio '[' e ']' per testo perduto (ripristinato o in lacune). Ci sono diverse variazioni minori di Leiden ora in uso (Krummrey-Panciera e Petrae forse le più importanti). Una buona sintesi di Leiden può essere trovata all'indirizzo en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ è un sistema di codifica del testo, basato strettamente su Leiden, che però include nuovi segni e combinazioni per la codifica di apparati critici complessi, creato ad esempio, per l'ambiente editoriale "tags-free" del Papyrological Editor. Descrizione e documentazione completa di Leiden+ si trova presso papyri.info/editor/help.
Markup (Codifica)
Il Markup, Linguaggio di marcatura, è un modo per codificare il contenuto di un testo al fine di consentire diversi modi di rappresentazione e, ad esempio, per estrarre informazioni da raccogliere per indici, o strumenti di ricerca (cfr. Codifica ).
"Markup" a volte è anche usato come nome breve per la Markup List, una mailing list per la discussione di Wiki EpiDoc e di altre questioni di codifica dei testi antichi.
Morpheus
Il servizio di analisi morfologica Morpheus è uno strumento sviluppato originariamente da Perseus , le cui versioni sono in uso da Papyri.info e da TLG per la lemmatizzazione dei testi greci. La versione Perseus dello strumento si utilizza anche per la lemmatizzazione del latino e dell'arabo. (Maggiori informazioni su Bamboo e Perseus.)
Papyrological Navigator (PN) (Navigatore Papirologico)
L'interfaccia di "ricerca e sfoglia" della piattaforma Papyri.info, che incorpora i DDbDP, HGV, APIS e altri database papirologici.
Papyrological editor (PE) (Editor Papirologico)
Lo strumento per l'elaborazione e la gestione dei testi e del flusso di lavoro editoriale della piattaforma Papyri.info che permette il contributo della comunità e l'emendazione del corpus documentario papirologico, in particolare attraverso l'interfaccia editoriale "tags-free" Leiden + .
Perseus
Il Perseus Digital Library Project studia la progressione da fisico a biblioteche digitali ed offre un crescente numero di testi. Ricerche e una serie di altri strumenti possono essere utilizzati direttamente sul sito durante la lettura, come ad esempio il dizionario di Morpheus per i testi greci e latini.
Pleiades
Un dizionario geografico di toponimi del mondo antico basato sul progetto che ha prodotto il Barrington Atlas of the Greek and Roman World. Pleiades attribuisce IDs univoci a ciascun toponimo, creando un web di Linked Data come quello curato dal Pelagios project. Pleiades è accessible tramite pleiades.stoa.org.
TEI
Text Encoding Initiative. Linee guida e strumenti per la codifica di testi letterari e storici in XML . È il formato su cui è basata la Wiki EpiDoc. Le più recenti linee guida TEI si possono trovare online all'indirizzo http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
Il World Wide Web Consortium (W3C) è una comunità internazionale per lo sviluppo di standards utilizzati ovunque l'Internet. Il pubblico può partecipare, ma vi è anche personale a tempo pieno e intere organizzazioni membri dell'impresa. Per maggiori informazioni, vedere: www.w3.org.
XML
Extensible Markup Language. Un formato di codifica basato su testo che consente la codifica di testo strutturato o di dati in formato leggibile dall'uomo e dalla macchina. È la base tecnica di entrambe TEI e Wiki EpiDoc, ed è uno standard gestito da il World-wide Web Consortium. Vedere www.w3.org/XML per le specifiche e ulteriori informazioni.
XSLT
Extensible Stylesheet Language Transformations. XSLT è un linguaggio che può convertire documenti in XML verso un diverso formato XML o in altri formati, ad esempio il formato HTML utilizzato per i siti web, il formato di importazione per un database, o l'Open Document Format che sta dietro un documento di elaborazione testi. Gli EpiDoc Stylesheets (Fogli di Stile EpiDoc) sono un esempio di XSLT utilizzato per trasformare XML EpiDoc in formati di visualizzazione comuni. Un'introduzione utile per XSLT è offerta da W3 Schools.

Responsabilità per questa sezione

  1. Gabriel Bodard, autore
  2. Laura Löser, autore
  3. Tom Elliott, autore
  4. Eleonora Litta, traduzione italiana
  5. Pietro Liuzzo, correzione traduzione italiana
  6. Greta Franzini, correzione traduzione italiana

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary-pt-br.html b/gl/dev/app-glossary-pt-br.html index f1b5776c1..beb8d6c87 100644 --- a/gl/dev/app-glossary-pt-br.html +++ b/gl/dev/app-glossary-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Apêndice: Glossário

2023-04-27

Codificação
Codificação, neste contexto, significa a conversão de informação legível por humanos para informação legível por máquina como, por exemplo, no formato XML.
Crosswalk, crosswalking

Um termo geral que descreve a transferência de dados de um formato de schema de codificação ou de banco de dados para outro. Em termos EpiDoc, isto geralmente se refere à transformação dinâmica das distinções semânticas de edições epigráficas e papirológicas entre o XML EpiDoc e um ou mais banco de dados de texto ou registros de catálogos. Estas "crosswalks" podem acontecer em qualquer direção, e, alguns casos em ambas direções são reversíveis sem perda de informação. Crosswalks importantes executadas pela comunidade EpiDoc incluem: a conversão de IRT do EpiDoc para o formato de banco de dados de EDH; a migração de conteúdo doDuke Databank, HGV e APIS para EpiDoc como parte do projeto Papyri.info (o HGV-para-EpiDoc é bidirecional e sem perda); a atual conversão dos bancos de dados constituintes do EAGLE para XML EpiDoc como parte do projeto EAGLE Europeana.

EpiDoc Schema
Um conjunto de regras estruturado que diz a um processador ou editor de XML quais elementos, atributos ou outro conteúdo estão disponíveis num arquivo EpiDoc, e como estes devem estar organizados. Documentação e maiores informações são encontrados na página Schema no EpiDoc Wiki.
Folhas de Estilo de Exemplo EpiDoc
Código de software, escrito em linguagem Extensible Stylesheet (XSL ou XSLT), com a intenção de ser utilizado para transformar aquivos XML EpiDoc em outros formatos (principalmente em texto e HTML), utilizando uma gama de convenções tipográficas padrão (como Leiden). Documentação e maiores informações podem ser encontradas na página Folhas de Estilo no EpiDoc Wiki.
Leiden, Convenções Leiden
Um conjunto de normas para a codificação de textos clássicos, epigráficos e papirológicos, usando símbolos simples, arbitrários e claros para representar observações e intervenções editoriais, como '[' e ']' para texto perdido (restaurado ou uma lacuna). Existem várias pequenas variações do Leiden atualmente em uso (Krummrey-Panciera e PETRAE talvez sejam os mais importantes). Um bom resumo do Leiden pode ser encontrado em en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ is é um sistema de marcação baseado fortemente no Leiden mas incluindo novos sinais e combinações para marcação complexa de aparato, como, por exemplo, aquele feito para o ambiente de edição "tags-free" do Editor Papirológico. A descrição e documentação completa do Leiden+ se encontra em papyri.info/editor/help.
Marcação
Linguagem de marcação é uma forma de codificar um conteúdo de texto de modo a habilitar modos diferentes de representação e, por exemplo, extrair informação que será coletada por índices ou mecanismos de busca (veja. Codificação).
"Markup" é algumas vezes utilizado como abreviação para a Lista de Markup, uma lista de emails para a discussão do EpiDoc e outros assuntos referentes à marcação de textos antigos.
Morpheus
O serviço de análise morfológica Morpheus é uma ferramenta inicialmente desenvolvida pelo Perseus, com versões dele em uso pelo Papyri.info e pelo TLG para a lematização de seus textos gregos. A versão Perseus desta ferramenta também serve para a lematização do latim e do árabe. (Maiores informações em Bamboo e Perseus.)
Papyrological Navigator (PN)
A interface de navegação e busca da plataforma Papyri.info, que incorpora DDbDP, HGV, APIS e outros bancos de dados papirológicos.
Papyrological editor (PE)
A ferramenta de fluxo editorial, de gerenciamento e de edição da plataforma Papyri.info que permite a contribuição e as emendas da comunidade ao corpus de documentação papirológica, notadamente através da interface de edição tags-free do Leiden+.
Perseus
O Projeto de Biblioteca Digital Perseus estuda a progressão das bibliotecas, de físicas para digitais, e oferece um número cada vez maior de textos. Buscadores e uma quantidade de ferramentas podem ser utilizados diretamente no website enquanto se lê, como a ferramenta dicionário Morpheus para textos em grego e latim.
Pleiades
Um dicionário geográfico de locais e nomes de locais do mundo antigo, aumentando o projeto que produziu o Atlas Barrington do Mundo Grego e Romano. O Pleiades designa identificadores únicos para cada lugar, habilitando uma rede de Linked Data como a que tem a curadoria do projeto Pelagios. Pleiades pode ser encontrado no endereço pleiades.stoa.org.
TEI
Sigla para Text Encoding Initiative (Iniciativa de Codificação de Texto). Normas e ferramentas para a codificação de textos literários e históricos em XML. Este é o formato em que o EpiDoc se baseia. Normas TEI atualizadas podem ser encontgradas online no endereço http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
O World Wide Web Consortium (Consórcio da Rede Mundial - W3C) é uma comunidade internacional que desenvolve padrões para serem utilizados na Internet. O público pode participar, mas também existe uma equipe trabalhando em tempo integral e organizações inteiras que participam deste empreendimento. Para maiores informações, veja: www.w3.org.
XML
Sigla para Extensible Markup Language. Uma codificação baseada em texto que permite a codificação estruturada de textos ou dados em formato legível por humanos ou por máquinas. É a base técnica tanto para o TEI quanto para o EpiDoc, e é um padrão mantido pelo World-wide Web Consortium. Veja www.w3.org/XML para as especificações e para uma descrição mais completa.
XSLT
Sigla para Extensible Stylesheet Language Transformations. XSLT é uma linguagem que pode converter documentos em XML paraoutro tipo de XML ou para outros formatos, como o formato HTML utilizado para websites, o formato de importação para um banco de dados ou o Open Document Format que fica por trás de um documento de processamento de texto. As Folhas de Estilo EpiDoc são um exemplo de XSLT utilizado para transformar o XML do EpiDoc para formatos comuns de visualização. Uma intrsodução útil para o XSLT é fornecida pelas W3 Schools.

Responsabilidade por esta seção

  1. Gabriel Bodard, autor
  2. Laura Löser, autor
  3. Tom Elliott, autor
  4. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Apêndice: Glossário

2024-03-05

Codificação
Codificação, neste contexto, significa a conversão de informação legível por humanos para informação legível por máquina como, por exemplo, no formato XML.
Crosswalk, crosswalking

Um termo geral que descreve a transferência de dados de um formato de schema de codificação ou de banco de dados para outro. Em termos EpiDoc, isto geralmente se refere à transformação dinâmica das distinções semânticas de edições epigráficas e papirológicas entre o XML EpiDoc e um ou mais banco de dados de texto ou registros de catálogos. Estas "crosswalks" podem acontecer em qualquer direção, e, alguns casos em ambas direções são reversíveis sem perda de informação. Crosswalks importantes executadas pela comunidade EpiDoc incluem: a conversão de IRT do EpiDoc para o formato de banco de dados de EDH; a migração de conteúdo doDuke Databank, HGV e APIS para EpiDoc como parte do projeto Papyri.info (o HGV-para-EpiDoc é bidirecional e sem perda); a atual conversão dos bancos de dados constituintes do EAGLE para XML EpiDoc como parte do projeto EAGLE Europeana.

EpiDoc Schema
Um conjunto de regras estruturado que diz a um processador ou editor de XML quais elementos, atributos ou outro conteúdo estão disponíveis num arquivo EpiDoc, e como estes devem estar organizados. Documentação e maiores informações são encontrados na página Schema no EpiDoc Wiki.
Folhas de Estilo de Exemplo EpiDoc
Código de software, escrito em linguagem Extensible Stylesheet (XSL ou XSLT), com a intenção de ser utilizado para transformar aquivos XML EpiDoc em outros formatos (principalmente em texto e HTML), utilizando uma gama de convenções tipográficas padrão (como Leiden). Documentação e maiores informações podem ser encontradas na página Folhas de Estilo no EpiDoc Wiki.
Leiden, Convenções Leiden
Um conjunto de normas para a codificação de textos clássicos, epigráficos e papirológicos, usando símbolos simples, arbitrários e claros para representar observações e intervenções editoriais, como '[' e ']' para texto perdido (restaurado ou uma lacuna). Existem várias pequenas variações do Leiden atualmente em uso (Krummrey-Panciera e PETRAE talvez sejam os mais importantes). Um bom resumo do Leiden pode ser encontrado em en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ is é um sistema de marcação baseado fortemente no Leiden mas incluindo novos sinais e combinações para marcação complexa de aparato, como, por exemplo, aquele feito para o ambiente de edição "tags-free" do Editor Papirológico. A descrição e documentação completa do Leiden+ se encontra em papyri.info/editor/help.
Marcação
Linguagem de marcação é uma forma de codificar um conteúdo de texto de modo a habilitar modos diferentes de representação e, por exemplo, extrair informação que será coletada por índices ou mecanismos de busca (veja. Codificação).
"Markup" é algumas vezes utilizado como abreviação para a Lista de Markup, uma lista de emails para a discussão do EpiDoc e outros assuntos referentes à marcação de textos antigos.
Morpheus
O serviço de análise morfológica Morpheus é uma ferramenta inicialmente desenvolvida pelo Perseus, com versões dele em uso pelo Papyri.info e pelo TLG para a lematização de seus textos gregos. A versão Perseus desta ferramenta também serve para a lematização do latim e do árabe. (Maiores informações em Bamboo e Perseus.)
Papyrological Navigator (PN)
A interface de navegação e busca da plataforma Papyri.info, que incorpora DDbDP, HGV, APIS e outros bancos de dados papirológicos.
Papyrological editor (PE)
A ferramenta de fluxo editorial, de gerenciamento e de edição da plataforma Papyri.info que permite a contribuição e as emendas da comunidade ao corpus de documentação papirológica, notadamente através da interface de edição tags-free do Leiden+.
Perseus
O Projeto de Biblioteca Digital Perseus estuda a progressão das bibliotecas, de físicas para digitais, e oferece um número cada vez maior de textos. Buscadores e uma quantidade de ferramentas podem ser utilizados diretamente no website enquanto se lê, como a ferramenta dicionário Morpheus para textos em grego e latim.
Pleiades
Um dicionário geográfico de locais e nomes de locais do mundo antigo, aumentando o projeto que produziu o Atlas Barrington do Mundo Grego e Romano. O Pleiades designa identificadores únicos para cada lugar, habilitando uma rede de Linked Data como a que tem a curadoria do projeto Pelagios. Pleiades pode ser encontrado no endereço pleiades.stoa.org.
TEI
Sigla para Text Encoding Initiative (Iniciativa de Codificação de Texto). Normas e ferramentas para a codificação de textos literários e históricos em XML. Este é o formato em que o EpiDoc se baseia. Normas TEI atualizadas podem ser encontgradas online no endereço http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
O World Wide Web Consortium (Consórcio da Rede Mundial - W3C) é uma comunidade internacional que desenvolve padrões para serem utilizados na Internet. O público pode participar, mas também existe uma equipe trabalhando em tempo integral e organizações inteiras que participam deste empreendimento. Para maiores informações, veja: www.w3.org.
XML
Sigla para Extensible Markup Language. Uma codificação baseada em texto que permite a codificação estruturada de textos ou dados em formato legível por humanos ou por máquinas. É a base técnica tanto para o TEI quanto para o EpiDoc, e é um padrão mantido pelo World-wide Web Consortium. Veja www.w3.org/XML para as especificações e para uma descrição mais completa.
XSLT
Sigla para Extensible Stylesheet Language Transformations. XSLT é uma linguagem que pode converter documentos em XML paraoutro tipo de XML ou para outros formatos, como o formato HTML utilizado para websites, o formato de importação para um banco de dados ou o Open Document Format que fica por trás de um documento de processamento de texto. As Folhas de Estilo EpiDoc são um exemplo de XSLT utilizado para transformar o XML do EpiDoc para formatos comuns de visualização. Uma intrsodução útil para o XSLT é fornecida pelas W3 Schools.

Responsabilidade por esta seção

  1. Gabriel Bodard, autor
  2. Laura Löser, autor
  3. Tom Elliott, autor
  4. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-glossary.html b/gl/dev/app-glossary.html index c9393a029..3f4001ac8 100644 --- a/gl/dev/app-glossary.html +++ b/gl/dev/app-glossary.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Glossary

2023-04-27

Crosswalk, crosswalking
A general term for moving data from the format of one encoding scheme or database to another. In EpiDoc terms, it often refers to the dynamic transformation of the semantic distinctions of epigraphic and papyrological editions between EpiDoc XML and one or more database of texts or catalogue records. These "crosswalks" may take place in either direction, or in some cases in both directions and reversible without loss of information. Prominent crosswalks performed by the EpiDoc community include: the conversion of IRT from EpiDoc to the database format of EDH; the migration of the Duke Databank, HGV and APIS content to EpiDoc as part of the Papyri.info project (the HGV-to-EpiDoc is lossless and bidirectional); the current conversion of the EAGLE constituent databases into EpiDoc XML as part of the EAGLE Europeana project.
Encoding
Encoding in this context means the conversion of human-readable information into machine-readable information, e.g. in the form of XML.
EpiDoc Example Stylesheets
Software code, written in the Extensible Stylesheet Language (XSL or XSLT), and intended for use in transforming EpiDoc XML files into other formats (chiefly text and HTML) using a range of standard typographical conventions (e.g., Leiden). Documentation and further information are to be found on the Stylesheets page in the EpiDoc Wiki.
EpiDoc Schema
A formally structured set of rules that tells an XML editor or processor what elements, attributes and other content are available in an EpiDoc file and how these are to be structured. Documentation and further information are to be found on the Schema page in the EpiDoc Wiki.
Leiden, Leiden Conventions
A set of rules for the encoding of classical epigraphic and papyrological texts using simple, arbitrary and unambiguous symbols to represent editorial observations and interventions, e.g. '[' and ']' for lost text (restored or lacuna). There are several minor variations on Leiden now in use (Krummrey-Panciera and PETRAE perhaps prominent among them). A good summary of Leiden can be found at en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ is a system of text markup, based very closely on Leiden but including new signs and combinations for complex apparatus markup, for example, devised for the Papyrological Editor's "tags-free" editing environment. Full description and documentation of Leiden+ is at papyri.info/editor/help.
Markup
Markup language in a way to encode a text's contents in order to enable different ways of representation and e.g. to extract information to be collected for indexes, or search tools (cf. Encoding).
"Markup" is sometimes also used as shorthand for the Markup List, an email list for the discussion of EpiDoc and other ancient text markup matters.
Morpheus
The Morpheus morphological analysis service is a tool originally developed by Perseus, versions of which are in use by Papyri.info and the TLG for lemmatizing their Greek texts. The Perseus version of the tool also caters for Latin and Arabic lemmatization. (More information at Bamboo and Perseus.)
Papyrological Navigator (PN)
The search and browse interface of the Papyri.info platform, which incorporates the DDbDP, HGV, APIS and other papyrological databases.
Papyrological editor (PE)
The text-editing, management and editorial workflow tool of the Papyri.info platform, allowing community contribution to and emendation of the corpus of documentary papyrology, notably via the tags-free Leiden+ editing interface.
Perseus
The Perseus Digital Library Project studies the progression from physical to digital libraries and offers an increasing number of texts. Searches and a number of tools can be used directly on the website while reading, e.g. the Morpheus dictionary tool for Greek and Latin texts.
Pleiades
A gazetteer of places and place names from the ancient world, building on the project that produced the Barrington Atlas of the Greek and Roman World. Pleiades assigns unique identifiers to all places, enabling a web of Linked Data such as that curated by the Pelagios project. Pleiades can be found at pleiades.stoa.org.
TEI
Text Encoding Initiative. Guidelines and tools for the encoding of literary and historical texts in XML. It is the format on which EpiDoc is based. The latest TEI Guidelines can be found online at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
The World Wide Web Consortium (W3C) is an international community developing standards to be used across the Internet. The public can take part, but there is also full-time staff and entire organizations that are members of the endeavour. For further information, see: www.w3.org.
XML
Extensible Markup Language. A text-based encoding format that allows the structured encoding of text or data in human- and machine-readable format. It is the technical basis of both TEI and EpiDoc, and is a standard maintained by the World-wide Web Consortium. See www.w3.org/XML for the spec and further description.
XSLT
Extensible Stylesheet Language Transformations. XSLT is a language that can convert XML documents into either different XML or other forms, e.g. the HTML format used for websites, the import format for a database, or the Open Document Format behind a word-processing document. The EpiDoc Stylesheets are an example of XSLT used to transform EpiDoc XML to common display formats. A useful introduction to XSLT is offered by W3 Schools.

Responsibility for this section

  1. Gabriel Bodard, author
  2. Laura Löser, author
  3. Tom Elliott, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Glossary

2024-03-05

Crosswalk, crosswalking
A general term for moving data from the format of one encoding scheme or database to another. In EpiDoc terms, it often refers to the dynamic transformation of the semantic distinctions of epigraphic and papyrological editions between EpiDoc XML and one or more database of texts or catalogue records. These "crosswalks" may take place in either direction, or in some cases in both directions and reversible without loss of information. Prominent crosswalks performed by the EpiDoc community include: the conversion of IRT from EpiDoc to the database format of EDH; the migration of the Duke Databank, HGV and APIS content to EpiDoc as part of the Papyri.info project (the HGV-to-EpiDoc is lossless and bidirectional); the current conversion of the EAGLE constituent databases into EpiDoc XML as part of the EAGLE Europeana project.
Encoding
Encoding in this context means the conversion of human-readable information into machine-readable information, e.g. in the form of XML.
EpiDoc Example Stylesheets
Software code, written in the Extensible Stylesheet Language (XSL or XSLT), and intended for use in transforming EpiDoc XML files into other formats (chiefly text and HTML) using a range of standard typographical conventions (e.g., Leiden). Documentation and further information are to be found on the Stylesheets page in the EpiDoc Wiki.
EpiDoc Schema
A formally structured set of rules that tells an XML editor or processor what elements, attributes and other content are available in an EpiDoc file and how these are to be structured. Documentation and further information are to be found on the Schema page in the EpiDoc Wiki.
Leiden, Leiden Conventions
A set of rules for the encoding of classical epigraphic and papyrological texts using simple, arbitrary and unambiguous symbols to represent editorial observations and interventions, e.g. '[' and ']' for lost text (restored or lacuna). There are several minor variations on Leiden now in use (Krummrey-Panciera and PETRAE perhaps prominent among them). A good summary of Leiden can be found at en.wikipedia.org/wiki/Leiden_Conventions
Leiden+ (Leiden-plus)
Leiden+ is a system of text markup, based very closely on Leiden but including new signs and combinations for complex apparatus markup, for example, devised for the Papyrological Editor's "tags-free" editing environment. Full description and documentation of Leiden+ is at papyri.info/editor/help.
Markup
Markup language in a way to encode a text's contents in order to enable different ways of representation and e.g. to extract information to be collected for indexes, or search tools (cf. Encoding).
"Markup" is sometimes also used as shorthand for the Markup List, an email list for the discussion of EpiDoc and other ancient text markup matters.
Morpheus
The Morpheus morphological analysis service is a tool originally developed by Perseus, versions of which are in use by Papyri.info and the TLG for lemmatizing their Greek texts. The Perseus version of the tool also caters for Latin and Arabic lemmatization. (More information at Bamboo and Perseus.)
Papyrological Navigator (PN)
The search and browse interface of the Papyri.info platform, which incorporates the DDbDP, HGV, APIS and other papyrological databases.
Papyrological editor (PE)
The text-editing, management and editorial workflow tool of the Papyri.info platform, allowing community contribution to and emendation of the corpus of documentary papyrology, notably via the tags-free Leiden+ editing interface.
Perseus
The Perseus Digital Library Project studies the progression from physical to digital libraries and offers an increasing number of texts. Searches and a number of tools can be used directly on the website while reading, e.g. the Morpheus dictionary tool for Greek and Latin texts.
Pleiades
A gazetteer of places and place names from the ancient world, building on the project that produced the Barrington Atlas of the Greek and Roman World. Pleiades assigns unique identifiers to all places, enabling a web of Linked Data such as that curated by the Pelagios project. Pleiades can be found at pleiades.stoa.org.
TEI
Text Encoding Initiative. Guidelines and tools for the encoding of literary and historical texts in XML. It is the format on which EpiDoc is based. The latest TEI Guidelines can be found online at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index-toc.html.
World Wide Web Consortium
The World Wide Web Consortium (W3C) is an international community developing standards to be used across the Internet. The public can take part, but there is also full-time staff and entire organizations that are members of the endeavour. For further information, see: www.w3.org.
XML
Extensible Markup Language. A text-based encoding format that allows the structured encoding of text or data in human- and machine-readable format. It is the technical basis of both TEI and EpiDoc, and is a standard maintained by the World-wide Web Consortium. See www.w3.org/XML for the spec and further description.
XSLT
Extensible Stylesheet Language Transformations. XSLT is a language that can convert XML documents into either different XML or other forms, e.g. the HTML format used for websites, the import format for a database, or the Open Document Format behind a word-processing document. The EpiDoc Stylesheets are an example of XSLT used to transform EpiDoc XML to common display formats. A useful introduction to XSLT is offered by W3 Schools.

Responsibility for this section

  1. Gabriel Bodard, author
  2. Laura Löser, author
  3. Tom Elliott, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-papy-apis.html b/gl/dev/app-papy-apis.html index 1034df1a0..c7c8a07b4 100644 --- a/gl/dev/app-papy-apis.html +++ b/gl/dev/app-papy-apis.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc supporting data with APIS

2023-04-27

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc supporting data with APIS

2024-03-05

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-papy-ddbdp.html b/gl/dev/app-papy-ddbdp.html index 04f8967f7..c6ba7c4d9 100644 --- a/gl/dev/app-papy-ddbdp.html +++ b/gl/dev/app-papy-ddbdp.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc with DDbDP

2023-04-27

LeidenDescriptionEpiDoc page(s)
α(βγ)Modern expansion of an abbreviationAbbreviation fully expanded
[αβγ]Text lost, restored by the editorRestored text
[........]Up to 8 characters lost, cannot be restoredLost characters, quantity known
[ - ca.4 - ]Approximate number of characters lost, cannot be restoredLost characters, quantity approximate
[ - ca.9 - ]More than 8 characters lost, cannot be restored; note: DDbDP practice assumes that assertion of losses greater than 8 characters is imprecise, whether the editor writes [..........] or [- ca.10 - ]Lost characters, quantity known and Lost characters, quantity approximate
[ - ca.? - ]Unknown number of characters lost, cannot be restored
<αβγ>Characters erroneously omitted by the scribe, added by modern editorSupplement of omitted characters
\αβγ/Text added above the line in antiquityText added by ancient hand
/αβγ\Text added below the line in antiquityText added by ancient hand
{αβγ}Superfluous letters removed by the editorSuperfluous text
α̣β̣γ̣Underdotted by editor to indicate characters ambiguous outside of context, characters damaged, illegible or otherwise uncertainAmbiguous characters (Leiden underdot)
αβγCharacters seen by a previous editor now lost, or attested in an ancient duplicateText visible to previous editor and Text restored from parallel copy
〚αβγ〛Characters deleted in antiquityErased but legible text and Erased and lost
vac.Space left emptyVacat measured in charactrers
- ca.? -Traces Illegible / vestigesIllegible characters, quantity unknown
……..Up to 8 characters illegibleIllegible characters, quantity known
- ca.9 -More than 8 characters illegible; note: DDbDP practice assumes that assertion of illegible characters of length greater than 8 is imprecise.Illegible characters, quantity known and Illegible characters, quantity approximate
- ca.? -Unknown number of characters illegibleIllegible characters, quantity unknown
-- -- -- -- -- -- --Break in papyrus/ostracon/tablet, resulting in unknown number of lost linesLost lines, quantity unknown and Lines possibly lost / text possibly breaks

Table above taken from DDbDP Conventions. See also: Leiden+ Help Page.

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc with DDbDP

2024-03-05

LeidenDescriptionEpiDoc page(s)
α(βγ)Modern expansion of an abbreviationAbbreviation fully expanded
[αβγ]Text lost, restored by the editorRestored text
[........]Up to 8 characters lost, cannot be restoredLost characters, quantity known
[ - ca.4 - ]Approximate number of characters lost, cannot be restoredLost characters, quantity approximate
[ - ca.9 - ]More than 8 characters lost, cannot be restored; note: DDbDP practice assumes that assertion of losses greater than 8 characters is imprecise, whether the editor writes [..........] or [- ca.10 - ]Lost characters, quantity known and Lost characters, quantity approximate
[ - ca.? - ]Unknown number of characters lost, cannot be restored
<αβγ>Characters erroneously omitted by the scribe, added by modern editorSupplement of omitted characters
\αβγ/Text added above the line in antiquityText added by ancient hand
/αβγ\Text added below the line in antiquityText added by ancient hand
{αβγ}Superfluous letters removed by the editorSuperfluous text
α̣β̣γ̣Underdotted by editor to indicate characters ambiguous outside of context, characters damaged, illegible or otherwise uncertainAmbiguous characters (Leiden underdot)
αβγCharacters seen by a previous editor now lost, or attested in an ancient duplicateText visible to previous editor and Text restored from parallel copy
〚αβγ〛Characters deleted in antiquityErased but legible text and Erased and lost
vac.Space left emptyVacat measured in charactrers
- ca.? -Traces Illegible / vestigesIllegible characters, quantity unknown
……..Up to 8 characters illegibleIllegible characters, quantity known
- ca.9 -More than 8 characters illegible; note: DDbDP practice assumes that assertion of illegible characters of length greater than 8 is imprecise.Illegible characters, quantity known and Illegible characters, quantity approximate
- ca.? -Unknown number of characters illegibleIllegible characters, quantity unknown
-- -- -- -- -- -- --Break in papyrus/ostracon/tablet, resulting in unknown number of lost linesLost lines, quantity unknown and Lines possibly lost / text possibly breaks

Table above taken from DDbDP Conventions. See also: Leiden+ Help Page.

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/app-papy-hgv.html b/gl/dev/app-papy-hgv.html index 957ee1d99..72c062086 100644 --- a/gl/dev/app-papy-hgv.html +++ b/gl/dev/app-papy-hgv.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Appendix: Aligning EpiDoc supporting data with HGV

2023-04-27

tba

HGV fieldTranslationEpiDoc recommendations
PublikationSource publicationBibliographic references
DatierungDateDate of origin
OrtPlace of origin (or finding)Place of origin or Context of discovery (findspot)
OriginaltitelTitle in source publicationTitle and publication information
MaterialMaterialDescription and dimensions of monument or object
AbbildungPublished illustrationsBibliographic references or Figures or facsimile
BemerkungenCommentaryCommentary (line-by-line or introductory)
InhaltSubjectType of text, general keywords
TM_NrTrismegistos numberTitle and publication information

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Appendix: Aligning EpiDoc supporting data with HGV

2024-03-05

tba

HGV fieldTranslationEpiDoc recommendations
PublikationSource publicationBibliographic references
DatierungDateDate of origin
OrtPlace of origin (or finding)Place of origin or Context of discovery (findspot)
OriginaltitelTitle in source publicationTitle and publication information
MaterialMaterialDescription and dimensions of monument or object
AbbildungPublished illustrationsBibliographic references or Figures or facsimile
BemerkungenCommentaryCommentary (line-by-line or introductory)
InhaltSubjectType of text, general keywords
TM_NrTrismegistos numberTitle and publication information

Responsibility for this section

  1. Gabriel Bodard, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/encode-text-pt-br.html b/gl/dev/encode-text-pt-br.html index ac88be750..281135a9f 100644 --- a/gl/dev/encode-text-pt-br.html +++ b/gl/dev/encode-text-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Transcrevendo o Texto

2023-04-27

Explique e discuta a estrutura geral de transcrição, as formas alterenativasde se fazer isto. Só então desça ao nível dos elementos.

See also:

Responsabilidade por esta seção

  1. xx, author
  2. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Transcrevendo o Texto

2024-03-05

Explique e discuta a estrutura geral de transcrição, as formas alterenativasde se fazer isto. Só então desça ao nível dos elementos.

See also:

Responsabilidade por esta seção

  1. xx, author
  2. Assunção Medeiros, traduzido para o Português por

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/encode-text.html b/gl/dev/encode-text.html index 16c59c06b..78e81c586 100644 --- a/gl/dev/encode-text.html +++ b/gl/dev/encode-text.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Transcribing the Text

2023-04-27

Explain and discuss overall transcription structure, alternate ways of doing this. Then go down to the element level

See also:

Responsibility for this section

  1. xx, author

EpiDoc version: post-9.5

Date: 2023-04-27

\ No newline at end of file +

Transcribing the Text

2024-03-05

Explain and discuss overall transcription structure, alternate ways of doing this. Then go down to the element level

See also:

Responsibility for this section

  1. xx, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/idx-datesage.html b/gl/dev/idx-datesage.html index 0b94714d1..fc80725f8 100644 --- a/gl/dev/idx-datesage.html +++ b/gl/dev/idx-datesage.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Dates, dating formulae, ages

2023-04-27

Recording expressions of dates and durations in the transcribed text.

  • TEI definition: date ; EpiDoc-specific +

    Dates, dating formulae, ages

    2024-03-05

    Recording expressions of dates and durations in the transcribed text.

    • TEI definition: date ; EpiDoc-specific customization: date
    • TEI definition: rs ; EpiDoc-specific customization: rs
    • TEI definition: calendar ; EpiDoc-specific - customization: calendar

    Names of months, days of the week, or various other periods of time in the text, may be tagged as a reference string (rs) for purposes of indexing or other processing, as in the example below:

    ἔτι καὶ μηνεὶ <rs type="month"
     nymRef="months.xml#Ξανθικός">
    Ξανθικῷ</rs>

    Explicit dates that appear in the text (whether or not they can be parsed into Julian years) may also be tagged using the date element.

    ἐτελεύτισεν <date>μινὶ Παυνὶ ἑβδόμι</date>
    <calendar xml:id="creationOfWorld">
     <p>"Since the creation of the world"</p>
    </calendar>
    <!-- -->
    <date when="1382-06-28"
     when-custom="6890-06-20datingMethod="#creationOfWorld">
    μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
    </date>

    This example encodes the Roman consular date A.D. 154:

    <date from-custom="0154-01-01"
     to-custom="0154-12-31datingMethod="#juliantype="consulship">

     <persName type="imperialrole="consul"
      nymRef="#Commodus">
    Commodo</persName>
     <w lemma="et">et</w>
     <persName type="attestedrole="consul"
      nymRef="#Lateranus">
    Laterano</persName>
     <w lemma="consul">
      <expan>co<ex>n</ex>s</expan>
      <expan>
       <ex>ulibus</ex>
      </expan>
     </w>
    </date>
    <!-- ... Commodo et Laterano co(n)s(ulibus) -->
    (RIB: 452)

    Durations

    From time to time, it is desirable to mark-up durations of time. This is accomplished with the date element and the dur attribute. Rules for encoding dur values are codified in the W3C Recommendation on Datatypes.

    For the sake of consistency, the following optional typevalues are recommended for specifying the type of duration being marked up.

    • age
    • age-at-death
    • office-span
    • military-service-span
    • marriage-span
    Age (of person possibly still alive)
    ἧι ἐν μάχηι συνηγωνίσατο Αἰσχύλος ὁ ποιητὴς ἐτῶν ὢν
    <date rend="acrophonictype="age"
     dur="P35Y">
    ΔΔΔ𐅃</date>
    Note: Digital Marmor Parium, ll. 63-4.
    auguri co(n)s(uli) de[s(ignato)] / <date type="agedur="P14Y">an(nos) nat(o) XIIII</date> prin[c(ipi)] / [iuventutis]
    (EDH: HD037387)
    [honorato <date type="agedur="P18Y">ann(orum) XVIII</date> praef(ecto)]
    (EDH: HD030409)
    Age at death (i.e. completed life-span)
    biuerunt <date type="agedur="P70Y9M">annos plus minus septuaginta menses IX</date>
    (IRT: 844)
    uixit <date type="agedur="P3Y6M14D">annos III menses VI dies XIIII</date>
    (IRT: 835)
    v(ixit) <date type="life-spandur="P20Y">an(nos) <num atLeast="20">XX</num>
    </date>
    (RIB: 960)
    Office span
    βασιεύοντος Ἀθηνῶν Αἰσχύλου, <date type="office-spandur="P21Y">ἔτους εἰκοστοῦ καὶ ἑνός</date>
    Note: Digital Marmor Parium
    Military service span
    <date type="military-service-span"
     dur="P13Y">
    stip(endiorum) <num value="13">XIII</num>
    </date>
    (RIB: 485)
    Marriage span
    <date type="marriage-spandur="P30Y">a(nno) <num value="30">XXX</num>
    </date>
    (RIB: 295)

    Responsibility for this section

    1. Simona Stoyanova, author
    2. Gabriel Bodard, author
    3. Scott Vanderbilt, author

    EpiDoc version: post-9.5

    Date: 2023-04-27

    \ No newline at end of file + customization: calendar

Names of months, days of the week, or various other periods of time in the text, may be tagged as a reference string (rs) for purposes of indexing or other processing, as in the example below:

ἔτι καὶ μηνεὶ <rs type="month"
 nymRef="months.xml#Ξανθικός">
Ξανθικῷ</rs>

Explicit dates that appear in the text (whether or not they can be parsed into Julian years) may also be tagged using the date element.

ἐτελεύτισεν <date>μινὶ Παυνὶ ἑβδόμι</date>
<calendar xml:id="creationOfWorld">
 <p>"Since the creation of the world"</p>
</calendar>
<!-- -->
<date when="1382-06-28"
 when-custom="6890-06-20datingMethod="#creationOfWorld">
μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
</date>

This example encodes the Roman consular date A.D. 154:

<date from-custom="0154-01-01"
 to-custom="0154-12-31datingMethod="#juliantype="consulship">

 <persName type="imperialrole="consul"
  nymRef="#Commodus">
Commodo</persName>
 <w lemma="et">et</w>
 <persName type="attestedrole="consul"
  nymRef="#Lateranus">
Laterano</persName>
 <w lemma="consul">
  <expan>co<ex>n</ex>s</expan>
  <expan>
   <ex>ulibus</ex>
  </expan>
 </w>
</date>
<!-- ... Commodo et Laterano co(n)s(ulibus) -->
(RIB: 452)

Durations

From time to time, it is desirable to mark-up durations of time. This is accomplished with the date element and the dur attribute. Rules for encoding dur values are codified in the W3C Recommendation on Datatypes.

For the sake of consistency, the following optional typevalues are recommended for specifying the type of duration being marked up.

  • age
  • age-at-death
  • office-span
  • military-service-span
  • marriage-span
Age (of person possibly still alive)
ἧι ἐν μάχηι συνηγωνίσατο Αἰσχύλος ὁ ποιητὴς ἐτῶν ὢν
<date rend="acrophonictype="age"
 dur="P35Y">
ΔΔΔ𐅃</date>
Note: Digital Marmor Parium, ll. 63-4.
auguri co(n)s(uli) de[s(ignato)] / <date type="agedur="P14Y">an(nos) nat(o) XIIII</date> prin[c(ipi)] / [iuventutis]
(EDH: HD037387)
[honorato <date type="agedur="P18Y">ann(orum) XVIII</date> praef(ecto)]
(EDH: HD030409)
Age at death (i.e. completed life-span)
biuerunt <date type="agedur="P70Y9M">annos plus minus septuaginta menses IX</date>
(IRT: 844)
uixit <date type="agedur="P3Y6M14D">annos III menses VI dies XIIII</date>
(IRT: 835)
v(ixit) <date type="life-spandur="P20Y">an(nos) <num atLeast="20">XX</num>
</date>
(RIB: 960)
Office span
βασιεύοντος Ἀθηνῶν Αἰσχύλου, <date type="office-spandur="P21Y">ἔτους εἰκοστοῦ καὶ ἑνός</date>
Note: Digital Marmor Parium
Military service span
<date type="military-service-span"
 dur="P13Y">
stip(endiorum) <num value="13">XIII</num>
</date>
(RIB: 485)
Marriage span
<date type="marriage-spandur="P30Y">a(nno) <num value="30">XXX</num>
</date>
(RIB: 295)

Responsibility for this section

  1. Simona Stoyanova, author
  2. Gabriel Bodard, author
  3. Scott Vanderbilt, author

EpiDoc version: post-9.5

Date: 2024-03-05

\ No newline at end of file diff --git a/gl/dev/idx-events.html b/gl/dev/idx-events.html index 0979a264b..42649a537 100644 --- a/gl/dev/idx-events.html +++ b/gl/dev/idx-events.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

Events

2023-04-27

A list of historical events (battles, coronations, conversions, marriages, etc.)

  • TEI definition: listEvent ; EpiDoc-specific +

    Events

    2024-03-05

    A list of historical events (battles, coronations, conversions, marriages, etc.)

    • TEI definition: listEvent ; EpiDoc-specific customization: listEvent
    • TEI definition: event ; EpiDoc-specific customization: event
    • TEI definition: label ; EpiDoc-specific - customization: label

    <listEvent>
     <event xml:id="event0from="0161"
      to="0166">

      <label>Parthian War</label>
     </event>
     <event xml:id="event1when="0212">
      <label>Citizenship Edict of Caracalla</label>
     </event>
     <event xml:id="event2from="0222-03-13"
      to="0235-03-18">

      <label>Reign of Severus Alexander</label>
     </event>
     <event xml:id="event3when="0583">
      <label>Birth of the "New Theodosius"</label>
     </event>
    </listEvent>

    See also:

    Other pages describing <listEvent>:

      Other pages describing <event>:

        Other pages describing <label>:

          Responsibility for this section

          1. Gabriel Bodard, author
          2. Simona Stoyanova, author

          EpiDoc version: post-9.5

          Date: 2023-04-27

          \ No newline at end of file + customization: label

        <listEvent>
         <event xml:id="event0from="0161"
          to="0166">

          <label>Parthian War</label>
         </event>
         <event xml:id="event1when="0212">
          <label>Citizenship Edict of Caracalla</label>
         </event>
         <event xml:id="event2from="0222-03-13"
          to="0235-03-18">

          <label>Reign of Severus Alexander</label>
         </event>
         <event xml:id="event3when="0583">
          <label>Birth of the "New Theodosius"</label>
         </event>
        </listEvent>

        See also:

        Other pages describing <listEvent>:

          Other pages describing <event>:

            Other pages describing <label>:

              Responsibility for this section

              1. Gabriel Bodard, author
              2. Simona Stoyanova, author

              EpiDoc version: post-9.5

              Date: 2024-03-05

              \ No newline at end of file diff --git a/gl/dev/idx-geognames.html b/gl/dev/idx-geognames.html index de3fd3290..e4574dad6 100644 --- a/gl/dev/idx-geognames.html +++ b/gl/dev/idx-geognames.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

              Place names and geographical terms mentioned in the text

              2023-04-27

              Elements used for identifying references to places and other geographical features, groups or entities.

              Relevant element documentation (TEI):

              • TEI definition: placeName ; EpiDoc-specific +

                Place names and geographical terms mentioned in the text

                2024-03-05

                Elements used for identifying references to places and other geographical features, groups or entities.

                Relevant element documentation (TEI):

                Names of places (cities, settlements)

                If explicit annotation of named entities is desired, references to places (such as settlements, regions, nations) may be identified in the transcribed text using the placeName element.

                <placeName>Συρίας</placeName>
                (InsAph: 12.214)

                Linking to place authorities

                To

                Normalizing placename spelling

                ...

                Names of geographical features (rivers, mountains)

                ...

                Divine geographic features

                ...

                Names of ethnic groups or tribes

                As per TEI Guidelines, ethnic groups and other collectives of people, even if referred to by a geographical name, are tagged with the orgName element.

                References to places (such as settlements, regions, nations), peoples (such as ethnic groups, civic populations) and other geographical features (such as seas, mountains, rivers) can be identified in the transcribed text using the elements placeName (for mostly political entities: cities, nations, etc.) or geogName (for physical features: rivers, mountains, etc.).

                <geogName>Tamesis</geogName>

                Further information about the kind of geographical entity being named may be specified using a type attribute, for example identifying ethnic names as opposed to the place names themselves; or sub-categorising geographic names as the type of physical entity being names.

                Names may be linked using the attribute nymRef, which will contain a URL or other URI pointing to the standard form of this name (nominative singular; normalized spelling) in a local XML table or database or online onomasticon. More usefully the names may be linked using the ref attribute to a place identifier, via a pointer to a local place database or online gazetteer such as Pleiades.

                <placeName type="ethnic"
                 nymRef="placenames.xml#Cyrenensisref="mentionedplace.xml#cyrene">
                Cyrenensium</placeName>
                <geogName type="river"
                 nymRef="placenames.xml#Εὐφράτης"
                 ref="http://pleiades.stoa.org/places/912849">
                Εὐφράτης</geogName>

                Personifications of places, for example, may be tagged as both placeName and persName, so they may be indexed or searched in either category.

                <persName type="divine"
                 ref="divinities.xml#phison">

                 <geogName ref="http://pleiades.stoa.org/places/59851">Φίσων</geogName>
                </persName>

                Responsibility for this section

                1. Simona Stoyanova, author
                2. Gabriel Bodard, author

                EpiDoc version: post-9.5

                Date: 2023-04-27

                \ No newline at end of file + customization: place

              Names of places (cities, settlements)

              If explicit annotation of named entities is desired, references to places (such as settlements, regions, nations) may be identified in the transcribed text using the placeName element.

              <placeName>Συρίας</placeName>
              (InsAph: 12.214)

              Linking to place authorities

              To

              Normalizing placename spelling

              ...

              Names of geographical features (rivers, mountains)

              ...

              Divine geographic features

              ...

              Names of ethnic groups or tribes

              As per TEI Guidelines, ethnic groups and other collectives of people, even if referred to by a geographical name, are tagged with the orgName element.

              References to places (such as settlements, regions, nations), peoples (such as ethnic groups, civic populations) and other geographical features (such as seas, mountains, rivers) can be identified in the transcribed text using the elements placeName (for mostly political entities: cities, nations, etc.) or geogName (for physical features: rivers, mountains, etc.).

              <geogName>Tamesis</geogName>

              Further information about the kind of geographical entity being named may be specified using a type attribute, for example identifying ethnic names as opposed to the place names themselves; or sub-categorising geographic names as the type of physical entity being names.

              Names may be linked using the attribute nymRef, which will contain a URL or other URI pointing to the standard form of this name (nominative singular; normalized spelling) in a local XML table or database or online onomasticon. More usefully the names may be linked using the ref attribute to a place identifier, via a pointer to a local place database or online gazetteer such as Pleiades.

              <placeName type="ethnic"
               nymRef="placenames.xml#Cyrenensisref="mentionedplace.xml#cyrene">
              Cyrenensium</placeName>
              <geogName type="river"
               nymRef="placenames.xml#Εὐφράτης"
               ref="http://pleiades.stoa.org/places/912849">
              Εὐφράτης</geogName>

              Personifications of places, for example, may be tagged as both placeName and persName, so they may be indexed or searched in either category.

              <persName type="divine"
               ref="divinities.xml#phison">

               <geogName ref="http://pleiades.stoa.org/places/59851">Φίσων</geogName>
              </persName>

              Responsibility for this section

              1. Simona Stoyanova, author
              2. Gabriel Bodard, author

              EpiDoc version: post-9.5

              Date: 2024-03-05

              \ No newline at end of file diff --git a/gl/dev/idx-keywords.html b/gl/dev/idx-keywords.html index beffaf5b3..de60ed448 100644 --- a/gl/dev/idx-keywords.html +++ b/gl/dev/idx-keywords.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

              Other taxonomies, general keywords

              2023-04-27

              • TEI definition: msContents ; EpiDoc-specific +

                Other taxonomies, general keywords

                2024-03-05

                Taxonomies for Attributes Not Described By Specific Elements in the Header

                Index terms of any kind can be tagged (by default using rs, but any other semantically appropriate element may be captured for this purpose) anywhere in the document where they appear in running text: e.g. in the Greek or Latin edition, translations, commentary, or any of the descriptive fields in the header. Depending on the needs of a particular project and any internal or external taxonomies in use, such a tag might look something like:

                <provenance type="observed">
                 <p>Outside the <rs type="monuListkey="db934">Cyrene Sculpture Museum</rs>.</p>
                </provenance>

                If a taxonomy is also in use, the rs may carry ref for the purpose of normalizing to a term in this taxonomy. In the example below, normalization is to the EDR vocabulary for materials (see Rei Material GoogleDoc):

                <material ref="edr:marmor">Blue-veined white marble.</material>

                You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                General keywords

                General keywords that do not belong in any particular part of the text or supporting data of the edition may be gathered conveniently in a keywords element in textClass. These keywords will generally be used only for purposes of search, indexing, or compatibility within a larger collection, rather than appearing in the human-readable part of the edition.

                <textClass>
                 <keywords scheme="IRCyr">
                  <term>
                   <placeName type="ancientRegion"
                    key="Cyrene">
                Cyrenaica</placeName>
                  </term>
                  <term>
                   <placeName type="modernCountry"
                    ref="iso3166-1:LY">
                Libya</placeName>
                  </term>
                  <term>
                   <placeName type="modernFindspot"
                    ref="http://sws.geonames.org/81584">
                Marsa Suza</placeName>
                  </term>
                 </keywords>
                </textClass>

                Prose description of the text

                For general prose descriptions of the text, the msContents and summary may be used:

                <msContents>
                 <summary>This is the first 2 lines of P.Lond. IV 1370, a letter (entagion) from the
                   governor of Egypt, Kurrah b. Sharik, to the pagarch, Basilius, seeking remedy of
                   a deficit in the "embola," or grain tax</summary>
                </msContents>

                Responsibility for this section

                1. Gabriel Bodard, author
                2. Simona Stoyanova, author
                3. Irene Vagionakis, author
                4. Scott Vanderbilt, author

                EpiDoc version: post-9.5

                Date: 2023-04-27

                \ No newline at end of file + customization: term

              Taxonomies for Attributes Not Described By Specific Elements in the Header

              Index terms of any kind can be tagged (by default using rs, but any other semantically appropriate element may be captured for this purpose) anywhere in the document where they appear in running text: e.g. in the Greek or Latin edition, translations, commentary, or any of the descriptive fields in the header. Depending on the needs of a particular project and any internal or external taxonomies in use, such a tag might look something like:

              <provenance type="observed">
               <p>Outside the <rs type="monuListkey="db934">Cyrene Sculpture Museum</rs>.</p>
              </provenance>

              If a taxonomy is also in use, the rs may carry ref for the purpose of normalizing to a term in this taxonomy. In the example below, normalization is to the EDR vocabulary for materials (see Rei Material GoogleDoc):

              <material ref="edr:marmor">Blue-veined white marble.</material>

              You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

              General keywords

              General keywords that do not belong in any particular part of the text or supporting data of the edition may be gathered conveniently in a keywords element in textClass. These keywords will generally be used only for purposes of search, indexing, or compatibility within a larger collection, rather than appearing in the human-readable part of the edition.

              <textClass>
               <keywords scheme="IRCyr">
                <term>
                 <placeName type="ancientRegion"
                  key="Cyrene">
              Cyrenaica</placeName>
                </term>
                <term>
                 <placeName type="modernCountry"
                  ref="iso3166-1:LY">
              Libya</placeName>
                </term>
                <term>
                 <placeName type="modernFindspot"
                  ref="http://sws.geonames.org/81584">
              Marsa Suza</placeName>
                </term>
               </keywords>
              </textClass>

              Prose description of the text

              For general prose descriptions of the text, the msContents and summary may be used:

              <msContents>
               <summary>This is the first 2 lines of P.Lond. IV 1370, a letter (entagion) from the
                 governor of Egypt, Kurrah b. Sharik, to the pagarch, Basilius, seeking remedy of
                 a deficit in the "embola," or grain tax</summary>
              </msContents>

              Responsibility for this section

              1. Gabriel Bodard, author
              2. Simona Stoyanova, author
              3. Irene Vagionakis, author
              4. Scott Vanderbilt, author

              EpiDoc version: post-9.5

              Date: 2024-03-05

              \ No newline at end of file diff --git a/gl/dev/idx-nontei.html b/gl/dev/idx-nontei.html index 91e4fb51a..7521d0703 100644 --- a/gl/dev/idx-nontei.html +++ b/gl/dev/idx-nontei.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

              External Vocabularies (non TEI)

              2023-04-27

              Controlled Vocabularies and Authority Lists available online, or maintained in a non-TEI environment.

              If you want to link to a specific definition of an information as a reference, you might want to point to external vocabularies, contribute in those with new terms and align where possible. In your Epidoc file you can insert references to these Authority Lists or Controlled Vocabularies.

              The easiest way to do this is by inserting a stable uri into the element with a ref as in the following example.

              <objectType ref="http://www.eagle-network.eu/voc/objtyp/lod/29">Altar</objectType>

              The information contained in the TEI header which contains the type of monument on which the inscription is written. The uri in the ref points to an external vocabulary, which in this case is a vocabulary developed by the EAGLE consortium.

              These are the elements in which you might like to refer to an external source of information to align you definition.

              For each of these there might be many external vocabularies, which are listed below each one.

              To link to the EAGLE Vocabularies, you can browse them on Tematres and then insert the uri which is built in the following form: http://www.eagle-network.eu/voc/objtyp/lod/63

              If you already have XML files in EpiDoc and want to insert the links, you might find useful the XSLT (still under development) used by the Epigraphic Database Heidelberg, which you can find here

              Responsibility for this section

              1. Simona Stoyanova, author
              2. Pietro Liuzzo, author
              3. Gabriel Bodard, author

              EpiDoc version: post-9.5

              Date: 2023-04-27

              \ No newline at end of file +

              External Vocabularies (non TEI)

              2024-03-05

              Controlled Vocabularies and Authority Lists available online, or maintained in a non-TEI environment.

              If you want to link to a specific definition of an information as a reference, you might want to point to external vocabularies, contribute in those with new terms and align where possible. In your Epidoc file you can insert references to these Authority Lists or Controlled Vocabularies.

              The easiest way to do this is by inserting a stable uri into the element with a ref as in the following example.

              <objectType ref="http://www.eagle-network.eu/voc/objtyp/lod/29">Altar</objectType>

              The information contained in the TEI header which contains the type of monument on which the inscription is written. The uri in the ref points to an external vocabulary, which in this case is a vocabulary developed by the EAGLE consortium.

              These are the elements in which you might like to refer to an external source of information to align you definition.

              For each of these there might be many external vocabularies, which are listed below each one.

              To link to the EAGLE Vocabularies, you can browse them on Tematres and then insert the uri which is built in the following form: http://www.eagle-network.eu/voc/objtyp/lod/63

              If you already have XML files in EpiDoc and want to insert the links, you might find useful the XSLT (still under development) used by the Epigraphic Database Heidelberg, which you can find here

              Responsibility for this section

              1. Simona Stoyanova, author
              2. Pietro Liuzzo, author
              3. Gabriel Bodard, author

              EpiDoc version: post-9.5

              Date: 2024-03-05

              \ No newline at end of file diff --git a/gl/dev/idx-other.html b/gl/dev/idx-other.html index e83e593fc..4c8ebd65a 100644 --- a/gl/dev/idx-other.html +++ b/gl/dev/idx-other.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

              Other/generic authority lists

              2023-04-27

              Other vocabularies or authority lists not specially catered for by TEI person, place, event, etc. elements.

              • TEI definition: list ; EpiDoc-specific +

                Other/generic authority lists

                2024-03-05

                Other vocabularies or authority lists not specially catered for by TEI person, place, event, etc. elements.

                • TEI definition: list ; EpiDoc-specific customization: list
                • TEI definition: item ; EpiDoc-specific customization: item
                • TEI definition: term ; EpiDoc-specific customization: term
                • TEI definition: gloss ; EpiDoc-specific - customization: gloss

                <list>
                 <item xml:id="pictura">
                  <term xml:lang="ru">дипинто</term>
                  <term xml:lang="en">dipinto</term>
                 </item>
                 <item xml:id="scalpro">
                  <term xml:lang="ru">лапидарный</term>
                  <term xml:lang="en">lapidary</term>
                 </item>
                 <item xml:id="scariphatis">
                  <term xml:lang="ru">граффито</term>
                  <term xml:lang="en">graffito</term>
                 </item>
                </list>
                <!-- example from IOSPE -->
                <list>
                 <item xml:id="mon1">
                  <term xml:lang="ru">плита</term>
                  <gloss xml:lang="en">panel</gloss>
                 </item>
                 <item xml:id="mon2">
                  <term xml:lang="ru">плитка</term>
                  <gloss xml:lang="en">small panel</gloss>
                 </item>
                 <item xml:id="mon3">
                  <term xml:lang="ru">стела</term>
                  <gloss xml:lang="en">stele</gloss>
                 </item>
                </list>
                <!-- example from IOSPE -->

                See also:

                Other pages describing <list>:

                  Other pages describing <item>:

                    Other pages describing <term>:

                    Other pages describing <gloss>:

                    Responsibility for this section

                    1. Simona Stoyanova, author
                    2. Gabriel Bodard, author

                    EpiDoc version: post-9.5

                    Date: 2023-04-27

                    \ No newline at end of file + customization: gloss

                  <list>
                   <item xml:id="pictura">
                    <term xml:lang="ru">дипинто</term>
                    <term xml:lang="en">dipinto</term>
                   </item>
                   <item xml:id="scalpro">
                    <term xml:lang="ru">лапидарный</term>
                    <term xml:lang="en">lapidary</term>
                   </item>
                   <item xml:id="scariphatis">
                    <term xml:lang="ru">граффито</term>
                    <term xml:lang="en">graffito</term>
                   </item>
                  </list>
                  <!-- example from IOSPE -->
                  <list>
                   <item xml:id="mon1">
                    <term xml:lang="ru">плита</term>
                    <gloss xml:lang="en">panel</gloss>
                   </item>
                   <item xml:id="mon2">
                    <term xml:lang="ru">плитка</term>
                    <gloss xml:lang="en">small panel</gloss>
                   </item>
                   <item xml:id="mon3">
                    <term xml:lang="ru">стела</term>
                    <gloss xml:lang="en">stele</gloss>
                   </item>
                  </list>
                  <!-- example from IOSPE -->

                  See also:

                  Other pages describing <list>:

                    Other pages describing <item>:

                      Other pages describing <term>:

                      Other pages describing <gloss>:

                      Responsibility for this section

                      1. Simona Stoyanova, author
                      2. Gabriel Bodard, author

                      EpiDoc version: post-9.5

                      Date: 2024-03-05

                      \ No newline at end of file diff --git a/gl/dev/idx-persnames.html b/gl/dev/idx-persnames.html index 7b58f6af8..688e15fb9 100644 --- a/gl/dev/idx-persnames.html +++ b/gl/dev/idx-persnames.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                      Personal names and prosopographical links

                      2023-04-27

                      Tagging of names, person references, and links to prosopographical disambiguation.

                      • TEI definition: persName ; EpiDoc-specific +

                        Personal names and prosopographical links

                        2024-03-05

                        Tagging of names, person references, and links to prosopographical disambiguation.

                        • TEI definition: persName ; EpiDoc-specific customization: persName
                        • TEI definition: name ; EpiDoc-specific - customization: name

                        Personal names in the text may be tagged using the persName element.

                        <persName>Amias Olympias</persName>

                        TEI includes several elements for marking up the individual subparts of a personal name, including forename, surname, addName, genName and roleName. Most EpiDoc projects however have decided that these do not unproblematically map onto the nomenclature of Greek and Roman antiquity, or other cultures whose documentary texts are being encoded, and so the more generic element name has been used to encode the individual names within a complete person reference. The type attribute on name may be used to specify the class of name.

                        <persName type="attested">
                         <name type="praenomen">
                          <expan>
                           <abbr>Q</abbr>
                           <ex>uinto</ex>
                          </expan>
                         </name>
                         <name type="gentilicium">Flauio</name>
                         <name type="cognomen">Hiceto</name>
                        </persName>
                        (IRT: 95)

                        The recommended usage of type on persName, as applied in projects using the London style (IAph, IRT, IRCyr, IOSPE), inlcudes five values:

                        • attested
                        • Note: - stands for "Person attested locally"-- other than emperors, consuls, godsemperor
                        • Note: - stands for member of imperial family (in projects involving the Greek world outside of the Roman empire we have used "ruler" instead of emperor, as a more catch-all term)divine
                        • Note: - divinities, including both Olympian gods, angels/saints/etc., and abstract figures such as Agathe Tycheconsul
                        • Note: - (not actually used, but suitable for tagging the names of eponymous consuls, archons or priests *only* where they are used in dating formulae)other
                        <persName type="attestedref="#person138">
                         <name>Θεωδόρου</name>
                        </persName>

                        Just as the lemmata of words may be recorded to facilitate indexing or searching, names may be linked to their nominative-singular form (or similar in other languages). No lemma attribute is available on name or persName, however, so the more involved attribute nymRef should be used instead. This attribute can be used to link the instance of a name in text to a corresponding nym element that provides additional information about orthography, primary reference form (e.g., nominative singular), etc. Best practice is to develop a separate xml file in which the nym elements are encoded, usually inside a <nymList>. The following examples assume the existence of such a separate file (nametable.xml) and generally make use of the nominative form of the name as the linking value, appearing after the hash (#) character in nymRef and without hash or other prefix in the xml:id on the corresponding nym. More information on the extensive options available for describing the name and its forms inside the nym element may be found in the TEI Guidelines section "13.3.5 Names and Nyms". Note that the nymRef attribute links to information about the standard form of a name, not to the unique person to whom a name instance refers (on which see below).

                        <persName type="emperor">
                         <name nymRef="nametable.xml#Marcus"
                          type="praenomen">

                          <expan>
                           <abbr>M</abbr>
                           <ex>arco</ex>
                          </expan>
                         </name>
                         <name nymRef="nametable.xml#Aurellius"
                          type="gentilicium">
                        Aurellio</name>
                         <name nymRef="nametable.xml#Antoninus"
                          type="gentilicium">
                        Antonino</name>
                         <name nymRef="nametable.xml#Pius"
                          type="cognomen">
                        Pio</name>
                         <name nymRef="nametable.xml#Felix"
                          type="cognomen">
                        Felici</name>
                         <name nymRef="nametable.xml#Augustus"
                          type="cognomen">

                          <expan>
                           <abbr>Aug</abbr>
                           <ex>usto</ex>
                          </expan>
                         </name>
                         <name nymRef="nametable.xml#Parthicus"
                          type="cognomen">
                        Parthico</name>
                         <w lemma="magnus">maximo</w>
                         <name nymRef="nametable.xml#Britannicus"
                          type="cognomen">
                        Britanico</name>
                         <w lemma="magnus">maximo</w>
                         <name nymRef="nametable.xml#Germanicus"
                          type="cognomen">
                        Germanico</name>
                        </persName>
                        (IRT: 941)
                        <persName type="divinekey="ststephen">
                         <roleName>
                          <w lemma="ἅγιος">ἁγήου</w>
                         </roleName>
                         <name nymRef="nametable.xml#Στέφανος">Στεφάνου</name>
                        </persName>
                        <persName type="other">
                         <name nymRef="nametable.xml#Ἀνχίσης">Ἀνχίσου</name>
                        </persName>
                        (InsAph: 9.35)

                        A personal name of an attested individual, including cognomina but not "Imperator", shoud be tagged as a name. An imperial cognomen such as "Sarmaticus" should be tagged as a name. The element name cannot take part, so in the case of an incomplete name, a seg element needs to appear inside the name.

                        Where a personal name string includes a patronymic, or other references to people such as adoptive father, husband, owner/patron etc., a further persName element may be nested inside the first, such that, for example, "Apollonios son of Adrastos" is identified as one person, while his father "Adrastos" is another.

                        Individual persons may also identified by a ref attribute containing a URL or other URI pointing to an entry in a person database or online prosopography (see further Indexing and controlling persons and names).

                        <persName ref="prosopography.xml#p128">
                         <name nymRef="nametable.xml#Εὔμαχος">Εὔμαχος</name>
                         <persName ref="prosopography.xml#p129">
                          <name nymRef="nametable.xml#Ἀθηνάγορας">Ἀθηναγόρου</name>
                          <w>τοῦ</w>
                          <persName ref="prosopography.xml#p130">
                           <name nymRef="nametable.xml#Ἀθηνάγορας">Ἀθηναγόρου</name>
                           <w>τοῦ</w>
                           <persName ref="prosopography.xml#p131">
                            <name nymRef="nametable.xml#Εὔμαχος">Εὐμάχου</name>
                           </persName>
                          </persName>
                         </persName>
                         <name nymRef="nametable.xml#Διογένης">Διογένης</name>
                        </persName>
                        (InsAph: 1.4)

                        See also:

                        Other pages describing <persName>:

                        Other pages describing <name>:

                        Responsibility for this section

                        1. Simona Stoyanova, author
                        2. Gabriel Bodard, author

                        EpiDoc version: post-9.5

                        Date: 2023-04-27

                        \ No newline at end of file + customization: name

                      Personal names in the text may be tagged using the persName element.

                      <persName>Amias Olympias</persName>

                      TEI includes several elements for marking up the individual subparts of a personal name, including forename, surname, addName, genName and roleName. Most EpiDoc projects however have decided that these do not unproblematically map onto the nomenclature of Greek and Roman antiquity, or other cultures whose documentary texts are being encoded, and so the more generic element name has been used to encode the individual names within a complete person reference. The type attribute on name may be used to specify the class of name.

                      <persName type="attested">
                       <name type="praenomen">
                        <expan>
                         <abbr>Q</abbr>
                         <ex>uinto</ex>
                        </expan>
                       </name>
                       <name type="gentilicium">Flauio</name>
                       <name type="cognomen">Hiceto</name>
                      </persName>
                      (IRT: 95)

                      The recommended usage of type on persName, as applied in projects using the London style (IAph, IRT, IRCyr, IOSPE), inlcudes five values:

                      • attested
                      • Note: - stands for "Person attested locally"-- other than emperors, consuls, godsemperor
                      • Note: - stands for member of imperial family (in projects involving the Greek world outside of the Roman empire we have used "ruler" instead of emperor, as a more catch-all term)divine
                      • Note: - divinities, including both Olympian gods, angels/saints/etc., and abstract figures such as Agathe Tycheconsul
                      • Note: - (not actually used, but suitable for tagging the names of eponymous consuls, archons or priests *only* where they are used in dating formulae)other
                      <persName type="attestedref="#person138">
                       <name>Θεωδόρου</name>
                      </persName>

                      Just as the lemmata of words may be recorded to facilitate indexing or searching, names may be linked to their nominative-singular form (or similar in other languages). No lemma attribute is available on name or persName, however, so the more involved attribute nymRef should be used instead. This attribute can be used to link the instance of a name in text to a corresponding nym element that provides additional information about orthography, primary reference form (e.g., nominative singular), etc. Best practice is to develop a separate xml file in which the nym elements are encoded, usually inside a <nymList>. The following examples assume the existence of such a separate file (nametable.xml) and generally make use of the nominative form of the name as the linking value, appearing after the hash (#) character in nymRef and without hash or other prefix in the xml:id on the corresponding nym. More information on the extensive options available for describing the name and its forms inside the nym element may be found in the TEI Guidelines section "13.3.5 Names and Nyms". Note that the nymRef attribute links to information about the standard form of a name, not to the unique person to whom a name instance refers (on which see below).

                      <persName type="emperor">
                       <name nymRef="nametable.xml#Marcus"
                        type="praenomen">

                        <expan>
                         <abbr>M</abbr>
                         <ex>arco</ex>
                        </expan>
                       </name>
                       <name nymRef="nametable.xml#Aurellius"
                        type="gentilicium">
                      Aurellio</name>
                       <name nymRef="nametable.xml#Antoninus"
                        type="gentilicium">
                      Antonino</name>
                       <name nymRef="nametable.xml#Pius"
                        type="cognomen">
                      Pio</name>
                       <name nymRef="nametable.xml#Felix"
                        type="cognomen">
                      Felici</name>
                       <name nymRef="nametable.xml#Augustus"
                        type="cognomen">

                        <expan>
                         <abbr>Aug</abbr>
                         <ex>usto</ex>
                        </expan>
                       </name>
                       <name nymRef="nametable.xml#Parthicus"
                        type="cognomen">
                      Parthico</name>
                       <w lemma="magnus">maximo</w>
                       <name nymRef="nametable.xml#Britannicus"
                        type="cognomen">
                      Britanico</name>
                       <w lemma="magnus">maximo</w>
                       <name nymRef="nametable.xml#Germanicus"
                        type="cognomen">
                      Germanico</name>
                      </persName>
                      (IRT: 941)
                      <persName type="divinekey="ststephen">
                       <roleName>
                        <w lemma="ἅγιος">ἁγήου</w>
                       </roleName>
                       <name nymRef="nametable.xml#Στέφανος">Στεφάνου</name>
                      </persName>
                      <persName type="other">
                       <name nymRef="nametable.xml#Ἀνχίσης">Ἀνχίσου</name>
                      </persName>
                      (InsAph: 9.35)

                      A personal name of an attested individual, including cognomina but not "Imperator", shoud be tagged as a name. An imperial cognomen such as "Sarmaticus" should be tagged as a name. The element name cannot take part, so in the case of an incomplete name, a seg element needs to appear inside the name.

                      Where a personal name string includes a patronymic, or other references to people such as adoptive father, husband, owner/patron etc., a further persName element may be nested inside the first, such that, for example, "Apollonios son of Adrastos" is identified as one person, while his father "Adrastos" is another.

                      Individual persons may also identified by a ref attribute containing a URL or other URI pointing to an entry in a person database or online prosopography (see further Indexing and controlling persons and names).

                      <persName ref="prosopography.xml#p128">
                       <name nymRef="nametable.xml#Εὔμαχος">Εὔμαχος</name>
                       <persName ref="prosopography.xml#p129">
                        <name nymRef="nametable.xml#Ἀθηνάγορας">Ἀθηναγόρου</name>
                        <w>τοῦ</w>
                        <persName ref="prosopography.xml#p130">
                         <name nymRef="nametable.xml#Ἀθηνάγορας">Ἀθηναγόρου</name>
                         <w>τοῦ</w>
                         <persName ref="prosopography.xml#p131">
                          <name nymRef="nametable.xml#Εὔμαχος">Εὐμάχου</name>
                         </persName>
                        </persName>
                       </persName>
                       <name nymRef="nametable.xml#Διογένης">Διογένης</name>
                      </persName>
                      (InsAph: 1.4)

                      See also:

                      Other pages describing <persName>:

                      Other pages describing <name>:

                      Responsibility for this section

                      1. Simona Stoyanova, author
                      2. Gabriel Bodard, author

                      EpiDoc version: post-9.5

                      Date: 2024-03-05

                      \ No newline at end of file diff --git a/gl/dev/idx-persons.html b/gl/dev/idx-persons.html index 4798646e6..92ce16b13 100644 --- a/gl/dev/idx-persons.html +++ b/gl/dev/idx-persons.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                      Indexing and controlling persons and names

                      2023-04-27

                      • TEI definition: person ; EpiDoc-specific +

                        Indexing and controlling persons and names

                        2024-03-05

                        When person-referencess and/or individual names are tagged in the epigraphic text (see under Personal names) it may also be useful to maintain an authority of names or persons (onomasticon or prosopography), either in TEI or in an external database format.

                        <listPerson>
                         <person xml:id="person1">
                          <persName xml:lang="grc">Κόστας</persName>
                          <persName xml:lang="ru">Коста</persName>
                          <persName xml:lang="en">Kostas</persName>
                          <floruit notBefore="1451notAfter="1452">
                           <seg xml:lang="ru">1451–1452 гг.</seg>
                           <seg xml:lang="en">1451–1452 C.E.</seg>
                          </floruit>
                         </person>
                         <person xml:id="person2">
                          <persName xml:lang="grc">Θεόδωρος</persName>
                          <persName xml:lang="ru">Феодор</persName>
                          <persName xml:lang="en">Theodoros</persName>
                          <floruit notBefore="1439notAfter="1439">
                           <seg xml:lang="ru">1439 г.</seg>
                           <seg xml:lang="en">1439 C.E.</seg>
                          </floruit>
                         </person>
                        </listPerson>
                        <!-- example from IOSPE -->
                        <listNym>
                         <nym xml:id="Ἰωάννης">
                          <ab>Ἰωάννης</ab>
                         </nym>
                         <nym xml:id="Κόστα">
                          <ab>Κόστα</ab>
                         </nym>
                         <nym xml:id="Στέφανος">
                          <ab>Στέφανος</ab>
                         </nym>
                        </listNym>
                        <!-- example from IOSPE -->

                        See also:

                        Other pages describing <person>:

                          Other pages describing <listPerson>:

                            Other pages describing <persName>:

                            Other pages describing <nym>:

                              Other pages describing <listNym>:

                                Responsibility for this section

                                1. Simona Stoyanova, author
                                2. Gabriel Bodard, author

                                EpiDoc version: post-9.5

                                Date: 2023-04-27

                                \ No newline at end of file + customization: listNym

                              When person-referencess and/or individual names are tagged in the epigraphic text (see under Personal names) it may also be useful to maintain an authority of names or persons (onomasticon or prosopography), either in TEI or in an external database format.

                              <listPerson>
                               <person xml:id="person1">
                                <persName xml:lang="grc">Κόστας</persName>
                                <persName xml:lang="ru">Коста</persName>
                                <persName xml:lang="en">Kostas</persName>
                                <floruit notBefore="1451notAfter="1452">
                                 <seg xml:lang="ru">1451–1452 гг.</seg>
                                 <seg xml:lang="en">1451–1452 C.E.</seg>
                                </floruit>
                               </person>
                               <person xml:id="person2">
                                <persName xml:lang="grc">Θεόδωρος</persName>
                                <persName xml:lang="ru">Феодор</persName>
                                <persName xml:lang="en">Theodoros</persName>
                                <floruit notBefore="1439notAfter="1439">
                                 <seg xml:lang="ru">1439 г.</seg>
                                 <seg xml:lang="en">1439 C.E.</seg>
                                </floruit>
                               </person>
                              </listPerson>
                              <!-- example from IOSPE -->
                              <listNym>
                               <nym xml:id="Ἰωάννης">
                                <ab>Ἰωάννης</ab>
                               </nym>
                               <nym xml:id="Κόστα">
                                <ab>Κόστα</ab>
                               </nym>
                               <nym xml:id="Στέφανος">
                                <ab>Στέφανος</ab>
                               </nym>
                              </listNym>
                              <!-- example from IOSPE -->

                              See also:

                              Other pages describing <person>:

                                Other pages describing <listPerson>:

                                  Other pages describing <persName>:

                                  Other pages describing <nym>:

                                    Other pages describing <listNym>:

                                      Responsibility for this section

                                      1. Simona Stoyanova, author
                                      2. Gabriel Bodard, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/idx-places.html b/gl/dev/idx-places.html index 86612136c..cc113d325 100644 --- a/gl/dev/idx-places.html +++ b/gl/dev/idx-places.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Place authority lists/gazetteers

                                      2023-04-27

                                      A project that tags place and geographic names in transcribed text, or references to places in history of object, is strongly advised to link these names to an internal authority list of places, or to an external gazetteer, such as Pleiades or similar.

                                      <listPlace>
                                       <place xml:id="p001">
                                        <placeName xml:lang="ru">Белгород-Днестровский</placeName>
                                        <placeName xml:lang="en">Belgorod-Dnestrovsky</placeName>
                                        <placeName xml:lang="grc">Τύρας</placeName>
                                        <idno type="pleiades">http://pleiades.stoa.org/places/226800</idno>
                                       </place>
                                       <place xml:id="p003">
                                        <placeName xml:lang="ru">Херсон</placeName>
                                        <placeName xml:lang="en">Chersonesos</placeName>
                                        <placeName xml:lang="grc">Χερσόνησος</placeName>
                                        <idno type="pleiades">http://pleiades.stoa.org/places/226778</idno>
                                       </place>
                                      </listPlace>

                                      explanation and examples to be added

                                      These authority lists will often be linked to and from geographical terms in the text, and in the history of the object. See Place names and geographical terms mentioned in the text and Dates and locations of modern observations.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Simona Stoyanova, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/idx-socialterms.html b/gl/dev/idx-socialterms.html index 365db1068..8adde6849 100644 --- a/gl/dev/idx-socialterms.html +++ b/gl/dev/idx-socialterms.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Military, religious, socio-economic terminology

                                      2023-04-27

                                      Military terminology, titulature, religious indicators, social/political/economic vocabulary, all terms in EDH, are not often tagged in EpiDoc projects, although they can be useful if crosswalking to EAGLE is desired.

                                      One way of extracting this terminology is through the vocabulary, using the lemma attribute of the w element (see explanation under Titles and Offices).

                                      Another way could be using the rs element and the different values of the type attribute could be similar to the categories used by the EDH. A key or a ref attribute could point to an authority list (see External Authorities (non-TEI)).

                                      <rs type="military">
                                       <expan>
                                        <abbr>uet</abbr>
                                        <ex>eranus</ex>
                                       </expan>
                                      </rs>
                                      (IRT: 108)
                                      <title>
                                       <rs type="socecon">Building dedication to Tiberius for road paving</rs>
                                      </title>
                                      (IRT: 330)

                                      Responsibility for this section

                                      1. Simona Stoyanova, author
                                      2. Gabriel Bodard, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/idx-titlesoffices.html b/gl/dev/idx-titlesoffices.html index 065cbabb4..9b490f833 100644 --- a/gl/dev/idx-titlesoffices.html +++ b/gl/dev/idx-titlesoffices.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Titles, offices, political posts, honorifics, occupations

                                      2023-04-27

                                      Tagging of different types of offices, posts, and other titles in the transcribed text or elsewhere, usually for the purposes of indexing or searching the corpus.

                                      There are two broad methods for generating indices of titles, occupations and the like in an EpiDoc edition:

                                      (1) Using a defined list of lemmatized words, and drawing these from the general word list (assuming words are lemmatized in the first place). A specific indexer could pull terms such as consul, comes, beneficarius, quaestor, ἀρχών, εὐτυχὴς, σχολαστικός into themed indices of titles and the like. If words are explicitly lemmatized in the text (as in the example below, using the lemma attribute of the w element) no extra encoding is needed; alternatively the lemmata might be pulled from a list generated from the texts by a tool such as Morpheus.

                                      <w lemma="consul">
                                       <expan>
                                        <abbr>co</abbr>
                                        <ex>n</ex>
                                        <abbr>s</abbr>
                                        <ex>ul</ex>
                                       </expan>
                                      </w>

                                      (2) Another more explicit way to tag titulature in a transcribed text might be to use the rs element with a defined type attribute, to encode arbitrary categories of terms and keywords within the text, regardless of their language, spelling or expression. In this case, ideally a ref or key attribute would point to an authority list elsewhere in the project.

                                      <rs type="officialkey="archon">ἀρχόντων</rs>
                                      (InsAph: 12.644)

                                      Responsibility for this section

                                      1. Simona Stoyanova, author
                                      2. Gabriel Bodard, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/idx-wordslemmata.html b/gl/dev/idx-wordslemmata.html index 329c4f0c5..87b547011 100644 --- a/gl/dev/idx-wordslemmata.html +++ b/gl/dev/idx-wordslemmata.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Words and Lemmatization

                                      2023-04-27

                                      Tagging lexical words in the text and/or linking to lemmata for purposes of indexing or search.

                                      • TEI definition: w ; EpiDoc-specific - customization: w

                                      Explicit markup of words (tokenization) and identification of their dictionary headwords (lemmatization) are both optional. Many projects simply leave these features unmarked, or rely on automated processes in search software to detect word-breaks and link to lemmatizing tools such as Morpheus. (The Papyrological Navigator, Perseus, and the TLG all use methods similar to this.)

                                      To explicitly mark-up lexical words in a papyrological or epigraphic text, however, each word in the text should be enclosed in a w element. (For ease of processing, it is advised that inter-word spacing, punctuation and other features be left outside of this element, and if possible there should be no spaces or carriage returns within the w element.)

                                      <w>maximo</w>
                                      <w>tribunicia</w>
                                      <w>potestate</w>
                                      <num>XXIIII</num>
                                      <w>imperatori</w>
                                      (IRT: 22)

                                      To record the lemma or dictionary headword of the word in question, the simplest solution is to enter the uninflected form in a lemma attribute, which may be used, for example, to generate the entries in a lexical index to the corpus.

                                      <w lemma="ἵστημι">ἕστηκα</w>

                                      A slightly more sophisticated solution is to enter in a lemmaRef attribute a URL or other URI that points to the entry for the word in question in a database or online dictionary. This solution allows for better disambiguation of homonymous words, for example, or linking to morphological and statistical information about the word.

                                      <w lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=fero&amp;la=la">tulisti</w>

                                      Multiple lemmata

                                      If a single word tag contains more than one indexable word (e.g. "populusque" in Latin or "κἀκ" in Greek), or an incomplete word is ambiguous and might correspond to either of two or more lemmata (e.g. ΕΚΦΕΥΞ), then all lemmata that should be indexed may be included in the lemma attribute, separated by spaces:

                                      <w lemma="suus que">suisque</w>
                                      <w lemma="καὶ ἐκ">κἀκ</w>
                                      <w lemma="ἔκφευξις ἐκφεύγωpart="I">ΕΚΦΕΥΞ</w>
                                      <gap reason="lostextent="unknown"
                                       unit="character"/>

                                      Interaction with editorial markup

                                      The w element may contain further editorial tags, such as expansions of abbreviations. Wherever possible the w element should remain intact (cf. Editorial restoration: Segmented or adjacent lacunae).

                                      <w lemma="Κύριος"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=kurie&amp;la=greek">

                                       <expan>
                                        <abbr>Κ</abbr>
                                        <ex>ύρι</ex>ε</expan>
                                      </w>
                                      <w lemma="βοηθέω"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=bohqei&amp;la=greek">

                                       <expan>
                                        <abbr>β</abbr>
                                        <ex>οή</ex>
                                        <abbr>θ</abbr>
                                        <ex>ει</ex>
                                       </expan>
                                      </w>

                                      displayed in the edition as: Κ(ύρι)ε β(οή)θ(ει); or some restored text:

                                      <w lemma="σός"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=sw&amp;la=greek">

                                       <supplied reason="lost">σ</supplied>

                                      </w>

                                      displayed in the edition as: [σ]ῷ; a slighly more complicated situation could be the following, with a lemma written across two lines:

                                      <w lemma="φέρω"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=ferousa&amp;la=greek">
                                      φ<supplied reason="lost">έ
                                       <lb n="6break="no"/>ρ</supplied>ουσα
                                      </w>

                                      displayed as:
                                      φ[έ-
                                      6 ρ]ουσα

                                      It should be noticed that in all these examples the w element overlaps the other tags.

                                      Responsibility for this section

                                      1. Simona Stoyanova, author
                                      2. Gabriel Bodard, author
                                      3. Alessio Sopracasa, author
                                      4. Martina Filosa, author

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Words and Lemmatization

                                      2024-03-05

                                      Tagging lexical words in the text and/or linking to lemmata for purposes of indexing or search.

                                      • TEI definition: w ; EpiDoc-specific + customization: w

                                      Explicit markup of words (tokenization) and identification of their dictionary headwords (lemmatization) are both optional. Many projects simply leave these features unmarked, or rely on automated processes in search software to detect word-breaks and link to lemmatizing tools such as Morpheus. (The Papyrological Navigator, Perseus, and the TLG all use methods similar to this.)

                                      To explicitly mark-up lexical words in a papyrological or epigraphic text, however, each word in the text should be enclosed in a w element. (For ease of processing, it is advised that inter-word spacing, punctuation and other features be left outside of this element, and if possible there should be no spaces or carriage returns within the w element.)

                                      <w>maximo</w>
                                      <w>tribunicia</w>
                                      <w>potestate</w>
                                      <num>XXIIII</num>
                                      <w>imperatori</w>
                                      (IRT: 22)

                                      To record the lemma or dictionary headword of the word in question, the simplest solution is to enter the uninflected form in a lemma attribute, which may be used, for example, to generate the entries in a lexical index to the corpus.

                                      <w lemma="ἵστημι">ἕστηκα</w>

                                      A slightly more sophisticated solution is to enter in a lemmaRef attribute a URL or other URI that points to the entry for the word in question in a database or online dictionary. This solution allows for better disambiguation of homonymous words, for example, or linking to morphological and statistical information about the word.

                                      <w lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=fero&amp;la=la">tulisti</w>

                                      Multiple lemmata

                                      If a single word tag contains more than one indexable word (e.g. "populusque" in Latin or "κἀκ" in Greek), or an incomplete word is ambiguous and might correspond to either of two or more lemmata (e.g. ΕΚΦΕΥΞ), then all lemmata that should be indexed may be included in the lemma attribute, separated by spaces:

                                      <w lemma="suus que">suisque</w>
                                      <w lemma="καὶ ἐκ">κἀκ</w>
                                      <w lemma="ἔκφευξις ἐκφεύγωpart="I">ΕΚΦΕΥΞ</w>
                                      <gap reason="lostextent="unknown"
                                       unit="character"/>

                                      Interaction with editorial markup

                                      The w element may contain further editorial tags, such as expansions of abbreviations. Wherever possible the w element should remain intact (cf. Editorial restoration: Segmented or adjacent lacunae).

                                      <w lemma="Κύριος"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=kurie&amp;la=greek">

                                       <expan>
                                        <abbr>Κ</abbr>
                                        <ex>ύρι</ex>ε</expan>
                                      </w>
                                      <w lemma="βοηθέω"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=bohqei&amp;la=greek">

                                       <expan>
                                        <abbr>β</abbr>
                                        <ex>οή</ex>
                                        <abbr>θ</abbr>
                                        <ex>ει</ex>
                                       </expan>
                                      </w>

                                      displayed in the edition as: Κ(ύρι)ε β(οή)θ(ει); or some restored text:

                                      <w lemma="σός"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=sw&amp;la=greek">

                                       <supplied reason="lost">σ</supplied>

                                      </w>

                                      displayed in the edition as: [σ]ῷ; a slighly more complicated situation could be the following, with a lemma written across two lines:

                                      <w lemma="φέρω"
                                       lemmaRef="http://www.perseus.tufts.edu/hopper/morph?l=ferousa&amp;la=greek">
                                      φ<supplied reason="lost">έ
                                       <lb n="6break="no"/>ρ</supplied>ουσα
                                      </w>

                                      displayed as:
                                      φ[έ-
                                      6 ρ]ουσα

                                      It should be noticed that in all these examples the w element overlaps the other tags.

                                      Responsibility for this section

                                      1. Simona Stoyanova, author
                                      2. Gabriel Bodard, author
                                      3. Alessio Sopracasa, author
                                      4. Martina Filosa, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/index-body.1_div.301.html b/gl/dev/index-body.1_div.301.html index 3df4feb2e..0af83572b 100644 --- a/gl/dev/index-body.1_div.301.html +++ b/gl/dev/index-body.1_div.301.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      2023-04-27

                                      Schema tei-epidoc: Elements

                                      Schema tei-epidoc: Model classes

                                      Schema tei-epidoc: Attribute classes

                                      Schema tei-epidoc: Macros

                                      Schema tei-epidoc: Datatypes

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      2024-03-05

                                      Schema tei-epidoc: Elements

                                      Schema tei-epidoc: Model classes

                                      Schema tei-epidoc: Attribute classes

                                      Schema tei-epidoc: Macros

                                      Schema tei-epidoc: Datatypes

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/index.html b/gl/dev/index.html index 22cb426d6..ae2e60b6d 100644 --- a/gl/dev/index.html +++ b/gl/dev/index.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      EpiDoc Guidelines post-9.5

                                      2023-04-27

                                      EpiDoc Guidelines: Ancient documents in TEI XML

                                      (This page in Bulgarian | Spanish | Italian | Português)

                                      EpiDoc is an international, collaborative effort that provides guidelines and tools for encoding scholarly and educational editions of ancient documents. These pages are the EpiDoc Guidelines produced by the collaborative. In addition, the EpiDoc Website provides access to other tools and collaboration environments supported by the collaborative.

                                      EpiDoc specifies a subset of the Text Encoding Initiative's standard for the representation of texts in digital form using the Extensible Markup Language (XML), a technical standard promulgated by the World-Wide Web Consortium. It addresses not only the transcription and editorial preparation of the texts themselves, but also the history, materiality and metadata of the objects on which the texts appear.

                                      These Guidelines contain descriptions of the textual, descriptive, and other features expressed with EpiDoc, as well as the TEI elements and attributes used to encode them. The pages below provide a number of entry points into the full documentation, via a series of thematic indexes into the content of the Guidelines, rather than a single "table of contents" reflecting a (nonexistent) ordered, hierarchical document structure.

                                      Appendices

                                      Externally maintained guidelines for specialized communities:

                                      You can also download a zipped copy of the latest Guidelines from our Files section if you need to use them offline.

                                      You can consult previous versions of the Guidelines in the Archive area of the Files section.

                                      To cite the EpiDoc Guidelines, please use the following information:

                                      Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2022), EpiDoc Guidelines: Ancient documents in TEI XML (Version 9). Available: https://epidoc.stoa.org/gl/latest/.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Elli Mylonas, author
                                      3. Tom Elliott, author
                                      4. Simona Stoyanova, author
                                      5. Charlotte Tupman, author
                                      6. Irene Vagionakis, author

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc Guidelines post-9.5

                                      2024-03-05

                                      EpiDoc Guidelines: Ancient documents in TEI XML

                                      (This page in Bulgarian | Spanish | Italian | Português)

                                      EpiDoc is an international, collaborative effort that provides guidelines and tools for encoding scholarly and educational editions of ancient documents. These pages are the EpiDoc Guidelines produced by the collaborative. In addition, the EpiDoc Website provides access to other tools and collaboration environments supported by the collaborative.

                                      EpiDoc specifies a subset of the Text Encoding Initiative's standard for the representation of texts in digital form using the Extensible Markup Language (XML), a technical standard promulgated by the World-Wide Web Consortium. It addresses not only the transcription and editorial preparation of the texts themselves, but also the history, materiality and metadata of the objects on which the texts appear.

                                      These Guidelines contain descriptions of the textual, descriptive, and other features expressed with EpiDoc, as well as the TEI elements and attributes used to encode them. The pages below provide a number of entry points into the full documentation, via a series of thematic indexes into the content of the Guidelines, rather than a single "table of contents" reflecting a (nonexistent) ordered, hierarchical document structure.

                                      Appendices

                                      Externally maintained guidelines for specialized communities:

                                      You can also download a zipped copy of the latest Guidelines from our Files section if you need to use them offline.

                                      You can consult previous versions of the Guidelines in the Archive area of the Files section.

                                      To cite the EpiDoc Guidelines, please use the following information:

                                      Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2022), EpiDoc Guidelines: Ancient documents in TEI XML (Version 9). Available: https://epidoc.stoa.org/gl/latest/.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Elli Mylonas, author
                                      3. Tom Elliott, author
                                      4. Simona Stoyanova, author
                                      5. Charlotte Tupman, author
                                      6. Irene Vagionakis, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-bg.html b/gl/dev/intro-eps-bg.html index 225b325eb..37d79a26e 100644 --- a/gl/dev/intro-eps-bg.html +++ b/gl/dev/intro-eps-bg.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Деликатно въведение в маркирането с xml за епиграфи

                                      2023-04-27

                                      Концепцията зад EpiDoc събира на едно място в полза на епиграфите както традиционни, така и напълно модерни методи за редактиране и установени практики.

                                      Установени епиграфски практики

                                      През последния век епиграфите се сблъскаха с проблеми, свързани с това как да се представи невербалната информация чрез писмения текст. До края на 19 в. издателите обикновено са създавали факсимиле на текста, но това постепенно е ставало все по-слабо разпространено и издателите не демонстрирали еднаква готовност да предоставят пълни фотографски данни за всеки текст. Установените практики, които са мъчно създадени да представят липсващ текст, съкращения и т.н. са били малко или много съгласувани през 30-те г. на 20в. и в известна степен се припокриват с тези, използвани в папирусологията и палеографията. На всички епиграфи им се налага да се справят с трудностите, свързани с това да се пренесе информацията в една електронна среда - например, с това да се намери шрифт, който би позволил слагането на точки под буквите. Повечето от нас обаче вече са привикнали към тези нови ограничения.

                                      Трудността да се предадат такива условности и най-вече гръцките символи в пълноценни шрифтове и в Мрежата досега задържаше публикацията на пълни епиграфски текстове онлайн. Вместо това бяха създадени изключително богати колекции за търсене, сред които най-забележителни са следните:

                                      Виж също: Съответствия (EpiDoc Съвместимост).

                                      Всички тези разработки се определяха от развитието на съществуващите технологии, тъй като те се усъвършенстваха през 20в. Стремежът на EpiDoc бе да се възползва от нови и развити технологии за традиционните цели на епиграфиката. Много от задачите, споменати по-горе, включваха борба срещу технологичните стандарти - например в печатните публикации, за да приспособим възможно най-много от нашите нужди. През този период постепенно ставаше все по-трудно да бъдат убедени конвенционалните издатели да посрещнат нашите изисквания да бъде включена мета-текстуална информация, освен на много висока цена. В същото време очакванията към обема на информацията, която би съпътствала един текст, се увеличиха значително; също като информацията за физическите детайли, фотографската илюстрация се превърна в стандарт.

                                      През последните 15 години учените обичайно се сблъскваха с подобни изисквания да включват метаданни в текстовете в електронната им форма и се появиха средства, които да направят това все по-лесно, а резултатите - все по-ценни. Софтуерът за обработка на думи, който е известен още от 80-те г. на 20в. ни позволява да контролираме форматирането на нашите текстове, като използваме маркиране, което до сега бе незабележимо предоставено от софтуера. По-взискателните нужди на колекциите от документи с голям размер - правни документи, индустриална документация, комерсиално издаване - доведоха през 80-те до откриването на начини за включване на по-широк набор от информация и инструкции вътре в електронните текстове. В началото акцентът бе върху това да се включат инструкции за форматиране, но скоро се появиха и методи за включване на по-сложна семантична информация за структурата на документа и дори за неговото съдържание. Пример за това е маркирането на заглавие на книга именно като заглавие, а не просто то да бъде маркирано като курсив. Употребата на това по-абстрактно маркиране позволява едно разделяне на структура и представяне, така че структурата да е сравнително основна за жанра на документа, докато представянето може да се различава в зависимост от формата на публикацията. В известен смисъл тази промяна представлява завръщане към един по-ранен метод, в който авторите са се занимавали със същността на текста, а всички детайли по презентацията му се изготвяли в процеса на публикация - едно разделение, което се заличава в епохата на готовите копия.

                                      Протоколите, които бяха създадени чрез споменатите усилия, бяха унифицирани в края на 80-те години като Стандартизиран генерализиран маркиращ език (Standard Generalized Markup Language) и наскоро им бе дадена по-опростена и по-гъвкава форма за употреба в Световната мрежа като XML: Extensible Markup Language. XML сега се използва от учените в широк кръг от хуманитарни дисциплини, за да улови, представи и запази изследвания за различни по обхват цели.

                                      И така, привлекателните страни на XML за епиграфите са значителни. Например: липсващият материал може да бъде маркиран като такъв и след това представен между квадратни скоби; в същото време търсенето може да се ограничи само в това да открива текст, който не е маркиран като липсващ (и по този начин да предоставя само изрично засвидетелствани текстове). Неясните букви могат да бъдат обозначени като такива, а сетне е възможно да се вземе решение дали да бъдат представени с точка под тях или по някакъв друг начин. Думите могат да бъдат систематизирани по време на обработката, така че да бъдат създадени индекси, които да нарастват с нарастването на колекцията. Но най-важното при това положение е да се повтори Лайденската практика, а именно - да се съгласуват електронните еквиваленти на разнообразните сигли, които използваме. На първо място това е ценно дори само за да ни спестява време и усилия, но също така самата единност, без да бъде натрапвана еднаквост, е ценна на свой ред. Тя не само подпомага потребителя, както на отпечатаната страница, но освен това документите, създадени по този начин и публикувани електронно, биха могли да бъдат използвани заедно, дори когато са били подготвени поотделно.

                                      Нуждата от съгласувани стандарти не се ограничава единствено по отношение на епиграфиката. От 1967г. международен консорциум учени, занимаващи се в по-голямата си част в полето на хуманитарните науки, работят заедно за развиването и усъвършенстването на набор от указания за описване на структура и съдържание на документи. Резултатът от това начинание доведе до създаването на кодиращ език, реализиран чрез XML и описан от името на групата - TEI, Text Encoding Initiative.

                                      TEI за епиграфи: Какво е това и защо да го използваме?

                                      TEI (The Text Encoding Initiative) е опит за изследване, насочено към дефинирането на кодиращ език, който покрива нуждите на учените-хуманитаристи в най-общ смисъл. Има две основни цели, които обуславят развитието на TEI. Първата е необходимостта да се даде възможност на учените да представят материалите на своите изследвания в дигитална форма, като използват дескриптивен език, който имитира видовете аналитични термини и концепциии, познати и базови за хуманитаристиката. Втората цел е да се направи възможно учените да споделят по разбираем начин получените резултати, използвайки един познат и общ дескриптивен език.

                                      Бихме могли да мислим за кодиращия език TEI като за подражаващ на човешкия език: ядро от общи термини в центъра, обгърнато от по-малко широка лексика, включително и местна употреба, специализирана терминология и други вариации. В ядрото на TEI са общите термини и концепции, които са широко споделяни от учените в повечето дисциплини: категории като параграфи, родови текстови разделения, заглавия, списъци и т.н. По-специализирани елементи са групирани заедно според употребата им: например, елементи за детайлно кодиране на имена, елементи за представяне на особености на манускриптите, елементи за улавяне на структурата на речниците и пр. TEI умишлено е организирана в модули по този начин, така че учените, които работят в специфични дисциплини да могат да използват само модулите, които се отнасят до тяхната работа, и да пропуснат останалите. Така именно TEI може да постигне голяма широта на употреба, без да натоварва отделните учени и проекти с необходимостта да се овладява много голямо поле, значителна част от което се отнася единствено до други дисциплини. Тъкмо напротив, кодиращият език TEI може много директно да бъде насочен към специфично поле или задача и може да бъде ограничен да предоставя нещата, които са съществени за работата на конкретния проект.

                                      Също като един човешки език, TEI може да бъде използван така, че да си служи с богат и нюансиран речник, с детайлно кодиране, което описва огромно количество особености в текста, но би могъл да се използва и съвсем просто, служейки си единствено с няколко съществени понятия, които описват само най-основните данни за текста: раздели, заглавия, параграфи. Колкото по-детайлно е кодирането, толкова повече възможности има то да бъде използвано, но фактори като време, разходи, налични кадри и местни особености могат да поставят ограничения в постижимото ниво на детайлност.

                                      В допълнение към предоставянето на кодираща система, която учените могат да използват в оригиналното й състояние, TEI също така предлага начин научните проекти да дефинират собствени версии за употреба вътре в общата рамка на TEI. Те могат да използват широко познатото му ядро от термини и понятия, като по този начин си спестяват ненужната трудност да ги измислят наново. И тъкмо защото TEI предоставя една обща рамка за създаване и описване на индивидуални подходи, те могат да бъдат споделяни лесно и с реален смисъл. Като резултат от това групи от учени в конкретни дисциплини могат да артикулират специфичните цели и методи, които характеризират тяхната работа, и разликите, които ги разграничават от други, работещи в подобни сфери. Вместо взаимно неразбираеми подходи, различните проекти могат да създават резултати, чиито различия да са плод по-скоро на реално различаващи се мнения, отколкото на прости случайни несъответствия.

                                      Персонализацията EpiDoc: TEI за епиграфи

                                      В тази рамка обществото EpiDoc работи от 2000г. за създаването на персонализирана версия на насоките на TEI, за да подпомогнат специфичните нужди на епиграфите. Идеята беше създадена от Том Елиът, специалист по антична история в Университета на Северна Каролина в Чапъл Хил. Целта беше както да се използват по най-пълноценния възможен начин постиженията, които вече са направени, така и да се гарантира, че описаните текстовете са третирани по начин, съответстващ на този, който е използван за други текстове, а не различен от него. Персонализацията EpiDoc премахва неуместните елементи от основното тяло на TEI и добавя материал за специфичните видове транскрипции, анализи, описания и класификации, които са същностно важни за епиграфската работа. Резултатът е един прост език, но с големи възможности, който може да бъде използван за отбелязването на всички значими особености на надписите, а също така представя и съпътстващата информация за самия епиграфски обект.

                                      За да допълни кодиращия език EpiDoc, общността създаде също така набор от насоки за кодиране и софтуерни инструменти, както и документация, която описва как да бъде използван кодиращият език, инструментите и другите елементи от метода EpiDoc. Целта е да се установи една рамка, която е лесна за възприемане и употреба дори за учени без техническа подготовка или подкрепа. Това може би звучи невероятно, но начинанието е от същия порядък като това да се овладее знанието да се маркира стандартен епиграфски текст със съществуващата система от сигли.

                                      Обществото работи за развитието на представянето на всички установени епиграфски понятия. То разшири труда си така, че да бъде приложим към различните полета, които биха могли да се представят в една епиграфска публикация, включително:

                                      Виж още: Структура на документа.

                                      Друга област, която активно се разработва, е създаването на оперативна съвместимост. Вече е създаден софтуерен инструмент за конвертиране на текстове от нормално епиграфско маркиране в EpiDoc XML (т.нар. Chapel Hill Electronic Text Converter (CHETC)). Други сфери включват употребата на авторитетна лексика. Например, работата по проекта "Надписите от Афродизиас" е тясно обвързана с Речника на гръцките лични имена, за да осигури пълно покритие и адекватна употреба.

                                      Работата, водена от д-р Елиът, беше подемана от няколко различни учени, които работеха в тясно сътрудничество и в постоянен контакт с по-широко поле на специализация. Те очертаха опита на един вече осъществен EpiDoc проект, Vindolanda Tablets on line, и на два текущи проекта: US Epigraphy Project (USEP) (поддържан от Университетите Браун, Принстън и Рутгерс) и Inscriptions of Aphrodisias Project (InsAph) (поддържан от Arts and Humanities Research Council). Щедрата подкрепа на AHRC позволи провеждането на интензивния уъркшоп през март 2006г., където бяха установени тези насоки.

                                      За тази страница работиха:

                                      1. Шарлот Руше, автор
                                      2. Джулия Фландърс, автор
                                      3. Полина Йорданова, преведе на български език
                                      4. Том Елиът, препратки към TEI-Lite и различни редакции по форматирането
                                      5. Габриел Бодар, поправи и актуализира много от линковете

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Деликатно въведение в маркирането с xml за епиграфи

                                      2024-03-05

                                      Концепцията зад EpiDoc събира на едно място в полза на епиграфите както традиционни, така и напълно модерни методи за редактиране и установени практики.

                                      Установени епиграфски практики

                                      През последния век епиграфите се сблъскаха с проблеми, свързани с това как да се представи невербалната информация чрез писмения текст. До края на 19 в. издателите обикновено са създавали факсимиле на текста, но това постепенно е ставало все по-слабо разпространено и издателите не демонстрирали еднаква готовност да предоставят пълни фотографски данни за всеки текст. Установените практики, които са мъчно създадени да представят липсващ текст, съкращения и т.н. са били малко или много съгласувани през 30-те г. на 20в. и в известна степен се припокриват с тези, използвани в папирусологията и палеографията. На всички епиграфи им се налага да се справят с трудностите, свързани с това да се пренесе информацията в една електронна среда - например, с това да се намери шрифт, който би позволил слагането на точки под буквите. Повечето от нас обаче вече са привикнали към тези нови ограничения.

                                      Трудността да се предадат такива условности и най-вече гръцките символи в пълноценни шрифтове и в Мрежата досега задържаше публикацията на пълни епиграфски текстове онлайн. Вместо това бяха създадени изключително богати колекции за търсене, сред които най-забележителни са следните:

                                      Виж също: Съответствия (EpiDoc Съвместимост).

                                      Всички тези разработки се определяха от развитието на съществуващите технологии, тъй като те се усъвършенстваха през 20в. Стремежът на EpiDoc бе да се възползва от нови и развити технологии за традиционните цели на епиграфиката. Много от задачите, споменати по-горе, включваха борба срещу технологичните стандарти - например в печатните публикации, за да приспособим възможно най-много от нашите нужди. През този период постепенно ставаше все по-трудно да бъдат убедени конвенционалните издатели да посрещнат нашите изисквания да бъде включена мета-текстуална информация, освен на много висока цена. В същото време очакванията към обема на информацията, която би съпътствала един текст, се увеличиха значително; също като информацията за физическите детайли, фотографската илюстрация се превърна в стандарт.

                                      През последните 15 години учените обичайно се сблъскваха с подобни изисквания да включват метаданни в текстовете в електронната им форма и се появиха средства, които да направят това все по-лесно, а резултатите - все по-ценни. Софтуерът за обработка на думи, който е известен още от 80-те г. на 20в. ни позволява да контролираме форматирането на нашите текстове, като използваме маркиране, което до сега бе незабележимо предоставено от софтуера. По-взискателните нужди на колекциите от документи с голям размер - правни документи, индустриална документация, комерсиално издаване - доведоха през 80-те до откриването на начини за включване на по-широк набор от информация и инструкции вътре в електронните текстове. В началото акцентът бе върху това да се включат инструкции за форматиране, но скоро се появиха и методи за включване на по-сложна семантична информация за структурата на документа и дори за неговото съдържание. Пример за това е маркирането на заглавие на книга именно като заглавие, а не просто то да бъде маркирано като курсив. Употребата на това по-абстрактно маркиране позволява едно разделяне на структура и представяне, така че структурата да е сравнително основна за жанра на документа, докато представянето може да се различава в зависимост от формата на публикацията. В известен смисъл тази промяна представлява завръщане към един по-ранен метод, в който авторите са се занимавали със същността на текста, а всички детайли по презентацията му се изготвяли в процеса на публикация - едно разделение, което се заличава в епохата на готовите копия.

                                      Протоколите, които бяха създадени чрез споменатите усилия, бяха унифицирани в края на 80-те години като Стандартизиран генерализиран маркиращ език (Standard Generalized Markup Language) и наскоро им бе дадена по-опростена и по-гъвкава форма за употреба в Световната мрежа като XML: Extensible Markup Language. XML сега се използва от учените в широк кръг от хуманитарни дисциплини, за да улови, представи и запази изследвания за различни по обхват цели.

                                      И така, привлекателните страни на XML за епиграфите са значителни. Например: липсващият материал може да бъде маркиран като такъв и след това представен между квадратни скоби; в същото време търсенето може да се ограничи само в това да открива текст, който не е маркиран като липсващ (и по този начин да предоставя само изрично засвидетелствани текстове). Неясните букви могат да бъдат обозначени като такива, а сетне е възможно да се вземе решение дали да бъдат представени с точка под тях или по някакъв друг начин. Думите могат да бъдат систематизирани по време на обработката, така че да бъдат създадени индекси, които да нарастват с нарастването на колекцията. Но най-важното при това положение е да се повтори Лайденската практика, а именно - да се съгласуват електронните еквиваленти на разнообразните сигли, които използваме. На първо място това е ценно дори само за да ни спестява време и усилия, но също така самата единност, без да бъде натрапвана еднаквост, е ценна на свой ред. Тя не само подпомага потребителя, както на отпечатаната страница, но освен това документите, създадени по този начин и публикувани електронно, биха могли да бъдат използвани заедно, дори когато са били подготвени поотделно.

                                      Нуждата от съгласувани стандарти не се ограничава единствено по отношение на епиграфиката. От 1967г. международен консорциум учени, занимаващи се в по-голямата си част в полето на хуманитарните науки, работят заедно за развиването и усъвършенстването на набор от указания за описване на структура и съдържание на документи. Резултатът от това начинание доведе до създаването на кодиращ език, реализиран чрез XML и описан от името на групата - TEI, Text Encoding Initiative.

                                      TEI за епиграфи: Какво е това и защо да го използваме?

                                      TEI (The Text Encoding Initiative) е опит за изследване, насочено към дефинирането на кодиращ език, който покрива нуждите на учените-хуманитаристи в най-общ смисъл. Има две основни цели, които обуславят развитието на TEI. Първата е необходимостта да се даде възможност на учените да представят материалите на своите изследвания в дигитална форма, като използват дескриптивен език, който имитира видовете аналитични термини и концепциии, познати и базови за хуманитаристиката. Втората цел е да се направи възможно учените да споделят по разбираем начин получените резултати, използвайки един познат и общ дескриптивен език.

                                      Бихме могли да мислим за кодиращия език TEI като за подражаващ на човешкия език: ядро от общи термини в центъра, обгърнато от по-малко широка лексика, включително и местна употреба, специализирана терминология и други вариации. В ядрото на TEI са общите термини и концепции, които са широко споделяни от учените в повечето дисциплини: категории като параграфи, родови текстови разделения, заглавия, списъци и т.н. По-специализирани елементи са групирани заедно според употребата им: например, елементи за детайлно кодиране на имена, елементи за представяне на особености на манускриптите, елементи за улавяне на структурата на речниците и пр. TEI умишлено е организирана в модули по този начин, така че учените, които работят в специфични дисциплини да могат да използват само модулите, които се отнасят до тяхната работа, и да пропуснат останалите. Така именно TEI може да постигне голяма широта на употреба, без да натоварва отделните учени и проекти с необходимостта да се овладява много голямо поле, значителна част от което се отнася единствено до други дисциплини. Тъкмо напротив, кодиращият език TEI може много директно да бъде насочен към специфично поле или задача и може да бъде ограничен да предоставя нещата, които са съществени за работата на конкретния проект.

                                      Също като един човешки език, TEI може да бъде използван така, че да си служи с богат и нюансиран речник, с детайлно кодиране, което описва огромно количество особености в текста, но би могъл да се използва и съвсем просто, служейки си единствено с няколко съществени понятия, които описват само най-основните данни за текста: раздели, заглавия, параграфи. Колкото по-детайлно е кодирането, толкова повече възможности има то да бъде използвано, но фактори като време, разходи, налични кадри и местни особености могат да поставят ограничения в постижимото ниво на детайлност.

                                      В допълнение към предоставянето на кодираща система, която учените могат да използват в оригиналното й състояние, TEI също така предлага начин научните проекти да дефинират собствени версии за употреба вътре в общата рамка на TEI. Те могат да използват широко познатото му ядро от термини и понятия, като по този начин си спестяват ненужната трудност да ги измислят наново. И тъкмо защото TEI предоставя една обща рамка за създаване и описване на индивидуални подходи, те могат да бъдат споделяни лесно и с реален смисъл. Като резултат от това групи от учени в конкретни дисциплини могат да артикулират специфичните цели и методи, които характеризират тяхната работа, и разликите, които ги разграничават от други, работещи в подобни сфери. Вместо взаимно неразбираеми подходи, различните проекти могат да създават резултати, чиито различия да са плод по-скоро на реално различаващи се мнения, отколкото на прости случайни несъответствия.

                                      Персонализацията EpiDoc: TEI за епиграфи

                                      В тази рамка обществото EpiDoc работи от 2000г. за създаването на персонализирана версия на насоките на TEI, за да подпомогнат специфичните нужди на епиграфите. Идеята беше създадена от Том Елиът, специалист по антична история в Университета на Северна Каролина в Чапъл Хил. Целта беше както да се използват по най-пълноценния възможен начин постиженията, които вече са направени, така и да се гарантира, че описаните текстовете са третирани по начин, съответстващ на този, който е използван за други текстове, а не различен от него. Персонализацията EpiDoc премахва неуместните елементи от основното тяло на TEI и добавя материал за специфичните видове транскрипции, анализи, описания и класификации, които са същностно важни за епиграфската работа. Резултатът е един прост език, но с големи възможности, който може да бъде използван за отбелязването на всички значими особености на надписите, а също така представя и съпътстващата информация за самия епиграфски обект.

                                      За да допълни кодиращия език EpiDoc, общността създаде също така набор от насоки за кодиране и софтуерни инструменти, както и документация, която описва как да бъде използван кодиращият език, инструментите и другите елементи от метода EpiDoc. Целта е да се установи една рамка, която е лесна за възприемане и употреба дори за учени без техническа подготовка или подкрепа. Това може би звучи невероятно, но начинанието е от същия порядък като това да се овладее знанието да се маркира стандартен епиграфски текст със съществуващата система от сигли.

                                      Обществото работи за развитието на представянето на всички установени епиграфски понятия. То разшири труда си така, че да бъде приложим към различните полета, които биха могли да се представят в една епиграфска публикация, включително:

                                      Виж още: Структура на документа.

                                      Друга област, която активно се разработва, е създаването на оперативна съвместимост. Вече е създаден софтуерен инструмент за конвертиране на текстове от нормално епиграфско маркиране в EpiDoc XML (т.нар. Chapel Hill Electronic Text Converter (CHETC)). Други сфери включват употребата на авторитетна лексика. Например, работата по проекта "Надписите от Афродизиас" е тясно обвързана с Речника на гръцките лични имена, за да осигури пълно покритие и адекватна употреба.

                                      Работата, водена от д-р Елиът, беше подемана от няколко различни учени, които работеха в тясно сътрудничество и в постоянен контакт с по-широко поле на специализация. Те очертаха опита на един вече осъществен EpiDoc проект, Vindolanda Tablets on line, и на два текущи проекта: US Epigraphy Project (USEP) (поддържан от Университетите Браун, Принстън и Рутгерс) и Inscriptions of Aphrodisias Project (InsAph) (поддържан от Arts and Humanities Research Council). Щедрата подкрепа на AHRC позволи провеждането на интензивния уъркшоп през март 2006г., където бяха установени тези насоки.

                                      За тази страница работиха:

                                      1. Шарлот Руше, автор
                                      2. Джулия Фландърс, автор
                                      3. Полина Йорданова, преведе на български език
                                      4. Том Елиът, препратки към TEI-Lite и различни редакции по форматирането
                                      5. Габриел Бодар, поправи и актуализира много от линковете

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-de.html b/gl/dev/intro-eps-de.html index 2111d3c9e..ebf36ca21 100644 --- a/gl/dev/intro-eps-de.html +++ b/gl/dev/intro-eps-de.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Erste Einführung in die Textauszeichnung für Epigraphiker

                                      2023-04-27

                                      Die Konzepte von EpiDoc vereinigen traditionelle und hochmoderne Editionsmethoden und –konventionen für Epigraphiker.

                                      Epigraphische Konventionen

                                      Während des vergangenen Jahrhunderts hatten Epigraphiker mit den Problemen der Darstellung von non-verbaler Information in ihren schriftlichen Texten zu kämpfen. Bis zum Ende des neunzehnten Jahrhunderts konnte von Herausgebern erwartet werden, ein Faksimile des Textes herzustellen, dies wurde jedoch immer unüblicher, und parallel dazu hatten Verleger nicht den Willen, jeden Text ausführlich fotografisch zu dokumentieren. Die Konventionen, die mühevoll erarbeitet wurden, um fehlenden Text, Abkürzungen usw. darzustellen, fanden seit den 1930er Jahren mehr oder weniger allgemeine Zustimmung und überschneiden sich zu einem gewissen Grade mit denen, die in Papyrologie und Paläographie verwendet werden. Alle Epigraphiker mussten sich mit den Problemen auseinandersetzen, die mit der Übertragung dieser Darstellungsweisen in ein elektronisches Umfeld einhergingen – beispielsweise, eine Schriftart zu finden, die es ermöglicht, einen Punkt unter einen unsicheren Buchstaben zu setzen; die meisten von uns haben sich allerdings mittlerweile an diese neuen Beschränkungen angepasst.

                                      Die Schwierigkeit, solche Konventionen und insbesondere griechische Buchstaben in einheitlichen Schriftarten und im Internet wiederzugeben, verspätete häufig die Veröffentlichung vollständiger epigraphischer Texte online. Stattdessen wurden außerordentlich inhaltsreiche durchsuchbare Sammlungen erstellt; darunter sind die bedeutsamsten:

                                      Siehe auch: Conformance (EpiDoc Kompatibilität).

                                      All diese Entwicklungen waren daher bestimmt durch den Stand der bestehenden technischen Möglichkeiten, die im Laufe des 20. Jahrhunderts voranschritten. Das Ziel von EpiDoc ist es, neue und vielversprechende Technologien für die traditionellen Zwecke der Epigraphik zu nutzen. Viele der oben beschriebenen Prozesse bedeuteten Konflikte mit den technologischen Standards, etwa in gedruckten Publikationen, um so vielen unserer Anforderungen wie möglich entgegenzukommen. In diesem Zeitraum wurde es dauernd schwieriger, konventionelle Verlage zu überzeugen, unseren Bedürfnissen entgegenzukommen, um Meta-Text-Informationen einzubauen, außer unter enormem Kostenaufwand. Gleichzeitig wuchsen die Erwartungen über das Volumen von Begleitinformationen beträchtlich; ebenso wie Informationen über die Beschaffenheit sind fotografische Illustrationen heute Standard.

                                      Seit etwa fünfzehn Jahren setzen sich Wissenschaftler allgemein mit ähnlichen Anforderungen auseinander, Meta-Daten ihrer Texte in deren elektronische Form zu integrieren, und es sind Tools entstanden, die dies immer weiter vereinfachen und die Resultate immer wertvoller machen. Textverarbeitungsprogramme, die seit den 1980er Jahren im Umlauf sind, erlauben uns, die Formatierung unserer Texte durch Markup, das jetzt unsichtbar durch die Software integriert wird, zu kontrollieren. Die anspruchsvolleren Bedürfnisse von Dokumentsammlungen mit großem Umfang – Gesetzestexte, industrielle Dokumentation, kommerzielles Publizieren – führte in den 1980er Jahren zur Erkundung von Möglichkeiten, ein weiteres Repertoire an Informationen und Instruktionen in elektronischem Text einzubauen. Zunächst wurde dem Einsatz von Formatierungsinstruktionen Aufmerksamkeit geschenkt, bald aber entstanden Methoden, komplexere semantische Informationen über die Dokumentstruktur, und sogar den Inhalt zu umfassen. Ein einfaches Beispiel ist, einen Buchtitel als Titel zu markieren, anstatt ihn einfach als Kursivschrift auszuzeichnen. Der Gebrauch von abstrakterem Markup ermöglicht eine Differenzierung von Struktur und Darstellung, wo die Struktur recht wesentlich für das Genre eines Dokuments ist, während die Darstellung je nach Form der Publikation variiert werden kann. In gewisser Weise versinnbildlicht diese Verschiebung eine Rückkehr zu einer früheren Arbeitsweise, nach der die Materie eines Textes Sache der Autoren waren und alle Details der Darstellung im Publikationsprozess bearbeitet wurden – eine Unterscheidung, die in den Tagen der druckreifen Kopie verloren geht.

                                      Die Protokolle, die aus diesen letzteren Bemühungen entstanden, wurden in den späteren 1980er Jahren standardisiert, da die Normierte Verallgemeinerte Auszeichnungssprache (Standard Generalized Markup Language), und erhielten in noch jüngerer Zeit in der Form der erweiterbaren Auszeichnungssprache XML (Extensible Markup Language) eine einfachere und flexiblere Form für den Gebrauch im Internet. XML wird nun in einem breiten Spektrum geisteswissenschaftlicher Disziplinen von Wissenschaftlern verwendet, um Forschungsmaterialien zu erfassen, darzustellen und für ein weites Spektrum von Nutzungsmöglichkeiten zu bewahren.

                                      Die Vorteile von XML für Epigraphiker sind also beträchtlich. Ein Beispiel: Fehlendes Material kann als solches ausgezeichnet werden und dann mit eckigen Klammern dargestellt werden; gleichzeitig kann eine Suche ausgeführt werden, die nur Text findet, der nicht als fehlend ausgezeichnet wurde (d.h. nur solchen, der mit Sicherheit attestiert ist). Unsichere Buchstaben können als solche ausgezeichnet werden, sodass zu einem späteren Zeitpunkt entschieden werden kann, ob sie mit einem Unterpunkt oder auf eine andere Weise dargestellt werden sollen. Wörter können bei der Herausgabe lemmatisiert werden, um Indices zu erstellen, die mit Heranwachsen der Sammlung ebenfalls größer werden. An diesem Punkt ist es jedoch von Bedeutung, die „Leiden“-Prozedur erneut durchzugehen: das heißt, elektronische Äquivalente für die verschiedenen Siglen, die wir verwenden, zu vereinbaren. Dies ist erstens ganz einfach für die Einsparung von Zeit und Mühen relevant; aber ebenso relevant bleibt Kontinuität (die keine Einheitlichkeit erzwingt). Sie unterstützt nicht nur den Anwender wie auf einer gedruckten Seite, sondern Dokumente, die auf diese Weise herausgegeben und elektronisch publiziert werden, sind gemeinsam nutzbar, auch wenn sie unabhängig voneinander erarbeitet wurden.

                                      Die Notwenigkeit vereinbarter Standards beschränkt sich nicht auf Epigraphik. Seit 1987 arbeitete eine Gruppe überwiegend von Geisteswissenschaftlern daran, eine Reihe von Richtlinien für die Beschreibung der Struktur und des Inhalts von Dokumenten zu entwickelt und zu verbessern. Die Ergebnisse dieses Bestrebens resultierten in einer Kodierungssprache, verwirklicht in XML und beschrieben durch den Namen der Gruppe, Initiative für Textkodierung (Text Encoding Initiatve, TEI)

                                      TEI für Epigraphiker: Was ist es, und wozu wird es verwendet?

                                      Die Text Encoding Initiative ist ein Forschungsprojekt, das die Definition einer Kodierungssprache zum Ziel hat, die ganz allgemein die Bedürfnisse von Geisteswissenschaftlern erfüllt. Es gibt zwei Hauptziele, die die Entwicklung der TEI motivieren. Das erste ist es, Wissenschaftlern zu ermöglichen, ihre Forschungsmaterialien durch Gebrauch einer Beschreibungssprache, die die analytische Terminologie und Konzepte reflektiert, die in den Geisteswissenschaften gebräuchlich und von Bedeutung sind, in digitaler Form zu präsentieren. Das zweite ist, Wissenschaftlern zu ermöglichen, die resultierenden Materialien verständlich zu präsentieren, indem eine gemeinsame Beschreibungssprache genutzt wird.

                                      Wir können uns die TEI-Kodierungssprache ähnlich wie eine menschliche Sprache vorstellen: ein Kern an gemeinsamen Begriffen in der Mitte, umgeben von weniger weit verbreiteten Vokabularien, die lokale Verwendungen beinhalten, spezialisierte Terminologie und andere Variationen. Im Kern der TEI stehen gemeinsame Begriffe und Konzepte, an deren Gebrauch Wissenschaftler der meisten Disziplinen teilhaben: Elemente wie Absätze, genrespezifische Textunterteilungen, Überschriften, Listen und so weiter. Spezialisiertere Elemente werden je nach Anwendung gruppiert, beispielsweise Elemente zur detaillierten Auszeichnung von Namen, Elemente zur Wiedergabe der Eigenschaften eines Manuskripts, Elemente zur Fassung der Struktur eines Wörterbuches und so weiter. Die TEI ist so international in Module eingeordnet, sodass Wissenschaftler aus in bestimmten Fachbereichen nur die Module, die für ihre Arbeit relevant sind, verwenden und andere auslassen können. Die TEI kann somit eine große Breite erreichen, ohne einzelne Wissenschaftler und Projekte damit zu belasten, eine große Masse an Fähigkeiten bewältigen zu müssen, von der vieles nur für andere Fachbereiche relevant ist. Im Gegenteil, die TEI-Kodierungssprache kann sehr direkt auf spezielle Bereiche oder Aufgaben angepasst und auf das, was für die Arbeit eines Projektes essenziell ist, beschränkt werden.

                                      Wie eine menschliche Sprache kann TEI auf eine Weise genutzt werden, die sich vielfältigen und nuancierten Vokabulars bedient, mit detaillierten Kodierungen, die eine lange Reihe an Textphänomenen beschreibt, aber sie kann ebenso sehr einfach verwendet werden, indem nur ein paar essenzielle Konzepte gebraucht werden, die nur die grundlegendsten Textdaten beschreiben: Unterteilungen, Überschriften, Absätze. Je detaillierter die Kodierung ist, umso breiter sind die Verwendungsmöglichkeiten des Textes, aber Faktoren wie Zeit, Kosten, verfügbare Mitarbeiter und lokale Sachkunde können dem machbaren Detailreichtum Grenzen setzen.

                                      Über die Bereitstellung eines Kodierungssystems hinaus, das Wissenschaftler in seiner ursprünglichen Form nutzen können, bietet die TEI wissenschaftlichen Projekten auch die Möglichkeit, angepasste Versionen der TEI-Sprache zu definieren, die Änderungen enthalten, die für die Unterstützung von lokalen Bedürfnissen notwendig sind. Da diese angepassten Versionen innerhalb des Rahmens von TEI funktionieren, können sie den weit verbreitet verwendeten Kern von Begriffen und Konzepten verwenden und dadurch unnötige Arbeit in deren Neuschaffung vermeiden. Und da die TEI einen gemeinsamen Rahmen für die Schaffung und Beschreibung von Anpassungen bietet, können diese Anpassungen einfach und fruchtbar verbreitet werden. Dadurch können Gruppen von Wissenschaftlern in einzelnen Fachbereichen die besonderen Zwecke und Methoden artikulieren, die ihre Arbeit charakterisieren, und die Unterschiede, die sie von anderen, die in verwandten Bereichen arbeiten, differenzieren. Anstelle von untereinander nicht verständlichen Ansätzen können verschiedene Projekte Ergebnisse produzieren, deren Unterschiede aus tatsächlichen Diskrepanzen herrühren, und nicht von einfachen Zufallsabweichungen.

                                      Die Anpassung durch EpiDoc: TEI für Epigraphiker

                                      In diesem Rahmen arbeitet die EpiDoc-Gemeinschaft seit 2000 daran, eine angepasste Version der TEI-Richtlinien zu entwickeln, um den besonderen Bedürfnissen von Epigraphikern gerecht zu werden. Die Idee wurde von Tom Elliott, einem Althistoriker an der University of North Carolina at Chapel Hill, in Angriff genommen. Das Ziel ist, sowohl die bereits getane Arbeit so gut wie möglich zu nutzen und sicherzustellen, dass Texte, die eingemeißelt sind, auf eine Weise behandelt werden, die mit der für andere Texte vereinbar ist, und sie nicht ausgrenzt. Die EpiDoc-Anpassung entfernt irrelevante Elemente aus dem Corpus der TEI und fügt Bestimmungen für bestimmte Arten der Transkription, Analyse, Beschreibung und Klassifizierung hinzu, die für epigraphische Arbeit von Bedeutung sind. Das Ergebnis ist eine einfache, und doch ausdrucksstarke Sprache, die verwendet werden kann, um alle Eigenschaften von Inschriften auszuzeichnen und auch die begleitenden Informationen über das epigraphische Objekt selbst wiederzugeben.

                                      Als Ergänzung zur EpiDoc-Kodierungssprache produzierte die EpiDoc-Gemeinschaft eine Sammlung von Kodierungsrichtlinien (Guidelines) und Software-Tools, sowie Aufzeichnungen, die beschreiben, wie die Kodierungssprache, die Tools und die anderen Elemente der EpiDoc-Methodik anzuwenden sind. Das Ziel ist es, einen Referenzrahmen zu etablieren, der leicht zu erlernen und zu nutzen ist, sogar für Wissenschaftler, die kein technisches Hintergrundwissen oder Unterstützung haben. Das mag unwahrscheinlich klingen, aber das Unternehmen hat denselben Stellenwert wie das Erlernen der Auszeichnung eines epigraphischen Textes mit der vorhandenen Reihe an Siglen.

                                      Die Gruppe arbeitet daran, Ausdrücke für alle vereinbarten epigraphischen Konventionen zu entwickeln. Sie erweiterte diese Anleitung, um verschiedene Bereiche anzusprechen, die in einer epigraphischen Publikation wiedergegeben werden könnten, unter anderem:

                                      Siehe auch: Dokumentstruktur (Document Structure).

                                      Ein weiterer Bereich, der gegenwärtig erkundet wird, ist die Entwicklung von Kompatibilität. Ein Software-Tool für die Umwandlung von Texten in normalem epigraphischen Markup in EpiDoc-XML wurde bereits entwickelt (der sogenannte Chapel Hill Electronic Text Converter (CHETC)). Andere Bereiche beziehen sich auf den Gebrauch autoritativer Lexika. Beispielsweise arbeitet das Projekt Inschriften von Aphrodisias (Inscriptions of Aphrodisias) eng mit dem Lexikon für Eigennamen (Lexicon of Greek Personal Names) zusammen, um volle Erfassung und einheitlichen Gebrauch zu gewährleisten.

                                      Die Arbeit unter der Leitung von Dr. Elliott wurde von zahlreichen Wissenschaftlern unternommen, die eng zusammenarbeiten und in regelmäßigem Kontakt mit dem weiteren Berufskreis stehen. Sie haben die Erfahrungen eines etablierten EpiDoc-Projekts, Vindolanda Tablets on line, und zweier neuer Projekte genutzt: Das USA Epigraphik Projekt (US Epigraphy Project (USEP)), unterstützt von den Universitäten Brown, Princeton und Rutgers, und das Projekt Inschriften von Aphrodisias (Inscriptions of Aphrodisias Project (InsAph)) (unterstützt durch den Forschungsrat der Geisteswissenschaften (Arts and Humanities Research Council)). Die großzügige Unterstützung des AHRC erlaubte den Intensivworkshop im März 2006, auf dem diese Richtlinien verbessert wurden.

                                      Verantwortlich für diesen Abschnitt

                                      1. Charlotte Roueché, Autorin
                                      2. Julia Flanders, Autorin
                                      3. Laura Löser, Übersetzung aus dem Englischen
                                      4. Tom Elliott, Umwandlung aus TEI-Lite und verschiedene Reformatierungsänderungen
                                      5. Gabriel Bodard, Korrigiert einige Links

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Erste Einführung in die Textauszeichnung für Epigraphiker

                                      2024-03-05

                                      Die Konzepte von EpiDoc vereinigen traditionelle und hochmoderne Editionsmethoden und –konventionen für Epigraphiker.

                                      Epigraphische Konventionen

                                      Während des vergangenen Jahrhunderts hatten Epigraphiker mit den Problemen der Darstellung von non-verbaler Information in ihren schriftlichen Texten zu kämpfen. Bis zum Ende des neunzehnten Jahrhunderts konnte von Herausgebern erwartet werden, ein Faksimile des Textes herzustellen, dies wurde jedoch immer unüblicher, und parallel dazu hatten Verleger nicht den Willen, jeden Text ausführlich fotografisch zu dokumentieren. Die Konventionen, die mühevoll erarbeitet wurden, um fehlenden Text, Abkürzungen usw. darzustellen, fanden seit den 1930er Jahren mehr oder weniger allgemeine Zustimmung und überschneiden sich zu einem gewissen Grade mit denen, die in Papyrologie und Paläographie verwendet werden. Alle Epigraphiker mussten sich mit den Problemen auseinandersetzen, die mit der Übertragung dieser Darstellungsweisen in ein elektronisches Umfeld einhergingen – beispielsweise, eine Schriftart zu finden, die es ermöglicht, einen Punkt unter einen unsicheren Buchstaben zu setzen; die meisten von uns haben sich allerdings mittlerweile an diese neuen Beschränkungen angepasst.

                                      Die Schwierigkeit, solche Konventionen und insbesondere griechische Buchstaben in einheitlichen Schriftarten und im Internet wiederzugeben, verspätete häufig die Veröffentlichung vollständiger epigraphischer Texte online. Stattdessen wurden außerordentlich inhaltsreiche durchsuchbare Sammlungen erstellt; darunter sind die bedeutsamsten:

                                      Siehe auch: Conformance (EpiDoc Kompatibilität).

                                      All diese Entwicklungen waren daher bestimmt durch den Stand der bestehenden technischen Möglichkeiten, die im Laufe des 20. Jahrhunderts voranschritten. Das Ziel von EpiDoc ist es, neue und vielversprechende Technologien für die traditionellen Zwecke der Epigraphik zu nutzen. Viele der oben beschriebenen Prozesse bedeuteten Konflikte mit den technologischen Standards, etwa in gedruckten Publikationen, um so vielen unserer Anforderungen wie möglich entgegenzukommen. In diesem Zeitraum wurde es dauernd schwieriger, konventionelle Verlage zu überzeugen, unseren Bedürfnissen entgegenzukommen, um Meta-Text-Informationen einzubauen, außer unter enormem Kostenaufwand. Gleichzeitig wuchsen die Erwartungen über das Volumen von Begleitinformationen beträchtlich; ebenso wie Informationen über die Beschaffenheit sind fotografische Illustrationen heute Standard.

                                      Seit etwa fünfzehn Jahren setzen sich Wissenschaftler allgemein mit ähnlichen Anforderungen auseinander, Meta-Daten ihrer Texte in deren elektronische Form zu integrieren, und es sind Tools entstanden, die dies immer weiter vereinfachen und die Resultate immer wertvoller machen. Textverarbeitungsprogramme, die seit den 1980er Jahren im Umlauf sind, erlauben uns, die Formatierung unserer Texte durch Markup, das jetzt unsichtbar durch die Software integriert wird, zu kontrollieren. Die anspruchsvolleren Bedürfnisse von Dokumentsammlungen mit großem Umfang – Gesetzestexte, industrielle Dokumentation, kommerzielles Publizieren – führte in den 1980er Jahren zur Erkundung von Möglichkeiten, ein weiteres Repertoire an Informationen und Instruktionen in elektronischem Text einzubauen. Zunächst wurde dem Einsatz von Formatierungsinstruktionen Aufmerksamkeit geschenkt, bald aber entstanden Methoden, komplexere semantische Informationen über die Dokumentstruktur, und sogar den Inhalt zu umfassen. Ein einfaches Beispiel ist, einen Buchtitel als Titel zu markieren, anstatt ihn einfach als Kursivschrift auszuzeichnen. Der Gebrauch von abstrakterem Markup ermöglicht eine Differenzierung von Struktur und Darstellung, wo die Struktur recht wesentlich für das Genre eines Dokuments ist, während die Darstellung je nach Form der Publikation variiert werden kann. In gewisser Weise versinnbildlicht diese Verschiebung eine Rückkehr zu einer früheren Arbeitsweise, nach der die Materie eines Textes Sache der Autoren waren und alle Details der Darstellung im Publikationsprozess bearbeitet wurden – eine Unterscheidung, die in den Tagen der druckreifen Kopie verloren geht.

                                      Die Protokolle, die aus diesen letzteren Bemühungen entstanden, wurden in den späteren 1980er Jahren standardisiert, da die Normierte Verallgemeinerte Auszeichnungssprache (Standard Generalized Markup Language), und erhielten in noch jüngerer Zeit in der Form der erweiterbaren Auszeichnungssprache XML (Extensible Markup Language) eine einfachere und flexiblere Form für den Gebrauch im Internet. XML wird nun in einem breiten Spektrum geisteswissenschaftlicher Disziplinen von Wissenschaftlern verwendet, um Forschungsmaterialien zu erfassen, darzustellen und für ein weites Spektrum von Nutzungsmöglichkeiten zu bewahren.

                                      Die Vorteile von XML für Epigraphiker sind also beträchtlich. Ein Beispiel: Fehlendes Material kann als solches ausgezeichnet werden und dann mit eckigen Klammern dargestellt werden; gleichzeitig kann eine Suche ausgeführt werden, die nur Text findet, der nicht als fehlend ausgezeichnet wurde (d.h. nur solchen, der mit Sicherheit attestiert ist). Unsichere Buchstaben können als solche ausgezeichnet werden, sodass zu einem späteren Zeitpunkt entschieden werden kann, ob sie mit einem Unterpunkt oder auf eine andere Weise dargestellt werden sollen. Wörter können bei der Herausgabe lemmatisiert werden, um Indices zu erstellen, die mit Heranwachsen der Sammlung ebenfalls größer werden. An diesem Punkt ist es jedoch von Bedeutung, die „Leiden“-Prozedur erneut durchzugehen: das heißt, elektronische Äquivalente für die verschiedenen Siglen, die wir verwenden, zu vereinbaren. Dies ist erstens ganz einfach für die Einsparung von Zeit und Mühen relevant; aber ebenso relevant bleibt Kontinuität (die keine Einheitlichkeit erzwingt). Sie unterstützt nicht nur den Anwender wie auf einer gedruckten Seite, sondern Dokumente, die auf diese Weise herausgegeben und elektronisch publiziert werden, sind gemeinsam nutzbar, auch wenn sie unabhängig voneinander erarbeitet wurden.

                                      Die Notwenigkeit vereinbarter Standards beschränkt sich nicht auf Epigraphik. Seit 1987 arbeitete eine Gruppe überwiegend von Geisteswissenschaftlern daran, eine Reihe von Richtlinien für die Beschreibung der Struktur und des Inhalts von Dokumenten zu entwickelt und zu verbessern. Die Ergebnisse dieses Bestrebens resultierten in einer Kodierungssprache, verwirklicht in XML und beschrieben durch den Namen der Gruppe, Initiative für Textkodierung (Text Encoding Initiatve, TEI)

                                      TEI für Epigraphiker: Was ist es, und wozu wird es verwendet?

                                      Die Text Encoding Initiative ist ein Forschungsprojekt, das die Definition einer Kodierungssprache zum Ziel hat, die ganz allgemein die Bedürfnisse von Geisteswissenschaftlern erfüllt. Es gibt zwei Hauptziele, die die Entwicklung der TEI motivieren. Das erste ist es, Wissenschaftlern zu ermöglichen, ihre Forschungsmaterialien durch Gebrauch einer Beschreibungssprache, die die analytische Terminologie und Konzepte reflektiert, die in den Geisteswissenschaften gebräuchlich und von Bedeutung sind, in digitaler Form zu präsentieren. Das zweite ist, Wissenschaftlern zu ermöglichen, die resultierenden Materialien verständlich zu präsentieren, indem eine gemeinsame Beschreibungssprache genutzt wird.

                                      Wir können uns die TEI-Kodierungssprache ähnlich wie eine menschliche Sprache vorstellen: ein Kern an gemeinsamen Begriffen in der Mitte, umgeben von weniger weit verbreiteten Vokabularien, die lokale Verwendungen beinhalten, spezialisierte Terminologie und andere Variationen. Im Kern der TEI stehen gemeinsame Begriffe und Konzepte, an deren Gebrauch Wissenschaftler der meisten Disziplinen teilhaben: Elemente wie Absätze, genrespezifische Textunterteilungen, Überschriften, Listen und so weiter. Spezialisiertere Elemente werden je nach Anwendung gruppiert, beispielsweise Elemente zur detaillierten Auszeichnung von Namen, Elemente zur Wiedergabe der Eigenschaften eines Manuskripts, Elemente zur Fassung der Struktur eines Wörterbuches und so weiter. Die TEI ist so international in Module eingeordnet, sodass Wissenschaftler aus in bestimmten Fachbereichen nur die Module, die für ihre Arbeit relevant sind, verwenden und andere auslassen können. Die TEI kann somit eine große Breite erreichen, ohne einzelne Wissenschaftler und Projekte damit zu belasten, eine große Masse an Fähigkeiten bewältigen zu müssen, von der vieles nur für andere Fachbereiche relevant ist. Im Gegenteil, die TEI-Kodierungssprache kann sehr direkt auf spezielle Bereiche oder Aufgaben angepasst und auf das, was für die Arbeit eines Projektes essenziell ist, beschränkt werden.

                                      Wie eine menschliche Sprache kann TEI auf eine Weise genutzt werden, die sich vielfältigen und nuancierten Vokabulars bedient, mit detaillierten Kodierungen, die eine lange Reihe an Textphänomenen beschreibt, aber sie kann ebenso sehr einfach verwendet werden, indem nur ein paar essenzielle Konzepte gebraucht werden, die nur die grundlegendsten Textdaten beschreiben: Unterteilungen, Überschriften, Absätze. Je detaillierter die Kodierung ist, umso breiter sind die Verwendungsmöglichkeiten des Textes, aber Faktoren wie Zeit, Kosten, verfügbare Mitarbeiter und lokale Sachkunde können dem machbaren Detailreichtum Grenzen setzen.

                                      Über die Bereitstellung eines Kodierungssystems hinaus, das Wissenschaftler in seiner ursprünglichen Form nutzen können, bietet die TEI wissenschaftlichen Projekten auch die Möglichkeit, angepasste Versionen der TEI-Sprache zu definieren, die Änderungen enthalten, die für die Unterstützung von lokalen Bedürfnissen notwendig sind. Da diese angepassten Versionen innerhalb des Rahmens von TEI funktionieren, können sie den weit verbreitet verwendeten Kern von Begriffen und Konzepten verwenden und dadurch unnötige Arbeit in deren Neuschaffung vermeiden. Und da die TEI einen gemeinsamen Rahmen für die Schaffung und Beschreibung von Anpassungen bietet, können diese Anpassungen einfach und fruchtbar verbreitet werden. Dadurch können Gruppen von Wissenschaftlern in einzelnen Fachbereichen die besonderen Zwecke und Methoden artikulieren, die ihre Arbeit charakterisieren, und die Unterschiede, die sie von anderen, die in verwandten Bereichen arbeiten, differenzieren. Anstelle von untereinander nicht verständlichen Ansätzen können verschiedene Projekte Ergebnisse produzieren, deren Unterschiede aus tatsächlichen Diskrepanzen herrühren, und nicht von einfachen Zufallsabweichungen.

                                      Die Anpassung durch EpiDoc: TEI für Epigraphiker

                                      In diesem Rahmen arbeitet die EpiDoc-Gemeinschaft seit 2000 daran, eine angepasste Version der TEI-Richtlinien zu entwickeln, um den besonderen Bedürfnissen von Epigraphikern gerecht zu werden. Die Idee wurde von Tom Elliott, einem Althistoriker an der University of North Carolina at Chapel Hill, in Angriff genommen. Das Ziel ist, sowohl die bereits getane Arbeit so gut wie möglich zu nutzen und sicherzustellen, dass Texte, die eingemeißelt sind, auf eine Weise behandelt werden, die mit der für andere Texte vereinbar ist, und sie nicht ausgrenzt. Die EpiDoc-Anpassung entfernt irrelevante Elemente aus dem Corpus der TEI und fügt Bestimmungen für bestimmte Arten der Transkription, Analyse, Beschreibung und Klassifizierung hinzu, die für epigraphische Arbeit von Bedeutung sind. Das Ergebnis ist eine einfache, und doch ausdrucksstarke Sprache, die verwendet werden kann, um alle Eigenschaften von Inschriften auszuzeichnen und auch die begleitenden Informationen über das epigraphische Objekt selbst wiederzugeben.

                                      Als Ergänzung zur EpiDoc-Kodierungssprache produzierte die EpiDoc-Gemeinschaft eine Sammlung von Kodierungsrichtlinien (Guidelines) und Software-Tools, sowie Aufzeichnungen, die beschreiben, wie die Kodierungssprache, die Tools und die anderen Elemente der EpiDoc-Methodik anzuwenden sind. Das Ziel ist es, einen Referenzrahmen zu etablieren, der leicht zu erlernen und zu nutzen ist, sogar für Wissenschaftler, die kein technisches Hintergrundwissen oder Unterstützung haben. Das mag unwahrscheinlich klingen, aber das Unternehmen hat denselben Stellenwert wie das Erlernen der Auszeichnung eines epigraphischen Textes mit der vorhandenen Reihe an Siglen.

                                      Die Gruppe arbeitet daran, Ausdrücke für alle vereinbarten epigraphischen Konventionen zu entwickeln. Sie erweiterte diese Anleitung, um verschiedene Bereiche anzusprechen, die in einer epigraphischen Publikation wiedergegeben werden könnten, unter anderem:

                                      Siehe auch: Dokumentstruktur (Document Structure).

                                      Ein weiterer Bereich, der gegenwärtig erkundet wird, ist die Entwicklung von Kompatibilität. Ein Software-Tool für die Umwandlung von Texten in normalem epigraphischen Markup in EpiDoc-XML wurde bereits entwickelt (der sogenannte Chapel Hill Electronic Text Converter (CHETC)). Andere Bereiche beziehen sich auf den Gebrauch autoritativer Lexika. Beispielsweise arbeitet das Projekt Inschriften von Aphrodisias (Inscriptions of Aphrodisias) eng mit dem Lexikon für Eigennamen (Lexicon of Greek Personal Names) zusammen, um volle Erfassung und einheitlichen Gebrauch zu gewährleisten.

                                      Die Arbeit unter der Leitung von Dr. Elliott wurde von zahlreichen Wissenschaftlern unternommen, die eng zusammenarbeiten und in regelmäßigem Kontakt mit dem weiteren Berufskreis stehen. Sie haben die Erfahrungen eines etablierten EpiDoc-Projekts, Vindolanda Tablets on line, und zweier neuer Projekte genutzt: Das USA Epigraphik Projekt (US Epigraphy Project (USEP)), unterstützt von den Universitäten Brown, Princeton und Rutgers, und das Projekt Inschriften von Aphrodisias (Inscriptions of Aphrodisias Project (InsAph)) (unterstützt durch den Forschungsrat der Geisteswissenschaften (Arts and Humanities Research Council)). Die großzügige Unterstützung des AHRC erlaubte den Intensivworkshop im März 2006, auf dem diese Richtlinien verbessert wurden.

                                      Verantwortlich für diesen Abschnitt

                                      1. Charlotte Roueché, Autorin
                                      2. Julia Flanders, Autorin
                                      3. Laura Löser, Übersetzung aus dem Englischen
                                      4. Tom Elliott, Umwandlung aus TEI-Lite und verschiedene Reformatierungsänderungen
                                      5. Gabriel Bodard, Korrigiert einige Links

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-es.html b/gl/dev/intro-eps-es.html index 9e419a193..80ed85091 100644 --- a/gl/dev/intro-eps-es.html +++ b/gl/dev/intro-eps-es.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Primera introducción al marcaje para epigrafistas

                                      2023-04-27

                                      Los principios sobre los que se sustenta el sistema EpiDoc reúnen convenciones y métodos de edición tradicionales y modernos para epigrafistas.

                                      Las convenciones epigráficas

                                      A lo largo del último siglo, los epigrafistas han batallado con los problemas derivados de la representación de información no verbal en sus textos. Hasta finales del siglo XIX, los editores elaboraban una edición diplomática del texto acompañada por una representación gráfica de la pieza, práctica que, sin embargo, se volvió cada vez más infrecuente. Por otra parte, las casas editoriales se mostraron reacias a publicar una o más imágenes por cada epígrafe, lo que implicó una considerable pérdida de información. Las convenciones para indicar texto perdido, abreviaturas, etc., fueron desarrolladas con gran esfuerzo, solapándose, hasta cierto punto, con las utilizadas en papirología y paleografía. Sobre su uso, y si bien existe común acuerdo entre los investigadores desde la década de 1930, todos los epigrafistas han tenido que lidiar con los problemas que conlleva trasladar las convenciones a medios electrónicos (por ejemplo, encontrar una fuente que permita añadir puntos bajo las letras), aunque muchos de nosotros ya nos hemos adaptado a estos nuevos inconvenientes.

                                      La dificultad de transmitir estas convenciones y, en particular, la complejidad de representar los caracteres griegos en la web, ha provocado un retraso en la publicación de corpora completos en línea. En su lugar, han sido creadas bases de datos enormemente ricas, entre las que destacan:

                                      Véase también: Conformance (EpiDoc Compatibility).

                                      Todos estos logros han estado condicionados, por tanto, por el estado de las tecnologías existentes y su evolución a lo largo del siglo XX. Objetivo de EpiDoc es explotar las nuevas tecnologías en aras de alcanzar los propósitos tradicionales de la epigrafía. Por ello, muchos de los procesos arriba descritos han supuesto una lucha contra las limitaciones tecnológicas (por ejemplo, en publicaciones impresas) con el propósito de responder al mayor número posible de exigencias de carácter epigráfico. Durante este periodo, y a menos que se asumiesen elevados costes, resultaba cada vez más complicado convencer a las editoriales tradicionales para que aceptasen las condiciones relativas a la inserción de información meta-textual. De forma simultánea, las expectativas con respecto al volumen de información que debería acompañar al texto han aumentado enormemente: además de la información relativa a los aspectos formales, lo normal es añadir una reproducción fotográfica.

                                      En los últimos 15 años, los investigadores se han enfrentado, por lo general, a problemas similares en lo referente a la incorporación de meta-datos dentro de textos en formato electrónico, surgiendo así herramientas que simplifican cada vez más esta labor y que, a la vez, revalorizan los resultados. Los procesadores de textos, habituales desde la década de 1980, nos permiten controlar el formato de los escritos utilizando una señalización que, en la actualidad, es insertada automáticamente por el propio software. A partir de 1980, la mayor exigencia en las necesidades técnicas por parte de vastas colecciones documentales (escritos legales, documentación industrial, publicaciones comerciales,...) conllevaron la investigación de nuevas formas de inserción de un amplio repertorio de características e instrucciones. Al principio, se hizo especial hincapié en insertar órdenes de formateo, aunque pronto surgieron métodos para incluir información semántica más compleja en lo que a la estructura del documento y a su contenido se refiere. Un sencillo ejemplo de esto sería el señalar un título de libro como título, en lugar de destacarlo en cursiva. Así, el uso más abstracto de una señalización permite establecer una separación entre estructura y presentación, donde la estructura es propia al género del documento, mientras que la presentación puede variar dependiendo de la forma de publicación. En cierto modo, pues, este cambio representa un retorno al estadio anterior, en el cual los autores trataban con la sustancia del texto y todos los detalles de presentación se solucionaban durante el proceso de publicación, distinción que se ha perdido con la llegada de los sistemas de reproducción fotográfica.

                                      Los protocolos surgidos de este último esfuerzo se estandarizaron a finales de los años ochenta bajo la denominación Standard Generalized Markup Language, si bien recientemente se les ha dado una forma más sencilla y flexible para su uso en la web, conocida como XML: Extensible Markup Language. Hoy en día, el XML es utilizado frecuentemente por los expertos en un gran número de disciplinas humanísticas para recopilar, representar y conservar materiales de investigación empleados con multitud de propósitos.

                                      Los atractivos del XML para los epigrafistas son, por consiguiente, considerables. Por ejemplo, es posible señalar el texto perdido como tal, para luego presentarlo entre corchetes. Al mismo tiempo, es posible hacer una búsqueda sobre texto que no ha sido señalado como perdido (es decir, sólo sobre términos atestiguados). Las letras inciertas también pueden señalarse como tales, y decidir en otro momento si editarlas con un punto debajo o de otro modo. Durante la edición, es posible además seleccionar palabras como términos de búsqueda, lo cual permite crear índices que aumentan de forma simultánea al incremento de la propia colección. Sin embargo, en las condiciones actuales, lo esencial sería emular las ‘convenciones de Leiden’, es decir, acordar los equivalentes electrónicos de los distintos signos diacríticos usados. En primer lugar, este gesto resultaría extremadamente útil no sólo por el ahorro de tiempo y trabajo; sino también, por el hecho de ofrecer una homologación coherente (aunque exenta de uniformidad). No son pocas las ventajas: por un lado, el sistema expone la información al usuario igual que una página impresa; mientras que por el otro, los documentos editados de este modo y publicados en formato electrónico pueden ser utilizados de forma conjunta con posterioridad, aunque hayan sido preparados separadamente por diferentes equipos.

                                      La necesidad de acordar estándares no se limita a la epigrafía. Desde 1987, un grupo internacional de investigadores (principalmente del ámbito de las humanidades), han unido esfuerzos para desarrollar y refinar un conjunto de guías para describir la estructura y el contenido de los documentos. Los resultados de esta labor se han plasmado en la producción de un lenguaje de codificación realizado en XML, y denominado como el propio grupo: TEI, o Text Encoding Initiatve.

                                      TEI para epigrafistas: ¿qué es? y ¿por qué usarlo?

                                      La Text Encoding Iniciative (TEI) es un trabajo de investigación destinado a definir un lenguaje de codificación que englobe, de forma general, las necesidades de los investigadores de humanidades. Dos propósitos fundamentales motivan el desarrollo de TEI. El primero de ellos es permitir a los investigadores la transcripción de sus textos en formato digital, usando un lenguaje descriptivo que refleje los diferentes términos y conceptos analíticos, usuales y necesarios en las disciplinas de humanidades. El segundo objetivo es permitir a los investigadores compartir sus resultados con la comunidad científica de forma inteligible, usando para ello un lenguaje descriptivo común.

                                      Podemos pensar en el lenguaje de codificación TEI como algo parecido al lenguaje humano: un núcleo de términos comunes en el centro, rodeado por un vocabulario menos difundido, como localismos, términos especializados, y otras variantes. En el centro de TEI están los términos y conceptos comunes empleados por investigadores procedentes de un gran número de disciplinas: elementos como párrafos, divisores de textos, encabezamientos, listas, etc. Otros elementos más especializados se agrupan conjuntamente de acuerdo a sus funciones: por ejemplo, signos para la codificación detallada de nombres, signos para representar las características de un manuscrito, signos para reproducir la estructura de diccionarios, etc. TEI está intencionalmente organizada de esta forma, en módulos, para que los investigadores que trabajen en áreas específicas de conocimiento puedan emplear únicamente los componentes relativos a su trabajo, omitiendo el resto. TEI puede, por tanto, ofrecer una gran libertad de trabajo sin abrumar a los investigadores o a los proyectos con la necesidad de aprender vastos conocimientos, la mayor parte de los cuales resultan pertinentes sólo a ciertas disciplinas. Así, el sistema TEI de codificación del lenguaje puede ser enfocado de forma directa a un ámbito o tarea específica, limitándose a un aspecto concreto y esencial de un proyecto.

                                      Como un lenguaje humano, TEI puede utilizarse de forma extensa, empleando un vocabulario rico y lleno de matices, con una codificación detallada que permita describir diferentes fenómenos textuales; aunque también puede utilizarse de forma sencilla, empleando sólo conceptos esenciales que representen exclusivamente elementos textuales básicos: secciones, encabezamientos y párrafos. Cuanto más detallada sea la codificación, más posibilidades de tratamiento existen; aunque factores como el tiempo, los costes, el personal disponible y la experiencia particular pueden limitar el nivel de codificación.

                                      Además de proveer de un sistema de codificación que los investigadores puedan usar en su forma original, TEI puede ser ajustada por los propios proyectos de investigación, creando versiones “a medida”, que respondan a necesidades específicas. Como estas versiones particulares de TEI operan dentro del marco general del sistema, no es necesario reinventar el núcleo común: estas pueden emplear un amplio repertorio de términos y conceptos, evitando la innecesaria labor de crearlos. Por otra parte, y como TEI ofrece un marco común para crear y describir versiones particulares, estas pueden ser compartidas de forma sencilla y plenamente significativa. Así, y aunque procedentes de diversas disciplinas, los grupos de investigación pueden expresar con claridad los objetivos y métodos que caracterizan su trabajo, y las diferencias que los distinguen de otros, pese a proceder de áreas afines. En lugar de emplear enfoques ininteligibles, diversos proyectos de investigación pueden producir resultados cuyas diferencias sean el resultado de desacuerdos reales, más que de divergencias fortuitas.

                                      EpiDoc personalizado: TEI para epigrafistas.

                                      Dentro de este marco general y desde el año 2000, la comunidad EpiDoc ha estado trabajando para desarrollar una versión específica de las normas TEI, con el objetivo de apoyar las necesidades propias de los epigrafistas. La idea fue promovida por Tom Elliott, un historiador de la antigüedad de la Universidad de Carolina del Norte (campus de Chapel Hill), con un doble propósito: explotar al máximo los beneficios del trabajo ya realizado y asegurar que los epígrafes se trataban de la forma más próxima posible a como se trataban otro tipo de textos. Así, EpiDoc elimina elementos irrelevantes del núcleo de TEI, añadiendo los componentes necesarios para los tipos específicos de transcripción, análisis, descripción y clasificación, esenciales para el trabajo epigráfico. El resultado es, simplemente, un lenguaje todavía más potente, que puede ser empleado para señalar todas las características de las inscripciones y también para representar la información relativa al objeto que porta el epígrafe.

                                      Para acompañar el lenguaje de codificación EpiDoc, la comunidad EpiDoc ha creado también una serie de líneas maestras y herramientas de software, así como documentación que describe cómo usar el lenguaje de codificación, los instrumentos y el resto de elementos del método EpiDoc. El propósito es establecer un marco general fácil de aprender y de usar, incluso por parte de investigadores que carezcan de una experiencia y/o asistencia de carácter técnico. Aunque pueda parecer improbable, la labor es en realidad similar al aprendizaje de la edición de un epígrafe estándar con los signos existentes.

                                      El grupo ha trabajado para tratar de representar todas las convenciones epigráficas en uso, ampliando la guía para abordar los varios aspectos que deben ser representados en una publicación de carácter epigráfico, incluyendo:

                                      Véase también: Estructura del documento.

                                      Actualmente, existen otras áreas en estudio, como aquellas relativas al desarrollo de la interoperabilidad. Así, se ha desarrollado una herramienta de software destinada a convertir textos editados según el sistema tradicional epigráfico en EpiDoc XML, el llamado Chapel Hill Electronic Text Converter (CHETC). Otras áreas incluyen el uso de léxicos especializados. Por ejemplo, el proyecto de las inscripciones de Aphrodisias está trabajando estrechamente con el Lexicon of Greek Personal Names, con el objetivo de garantizar la documentación exhaustiva y conforme a las normas en uso del mismo.

                                      La labor, dirigida por el Dr. Elliott, ha sido asumida por diferentes investigadores que trabajan en estrecha colaboración, manteniendo además un contacto regular con el resto de profesionales. El equipo se ha beneficiado de las ventajas de un proyecto EpiDoc ya consolidado, las Vindolanda Tablets on line, y de otros dos proyectos que se encuentran actualmente en curso: el US Epigraphy Project (USEP) (con el apoyo de las universidades de Brown, Princeton y Rutgers), y el Inscriptions of Aphrodisias Project (InsAph) (con el apoyo del Arts and Humanities Research Council). De hecho, el generoso apoyo de AHRC permitió celebrar un workshop intensivo en Marzo de 2006, donde fue perfeccionada la presente guía.

                                      Responsibility for this section

                                      1. Charlotte Roueché, author
                                      2. Julia Flanders, author
                                      3. Núria Garcia Casacuberta, traducido al español
                                      4. Celia Sánchez Natalías, traducido al español
                                      5. Tom Elliott, coerced from TEI-Lite and various reformatting edits
                                      6. Gabriel Bodard, tagged and updated links

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Primera introducción al marcaje para epigrafistas

                                      2024-03-05

                                      Los principios sobre los que se sustenta el sistema EpiDoc reúnen convenciones y métodos de edición tradicionales y modernos para epigrafistas.

                                      Las convenciones epigráficas

                                      A lo largo del último siglo, los epigrafistas han batallado con los problemas derivados de la representación de información no verbal en sus textos. Hasta finales del siglo XIX, los editores elaboraban una edición diplomática del texto acompañada por una representación gráfica de la pieza, práctica que, sin embargo, se volvió cada vez más infrecuente. Por otra parte, las casas editoriales se mostraron reacias a publicar una o más imágenes por cada epígrafe, lo que implicó una considerable pérdida de información. Las convenciones para indicar texto perdido, abreviaturas, etc., fueron desarrolladas con gran esfuerzo, solapándose, hasta cierto punto, con las utilizadas en papirología y paleografía. Sobre su uso, y si bien existe común acuerdo entre los investigadores desde la década de 1930, todos los epigrafistas han tenido que lidiar con los problemas que conlleva trasladar las convenciones a medios electrónicos (por ejemplo, encontrar una fuente que permita añadir puntos bajo las letras), aunque muchos de nosotros ya nos hemos adaptado a estos nuevos inconvenientes.

                                      La dificultad de transmitir estas convenciones y, en particular, la complejidad de representar los caracteres griegos en la web, ha provocado un retraso en la publicación de corpora completos en línea. En su lugar, han sido creadas bases de datos enormemente ricas, entre las que destacan:

                                      Véase también: Conformance (EpiDoc Compatibility).

                                      Todos estos logros han estado condicionados, por tanto, por el estado de las tecnologías existentes y su evolución a lo largo del siglo XX. Objetivo de EpiDoc es explotar las nuevas tecnologías en aras de alcanzar los propósitos tradicionales de la epigrafía. Por ello, muchos de los procesos arriba descritos han supuesto una lucha contra las limitaciones tecnológicas (por ejemplo, en publicaciones impresas) con el propósito de responder al mayor número posible de exigencias de carácter epigráfico. Durante este periodo, y a menos que se asumiesen elevados costes, resultaba cada vez más complicado convencer a las editoriales tradicionales para que aceptasen las condiciones relativas a la inserción de información meta-textual. De forma simultánea, las expectativas con respecto al volumen de información que debería acompañar al texto han aumentado enormemente: además de la información relativa a los aspectos formales, lo normal es añadir una reproducción fotográfica.

                                      En los últimos 15 años, los investigadores se han enfrentado, por lo general, a problemas similares en lo referente a la incorporación de meta-datos dentro de textos en formato electrónico, surgiendo así herramientas que simplifican cada vez más esta labor y que, a la vez, revalorizan los resultados. Los procesadores de textos, habituales desde la década de 1980, nos permiten controlar el formato de los escritos utilizando una señalización que, en la actualidad, es insertada automáticamente por el propio software. A partir de 1980, la mayor exigencia en las necesidades técnicas por parte de vastas colecciones documentales (escritos legales, documentación industrial, publicaciones comerciales,...) conllevaron la investigación de nuevas formas de inserción de un amplio repertorio de características e instrucciones. Al principio, se hizo especial hincapié en insertar órdenes de formateo, aunque pronto surgieron métodos para incluir información semántica más compleja en lo que a la estructura del documento y a su contenido se refiere. Un sencillo ejemplo de esto sería el señalar un título de libro como título, en lugar de destacarlo en cursiva. Así, el uso más abstracto de una señalización permite establecer una separación entre estructura y presentación, donde la estructura es propia al género del documento, mientras que la presentación puede variar dependiendo de la forma de publicación. En cierto modo, pues, este cambio representa un retorno al estadio anterior, en el cual los autores trataban con la sustancia del texto y todos los detalles de presentación se solucionaban durante el proceso de publicación, distinción que se ha perdido con la llegada de los sistemas de reproducción fotográfica.

                                      Los protocolos surgidos de este último esfuerzo se estandarizaron a finales de los años ochenta bajo la denominación Standard Generalized Markup Language, si bien recientemente se les ha dado una forma más sencilla y flexible para su uso en la web, conocida como XML: Extensible Markup Language. Hoy en día, el XML es utilizado frecuentemente por los expertos en un gran número de disciplinas humanísticas para recopilar, representar y conservar materiales de investigación empleados con multitud de propósitos.

                                      Los atractivos del XML para los epigrafistas son, por consiguiente, considerables. Por ejemplo, es posible señalar el texto perdido como tal, para luego presentarlo entre corchetes. Al mismo tiempo, es posible hacer una búsqueda sobre texto que no ha sido señalado como perdido (es decir, sólo sobre términos atestiguados). Las letras inciertas también pueden señalarse como tales, y decidir en otro momento si editarlas con un punto debajo o de otro modo. Durante la edición, es posible además seleccionar palabras como términos de búsqueda, lo cual permite crear índices que aumentan de forma simultánea al incremento de la propia colección. Sin embargo, en las condiciones actuales, lo esencial sería emular las ‘convenciones de Leiden’, es decir, acordar los equivalentes electrónicos de los distintos signos diacríticos usados. En primer lugar, este gesto resultaría extremadamente útil no sólo por el ahorro de tiempo y trabajo; sino también, por el hecho de ofrecer una homologación coherente (aunque exenta de uniformidad). No son pocas las ventajas: por un lado, el sistema expone la información al usuario igual que una página impresa; mientras que por el otro, los documentos editados de este modo y publicados en formato electrónico pueden ser utilizados de forma conjunta con posterioridad, aunque hayan sido preparados separadamente por diferentes equipos.

                                      La necesidad de acordar estándares no se limita a la epigrafía. Desde 1987, un grupo internacional de investigadores (principalmente del ámbito de las humanidades), han unido esfuerzos para desarrollar y refinar un conjunto de guías para describir la estructura y el contenido de los documentos. Los resultados de esta labor se han plasmado en la producción de un lenguaje de codificación realizado en XML, y denominado como el propio grupo: TEI, o Text Encoding Initiatve.

                                      TEI para epigrafistas: ¿qué es? y ¿por qué usarlo?

                                      La Text Encoding Iniciative (TEI) es un trabajo de investigación destinado a definir un lenguaje de codificación que englobe, de forma general, las necesidades de los investigadores de humanidades. Dos propósitos fundamentales motivan el desarrollo de TEI. El primero de ellos es permitir a los investigadores la transcripción de sus textos en formato digital, usando un lenguaje descriptivo que refleje los diferentes términos y conceptos analíticos, usuales y necesarios en las disciplinas de humanidades. El segundo objetivo es permitir a los investigadores compartir sus resultados con la comunidad científica de forma inteligible, usando para ello un lenguaje descriptivo común.

                                      Podemos pensar en el lenguaje de codificación TEI como algo parecido al lenguaje humano: un núcleo de términos comunes en el centro, rodeado por un vocabulario menos difundido, como localismos, términos especializados, y otras variantes. En el centro de TEI están los términos y conceptos comunes empleados por investigadores procedentes de un gran número de disciplinas: elementos como párrafos, divisores de textos, encabezamientos, listas, etc. Otros elementos más especializados se agrupan conjuntamente de acuerdo a sus funciones: por ejemplo, signos para la codificación detallada de nombres, signos para representar las características de un manuscrito, signos para reproducir la estructura de diccionarios, etc. TEI está intencionalmente organizada de esta forma, en módulos, para que los investigadores que trabajen en áreas específicas de conocimiento puedan emplear únicamente los componentes relativos a su trabajo, omitiendo el resto. TEI puede, por tanto, ofrecer una gran libertad de trabajo sin abrumar a los investigadores o a los proyectos con la necesidad de aprender vastos conocimientos, la mayor parte de los cuales resultan pertinentes sólo a ciertas disciplinas. Así, el sistema TEI de codificación del lenguaje puede ser enfocado de forma directa a un ámbito o tarea específica, limitándose a un aspecto concreto y esencial de un proyecto.

                                      Como un lenguaje humano, TEI puede utilizarse de forma extensa, empleando un vocabulario rico y lleno de matices, con una codificación detallada que permita describir diferentes fenómenos textuales; aunque también puede utilizarse de forma sencilla, empleando sólo conceptos esenciales que representen exclusivamente elementos textuales básicos: secciones, encabezamientos y párrafos. Cuanto más detallada sea la codificación, más posibilidades de tratamiento existen; aunque factores como el tiempo, los costes, el personal disponible y la experiencia particular pueden limitar el nivel de codificación.

                                      Además de proveer de un sistema de codificación que los investigadores puedan usar en su forma original, TEI puede ser ajustada por los propios proyectos de investigación, creando versiones “a medida”, que respondan a necesidades específicas. Como estas versiones particulares de TEI operan dentro del marco general del sistema, no es necesario reinventar el núcleo común: estas pueden emplear un amplio repertorio de términos y conceptos, evitando la innecesaria labor de crearlos. Por otra parte, y como TEI ofrece un marco común para crear y describir versiones particulares, estas pueden ser compartidas de forma sencilla y plenamente significativa. Así, y aunque procedentes de diversas disciplinas, los grupos de investigación pueden expresar con claridad los objetivos y métodos que caracterizan su trabajo, y las diferencias que los distinguen de otros, pese a proceder de áreas afines. En lugar de emplear enfoques ininteligibles, diversos proyectos de investigación pueden producir resultados cuyas diferencias sean el resultado de desacuerdos reales, más que de divergencias fortuitas.

                                      EpiDoc personalizado: TEI para epigrafistas.

                                      Dentro de este marco general y desde el año 2000, la comunidad EpiDoc ha estado trabajando para desarrollar una versión específica de las normas TEI, con el objetivo de apoyar las necesidades propias de los epigrafistas. La idea fue promovida por Tom Elliott, un historiador de la antigüedad de la Universidad de Carolina del Norte (campus de Chapel Hill), con un doble propósito: explotar al máximo los beneficios del trabajo ya realizado y asegurar que los epígrafes se trataban de la forma más próxima posible a como se trataban otro tipo de textos. Así, EpiDoc elimina elementos irrelevantes del núcleo de TEI, añadiendo los componentes necesarios para los tipos específicos de transcripción, análisis, descripción y clasificación, esenciales para el trabajo epigráfico. El resultado es, simplemente, un lenguaje todavía más potente, que puede ser empleado para señalar todas las características de las inscripciones y también para representar la información relativa al objeto que porta el epígrafe.

                                      Para acompañar el lenguaje de codificación EpiDoc, la comunidad EpiDoc ha creado también una serie de líneas maestras y herramientas de software, así como documentación que describe cómo usar el lenguaje de codificación, los instrumentos y el resto de elementos del método EpiDoc. El propósito es establecer un marco general fácil de aprender y de usar, incluso por parte de investigadores que carezcan de una experiencia y/o asistencia de carácter técnico. Aunque pueda parecer improbable, la labor es en realidad similar al aprendizaje de la edición de un epígrafe estándar con los signos existentes.

                                      El grupo ha trabajado para tratar de representar todas las convenciones epigráficas en uso, ampliando la guía para abordar los varios aspectos que deben ser representados en una publicación de carácter epigráfico, incluyendo:

                                      Véase también: Estructura del documento.

                                      Actualmente, existen otras áreas en estudio, como aquellas relativas al desarrollo de la interoperabilidad. Así, se ha desarrollado una herramienta de software destinada a convertir textos editados según el sistema tradicional epigráfico en EpiDoc XML, el llamado Chapel Hill Electronic Text Converter (CHETC). Otras áreas incluyen el uso de léxicos especializados. Por ejemplo, el proyecto de las inscripciones de Aphrodisias está trabajando estrechamente con el Lexicon of Greek Personal Names, con el objetivo de garantizar la documentación exhaustiva y conforme a las normas en uso del mismo.

                                      La labor, dirigida por el Dr. Elliott, ha sido asumida por diferentes investigadores que trabajan en estrecha colaboración, manteniendo además un contacto regular con el resto de profesionales. El equipo se ha beneficiado de las ventajas de un proyecto EpiDoc ya consolidado, las Vindolanda Tablets on line, y de otros dos proyectos que se encuentran actualmente en curso: el US Epigraphy Project (USEP) (con el apoyo de las universidades de Brown, Princeton y Rutgers), y el Inscriptions of Aphrodisias Project (InsAph) (con el apoyo del Arts and Humanities Research Council). De hecho, el generoso apoyo de AHRC permitió celebrar un workshop intensivo en Marzo de 2006, donde fue perfeccionada la presente guía.

                                      Responsibility for this section

                                      1. Charlotte Roueché, author
                                      2. Julia Flanders, author
                                      3. Núria Garcia Casacuberta, traducido al español
                                      4. Celia Sánchez Natalías, traducido al español
                                      5. Tom Elliott, coerced from TEI-Lite and various reformatting edits
                                      6. Gabriel Bodard, tagged and updated links

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-fi.html b/gl/dev/intro-eps-fi.html index 3dad7c9ab..7a3a37be8 100644 --- a/gl/dev/intro-eps-fi.html +++ b/gl/dev/intro-eps-fi.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Kevyt johdatus EpiDoc-merkintäkieleen epigraafikoille

                                      2023-04-27

                                      EpiDoc yhdistää perinteiset ja täysin uudet piirtokirjoitusten editointimenetelmät ja -tavat.

                                      Epigrafinen merkintätapa

                                      Viimeisen vuosisadan ajan piirtokirjoitustutkijat ovat saaneet painia sen kanssa, kuinka esittää tutkimuksen kohteena oleviin kirjoitettuihin teksteihin liittyvä ei-kielellinen tieto. Aina 1800-luvun lopulle saakka kustantajien saatettiin edellyttää painavan piirtokirjoitustekstistä näköispainoksen. Tämä tapa on kuitenkin jäänyt miltei tyystin käytöstä, eivätkä kustantajat ole osoittaneet vastaavaa halukkuutta liittää julkaisuihin täydellistä valokuvakokoelmaa, joka sisältäisi jokaisen julkaisussa käsitellyn piirtokirjoitustekstin. Merkintätapa, joka luotiin kertomaan puuttuvasta tekstistä, lyhenteistä jne., on tullut enemmän tai vähemmän yleisesti hyväksytyksi 1930-luvulta alkaen ja on jossakin määrin päällekkäinen papyrologiassa ja paleografiassa käytetyn kanssa. Jokainen piirtokirjoitustutkija joutuu käsittelemään ongelmia, jotka syntyvät siirrettäessä merkintätapaan liittyviä seikkoja sähköiseen muotoon, esimerkiksi etsimään fontit, joihin voi liittää alapisteen. Useimmat meistä ovat kuitenkin nykyään sopeutuneet näihin uusiin rajoitteisiin.

                                      Kokonaisten piirtokirjoituseditioiden verkkojulkaisemista on hidastanut vaikeudet merkintätavan esittämisessä internet-ympäristössä. Lisäksi ongelmana on ollut kreikan kirjaimiston tuottaminen yhdenmukaisesti ja ominaisuutensa säilyttäen. Sen sijaan on syntynyt huomattavan runsaita hakukokoelmia, joista mainittakoon:

                                      Katso myös: Mukauttaminen (EpiDoc -yhteensopivuus).

                                      Teknologian kehittyminen 1900-luvun kuluessa ja sen kulloinkin tarjoamat menetelmät ovat vaikuttaneet ratkaisevasti yllämainittuihin muutoksiin. EpiDocin tavoite on hyödyntää uutta ja monimuotoista teknologiaa pyrittäessä piirtokirjoitustutkimuksen perinteisiin tavoitteisiin. Monet aiemmin mainituista seikoista ovat vaatineet taistelua olemassa olevien teknisten standardien kanssa esimerkiksi laadittaessa tekstiä painojulkaisuihin, jotta voisimme sisällyttää niihin mahdollisimman monta edellyttämäämme asiaa. Jo jonkin aikaa on tullut aina vain hankalammaksi saada perinteiset kustantajat taipumaan vaatimustasoomme yksityiskohtaisen taustatiedon liittämisessä piirtokirjoitusjulkaisuihin - paitsi kohtuuttoman korkein kustannuksin. Samalla odotukset siitä, kuinka paljon tietoa kustakin piirtokirjoitustekstistä tulisi tarjota, ovat kasvaneet huomattavasti. Yhtä lailla kuin selvitys kunkin piirtokirjoituksen materiaalisista yksityiskohdista, valokuvan liittämisestä piirtokirjoituseditioon on tullut normaali tapa.

                                      Viimeisten 15 vuoden aikana tutkijat ovat joutuneet kohtaamaan samoja ongelmia pyrkiessään liittämään taustatietoa sähköisessä muodossa työstettävien piirtokirjoitustekstien yhteyteen. Käyttöön on kuitenkin tullut työkaluja, jotka tekevät siitä aina vain helpompaa ja kasvattavat tulosten arvoa. 1980-luvulta lähtien tekstinkäsittelyohjelmat ovat tehneet mahdolliseksi sen, että voimme hallita tekstin muokkausta. Niissä käytetty merkintäkieli on nykyisin upotettu näkymättömiin ohjelmien sisään. Laajojen oikeusasioihin, teollisuuteen ja kaupalliseen julkaisutoimintaan liittyvien dokumenttikokoelmien asettamat suuremmat vaatimukset johtivat 1980-luvulla tutkimuksiin tavoista, joilla sisällyttää suurempi määrä tietoa ja ohjeita sähköisessä muodossa oleviin teksteihin. Aluksi keskityttiin lisäämään muotoiluohjeita, mutta monimutkaisemman, dokumentin rakenteeseen ja jopa sisältöön liittyvän semanttisen tiedon sisällyttäminen kehittyi pian. Yksinkertaisena esimerkkinä voidaan mainita kirjan otsikon merkitseminen otsikoksi sen sijaan, että se merkittäisiin vain kursiivilla kirjoitetuksi. Tässä abstraktimmassa merkintäkielessä on mahdollista tehdä ero rakenteen ja ulkoasun välillä. Rakenne on tekstilajin keskeinen ominaisuus kun taas ulkoasu voi vaihdella julkaisumuodosta riippuen. Tavallaan tämä muutos on paluuta aikaisempaan tapaan, jolloin kirjoittaja keskittyi tekstin sisältöön, kun taas kaikki tekstin ulkoasua koskevat seikat hoidettiin painatusprosessissa - ero, joka on ollut kadoksissa näinä painovalmiiden käsikirjoitusten päivinä.

                                      Protokolla, joka syntyi näistä viimeksi mainituista aikaansaannoksista, standardoitiin 1980-luvun lopulla nimellä Standard Generalized Markup Language. Hieman myöhemmin siitä tehtiin yksinkertaisempi ja joustavampi versio verkkokäyttöä varten. Tämä tunnetaan nimellä XML: the Extensible Markup Language. Monenlaisten humanististen oppiaineiden tutkijat käyttävät XML-merkintäkieltä hyvinkin laajalti erilaisten tutkimusaineistojen tallentamiseen/esittämiseen ja säilyttämiseen useita eri tarkoituksia varten.

                                      XML on tavattoman kiinnostava piirtokirjoitustutkijan näkökulmasta. Esimerkiksi puuttuva tekstiosa voidaan merkitä sellaiseksi ja esittää sitten kulmasulkeiden sisässä; samalla tekstiin kohdistuva haku voidaan ohjata tutkimaan vain sitä osaa tekstistä, jota ei ole merkitty puuttuvaksi (eli vain varmoiksi osoitettuja ilmauksia). Epävarmat kirjaimet voidaan merkitä sellaisina ja tehdä vasta myöhemmin päätös siitä, esittääkö ne alapisteen kanssa vai jollakin muulla tavalla. Sanaston perusmuodot voidaan merkitä jo editoinnin aikana hakemistoja varten. Tekstikokoelman kasvaessa hakemisto tekee samoin. Tärkeää on kuitenkin, että jatketaan Leidenin sopimuksen periaatteen tiellä, eli että sovimme mitkä digitaaliset käskyt vastaavat niitä merkintätapoja, joita muutoinkin käytämme. Sillä on merkitystä ensinnäkin siksi, että se yksinkertaisesti säästää aikaa ja vaivaa. Toisaalta yhdenmukaisuus, ilman samankaltaisuuden pakkoa, on yhä hyödyllistä. Käyttäjän on mahdollista tukeutua siihen aivan samoin kuin painettuja sivuja lukiessaan. Lisäksi tällä tavalla editoidut ja sähköisesti julkaistut aineistot ovat hyödynnettävissä yhdessä, vaikka ne olisi laadittu erikseen.

                                      Yhdessä sovittujen toimintamallien tarve ei rajoitu piirtokirjoitustutkimukseen. Vuodesta 1987 kansainvälinen, pääosin humanistisen alan tutkijoista koostuva yhteistyöryhmä on työskennellyt kehittäen ja hioen ohjeistoa dokumenttien rakenteen ja sisällön kuvaamiseen. Näiden pyrkimysten tuloksena on syntynyt XML-perustainen koodauskieli, johon liitetään myös em. ryhmän nimi TEI, Text Encoding Initiatve.

                                      TEI epigraafikoille: Mikä se on ja miksi käyttää sitä?

                                      TEI on tutkimushanke, jonka tavoite on määritellä koodauskieli, joka hyvin yleisluontoisesti kattaa humanistisen alan tutkijoiden tarpeet. TEI:n kehittämisessä on kaksi olennaista päämäärää. Ensimmäinen on suoda tutkijoille mahdollisuus esittää tutkimusaineistonsa digitaalisessa muodossa käyttäen sellaista kuvauskieltä, joka heijastaa humanististen alojen tutkimukselle ominaisia ja keskeisiä analyyttisiä termejä ja käsitteitä. Toinen päämäärä on tehdä mahdolliseksi se, että tutkijat voivat jakaa aikaansaamansa aineistot ymmärrettävästi käyttämällä yhteistä kuvauskieltä.

                                      Voimme ajatella, että TEI koodauskieli muistuttaa luonnollista kieltä: ytimenä sen keskellä on kaikille yhteinen termistö, sitä ympäröi vähemmän yleinen sanasto, joka koostuu paikallisista kielenkäyttötavoista, erikoissanastosta ja muista vastaavista muunnelmista. TEI:n ydintä ovat sellaiset yhteiset termit ja käsitteet, jotka ovat yhteisiä tutkijoille suurimmassa osassa oppiaineita, esimerkiksi kappale, yleinen tekstijako, otsikko, luettelo jne. Tarkemmin määritellyt elementit on ryhmitelty sovellusten mukaan, esimerkiksi elementit yksityiskohtaiseen nimien koodaukseen tai käsikirjoitusten piirteiden esittämiseen tai sanakirjarakenteen kuvaamiseen jne. TEI on tarkoituksella muotoiltu tällä tavalla moduuleiksi, jotta kunkin erikoisalan tutkija voisi käyttää vain niitä osioita, joita hän tarvitsee työssään, ja unohtaa muut. TEI voi tällä tavalla laajeta melkoisiin mittasuhteisiin ilman että se rasittaisi yksittäistä tutkijaa tai tutkimushanketta pakolla hallita valtavaa toiminta-aluetta, josta suurella osalla on merkitystä aivan toisen alan tutkijoille. Sen sijaan TEI koodauskieli voidaan kohdistaa hyvinkin täsmällisesti johonkin aiheeseen tai tehtävään ja rajoittaa vain siihen, mikä on olennaista projektin työssä.

                                      Kuten luonnollista kieltä TEI:tä voidaan käyttää laajan ja vivahteikkaan sanaston luomiseen pienempiinkin yksityiskohtiin ulottuvalla koodauksella, jossa tekstin ilmiöt on seikkaperäisesti kuvattu. Sitä voidaan soveltaa myös hyvin yksinkertaisesti käyttämällä vain muutamaa oleellista käsitettä kuvaamassa keskeisimpiä yksityiskohtia, esim. osiota, otsikkoa, kappaletta. Mitä yksityiskohtaisempi koodaus on, sitä enemmän työn lopputuloksella on käyttöä. Aika, kustannukset, saatavilla oleva työvoima sekä paikallinen erikoisosaaminen saattavat kuitenkin rajoittaa sitä, kuinka yksityiskohtaisena hanke on toteutettavissa.

                                      Tutkijat voivat käyttää tätä koodausjärjestelmää sellaisenaan sen alkuperäisessä muodossa. Sen ohella TEI tarjoaa eri tutkimusaloille mahdollisuuden muokata juuri niiden tarpeiden mukaan sovellettuja versioita TEI -kielestä. Koska nämä mittatilausversiot toimivat yleisessä TEI kehyksessä, ne voivat käyttää sen yleisiä ydintermejä ja käsitteitä ja näin välttää niiden turhaa uudelleenkeksimistä. Lisäksi, koska TEI tarjoaa yleisen kehyksen mittatilausversioiden luomiseen ja kuvaamiseen, niitä voidaan jakaa helposti ja tarkoituksenmukaisesti. Tämän tuloksena eri oppiaineiden tutkijat voivat korostaa omaa työtään luonnehtivia erityisiä päämääriään ja menetelmiään samoin kuin niitä seikkoja, jotka erottavat heidän työnsä toisista, jollakin tavalla heidän alaansa sivuavista. TEI:n piirissä eri tutkimushankkeet voivat esittää tuloksia, jotka aidosti eroavat toisistaan sen sijaan, että erot johtuisivat eri osapuolille käsittämättömien lähestymistapojen aiheuttamasta satunnaisesta ristiriidasta.

                                      Epigraafikoille räätälöity TEI: EpiDoc

                                      EpiDoc -yhteisö on työskennellyt edellä mainituissa puitteissa vuodesta 2000 kehittääkseen erityisesti piirtokirjoitustutkijoiden tarpeisiin sovelletun version TEI:n ohjeistoista. Ajatuksen lanseerasi Pohjois-Carolinan yliopiston Chapel Hillin antiikin historian tutkija Tom Elliott. Tavoite on sekä hyödyntää mahdollisimman laajasti jo tehtyä tutkimustyötä että varmistaa, että piirtokirjoitustekstejä käsitellään samoin kuin muitakin tekstejä, eikä jollakin tavalla eroteltuina niistä. EpiDoc on muokattu poistamalla sille tarpeettomia TEI -elementtejä ja lisäämällä piirtokirjoitustutkimuksessa tarvittavia erityisominaisuuksia mm. transkriptioiden, analyysien, kuvauksien ja luokittelujen tekemiseen. Lopputuloksena on syntynyt yksinkertainen mutta tehokas kieli, jolla voidaan merkitä kaikki piirtokirjoituksissa ilmenevät huomionarvoiset piirteet sekä esittämään tekstien lisäksi myös monumentteihin ja piirtokirjoitusesineisiin liittyvät tiedot.

                                      EpiDoc koodauskielen rinnalle EpiDoc -yhteisö on luonut oppaan koodausta varten sekä ohjelmistotyökaluja ja ohjeistoa, joka kuvaa kuinka koodauskieltä, työkaluja ja muita EpiDoc -menetelmään liittyviä elementtejä käytetään. Tavoitteena on saada aikaan järjestelmä, joka on helppo oppia ja yksinkertainen käyttää myös ilman aiempaa teknistä taustaa tai teknistä tukea. Voi olla vaikea uskoa, mutta XML-koodin tuottaminen on yhtä helppoa kuin standardin piirtokirjoituksen merkitseminen jo olemassa olevan lyhennekokoelman kanssa.

                                      Ryhmä on työskennellyt kehittääkseen ilmaukset kaikille sovituille piirtokirjoitusten merkintätavoille. Ohjeistusta on laajennettu koskemaan myös monia muita piirteitä, joita piirtokirjoitusjulkaisuissa voi esiintyä, mm.

                                      Ks: Dokumentin rakenne.

                                      Muiden aktiivisen työn alla olevien aiheiden joukossa ovat mm. yhteensopivuuskysymykset. Ohjelmistotyökalu tavanomaisesti merkityn piirtokirjoitustekstin muuntamiseksi EpiDoc XML -merkintäkielelle on jo saatu aikaan (ns. Chapel Hill Electronic Text Converter (CHETC)). Toinen keskeinen teema on kattavan sanaston luominen. Esimerkiksi Afrodisiaksen piirtokirjoitustutkimushanke työskentelee kiinteästi Lexicon of Greek Personal Names-hankkeen kanssa saadakseen aikaan mahdollisimman kattavan ja yhdenmukaisesti käytettävän sanaston.

                                      Tätä työtä on johtanut Tom Elliott ja siihen ovat osallistuneet monet yksittäiset tutkijat tiiviissä yhteistyössä keskenään ja pitäen jatkuvasti yhteyttä laajempaan ammattiyhteisöön. Kehittäjät ovat saaneet kokemusta EpiDoc -projekteista, kuten Vindolanda Tablets on line, sekä kahdesta meneillään olevasta hankkeesta US Epigraphy Project (USEP) (jota rahoittavat yliopistot Brown, Princeton ja Rutgers), sekä Afrodisiaksen piirtokirjoitustutkimushanke (InsAph) (jota rahoittaa Arts and Humanities Research Council). AHRC:n runsaan rahoituksen turvin pidettiin marraskuussa 2006 intensiivinen työpaja, jossa nämä ohjeistot hiottiin nykyiseen muotoonsa.

                                      Osion vastuuhenkilöt

                                      1. Charlotte Roueché, kirjoittaja
                                      2. Julia Flanders, kirjoittaja
                                      3. Tom Elliott, muokkaus TEI-Lite:sta ja muita muokkauksia
                                      4. Gabriel Bodard, sääti ja päivitti monta linkkiä
                                      5. Katariina Kankaanpää, suomentaja
                                      6. Marja Vierros, suomentaja

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Kevyt johdatus EpiDoc-merkintäkieleen epigraafikoille

                                      2024-03-05

                                      EpiDoc yhdistää perinteiset ja täysin uudet piirtokirjoitusten editointimenetelmät ja -tavat.

                                      Epigrafinen merkintätapa

                                      Viimeisen vuosisadan ajan piirtokirjoitustutkijat ovat saaneet painia sen kanssa, kuinka esittää tutkimuksen kohteena oleviin kirjoitettuihin teksteihin liittyvä ei-kielellinen tieto. Aina 1800-luvun lopulle saakka kustantajien saatettiin edellyttää painavan piirtokirjoitustekstistä näköispainoksen. Tämä tapa on kuitenkin jäänyt miltei tyystin käytöstä, eivätkä kustantajat ole osoittaneet vastaavaa halukkuutta liittää julkaisuihin täydellistä valokuvakokoelmaa, joka sisältäisi jokaisen julkaisussa käsitellyn piirtokirjoitustekstin. Merkintätapa, joka luotiin kertomaan puuttuvasta tekstistä, lyhenteistä jne., on tullut enemmän tai vähemmän yleisesti hyväksytyksi 1930-luvulta alkaen ja on jossakin määrin päällekkäinen papyrologiassa ja paleografiassa käytetyn kanssa. Jokainen piirtokirjoitustutkija joutuu käsittelemään ongelmia, jotka syntyvät siirrettäessä merkintätapaan liittyviä seikkoja sähköiseen muotoon, esimerkiksi etsimään fontit, joihin voi liittää alapisteen. Useimmat meistä ovat kuitenkin nykyään sopeutuneet näihin uusiin rajoitteisiin.

                                      Kokonaisten piirtokirjoituseditioiden verkkojulkaisemista on hidastanut vaikeudet merkintätavan esittämisessä internet-ympäristössä. Lisäksi ongelmana on ollut kreikan kirjaimiston tuottaminen yhdenmukaisesti ja ominaisuutensa säilyttäen. Sen sijaan on syntynyt huomattavan runsaita hakukokoelmia, joista mainittakoon:

                                      Katso myös: Mukauttaminen (EpiDoc -yhteensopivuus).

                                      Teknologian kehittyminen 1900-luvun kuluessa ja sen kulloinkin tarjoamat menetelmät ovat vaikuttaneet ratkaisevasti yllämainittuihin muutoksiin. EpiDocin tavoite on hyödyntää uutta ja monimuotoista teknologiaa pyrittäessä piirtokirjoitustutkimuksen perinteisiin tavoitteisiin. Monet aiemmin mainituista seikoista ovat vaatineet taistelua olemassa olevien teknisten standardien kanssa esimerkiksi laadittaessa tekstiä painojulkaisuihin, jotta voisimme sisällyttää niihin mahdollisimman monta edellyttämäämme asiaa. Jo jonkin aikaa on tullut aina vain hankalammaksi saada perinteiset kustantajat taipumaan vaatimustasoomme yksityiskohtaisen taustatiedon liittämisessä piirtokirjoitusjulkaisuihin - paitsi kohtuuttoman korkein kustannuksin. Samalla odotukset siitä, kuinka paljon tietoa kustakin piirtokirjoitustekstistä tulisi tarjota, ovat kasvaneet huomattavasti. Yhtä lailla kuin selvitys kunkin piirtokirjoituksen materiaalisista yksityiskohdista, valokuvan liittämisestä piirtokirjoituseditioon on tullut normaali tapa.

                                      Viimeisten 15 vuoden aikana tutkijat ovat joutuneet kohtaamaan samoja ongelmia pyrkiessään liittämään taustatietoa sähköisessä muodossa työstettävien piirtokirjoitustekstien yhteyteen. Käyttöön on kuitenkin tullut työkaluja, jotka tekevät siitä aina vain helpompaa ja kasvattavat tulosten arvoa. 1980-luvulta lähtien tekstinkäsittelyohjelmat ovat tehneet mahdolliseksi sen, että voimme hallita tekstin muokkausta. Niissä käytetty merkintäkieli on nykyisin upotettu näkymättömiin ohjelmien sisään. Laajojen oikeusasioihin, teollisuuteen ja kaupalliseen julkaisutoimintaan liittyvien dokumenttikokoelmien asettamat suuremmat vaatimukset johtivat 1980-luvulla tutkimuksiin tavoista, joilla sisällyttää suurempi määrä tietoa ja ohjeita sähköisessä muodossa oleviin teksteihin. Aluksi keskityttiin lisäämään muotoiluohjeita, mutta monimutkaisemman, dokumentin rakenteeseen ja jopa sisältöön liittyvän semanttisen tiedon sisällyttäminen kehittyi pian. Yksinkertaisena esimerkkinä voidaan mainita kirjan otsikon merkitseminen otsikoksi sen sijaan, että se merkittäisiin vain kursiivilla kirjoitetuksi. Tässä abstraktimmassa merkintäkielessä on mahdollista tehdä ero rakenteen ja ulkoasun välillä. Rakenne on tekstilajin keskeinen ominaisuus kun taas ulkoasu voi vaihdella julkaisumuodosta riippuen. Tavallaan tämä muutos on paluuta aikaisempaan tapaan, jolloin kirjoittaja keskittyi tekstin sisältöön, kun taas kaikki tekstin ulkoasua koskevat seikat hoidettiin painatusprosessissa - ero, joka on ollut kadoksissa näinä painovalmiiden käsikirjoitusten päivinä.

                                      Protokolla, joka syntyi näistä viimeksi mainituista aikaansaannoksista, standardoitiin 1980-luvun lopulla nimellä Standard Generalized Markup Language. Hieman myöhemmin siitä tehtiin yksinkertaisempi ja joustavampi versio verkkokäyttöä varten. Tämä tunnetaan nimellä XML: the Extensible Markup Language. Monenlaisten humanististen oppiaineiden tutkijat käyttävät XML-merkintäkieltä hyvinkin laajalti erilaisten tutkimusaineistojen tallentamiseen/esittämiseen ja säilyttämiseen useita eri tarkoituksia varten.

                                      XML on tavattoman kiinnostava piirtokirjoitustutkijan näkökulmasta. Esimerkiksi puuttuva tekstiosa voidaan merkitä sellaiseksi ja esittää sitten kulmasulkeiden sisässä; samalla tekstiin kohdistuva haku voidaan ohjata tutkimaan vain sitä osaa tekstistä, jota ei ole merkitty puuttuvaksi (eli vain varmoiksi osoitettuja ilmauksia). Epävarmat kirjaimet voidaan merkitä sellaisina ja tehdä vasta myöhemmin päätös siitä, esittääkö ne alapisteen kanssa vai jollakin muulla tavalla. Sanaston perusmuodot voidaan merkitä jo editoinnin aikana hakemistoja varten. Tekstikokoelman kasvaessa hakemisto tekee samoin. Tärkeää on kuitenkin, että jatketaan Leidenin sopimuksen periaatteen tiellä, eli että sovimme mitkä digitaaliset käskyt vastaavat niitä merkintätapoja, joita muutoinkin käytämme. Sillä on merkitystä ensinnäkin siksi, että se yksinkertaisesti säästää aikaa ja vaivaa. Toisaalta yhdenmukaisuus, ilman samankaltaisuuden pakkoa, on yhä hyödyllistä. Käyttäjän on mahdollista tukeutua siihen aivan samoin kuin painettuja sivuja lukiessaan. Lisäksi tällä tavalla editoidut ja sähköisesti julkaistut aineistot ovat hyödynnettävissä yhdessä, vaikka ne olisi laadittu erikseen.

                                      Yhdessä sovittujen toimintamallien tarve ei rajoitu piirtokirjoitustutkimukseen. Vuodesta 1987 kansainvälinen, pääosin humanistisen alan tutkijoista koostuva yhteistyöryhmä on työskennellyt kehittäen ja hioen ohjeistoa dokumenttien rakenteen ja sisällön kuvaamiseen. Näiden pyrkimysten tuloksena on syntynyt XML-perustainen koodauskieli, johon liitetään myös em. ryhmän nimi TEI, Text Encoding Initiatve.

                                      TEI epigraafikoille: Mikä se on ja miksi käyttää sitä?

                                      TEI on tutkimushanke, jonka tavoite on määritellä koodauskieli, joka hyvin yleisluontoisesti kattaa humanistisen alan tutkijoiden tarpeet. TEI:n kehittämisessä on kaksi olennaista päämäärää. Ensimmäinen on suoda tutkijoille mahdollisuus esittää tutkimusaineistonsa digitaalisessa muodossa käyttäen sellaista kuvauskieltä, joka heijastaa humanististen alojen tutkimukselle ominaisia ja keskeisiä analyyttisiä termejä ja käsitteitä. Toinen päämäärä on tehdä mahdolliseksi se, että tutkijat voivat jakaa aikaansaamansa aineistot ymmärrettävästi käyttämällä yhteistä kuvauskieltä.

                                      Voimme ajatella, että TEI koodauskieli muistuttaa luonnollista kieltä: ytimenä sen keskellä on kaikille yhteinen termistö, sitä ympäröi vähemmän yleinen sanasto, joka koostuu paikallisista kielenkäyttötavoista, erikoissanastosta ja muista vastaavista muunnelmista. TEI:n ydintä ovat sellaiset yhteiset termit ja käsitteet, jotka ovat yhteisiä tutkijoille suurimmassa osassa oppiaineita, esimerkiksi kappale, yleinen tekstijako, otsikko, luettelo jne. Tarkemmin määritellyt elementit on ryhmitelty sovellusten mukaan, esimerkiksi elementit yksityiskohtaiseen nimien koodaukseen tai käsikirjoitusten piirteiden esittämiseen tai sanakirjarakenteen kuvaamiseen jne. TEI on tarkoituksella muotoiltu tällä tavalla moduuleiksi, jotta kunkin erikoisalan tutkija voisi käyttää vain niitä osioita, joita hän tarvitsee työssään, ja unohtaa muut. TEI voi tällä tavalla laajeta melkoisiin mittasuhteisiin ilman että se rasittaisi yksittäistä tutkijaa tai tutkimushanketta pakolla hallita valtavaa toiminta-aluetta, josta suurella osalla on merkitystä aivan toisen alan tutkijoille. Sen sijaan TEI koodauskieli voidaan kohdistaa hyvinkin täsmällisesti johonkin aiheeseen tai tehtävään ja rajoittaa vain siihen, mikä on olennaista projektin työssä.

                                      Kuten luonnollista kieltä TEI:tä voidaan käyttää laajan ja vivahteikkaan sanaston luomiseen pienempiinkin yksityiskohtiin ulottuvalla koodauksella, jossa tekstin ilmiöt on seikkaperäisesti kuvattu. Sitä voidaan soveltaa myös hyvin yksinkertaisesti käyttämällä vain muutamaa oleellista käsitettä kuvaamassa keskeisimpiä yksityiskohtia, esim. osiota, otsikkoa, kappaletta. Mitä yksityiskohtaisempi koodaus on, sitä enemmän työn lopputuloksella on käyttöä. Aika, kustannukset, saatavilla oleva työvoima sekä paikallinen erikoisosaaminen saattavat kuitenkin rajoittaa sitä, kuinka yksityiskohtaisena hanke on toteutettavissa.

                                      Tutkijat voivat käyttää tätä koodausjärjestelmää sellaisenaan sen alkuperäisessä muodossa. Sen ohella TEI tarjoaa eri tutkimusaloille mahdollisuuden muokata juuri niiden tarpeiden mukaan sovellettuja versioita TEI -kielestä. Koska nämä mittatilausversiot toimivat yleisessä TEI kehyksessä, ne voivat käyttää sen yleisiä ydintermejä ja käsitteitä ja näin välttää niiden turhaa uudelleenkeksimistä. Lisäksi, koska TEI tarjoaa yleisen kehyksen mittatilausversioiden luomiseen ja kuvaamiseen, niitä voidaan jakaa helposti ja tarkoituksenmukaisesti. Tämän tuloksena eri oppiaineiden tutkijat voivat korostaa omaa työtään luonnehtivia erityisiä päämääriään ja menetelmiään samoin kuin niitä seikkoja, jotka erottavat heidän työnsä toisista, jollakin tavalla heidän alaansa sivuavista. TEI:n piirissä eri tutkimushankkeet voivat esittää tuloksia, jotka aidosti eroavat toisistaan sen sijaan, että erot johtuisivat eri osapuolille käsittämättömien lähestymistapojen aiheuttamasta satunnaisesta ristiriidasta.

                                      Epigraafikoille räätälöity TEI: EpiDoc

                                      EpiDoc -yhteisö on työskennellyt edellä mainituissa puitteissa vuodesta 2000 kehittääkseen erityisesti piirtokirjoitustutkijoiden tarpeisiin sovelletun version TEI:n ohjeistoista. Ajatuksen lanseerasi Pohjois-Carolinan yliopiston Chapel Hillin antiikin historian tutkija Tom Elliott. Tavoite on sekä hyödyntää mahdollisimman laajasti jo tehtyä tutkimustyötä että varmistaa, että piirtokirjoitustekstejä käsitellään samoin kuin muitakin tekstejä, eikä jollakin tavalla eroteltuina niistä. EpiDoc on muokattu poistamalla sille tarpeettomia TEI -elementtejä ja lisäämällä piirtokirjoitustutkimuksessa tarvittavia erityisominaisuuksia mm. transkriptioiden, analyysien, kuvauksien ja luokittelujen tekemiseen. Lopputuloksena on syntynyt yksinkertainen mutta tehokas kieli, jolla voidaan merkitä kaikki piirtokirjoituksissa ilmenevät huomionarvoiset piirteet sekä esittämään tekstien lisäksi myös monumentteihin ja piirtokirjoitusesineisiin liittyvät tiedot.

                                      EpiDoc koodauskielen rinnalle EpiDoc -yhteisö on luonut oppaan koodausta varten sekä ohjelmistotyökaluja ja ohjeistoa, joka kuvaa kuinka koodauskieltä, työkaluja ja muita EpiDoc -menetelmään liittyviä elementtejä käytetään. Tavoitteena on saada aikaan järjestelmä, joka on helppo oppia ja yksinkertainen käyttää myös ilman aiempaa teknistä taustaa tai teknistä tukea. Voi olla vaikea uskoa, mutta XML-koodin tuottaminen on yhtä helppoa kuin standardin piirtokirjoituksen merkitseminen jo olemassa olevan lyhennekokoelman kanssa.

                                      Ryhmä on työskennellyt kehittääkseen ilmaukset kaikille sovituille piirtokirjoitusten merkintätavoille. Ohjeistusta on laajennettu koskemaan myös monia muita piirteitä, joita piirtokirjoitusjulkaisuissa voi esiintyä, mm.

                                      Ks: Dokumentin rakenne.

                                      Muiden aktiivisen työn alla olevien aiheiden joukossa ovat mm. yhteensopivuuskysymykset. Ohjelmistotyökalu tavanomaisesti merkityn piirtokirjoitustekstin muuntamiseksi EpiDoc XML -merkintäkielelle on jo saatu aikaan (ns. Chapel Hill Electronic Text Converter (CHETC)). Toinen keskeinen teema on kattavan sanaston luominen. Esimerkiksi Afrodisiaksen piirtokirjoitustutkimushanke työskentelee kiinteästi Lexicon of Greek Personal Names-hankkeen kanssa saadakseen aikaan mahdollisimman kattavan ja yhdenmukaisesti käytettävän sanaston.

                                      Tätä työtä on johtanut Tom Elliott ja siihen ovat osallistuneet monet yksittäiset tutkijat tiiviissä yhteistyössä keskenään ja pitäen jatkuvasti yhteyttä laajempaan ammattiyhteisöön. Kehittäjät ovat saaneet kokemusta EpiDoc -projekteista, kuten Vindolanda Tablets on line, sekä kahdesta meneillään olevasta hankkeesta US Epigraphy Project (USEP) (jota rahoittavat yliopistot Brown, Princeton ja Rutgers), sekä Afrodisiaksen piirtokirjoitustutkimushanke (InsAph) (jota rahoittaa Arts and Humanities Research Council). AHRC:n runsaan rahoituksen turvin pidettiin marraskuussa 2006 intensiivinen työpaja, jossa nämä ohjeistot hiottiin nykyiseen muotoonsa.

                                      Osion vastuuhenkilöt

                                      1. Charlotte Roueché, kirjoittaja
                                      2. Julia Flanders, kirjoittaja
                                      3. Tom Elliott, muokkaus TEI-Lite:sta ja muita muokkauksia
                                      4. Gabriel Bodard, sääti ja päivitti monta linkkiä
                                      5. Katariina Kankaanpää, suomentaja
                                      6. Marja Vierros, suomentaja

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-fr.html b/gl/dev/intro-eps-fr.html index bb73d26c1..ab6914eb3 100644 --- a/gl/dev/intro-eps-fr.html +++ b/gl/dev/intro-eps-fr.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Introduction pour les épigraphistes

                                      2023-04-27

                                      Les principes sous tendant EpiDoc rassemblent, pour les épigraphistes, des concepts traditionnels ainsi que des méthodes d'édition et des conventions tout à fait nouvelles.

                                      Conventions épigraphiques

                                      Au cours du siècle dernier, les épigraphistes ont été confrontés aux problèmes liés à la représentation d'informations non verbales dans leurs textes écrits. Les éditeurs ont, jusqu'à la fin du 19ème siècle, produit des facsimile des textes mais cette pratique devint ensuite de plus en plus rare, les éditeurs montrant en outre peu d'empressement à remplacer ces facsimile par des reproductions photographiques intégrales de chaque document. Des conventions furent par ailleurs (et non sans mal) développées pour représenter les zones de texte manquantes, les abréviations, etc., et sont globalement acceptées par tous depuis les années 1930, partageant nombre de points communs avec celles développées en papyrologie et en paléographie. Tous les épigraphistes ont depuis été confrontés aux conséquences du passage à l'informatique, notamment la difficulté de reproduire ces conventions, notamment la difficulté de trouver une police permettant de mettre un point sous un caractère. Cependant la plupart ont désormais surmonté ces obstacles.

                                      Les difficultés posées par ces questions, en particulier le rendu des caractères grecs avec des polices complètes et affichables sur le web, ont généralement ralentit la publication en ligne de textes épigraphiques. En lieu et place sont apparues des bases de données d'une grande richesse, parmi lesquelles :

                                      Se référer également à: Compatibilité d'EpiDoc.

                                      Tous ces développements ont en outre été déterminés par l'état de l'art technologique au moment de leur mise en œuvre, l'informatique ayant connu d'importantes évolutions au cours du 20ème siècle. L'objectif d'EpiDoc est d'exploiter ces nouvelles technologies pour poursuivre les objectifs traditionnels de l'épigraphie par de nouveaux moyens. Nombre des processus évoqués plus haut ont impliqué de lutter contre des limitations technologiques (notamment dans le domaine de l'impression papier) afin de répondre au plus grand nombre de besoins des épigraphistes. Avec le temps il est devenu de plus en plus difficile de persuader les imprimeurs classiques d'accepter les besoins spécifiques d'insertion d'information méta-textuelles, sauf à payer des tarifs exorbitants. Et ce alors même que la quantité d'information accompagnant chaque texte a grandement augmenté : outre les informations sur l'apparence physique ou les circonstances de découverte, la représentation photographique des documents étant également standard.

                                      Les quinze dernières années ont vu les chercheurs affronter des problèmes généralement similaires en terme d'intégration de métadonnées au sein de leurs textes en format électronique et divers outils ont rendu ces tâches de plus en plus aisée et les résultats de plus en plus bénéfiques. Les logiciels de traitement de texte familiers depuis les années 1980 nous permettent de contrôler l'apparence des textes en faisant usage d'un balisage qui de nos jour est invisible pour l'utilisateur, masqué dans le code du fichier par le programme. Les demandes plus importantes de projets de grande échelle (documents juridiques, documentation industrielle, publications commerciales, ...) ont conduit, dans les années 80, à la recherche de moyens permettant d'encoder plus d'informations et d'instructions au sein des documents électroniques. Au début l'attention s'est portée sur l'insertion d'informations de mise en page mais rapidement apparurent des moyens permettant d'inclure des informations sémantiques plus complexes relatives à la structure même des documents et à leur contenu. Un exemple simple consiste à indiquer que le titre d'un ouvrage est un titre, plutôt que de simplement le mettre en italique. L'utilisation de ce balisage plus abstrait a permis une séparation de la structure et de la présentation d'un document, où la structure est propre à un genre de document alors que la présentation peut varier en fonction de la méthode de publication. D'une certaine façon ce basculement est une forme de retour à une époque antérieure où les auteurs s'occupaient du contenu et où la question de la présentation relevait exclusivement du processus de publication, une distinction perdue lors de l'arrivée des systèmes de reproduction photographique.

                                      Les protocoles issus de ces efforts furent standardisés fin des années 80 en tant que "Standard Generalized Markup Language" (SGML) et furent plus récemment adaptés de manière à les rendre plus simples et plus souples afin de les rendre utilisables pour le web, sous le nom de XML : le Extensible Markup Language. XML aujourd'hui largement utilisé par la communauté scientifique dans un grand nombre de disciplines des sciences humaines afin de représenter et préserver du matériel de recherche pour de multiples usages.

                                      L'attrait de XML pour les épigraphistes est, de ce fait, considérable. Ainsi les lacunes peuvent être indiquées comme telles, et présentées au sein de crochets droits. Simultanément une recherche spécifiant que seul le texte marqué comme présent sur le document original doit être pris en compte peut être menée sur le corpus (et donc ne prendre en compte que les mots effectivement présents, indépendamment des reconstructions). Les lettres à la lecture incertaines peuvent être représentées comme telles et une décision quant à leur rendu lors de l'impression peut être prise ultérieurement (assurant leur identification par un point sous la lettre ou toute autre méthode souhaitée). Les mots peuvent également être lemmatisés durant l'édition, permettant de créer des indices qui se complèteront automatiquement au fur et à mesure de l'édition du corpus. Ce qui est important, en revanche, est de recréer un équivalent électronique des conventions de Leyden, c'est à dire de définir un standard pour représenter électroniquement les différents sigles en usage. Tout d'abord cela est utile pour économiser du temps et s'éviter divers soucis. Mais une telle standardisation a aussi (sans imposer une totale uniformité) une valeur intrinsèque : non seulement cela fournit une information au lecteur, tout comme les sigles imprimés sur les pages papiers, mais en outre cela permet une publication électronique permettant l'exploitation simultanée de plusieurs corpus même si ils ont été préparés par des équipes différentes.

                                      Ce besoin de standards repandus n'est pas limité au domaine de l'épigraphie. Depuis 1987 un groupe international de chercheurs, principalement issus du domaine des sciences humaines, travaille à développer et améliorer un jeu de consignes ("guidelines") pour décrire la structure et le contenu de documents. Le résultat de cet effort a été la naissance d'un langage d'encodage, produit en XML et appelé du nom du groupe qui lui a donné naissance : TEI, pour Text Encoding Initiatve.

                                      TEI pour les épigraphistes : De quoi s'agit-il ? Pourquoi l'utiliser ?

                                      La "Text Encoding Initiative" (TEI) est un effort scientifique visant à la définition d'un langage d'encodage permettant de subvenir de façon générale aux besoins des chercheurs en sciences humaines. Deux objectifs principaux ont conduit le développement de la TEI : le premier est de fournir aux chercheurs le moyen de représenter leur matériel de recherche dans un format numérique en utilisant un langage descriptif qui reproduit les termes et les concepts d'analyse familiers et essentiels à la recherche en sciences humaines. Le second objectif est de permettre au chercheur de partager le produit de cet encodage de façon intelligible grâce à l'utilisation d'un langage descriptif commun.

                                      On peut considérer le langage d'encodage TEI comme un langage humain : un noyau de termes partagés au centre, entourés par une série de vocabulaires à la diffusion plus restreinte, en ce compris des variantes locales, des termes spécifiques à certains domaines et d'autres variations. Au coeur du TEI se trouvent les termes communs et les concepts largement partagés par les chercheurs dans la plupart des disciplines : des éléments comme les paragraphes, les divisions courantes du texte, les chapitres, les listes, etc. Des éléments plus spécifiques sont regroupés en fonction de leur utilisation : ainsi les éléments pour l'encodage détaillé de noms, de caractéristiques de manuscrits, pour capturer la structure de dictionnaires, et ainsi de suite. Le TEI est volontairement construit ainsi, sous forme de modules, afin que les chercheurs actifs dans différentes disciplines puissent utiliser les seuls modules pertinents à leur recherche. La TEI permet ainsi d'offrir une grande liberté sans surcharger les chercheurs individuels et les projets plus larges avec le besoin d'apprendre nombre de connaissances sortant de leur domaine, la plupart desquelles n'étant relevant que pour d'autres disciplines. Au contraire, un encodage TEI peut être dirigé de manière très spécifique à un certain domaine ou une certaine tâche, et peut être limité à ce qui est essentiel à la réussite d'un projet.

                                      Tout comme un langage humain, le langage TEI peut être utilisé de manière à faire appel à un vocabulaire riche et nuancé, avec un encodage détaillé qui décrit une grande variété de phénomènes textuels, mais il peut aussi être utilisé de manière très simple, en se servant uniquement de quelques concepts essentiels qui ne fournissent qu'une information basique sur les éléments textuels : sections, chapitres, paragraphes. Le plus détaillé l'encodage, le plus de possibilités de traitement mais des facteurs comme le temps disponible, le coût, le personnel assignable ou l'expertise locale peuvent être sources de limitations dans le niveau de détails encodable.

                                      En plus de fournir un système d'encodage que les chercheurs peuvent utiliser dans son état standard, le TEI fournit également les outils permettant aux projets de recherche la définition d'une variante adaptée à leurs besoins du langage, laquelle contiendra l'ensemble des modifications nécessaires au support de besoins locaux spécifiques. Parce que ces versions localisées du langage TEI oeuvrent au sein du cadre général, il n'est pas nécessaire de réinventer le noyau commun : les concepts et termes généraux restent d'application et évitent d'avoir à les réinventer. En outre, comme la TEI fournit un cadre commun pour créer et décrire ces modifications spécifiques, elles peuvent être aisément partagées et réutilisées. De cette manière des groupes de chercheurs dans des disciplines différentes peuvent exprimer les méthodes et objectifs spécifiques à leurs disciplines et définir clairement ce qui les différencie des autres domaines proches. Au lieu d'avoir des approches complètement incompatibles, différents projets peuvent produire des résultats dont les différences sont le fruit de vraies oppositions et non de divergences aléatoires.

                                      The EpiDoc Customization: TEI for Epigraphers

                                      Au sein de ce cadre général, la Communauté EpiDoc travaille depuis l'an 2000 à développer une version spécifique des règles TEI adaptées aux besoins particuliers des épigraphistes. L'idée fut lancée par Tom Elliott, historien de l'Antiquité à l'Université de Caroline du Nord (campus de Chapel Hill). L'objectif est à la fois de faire la plus grande utilisation possible du travail déjà effectué et de veiller à ce que la manière dont la documentation épigraphique est traitée soit la plus proche possible de la manière dont sont traités les autres textes, plutôt que de s'éloigner de ces méthodes. EpiDoc élimine ainsi les éléments non pertinents de la TEI tout en introduisant les éléments nécessaires pour que les transcriptions, l'analyse, la description et la classification qui sont essentiels au travail de l'épigraphiste puisse se faire. Le résultat est un langage à la fois simple et puissant qui peut être utilisé pour marquer l'ensemble des caractéristiques d'une inscription et représenter l'information pertinente à l'objet porteur de l'inscription.

                                      Afin d'accompagner le language EpiDoc, la communauté EpiDoc a créé un jeu de "guidelines" et de logiciels, ainsi qu'une documentation expliquant comment utiliser le langage, les outils et tous les autres éléments constitutifs de la "méthode EpiDoc". L'objectif est de créer un cadre qu'il sera aisé d'apprendre et d'utiliser, y compris pour des chercheurs n'ayant aucune expérience technique ou manquant d'appuis. Cela peut sembler improbable, mais la tâche est en réalité similaire à l'apprentissage du marquage d'un texte à l'aide des conventions déjà en usage pour la description de textes épigraphiques.

                                      Le groupe a travaillé pour définir des moyens de représenter l'ensemble des conventions épigraphiques en usage. Ils ont en outre élargi le présent manuel afin de traiter de l'ensemble des champs susceptibles d'être présents dans une publication épigraphique, en ce compris :

                                      Voir également: Structure du document.

                                      D'autres domaines présentement à l'étude sont, notamment, ceux relatifs au développement de l'interopérabilité. Un outil de conversion automatique de texte en document au format XML EpiDoc a déjà été développé : le Chapel Hill Electronic Text Converter(CHETC). D'autres travaux visent à permettre l'utilisation de lexiques de contrôle. Ainsi le projet Inscriptions of Aphrodisias travaille de manière rapprochée avec le Lexicon of Greek Personal Names afin d'assurer une documentation exaustive et conforme aux normes en usage.

                                      Ce travail, mené sous la conduite du Dr. Elliott, a été entrepris par une série de chercheurs travaillant de manière concertée et veillant à rester régulièrement en contact avec le reste de la profession. L'équipe bénéficie également de l'expérience d'un projet EpiDoc bien établit, les Vindolanda Tablets on line, et de deux projets actuellement en cours, l'US Epigraphy Project (USEP) (avec l'appui des universités de Brown, Princeton and Rutgers), et le Inscriptions of Aphrodisias Project (InsAph) (avec l'appui de l'Arts and Humanities Research Council). Ce généreux support de l'AHRC a également permit la tenue d'un atelier de réflexion intensif en 2006 durant lequel les présentes "guidelines" purent être réorganisées.

                                      Responsables de cette section

                                      1. Charlotte Roueché, Auteur
                                      2. Julia Flanders, Auteur
                                      3. Pascal Lemaire, Traduction française
                                      4. Tom Elliott, Rendu via TEI-Lite et diverses opérations de mise en page
                                      5. Gabriel Bodard, Correction de plusieurs liens

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Introduction pour les épigraphistes

                                      2024-03-05

                                      Les principes sous tendant EpiDoc rassemblent, pour les épigraphistes, des concepts traditionnels ainsi que des méthodes d'édition et des conventions tout à fait nouvelles.

                                      Conventions épigraphiques

                                      Au cours du siècle dernier, les épigraphistes ont été confrontés aux problèmes liés à la représentation d'informations non verbales dans leurs textes écrits. Les éditeurs ont, jusqu'à la fin du 19ème siècle, produit des facsimile des textes mais cette pratique devint ensuite de plus en plus rare, les éditeurs montrant en outre peu d'empressement à remplacer ces facsimile par des reproductions photographiques intégrales de chaque document. Des conventions furent par ailleurs (et non sans mal) développées pour représenter les zones de texte manquantes, les abréviations, etc., et sont globalement acceptées par tous depuis les années 1930, partageant nombre de points communs avec celles développées en papyrologie et en paléographie. Tous les épigraphistes ont depuis été confrontés aux conséquences du passage à l'informatique, notamment la difficulté de reproduire ces conventions, notamment la difficulté de trouver une police permettant de mettre un point sous un caractère. Cependant la plupart ont désormais surmonté ces obstacles.

                                      Les difficultés posées par ces questions, en particulier le rendu des caractères grecs avec des polices complètes et affichables sur le web, ont généralement ralentit la publication en ligne de textes épigraphiques. En lieu et place sont apparues des bases de données d'une grande richesse, parmi lesquelles :

                                      Se référer également à: Compatibilité d'EpiDoc.

                                      Tous ces développements ont en outre été déterminés par l'état de l'art technologique au moment de leur mise en œuvre, l'informatique ayant connu d'importantes évolutions au cours du 20ème siècle. L'objectif d'EpiDoc est d'exploiter ces nouvelles technologies pour poursuivre les objectifs traditionnels de l'épigraphie par de nouveaux moyens. Nombre des processus évoqués plus haut ont impliqué de lutter contre des limitations technologiques (notamment dans le domaine de l'impression papier) afin de répondre au plus grand nombre de besoins des épigraphistes. Avec le temps il est devenu de plus en plus difficile de persuader les imprimeurs classiques d'accepter les besoins spécifiques d'insertion d'information méta-textuelles, sauf à payer des tarifs exorbitants. Et ce alors même que la quantité d'information accompagnant chaque texte a grandement augmenté : outre les informations sur l'apparence physique ou les circonstances de découverte, la représentation photographique des documents étant également standard.

                                      Les quinze dernières années ont vu les chercheurs affronter des problèmes généralement similaires en terme d'intégration de métadonnées au sein de leurs textes en format électronique et divers outils ont rendu ces tâches de plus en plus aisée et les résultats de plus en plus bénéfiques. Les logiciels de traitement de texte familiers depuis les années 1980 nous permettent de contrôler l'apparence des textes en faisant usage d'un balisage qui de nos jour est invisible pour l'utilisateur, masqué dans le code du fichier par le programme. Les demandes plus importantes de projets de grande échelle (documents juridiques, documentation industrielle, publications commerciales, ...) ont conduit, dans les années 80, à la recherche de moyens permettant d'encoder plus d'informations et d'instructions au sein des documents électroniques. Au début l'attention s'est portée sur l'insertion d'informations de mise en page mais rapidement apparurent des moyens permettant d'inclure des informations sémantiques plus complexes relatives à la structure même des documents et à leur contenu. Un exemple simple consiste à indiquer que le titre d'un ouvrage est un titre, plutôt que de simplement le mettre en italique. L'utilisation de ce balisage plus abstrait a permis une séparation de la structure et de la présentation d'un document, où la structure est propre à un genre de document alors que la présentation peut varier en fonction de la méthode de publication. D'une certaine façon ce basculement est une forme de retour à une époque antérieure où les auteurs s'occupaient du contenu et où la question de la présentation relevait exclusivement du processus de publication, une distinction perdue lors de l'arrivée des systèmes de reproduction photographique.

                                      Les protocoles issus de ces efforts furent standardisés fin des années 80 en tant que "Standard Generalized Markup Language" (SGML) et furent plus récemment adaptés de manière à les rendre plus simples et plus souples afin de les rendre utilisables pour le web, sous le nom de XML : le Extensible Markup Language. XML aujourd'hui largement utilisé par la communauté scientifique dans un grand nombre de disciplines des sciences humaines afin de représenter et préserver du matériel de recherche pour de multiples usages.

                                      L'attrait de XML pour les épigraphistes est, de ce fait, considérable. Ainsi les lacunes peuvent être indiquées comme telles, et présentées au sein de crochets droits. Simultanément une recherche spécifiant que seul le texte marqué comme présent sur le document original doit être pris en compte peut être menée sur le corpus (et donc ne prendre en compte que les mots effectivement présents, indépendamment des reconstructions). Les lettres à la lecture incertaines peuvent être représentées comme telles et une décision quant à leur rendu lors de l'impression peut être prise ultérieurement (assurant leur identification par un point sous la lettre ou toute autre méthode souhaitée). Les mots peuvent également être lemmatisés durant l'édition, permettant de créer des indices qui se complèteront automatiquement au fur et à mesure de l'édition du corpus. Ce qui est important, en revanche, est de recréer un équivalent électronique des conventions de Leyden, c'est à dire de définir un standard pour représenter électroniquement les différents sigles en usage. Tout d'abord cela est utile pour économiser du temps et s'éviter divers soucis. Mais une telle standardisation a aussi (sans imposer une totale uniformité) une valeur intrinsèque : non seulement cela fournit une information au lecteur, tout comme les sigles imprimés sur les pages papiers, mais en outre cela permet une publication électronique permettant l'exploitation simultanée de plusieurs corpus même si ils ont été préparés par des équipes différentes.

                                      Ce besoin de standards repandus n'est pas limité au domaine de l'épigraphie. Depuis 1987 un groupe international de chercheurs, principalement issus du domaine des sciences humaines, travaille à développer et améliorer un jeu de consignes ("guidelines") pour décrire la structure et le contenu de documents. Le résultat de cet effort a été la naissance d'un langage d'encodage, produit en XML et appelé du nom du groupe qui lui a donné naissance : TEI, pour Text Encoding Initiatve.

                                      TEI pour les épigraphistes : De quoi s'agit-il ? Pourquoi l'utiliser ?

                                      La "Text Encoding Initiative" (TEI) est un effort scientifique visant à la définition d'un langage d'encodage permettant de subvenir de façon générale aux besoins des chercheurs en sciences humaines. Deux objectifs principaux ont conduit le développement de la TEI : le premier est de fournir aux chercheurs le moyen de représenter leur matériel de recherche dans un format numérique en utilisant un langage descriptif qui reproduit les termes et les concepts d'analyse familiers et essentiels à la recherche en sciences humaines. Le second objectif est de permettre au chercheur de partager le produit de cet encodage de façon intelligible grâce à l'utilisation d'un langage descriptif commun.

                                      On peut considérer le langage d'encodage TEI comme un langage humain : un noyau de termes partagés au centre, entourés par une série de vocabulaires à la diffusion plus restreinte, en ce compris des variantes locales, des termes spécifiques à certains domaines et d'autres variations. Au coeur du TEI se trouvent les termes communs et les concepts largement partagés par les chercheurs dans la plupart des disciplines : des éléments comme les paragraphes, les divisions courantes du texte, les chapitres, les listes, etc. Des éléments plus spécifiques sont regroupés en fonction de leur utilisation : ainsi les éléments pour l'encodage détaillé de noms, de caractéristiques de manuscrits, pour capturer la structure de dictionnaires, et ainsi de suite. Le TEI est volontairement construit ainsi, sous forme de modules, afin que les chercheurs actifs dans différentes disciplines puissent utiliser les seuls modules pertinents à leur recherche. La TEI permet ainsi d'offrir une grande liberté sans surcharger les chercheurs individuels et les projets plus larges avec le besoin d'apprendre nombre de connaissances sortant de leur domaine, la plupart desquelles n'étant relevant que pour d'autres disciplines. Au contraire, un encodage TEI peut être dirigé de manière très spécifique à un certain domaine ou une certaine tâche, et peut être limité à ce qui est essentiel à la réussite d'un projet.

                                      Tout comme un langage humain, le langage TEI peut être utilisé de manière à faire appel à un vocabulaire riche et nuancé, avec un encodage détaillé qui décrit une grande variété de phénomènes textuels, mais il peut aussi être utilisé de manière très simple, en se servant uniquement de quelques concepts essentiels qui ne fournissent qu'une information basique sur les éléments textuels : sections, chapitres, paragraphes. Le plus détaillé l'encodage, le plus de possibilités de traitement mais des facteurs comme le temps disponible, le coût, le personnel assignable ou l'expertise locale peuvent être sources de limitations dans le niveau de détails encodable.

                                      En plus de fournir un système d'encodage que les chercheurs peuvent utiliser dans son état standard, le TEI fournit également les outils permettant aux projets de recherche la définition d'une variante adaptée à leurs besoins du langage, laquelle contiendra l'ensemble des modifications nécessaires au support de besoins locaux spécifiques. Parce que ces versions localisées du langage TEI oeuvrent au sein du cadre général, il n'est pas nécessaire de réinventer le noyau commun : les concepts et termes généraux restent d'application et évitent d'avoir à les réinventer. En outre, comme la TEI fournit un cadre commun pour créer et décrire ces modifications spécifiques, elles peuvent être aisément partagées et réutilisées. De cette manière des groupes de chercheurs dans des disciplines différentes peuvent exprimer les méthodes et objectifs spécifiques à leurs disciplines et définir clairement ce qui les différencie des autres domaines proches. Au lieu d'avoir des approches complètement incompatibles, différents projets peuvent produire des résultats dont les différences sont le fruit de vraies oppositions et non de divergences aléatoires.

                                      The EpiDoc Customization: TEI for Epigraphers

                                      Au sein de ce cadre général, la Communauté EpiDoc travaille depuis l'an 2000 à développer une version spécifique des règles TEI adaptées aux besoins particuliers des épigraphistes. L'idée fut lancée par Tom Elliott, historien de l'Antiquité à l'Université de Caroline du Nord (campus de Chapel Hill). L'objectif est à la fois de faire la plus grande utilisation possible du travail déjà effectué et de veiller à ce que la manière dont la documentation épigraphique est traitée soit la plus proche possible de la manière dont sont traités les autres textes, plutôt que de s'éloigner de ces méthodes. EpiDoc élimine ainsi les éléments non pertinents de la TEI tout en introduisant les éléments nécessaires pour que les transcriptions, l'analyse, la description et la classification qui sont essentiels au travail de l'épigraphiste puisse se faire. Le résultat est un langage à la fois simple et puissant qui peut être utilisé pour marquer l'ensemble des caractéristiques d'une inscription et représenter l'information pertinente à l'objet porteur de l'inscription.

                                      Afin d'accompagner le language EpiDoc, la communauté EpiDoc a créé un jeu de "guidelines" et de logiciels, ainsi qu'une documentation expliquant comment utiliser le langage, les outils et tous les autres éléments constitutifs de la "méthode EpiDoc". L'objectif est de créer un cadre qu'il sera aisé d'apprendre et d'utiliser, y compris pour des chercheurs n'ayant aucune expérience technique ou manquant d'appuis. Cela peut sembler improbable, mais la tâche est en réalité similaire à l'apprentissage du marquage d'un texte à l'aide des conventions déjà en usage pour la description de textes épigraphiques.

                                      Le groupe a travaillé pour définir des moyens de représenter l'ensemble des conventions épigraphiques en usage. Ils ont en outre élargi le présent manuel afin de traiter de l'ensemble des champs susceptibles d'être présents dans une publication épigraphique, en ce compris :

                                      Voir également: Structure du document.

                                      D'autres domaines présentement à l'étude sont, notamment, ceux relatifs au développement de l'interopérabilité. Un outil de conversion automatique de texte en document au format XML EpiDoc a déjà été développé : le Chapel Hill Electronic Text Converter(CHETC). D'autres travaux visent à permettre l'utilisation de lexiques de contrôle. Ainsi le projet Inscriptions of Aphrodisias travaille de manière rapprochée avec le Lexicon of Greek Personal Names afin d'assurer une documentation exaustive et conforme aux normes en usage.

                                      Ce travail, mené sous la conduite du Dr. Elliott, a été entrepris par une série de chercheurs travaillant de manière concertée et veillant à rester régulièrement en contact avec le reste de la profession. L'équipe bénéficie également de l'expérience d'un projet EpiDoc bien établit, les Vindolanda Tablets on line, et de deux projets actuellement en cours, l'US Epigraphy Project (USEP) (avec l'appui des universités de Brown, Princeton and Rutgers), et le Inscriptions of Aphrodisias Project (InsAph) (avec l'appui de l'Arts and Humanities Research Council). Ce généreux support de l'AHRC a également permit la tenue d'un atelier de réflexion intensif en 2006 durant lequel les présentes "guidelines" purent être réorganisées.

                                      Responsables de cette section

                                      1. Charlotte Roueché, Auteur
                                      2. Julia Flanders, Auteur
                                      3. Pascal Lemaire, Traduction française
                                      4. Tom Elliott, Rendu via TEI-Lite et diverses opérations de mise en page
                                      5. Gabriel Bodard, Correction de plusieurs liens

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-it.html b/gl/dev/intro-eps-it.html index d6acee308..2f19a2f9a 100644 --- a/gl/dev/intro-eps-it.html +++ b/gl/dev/intro-eps-it.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Codifica per Epigrafisti, un'introduzione gentile

                                      2023-04-27

                                      A monte di Epidoc c'è il desiderio di mettere assieme, per gli epigrafisti, metodi e convenzioni tradizionali e moderni.

                                      Convenzioni Epigrafiche

                                      Durante lo scorso secolo, gli epigrafisti si sono scontrati su questioni relative alla rappresentazioni di fenomeni non verbali all'interno di un testo scritto. Fino alla fine del XIX secolo ci si aspettava dagli editori un facsimile del testo, ma ciò divenne progressivamente una pratica meno diffusa e d'altro canto gli editori non mostravano la volontà di produrre documentazione fotografica di ciascun elemento. Le convenzioni che, con difficoltà, furono messe a punto per indicare parti di testo mancanti, abbreviazioni, ecc. sono grossomodo condivise fin dagli anni '30 del XX secolo e sono simili (fino ad un certo punto), a quelle in uso in papirologia e paleografia. Tutti gli epigrafisti hanno dovuto affrontare il problema di trasportare tutto ciò in un contesto digitale - per esempio, cercando fonts che permettessero di mettere il puntino sottoscritto; molti di noi ad oggi si sono adattati a questi vincoli.

                                      La difficoltà nel rendere questi simboli convenzionali, in particolare lettere greche, in font coerenti sul web ha ritardato le pubblicazioni dei testi epigrafici online; ma d'altro canto sono state create collezioni di testi estremamente ricche, tra le quali:

                                      Cfr. anche: Compatibilità con EpiDoc.

                                      Tutti questi sviluppi sono stati determinati dallo stato delle tecnologie esistenti, mano a mano che queste sono state sviluppate nel corso del XX secolo. Lo scopo di EpiDoc è di sfruttare nuove e fruttuose tecnologie per gli scopi tradizionali dell'epigrafia. Molti dei processi descritti sopra hanno coinvolto dure lotte contro gli standards tecnologici - per esempio, le pubblicazioni a stampa - per cercare di trovare un posto al maggior numero di requisiti. Durante questo periodo è stato sempre più complicato persuadere editori convenzionali ad adattarsi al nostro standard con l'inserimento di informazioni meta-testuali, se non con costi esosi. Allo stesso tempo tuttavia, le aspettative rispetto alla quantità di informazioni che accompagnano un testo è notevolmente cresciuta. Informazioni sulle caratteristiche fisiche e illustrazioni fotografiche sono diventate basilari.

                                      Negli scorsi 15 anni gli studiosi hanno avuto in generale a che fare con requisiti simili per incorporare i loro metadati in testi in formato elettronico e sono emersi strumenti che rendono tutto ciò sempre più semplice, rendendo i risultati sempre migliori. I software per l'elaborazione di testo, che ci sono familiari sin dagli anni '80, ci permettono di controllare la formattazione dei testi, usando un mark-up che è incorporato nel software ed invisibile. I requisiti complessi di ampie raccolte di documenti - documenti legali, documentazione industriale, pubblicazioni commerciali - hanno portato negli anni '80 alla ricerca di modi di inserire un maggior numero di informazioni ed istruzioni dentro i testi. In un primo tempo l'enfasi era sull'inserimento di informazioni relative al formato, ma presto emersero metodi per includere informazioni semantiche più complesse, relative alla struttura ed al contenuto. Un esempio è quello della codifica di un titolo in quanto titolo, piuttosto che la semplice codifica del suo aspetto corsivo. L'uso di questo mark-up più astratto permette la separazione di strutture e presentazione e mentre la struttura è fondamentale per il documento, la presentazione può essere variabile e dipende dalla forma della pubblicazione. In un certo senso, questo passaggio ha rappresentato un ritorno ad una metodologia più antica, nella quale gli autori si dedicavano solo alla sostanza del testo e tutti i dettagli della presentazione erano gestiti dal processo di pubblicazione - una distinzione che si è persa solo nell'epoca della documentazione pronta per la stampa.

                                      I protocolli emersi da quest'ultima fase sono stati standardizzati negli ultimi anni '80 come Standard Generalized Markup Language, e recentemente hanno ricevuto una struttura più semplice e flessibile, adatta all'uso sul web, con il nome di XML: Extensible Markup Language. XML è ad oggi utilizzato dagli studiosi in un numero sempre crescente di discipline umanistiche per conservare e rappresentare materiali di ricerca con diversi scopi.

                                      I motivi per cui gli epigrafisti sono attratti da XML sono dunque molti. Per esempio: parti mancanti possono essere annotate come tali, e poi rappresentate come parentesi quadre; allo stesso tempo si possono effettuare ricerche che chiedano di cercare solo nel testo conservato, ignorando le integrazioni (quindi è possibile cercare le sole attestazioni documentate). Le lettere incerte posso essere altrettanto annotate come tali, e si possono rimandare le decisioni su come renderle, se con un puntino sottoscritto o con un altro simbolo. Le parole possono essere lemmatizzate durante l'edizione dei testi per creare indici che crescono mentre cresce la raccolta. Ciò che è ancora più importante tuttavia, a questo punto è di ripetere l'"esercizio di Leyden", cioè, mettersi d'accordo su equivalenti elettronici delle varie sigle in uso. In primo luogo, questo è importante ai fini di conservare tempo ed energie; ma anche la coerenza interna ne beneficia, senza imporre uniformità. E questo vantaggio per gli utenti non è l'unico; documenti così editi e pubblicati in formato elettronico saranno poi utilizzabili insieme, anche se sono stati preparati indipendentemente.

                                      La necessità di standard non è propria dell'epigrafia. Fin dal 1987 un consorzio internazionale di ricercatori, soprattutto nelle discipline umanistiche ha lavorato insieme allo sviluppo e alla specifica di una serie di linee guida che descrivono le strutture e i contenuti dei documenti. I risultati di questo impegno collettivo hanno prodotto un linguaggio di codifica, realizzato in XML e descritto dal nome del gruppo - TEI, la Text Encoding Initiatve.

                                      TEI per Epigrafisti: cos'è? E perché usarlo?

                                      La Text Encoding Initiative è un progetto di ricerca volto alla definizione di un linguaggio di codifica che comprenda i requisiti degli studiosi di discipline umanistiche in senso molto ampio. Ci sono due scopi principali che spingono lo sviluppo di TEI. Il primo è rendere possibile agli studiosi di rappresentare i loro materiali di ricerca in formato digitale usando un linguaggio descrittivo che rispecchia le tipologie di termini analitici e di concetti che sono familiari ed essenziali alle scienze umanistiche. In secondo luogo suo scopo è rendere possibile agli studiosi di condividere i loro risultati in modo intellegibile, tramite l'uso di un linguaggio descrittivo comune.

                                      Possiamo pensare a TEI come ad un linguaggio di codifica simile alle lingue naturali: un nucleo di termini condivisi al centro, circondati da vocabolari più specifici, che includono usi locali, terminologie specialistiche e altre variabili. Al centro di TEI ci sono dei termini comuni e dei concetti ampiamente condivisi dagli studiosi di diverse discipline: elementi come paragrafi, generiche divisioni del testo, titoli, liste, etc. elementi più specifici sono raggruppati secondo le loro applicazioni: per esempio, elementi per la codifica di nomi, elementi per la rappresentazione di caratteristiche dei manoscritti, elementi che descrivono la struttura di dizionari e così via. TEI è intenzionalmente organizzato in moduli, così che gli studiosi di determinate aree possano usare solo i moduli a cui sono interessati per i loro lavori, omettendo gli altri. TEI può dunque raggiungere molti, senza oberare nessuno con una massa di informazioni importanti solo per altre discipline. Al contrario, TEI può essere adattato a scopi molto specifici e può essere limitato a ciò che è strettamente necessario per ciascun lavoro.

                                      Come in una lingua naturale, TEI può essere usato in qualsiasi modo, purché basato su un vocabolario ricco e specifico, con una codifica dettagliata in grado di descrivere moltissimi fenomeni testuali, ma che può anche essere usata in modo molto semplice, con pochi concetti essenziali che descrivono solo gli elementi testuali di base: sezioni, titoli, paragrafi. Più dettagliata è la codifica, più è possibile fare con i testi codificati, ma fattori quali i tempi, i costi, il personale e le competenze locali possono limitare il livello di dettagli possibile.

                                      In aggiunta a fornire un sistema di codifica che gli studiosi possono usare nella sua forma originale, TEI offre ai progetti di ricerca anche modi per definire versioni adattate di TEI, che includono modifiche necessaria per supportare requisiti specifici. Dato che queste versioni derivate operano all'interno del contesto TEI, possono servirsi dei suoi termini e concetti fondamentali, evitando il lavoro di re-inventarli. Inoltre, dato che TEI offre un modo per descrivere questi adattamenti, questi stessi possono essere significativamente condivisi. Ne risulta che gruppi di studiosi di particolari discipline possono articolare i loro obiettivi e metodi così come le differenze esistenti da altri che lavorano nel medesimo settore. Invece che sistemi mutualmente incomprensibili, progetti diversi possono così produrre risultati le cui differenze sono date da fondamentali discrepanze non da mere divergenze.

                                      La specifica di EpiDoc: TEI per epigrafisti

                                      All'interno di questo contesto, la comunità di EpiDoc community lavora fin dal 2000 allo sviluppo di una versione adattata delle linee guida della TEI, dedicate ai bisogni specifici degli epigrafisti. L'idea fu lanciata da Tom Elliott, uno storico antichista dell'University of North Carolina a Chapel Hill; lo scopo è sia di sfruttare al massimo il lavoro già fatto, sia di assicurare il fatto che testi iscritti siano trattati in modo coerente con quello di cui ci si serve per altri tipi di testo, e non in modo dissimile. La specifica di EpiDoc elimina elementi irrilevanti dal corpo principale di TEI e aggiunge elementi per gli specifici tipi di trascrizione, analisi, descrizione e classificazione che sono essenziali al lavoro epigrafico. Il risultato è un linguaggio semplice ma capace di codificare tutti gli aspetti significativi di un'iscrizione insieme a tutte le informazioni che accompagnano l'oggetto in sé.

                                      Per complementare EpiDoc come linguaggio di codifica, la comunità di EpiDoc ha prodotto anche un set di linee guida e di strumenti software, nonché la relativa documentazione che descrive come usare i linguaggi di codifica, gli strumenti e gli altri elementi del metodo EpiDoc. L'obiettivo è stabilire un contesto che sia facile da imparare ed usare, anche per studiosi che non abbiano competenze o supporto tecnico. Può sembrare improbabile ma l'impresa è dello stesso tipo di quella che si intraprende imparando a fare la normale edizione di un testo epigrafico usando le sigle in uso.

                                      Il gruppo ha lavorato allo sviluppo di espressioni adatte per ciascuna delle convenzioni epigrafiche in uso ed ha anche esteso le linee guida per affrontare i vari campi presenti in un pubblicazione epigrafica, quali:

                                      Vedi anche: Struttura del Documento.

                                      Ulteriori aree di ricerca includono l'interoperabilità. Esiste un software per convertire normali testi in EpiDoc XML, chiamato Chapel Hill Electronic Text Converter (CHETC). Altre aree includono l'uso di lessici di riferimento. Per esempio il progetto Inscriptions of Aphrodisias sta lavorando a stretto contatto con il Lexicon of Greek Personal Names, per garantirne la copertura completa e l'uso coerente.

                                      Il lavoro, diretto dal Dr. Elliott, è stato portato avanti da diversi studiosi che hanno lavorato in stretta collaborazione, e con regolari contatti con gli epigrafisti latu sensu. Si sono basati sull'esperienza di un progetto EpiDoc ben stabilito Vindolanda Tablets on line, e su due progetti in corso: the US Epigraphy Project (USEP) (sostenuto da Brown, Princeton e Rutgers Universities), e il progetto Inscriptions of Aphrodisias (InsAph) (finanziato dall'Arts and Humanities Research Council). Il generoso supporto dell'AHRC ha anche permesso di organizzare workshop intensivi in Marzo 2006 dove le linee guida sono state perfezionate.

                                      Responsabilità per questa sezione

                                      1. Charlotte Roueché, autore
                                      2. Julia Flanders, autore
                                      3. Pietro Maria Liuzzo, traduzione italiana
                                      4. Greta Franzini, correzione traduzione italiana
                                      5. Tom Elliott, coerced from TEI-Lite and various reformatting edits
                                      6. Gabriel Bodard, re-encoded and updated links

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Codifica per Epigrafisti, un'introduzione gentile

                                      2024-03-05

                                      A monte di Epidoc c'è il desiderio di mettere assieme, per gli epigrafisti, metodi e convenzioni tradizionali e moderni.

                                      Convenzioni Epigrafiche

                                      Durante lo scorso secolo, gli epigrafisti si sono scontrati su questioni relative alla rappresentazioni di fenomeni non verbali all'interno di un testo scritto. Fino alla fine del XIX secolo ci si aspettava dagli editori un facsimile del testo, ma ciò divenne progressivamente una pratica meno diffusa e d'altro canto gli editori non mostravano la volontà di produrre documentazione fotografica di ciascun elemento. Le convenzioni che, con difficoltà, furono messe a punto per indicare parti di testo mancanti, abbreviazioni, ecc. sono grossomodo condivise fin dagli anni '30 del XX secolo e sono simili (fino ad un certo punto), a quelle in uso in papirologia e paleografia. Tutti gli epigrafisti hanno dovuto affrontare il problema di trasportare tutto ciò in un contesto digitale - per esempio, cercando fonts che permettessero di mettere il puntino sottoscritto; molti di noi ad oggi si sono adattati a questi vincoli.

                                      La difficoltà nel rendere questi simboli convenzionali, in particolare lettere greche, in font coerenti sul web ha ritardato le pubblicazioni dei testi epigrafici online; ma d'altro canto sono state create collezioni di testi estremamente ricche, tra le quali:

                                      Cfr. anche: Compatibilità con EpiDoc.

                                      Tutti questi sviluppi sono stati determinati dallo stato delle tecnologie esistenti, mano a mano che queste sono state sviluppate nel corso del XX secolo. Lo scopo di EpiDoc è di sfruttare nuove e fruttuose tecnologie per gli scopi tradizionali dell'epigrafia. Molti dei processi descritti sopra hanno coinvolto dure lotte contro gli standards tecnologici - per esempio, le pubblicazioni a stampa - per cercare di trovare un posto al maggior numero di requisiti. Durante questo periodo è stato sempre più complicato persuadere editori convenzionali ad adattarsi al nostro standard con l'inserimento di informazioni meta-testuali, se non con costi esosi. Allo stesso tempo tuttavia, le aspettative rispetto alla quantità di informazioni che accompagnano un testo è notevolmente cresciuta. Informazioni sulle caratteristiche fisiche e illustrazioni fotografiche sono diventate basilari.

                                      Negli scorsi 15 anni gli studiosi hanno avuto in generale a che fare con requisiti simili per incorporare i loro metadati in testi in formato elettronico e sono emersi strumenti che rendono tutto ciò sempre più semplice, rendendo i risultati sempre migliori. I software per l'elaborazione di testo, che ci sono familiari sin dagli anni '80, ci permettono di controllare la formattazione dei testi, usando un mark-up che è incorporato nel software ed invisibile. I requisiti complessi di ampie raccolte di documenti - documenti legali, documentazione industriale, pubblicazioni commerciali - hanno portato negli anni '80 alla ricerca di modi di inserire un maggior numero di informazioni ed istruzioni dentro i testi. In un primo tempo l'enfasi era sull'inserimento di informazioni relative al formato, ma presto emersero metodi per includere informazioni semantiche più complesse, relative alla struttura ed al contenuto. Un esempio è quello della codifica di un titolo in quanto titolo, piuttosto che la semplice codifica del suo aspetto corsivo. L'uso di questo mark-up più astratto permette la separazione di strutture e presentazione e mentre la struttura è fondamentale per il documento, la presentazione può essere variabile e dipende dalla forma della pubblicazione. In un certo senso, questo passaggio ha rappresentato un ritorno ad una metodologia più antica, nella quale gli autori si dedicavano solo alla sostanza del testo e tutti i dettagli della presentazione erano gestiti dal processo di pubblicazione - una distinzione che si è persa solo nell'epoca della documentazione pronta per la stampa.

                                      I protocolli emersi da quest'ultima fase sono stati standardizzati negli ultimi anni '80 come Standard Generalized Markup Language, e recentemente hanno ricevuto una struttura più semplice e flessibile, adatta all'uso sul web, con il nome di XML: Extensible Markup Language. XML è ad oggi utilizzato dagli studiosi in un numero sempre crescente di discipline umanistiche per conservare e rappresentare materiali di ricerca con diversi scopi.

                                      I motivi per cui gli epigrafisti sono attratti da XML sono dunque molti. Per esempio: parti mancanti possono essere annotate come tali, e poi rappresentate come parentesi quadre; allo stesso tempo si possono effettuare ricerche che chiedano di cercare solo nel testo conservato, ignorando le integrazioni (quindi è possibile cercare le sole attestazioni documentate). Le lettere incerte posso essere altrettanto annotate come tali, e si possono rimandare le decisioni su come renderle, se con un puntino sottoscritto o con un altro simbolo. Le parole possono essere lemmatizzate durante l'edizione dei testi per creare indici che crescono mentre cresce la raccolta. Ciò che è ancora più importante tuttavia, a questo punto è di ripetere l'"esercizio di Leyden", cioè, mettersi d'accordo su equivalenti elettronici delle varie sigle in uso. In primo luogo, questo è importante ai fini di conservare tempo ed energie; ma anche la coerenza interna ne beneficia, senza imporre uniformità. E questo vantaggio per gli utenti non è l'unico; documenti così editi e pubblicati in formato elettronico saranno poi utilizzabili insieme, anche se sono stati preparati indipendentemente.

                                      La necessità di standard non è propria dell'epigrafia. Fin dal 1987 un consorzio internazionale di ricercatori, soprattutto nelle discipline umanistiche ha lavorato insieme allo sviluppo e alla specifica di una serie di linee guida che descrivono le strutture e i contenuti dei documenti. I risultati di questo impegno collettivo hanno prodotto un linguaggio di codifica, realizzato in XML e descritto dal nome del gruppo - TEI, la Text Encoding Initiatve.

                                      TEI per Epigrafisti: cos'è? E perché usarlo?

                                      La Text Encoding Initiative è un progetto di ricerca volto alla definizione di un linguaggio di codifica che comprenda i requisiti degli studiosi di discipline umanistiche in senso molto ampio. Ci sono due scopi principali che spingono lo sviluppo di TEI. Il primo è rendere possibile agli studiosi di rappresentare i loro materiali di ricerca in formato digitale usando un linguaggio descrittivo che rispecchia le tipologie di termini analitici e di concetti che sono familiari ed essenziali alle scienze umanistiche. In secondo luogo suo scopo è rendere possibile agli studiosi di condividere i loro risultati in modo intellegibile, tramite l'uso di un linguaggio descrittivo comune.

                                      Possiamo pensare a TEI come ad un linguaggio di codifica simile alle lingue naturali: un nucleo di termini condivisi al centro, circondati da vocabolari più specifici, che includono usi locali, terminologie specialistiche e altre variabili. Al centro di TEI ci sono dei termini comuni e dei concetti ampiamente condivisi dagli studiosi di diverse discipline: elementi come paragrafi, generiche divisioni del testo, titoli, liste, etc. elementi più specifici sono raggruppati secondo le loro applicazioni: per esempio, elementi per la codifica di nomi, elementi per la rappresentazione di caratteristiche dei manoscritti, elementi che descrivono la struttura di dizionari e così via. TEI è intenzionalmente organizzato in moduli, così che gli studiosi di determinate aree possano usare solo i moduli a cui sono interessati per i loro lavori, omettendo gli altri. TEI può dunque raggiungere molti, senza oberare nessuno con una massa di informazioni importanti solo per altre discipline. Al contrario, TEI può essere adattato a scopi molto specifici e può essere limitato a ciò che è strettamente necessario per ciascun lavoro.

                                      Come in una lingua naturale, TEI può essere usato in qualsiasi modo, purché basato su un vocabolario ricco e specifico, con una codifica dettagliata in grado di descrivere moltissimi fenomeni testuali, ma che può anche essere usata in modo molto semplice, con pochi concetti essenziali che descrivono solo gli elementi testuali di base: sezioni, titoli, paragrafi. Più dettagliata è la codifica, più è possibile fare con i testi codificati, ma fattori quali i tempi, i costi, il personale e le competenze locali possono limitare il livello di dettagli possibile.

                                      In aggiunta a fornire un sistema di codifica che gli studiosi possono usare nella sua forma originale, TEI offre ai progetti di ricerca anche modi per definire versioni adattate di TEI, che includono modifiche necessaria per supportare requisiti specifici. Dato che queste versioni derivate operano all'interno del contesto TEI, possono servirsi dei suoi termini e concetti fondamentali, evitando il lavoro di re-inventarli. Inoltre, dato che TEI offre un modo per descrivere questi adattamenti, questi stessi possono essere significativamente condivisi. Ne risulta che gruppi di studiosi di particolari discipline possono articolare i loro obiettivi e metodi così come le differenze esistenti da altri che lavorano nel medesimo settore. Invece che sistemi mutualmente incomprensibili, progetti diversi possono così produrre risultati le cui differenze sono date da fondamentali discrepanze non da mere divergenze.

                                      La specifica di EpiDoc: TEI per epigrafisti

                                      All'interno di questo contesto, la comunità di EpiDoc community lavora fin dal 2000 allo sviluppo di una versione adattata delle linee guida della TEI, dedicate ai bisogni specifici degli epigrafisti. L'idea fu lanciata da Tom Elliott, uno storico antichista dell'University of North Carolina a Chapel Hill; lo scopo è sia di sfruttare al massimo il lavoro già fatto, sia di assicurare il fatto che testi iscritti siano trattati in modo coerente con quello di cui ci si serve per altri tipi di testo, e non in modo dissimile. La specifica di EpiDoc elimina elementi irrilevanti dal corpo principale di TEI e aggiunge elementi per gli specifici tipi di trascrizione, analisi, descrizione e classificazione che sono essenziali al lavoro epigrafico. Il risultato è un linguaggio semplice ma capace di codificare tutti gli aspetti significativi di un'iscrizione insieme a tutte le informazioni che accompagnano l'oggetto in sé.

                                      Per complementare EpiDoc come linguaggio di codifica, la comunità di EpiDoc ha prodotto anche un set di linee guida e di strumenti software, nonché la relativa documentazione che descrive come usare i linguaggi di codifica, gli strumenti e gli altri elementi del metodo EpiDoc. L'obiettivo è stabilire un contesto che sia facile da imparare ed usare, anche per studiosi che non abbiano competenze o supporto tecnico. Può sembrare improbabile ma l'impresa è dello stesso tipo di quella che si intraprende imparando a fare la normale edizione di un testo epigrafico usando le sigle in uso.

                                      Il gruppo ha lavorato allo sviluppo di espressioni adatte per ciascuna delle convenzioni epigrafiche in uso ed ha anche esteso le linee guida per affrontare i vari campi presenti in un pubblicazione epigrafica, quali:

                                      Vedi anche: Struttura del Documento.

                                      Ulteriori aree di ricerca includono l'interoperabilità. Esiste un software per convertire normali testi in EpiDoc XML, chiamato Chapel Hill Electronic Text Converter (CHETC). Altre aree includono l'uso di lessici di riferimento. Per esempio il progetto Inscriptions of Aphrodisias sta lavorando a stretto contatto con il Lexicon of Greek Personal Names, per garantirne la copertura completa e l'uso coerente.

                                      Il lavoro, diretto dal Dr. Elliott, è stato portato avanti da diversi studiosi che hanno lavorato in stretta collaborazione, e con regolari contatti con gli epigrafisti latu sensu. Si sono basati sull'esperienza di un progetto EpiDoc ben stabilito Vindolanda Tablets on line, e su due progetti in corso: the US Epigraphy Project (USEP) (sostenuto da Brown, Princeton e Rutgers Universities), e il progetto Inscriptions of Aphrodisias (InsAph) (finanziato dall'Arts and Humanities Research Council). Il generoso supporto dell'AHRC ha anche permesso di organizzare workshop intensivi in Marzo 2006 dove le linee guida sono state perfezionate.

                                      Responsabilità per questa sezione

                                      1. Charlotte Roueché, autore
                                      2. Julia Flanders, autore
                                      3. Pietro Maria Liuzzo, traduzione italiana
                                      4. Greta Franzini, correzione traduzione italiana
                                      5. Tom Elliott, coerced from TEI-Lite and various reformatting edits
                                      6. Gabriel Bodard, re-encoded and updated links

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps-pt-br.html b/gl/dev/intro-eps-pt-br.html index 6e5c14e7a..077b4b3d0 100644 --- a/gl/dev/intro-eps-pt-br.html +++ b/gl/dev/intro-eps-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Suave Introdução de Marcação para Epígrafos

                                      2023-04-27

                                      Os conceitos por trás do EpiDoc reúnem, para epígrafos, métodos e convenções editoriais tradicionais e modernas.

                                      Convenções epigráficas

                                      Durante o último século, epígrafos lutaram por maneiras de representar informação não verbal presentes dentro de seus textos. Até o final do século 19, editores tinham a prática de produzir uma fac-símile do texto, mas isto se tornou cada vez menos comum, e editoras não demonstraram boa vontade para apresentar um registro fotográfico completo de cada texto. As convenções que foram laboriosamente desenvolvidas para indicar texto perdido, abreviações, etc. têm sido mais ou menos universalmente aceitas desde os anos 1930 e coincidem, até certo ponto, com aquelas utilizadas em papirologia e paleografia. Todos os epígrafos já tiveram que lidar com problemas relativos a transplantar isto para o ambiente eletrônico - por exemplo, encontrar uma fonte que permita o ponto subescrito; a maior parte de nós, no entanto, se ajustou a estas restições.

                                      A dificuldade de representar estas convenções (em particular, os caracteres gregos) em fontes consistentes e na Web tende a atrasar a publicação online de textros epigráficos completos; em vez disto, coleções de busca muito ricas foram criadas, notadamente:

                                      Veja também: Conformidade (Compatibilidade EpiDoc).

                                      Todos estes desenvolvimentos foram determinados pelo estado da arte das tecnologias existentes, à medida que estas evoluíram ao longo do século 20. O objetivo do EpiDoc é explorar novas e ricas tecnologias e utilizá-las em conjunto com os objetivos tradicionais da epigrafia. Muitos dos processos descritos acima envolvem lutas contra os padrões tecnológicos - por exemplo, os de publicações impressas - de modo a acomodar a maior parte possível de nossas necessidades. Ao longo do tempo se tornou gradativamente mais difícil persuadir editores convencionais a atender nossa necessidade de inserção de informação meta-textual, a não ser com um custo proibitivamente alto. Ao mesmo tempo, as expectativas referentes ao volume de informação que deveria acompanhar um texto cresceram imensamente; além da informação sobre as circunstâncias físicas, o registro fotográfico se tornou padrão.

                                      Nos últimos 15 anos os pesquisadores têm lidado, de modo geral, com necessidades similares de incorporação de meta-dados dentro dos textos em seu formato eletrônico, e ferramentas surgiram para tornar isto cada vez mais fácil, com resultados cada vez mais valiosos. O software de processamento de texto é familiar desde os anos 1980, e nos permite controlar a formatação de nossos textos, utilizando marcação que hoje está incorporada de modo invisível dentro do software. As necessidades mais complexas de grandes coleções de documentos - documentos legais e industriais, publicações comerciais - levou, nos anos 1980, à investigação de maneiras de se inserir uma gama maior de informação e instrução dentro de textos eletrônicos. Inicialmente a ênfase era na inserção de instruções de formatação, mas logo surgiram métodos de inclusão de informação semântica mais complexa relativa à estrutura do documento e até ao conteúdo. Um exemplo simples é a marcação de um título de livro como título, em vez de simplesmente destacá-lo colocando-o em itálico. O uso desta marcação mais abstrata permite uma separação entre a estrutura e a apresentação, onde a estrutura é comparativamente mais fundamental ao gênero do documento, e a apresentação pode ser variada, dependendo da forma de publicação. De certa forma, esta mudança representa um retorno a uma forma mais antiga, na qual os autores lidavam com a substância do texto e e todos os detalhes da apresentação eram tratados pelo processo de publicação - uma distinção que se perdeu nos tempos de cópias prontas para impressão.

                                      Os protocolos que surgiram deste último esforço foram padronizados no final dos anos 1980 com o nome Standard Generalized Markup Language, emais recentemente receberam uma forma mais simples e de uso mais flexível na rede mundial, o XML: a Linguagem Extensível de Marcação. XML é hoje utilizado amplamente por pesquisadores em uma variedade de disciplinas humanísticas para capturar/representar e preservar material de pesquisa para uma variedade de objetivos.

                                      Os atrativos do XML para os epígrafos são, portanto, consideráveis. Por exemplo, material perdido pode ser marcado como tal, e então apresentado dentro de colchetes; ao mesmo tempo, uma busca pode receber a instrução de apenas interrogar texto que não foi marcado como perdido (ou seja, apenas termos atestados). Letras incertas podem ser marcadas como tal, e mais adiante uma decisão pode ser tomada se a letra será representada com um símbolo diacrítico ou de outro modo. Palavras podem ser lematizadas durante a edição para criar índices que crescem junto com a coleção. O mais importante nesta cojuntura, no entanto, é repetir o exercício 'Leyden'; ou seja, concordar a respeito de quais sejam os equivalentes eletrônicos das diversas siglas que utilizamos. Primeiramente, isto é valioso apenas para economizar tempo e trabalho; mas a consistência, sem a imposição da uniformidade, continua a ser valiosa. Ela não apenas dá suporte ao usuário, mas também à página impressa; documentos editados desta forma e publicados eletronicamente podem ser explorados juntos, mesmo que tenham sido preparados separadamente.

                                      A necessidade de padrões universalmente aceitos não se limita à epigrafia. Desde 1987 um consórcio internacional de pesquisadores (principalmente de humanidades) tem trabalhado em conjunto para desenvolver e refinar um conjunto de normas para a descrição da estrutura e do conteúdo de documentos. O resultado deste empreendimento foi aprodução de uma linguagem de codificação, desenvolvida em XML e descrita pelo nome do grupo - TEI, a Text Encoding Initiative (Iniciativa de Codificação de Texto).

                                      TEI para Epígrafos: O que é, porque utilizar?

                                      A Iniciativa de Codificação de Texto é um trabalho de pesquisa com a meta de definir uma linguagem de codificação que atenda todas as necessidades dos estudiosos das humanidades, de modo geral. Há dois objetivos essenciais que motivam o desenvolvimento da TEI. O primeiro é ajudar pesquisadores a representar seus objetos de pesquisa na forma digital usando uma linguagem descritiva que espelhe o tipo de termos e conceitos analíticos que são familiares e essenciais ao estudo humanístico. O segundo objetivo é permitir que os pesquisadores compartilhem o material resultante de forma inteligível, através do uso de uma linguagem descritiva comum.

                                      Podemos pensar na linguagem de codificação TEI como algo que lembra a linguagem humana: um centro de termos compartilhados, cercado por um vocabulário menos compartilhado - incluindo uso local, terminologia especializada e outras variações. No centro da TEI ficam os termos comuns e os conceitos amplamente compartilhados por pesquisadores na maioria das disciplinas: elementos como parágrafos, divisões genéricas de texto, cabeçalhos, listas, e assim por diante. Elementos mais especializados são agrupados de acordo com suas aplicações: por exemplo, elementos para a codificação detalhada de nomes, elementos para a representação das características de manuscritos, elementos para a captura da estrutura de dicionários, etc. TEI é intencionalmente organizada em módulos, para que os pesquisadores que trabalham em áreas específicas de uma disciplina utilizem apenas aqueles módulos relevantes ao seu trabalho, e descartem os outros. TEI pode, desta forma, alcançar uma grande área de atuação sem sobrecarregar pesquisadores e projetos individuais com a necessidade de dominar um grande número de habilidades, muitas das quais só são relevantes para outras disciplinas. Ao contrário, a linguagem de codificação TEI pode ser diretamente orientada a um domínio ou tarefa específicos, e pode ser limitada àquilo que é essencial ao trabalho daquele projeto individual.

                                      Como uma linguagem humana, a TEI pode ser utilizada de forma valer-se de um vocábulário rico e cheio de nuances, com codificação detalhada que descreve muitos fenômenos textuais, mas também pode ser utilizada de forma simples, apenas com o uso dos fatos textuais mais básicos: seções, cabeçalhos, parágrafos. Quanto mais detalhada for a codificação, mais se pode fazer com ela, mas fatores como tempo, custo, equipe disponível e expertise local podem limitar o nível detalhe possível de alcançar.

                                      Além disso, para apresentar um sistema de codificação que pesquisadores podem utilizar em sua forma original, a TEI também oferece um método para que os projetos de pesquisa definam versões customizadas da linguagem TEI, que incluem modificações necessárias para dar suporte a necessidades locais específicas. Como as versões customizadas operam dentro da estrutura geral da TEI, elas podem fazer uso de termos e conceitos chave compartilhados, desta forma evitando o trabalho desnecessário de reinventá-los. E, como a TEI oferece uma estrutura comum para a criação e descrição de customizações, elas podem ser compartilhadas com facilidade e coerência. Como resultado, grupos de pesquisadores de disciplinas particulares podem articular metas e métodos específicos para caracterizar seu trabalho, e as diferenças que o distinguem de outros trabalhos de campos relacionados. No lugar de enfoques mutuamente initeligíveis, projetos diferentes podem produzir resultados cujas diferenças resultem de discordâncias reais, em vez de simples divergências acidentais.

                                      A Customização EpiDoc: TEI para epígrafos

                                      Dentro desta estrutura, a Comunidade EpiDoc está trabalhando desde 2000 para desenvolver uma versão customizada das Normas TEI que dê suporte às necessidades particulares dos epígrafos. A ideia foi lançada por Tom Elliott, um historiador da antiguadade na University of North Carolina em Chapel Hill; o objetivo é tanto aproveitar ao máximo o trabalho que já foi feito quanto assegurar que textos que aparecem inscritos sejam tratados de uma maneira consistente com a que foi utilizada por outros textos, e não se distanciar destes. A customização EpiDoc remove os elementos irrelevantes do corpo da TEI, e adiciona provisões para tipos específicos de transcrições, análises, descrições e classificações que são essenciais para o trabalho epigráfico. O resultado é uma linguagem simples mas poderosa que pode ser utilizada para marcar todos os elementos significativos de inscrições e também representar a informação anexa a respeito do objeto epigráfico em si.

                                      Para acompanhar a linguagem de codificação EpiDoc, a comunidade EpiDoc também produziu um conjunto de normas de codificação e ferramentas de software, bem como documentação que descreve como utilizar a linguagem de codificação, as ferramentas e os outros elementos do método EpiDoc. O objetivo é estabelecer uma estrutura que seja fácil de aprender e usar, mesmo para pesquisadores sem experiência ou suporte tecnológico. Pode parecer improvável, mas este empreendimento é da mesma ordem de se aprender a marcação de um texto epigráfico padrão, com as séries de siglas existentes.

                                      O grupo trabalhou para desenvolver expressões para todas as convenções epigráficas aceitas. Ele expandiu este guia para atender os diversos campos que podem estar presentes numa publicação epigráfica, inclusive:

                                      Veja mais em: Estrutura do Documento.

                                      Outras áreas que estão sendo ativamente exploradas incluem o desenvolvimento de interoperabilidade. Uma ferramenta de software para a conversão de textos de marcação epigráfica comum para XML de EpiDoc já foi desenvolvido (o assim chamado Conversor de Texto Eletrônico Chapel Hill (Chapel Hill Electronic Text Converter - CHETC)). Outras áreas envolvem to uso de léxico seguro. Por exemplo, o projeto Inscrições de Aphrodisias está trabalhando em proximidade com o Léxico de Nomes Pessoais Gregos, para assegurar total cobertura e uso consistente.

                                      O trabalho, liderado pelo Dr. Elliott, tem sido desempenhado por vários pesquisadores individuais trabalhando em colaboração e em contato regular com o resto da profissão. Eles fizeram uso da experiência de um projeto EpiDoc já estabelecido, o Tabletes Vindolanda on line, e dois projetos em curso: o US Epigraphy Project (USEP) (que recebe suporte das universidades Brown, Princeton e Rutgers), e o Projeto Inscrições de Aphrodisias (Inscriptions of Aphrodisias Project - InsAph) (que recebe suporte do Conselho de Pesquisa em Artes e Humanidades - AHRC). O apoio generoso do AHRC permitiu o acontecimento do workshop intensivo de março de 2006, onde estas normas foran refinadas.

                                      Responsabilidade por esta seção

                                      1. Charlotte Roueché, autor
                                      2. Julia Flanders, autor
                                      3. Tom Elliott, coagido para longe do TEI-Lite e diversas edições de reforma edits
                                      4. Gabriel Bodard, consertou e atualizou muitos links
                                      5. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Suave Introdução de Marcação para Epígrafos

                                      2024-03-05

                                      Os conceitos por trás do EpiDoc reúnem, para epígrafos, métodos e convenções editoriais tradicionais e modernas.

                                      Convenções epigráficas

                                      Durante o último século, epígrafos lutaram por maneiras de representar informação não verbal presentes dentro de seus textos. Até o final do século 19, editores tinham a prática de produzir uma fac-símile do texto, mas isto se tornou cada vez menos comum, e editoras não demonstraram boa vontade para apresentar um registro fotográfico completo de cada texto. As convenções que foram laboriosamente desenvolvidas para indicar texto perdido, abreviações, etc. têm sido mais ou menos universalmente aceitas desde os anos 1930 e coincidem, até certo ponto, com aquelas utilizadas em papirologia e paleografia. Todos os epígrafos já tiveram que lidar com problemas relativos a transplantar isto para o ambiente eletrônico - por exemplo, encontrar uma fonte que permita o ponto subescrito; a maior parte de nós, no entanto, se ajustou a estas restições.

                                      A dificuldade de representar estas convenções (em particular, os caracteres gregos) em fontes consistentes e na Web tende a atrasar a publicação online de textros epigráficos completos; em vez disto, coleções de busca muito ricas foram criadas, notadamente:

                                      Veja também: Conformidade (Compatibilidade EpiDoc).

                                      Todos estes desenvolvimentos foram determinados pelo estado da arte das tecnologias existentes, à medida que estas evoluíram ao longo do século 20. O objetivo do EpiDoc é explorar novas e ricas tecnologias e utilizá-las em conjunto com os objetivos tradicionais da epigrafia. Muitos dos processos descritos acima envolvem lutas contra os padrões tecnológicos - por exemplo, os de publicações impressas - de modo a acomodar a maior parte possível de nossas necessidades. Ao longo do tempo se tornou gradativamente mais difícil persuadir editores convencionais a atender nossa necessidade de inserção de informação meta-textual, a não ser com um custo proibitivamente alto. Ao mesmo tempo, as expectativas referentes ao volume de informação que deveria acompanhar um texto cresceram imensamente; além da informação sobre as circunstâncias físicas, o registro fotográfico se tornou padrão.

                                      Nos últimos 15 anos os pesquisadores têm lidado, de modo geral, com necessidades similares de incorporação de meta-dados dentro dos textos em seu formato eletrônico, e ferramentas surgiram para tornar isto cada vez mais fácil, com resultados cada vez mais valiosos. O software de processamento de texto é familiar desde os anos 1980, e nos permite controlar a formatação de nossos textos, utilizando marcação que hoje está incorporada de modo invisível dentro do software. As necessidades mais complexas de grandes coleções de documentos - documentos legais e industriais, publicações comerciais - levou, nos anos 1980, à investigação de maneiras de se inserir uma gama maior de informação e instrução dentro de textos eletrônicos. Inicialmente a ênfase era na inserção de instruções de formatação, mas logo surgiram métodos de inclusão de informação semântica mais complexa relativa à estrutura do documento e até ao conteúdo. Um exemplo simples é a marcação de um título de livro como título, em vez de simplesmente destacá-lo colocando-o em itálico. O uso desta marcação mais abstrata permite uma separação entre a estrutura e a apresentação, onde a estrutura é comparativamente mais fundamental ao gênero do documento, e a apresentação pode ser variada, dependendo da forma de publicação. De certa forma, esta mudança representa um retorno a uma forma mais antiga, na qual os autores lidavam com a substância do texto e e todos os detalhes da apresentação eram tratados pelo processo de publicação - uma distinção que se perdeu nos tempos de cópias prontas para impressão.

                                      Os protocolos que surgiram deste último esforço foram padronizados no final dos anos 1980 com o nome Standard Generalized Markup Language, emais recentemente receberam uma forma mais simples e de uso mais flexível na rede mundial, o XML: a Linguagem Extensível de Marcação. XML é hoje utilizado amplamente por pesquisadores em uma variedade de disciplinas humanísticas para capturar/representar e preservar material de pesquisa para uma variedade de objetivos.

                                      Os atrativos do XML para os epígrafos são, portanto, consideráveis. Por exemplo, material perdido pode ser marcado como tal, e então apresentado dentro de colchetes; ao mesmo tempo, uma busca pode receber a instrução de apenas interrogar texto que não foi marcado como perdido (ou seja, apenas termos atestados). Letras incertas podem ser marcadas como tal, e mais adiante uma decisão pode ser tomada se a letra será representada com um símbolo diacrítico ou de outro modo. Palavras podem ser lematizadas durante a edição para criar índices que crescem junto com a coleção. O mais importante nesta cojuntura, no entanto, é repetir o exercício 'Leyden'; ou seja, concordar a respeito de quais sejam os equivalentes eletrônicos das diversas siglas que utilizamos. Primeiramente, isto é valioso apenas para economizar tempo e trabalho; mas a consistência, sem a imposição da uniformidade, continua a ser valiosa. Ela não apenas dá suporte ao usuário, mas também à página impressa; documentos editados desta forma e publicados eletronicamente podem ser explorados juntos, mesmo que tenham sido preparados separadamente.

                                      A necessidade de padrões universalmente aceitos não se limita à epigrafia. Desde 1987 um consórcio internacional de pesquisadores (principalmente de humanidades) tem trabalhado em conjunto para desenvolver e refinar um conjunto de normas para a descrição da estrutura e do conteúdo de documentos. O resultado deste empreendimento foi aprodução de uma linguagem de codificação, desenvolvida em XML e descrita pelo nome do grupo - TEI, a Text Encoding Initiative (Iniciativa de Codificação de Texto).

                                      TEI para Epígrafos: O que é, porque utilizar?

                                      A Iniciativa de Codificação de Texto é um trabalho de pesquisa com a meta de definir uma linguagem de codificação que atenda todas as necessidades dos estudiosos das humanidades, de modo geral. Há dois objetivos essenciais que motivam o desenvolvimento da TEI. O primeiro é ajudar pesquisadores a representar seus objetos de pesquisa na forma digital usando uma linguagem descritiva que espelhe o tipo de termos e conceitos analíticos que são familiares e essenciais ao estudo humanístico. O segundo objetivo é permitir que os pesquisadores compartilhem o material resultante de forma inteligível, através do uso de uma linguagem descritiva comum.

                                      Podemos pensar na linguagem de codificação TEI como algo que lembra a linguagem humana: um centro de termos compartilhados, cercado por um vocabulário menos compartilhado - incluindo uso local, terminologia especializada e outras variações. No centro da TEI ficam os termos comuns e os conceitos amplamente compartilhados por pesquisadores na maioria das disciplinas: elementos como parágrafos, divisões genéricas de texto, cabeçalhos, listas, e assim por diante. Elementos mais especializados são agrupados de acordo com suas aplicações: por exemplo, elementos para a codificação detalhada de nomes, elementos para a representação das características de manuscritos, elementos para a captura da estrutura de dicionários, etc. TEI é intencionalmente organizada em módulos, para que os pesquisadores que trabalham em áreas específicas de uma disciplina utilizem apenas aqueles módulos relevantes ao seu trabalho, e descartem os outros. TEI pode, desta forma, alcançar uma grande área de atuação sem sobrecarregar pesquisadores e projetos individuais com a necessidade de dominar um grande número de habilidades, muitas das quais só são relevantes para outras disciplinas. Ao contrário, a linguagem de codificação TEI pode ser diretamente orientada a um domínio ou tarefa específicos, e pode ser limitada àquilo que é essencial ao trabalho daquele projeto individual.

                                      Como uma linguagem humana, a TEI pode ser utilizada de forma valer-se de um vocábulário rico e cheio de nuances, com codificação detalhada que descreve muitos fenômenos textuais, mas também pode ser utilizada de forma simples, apenas com o uso dos fatos textuais mais básicos: seções, cabeçalhos, parágrafos. Quanto mais detalhada for a codificação, mais se pode fazer com ela, mas fatores como tempo, custo, equipe disponível e expertise local podem limitar o nível detalhe possível de alcançar.

                                      Além disso, para apresentar um sistema de codificação que pesquisadores podem utilizar em sua forma original, a TEI também oferece um método para que os projetos de pesquisa definam versões customizadas da linguagem TEI, que incluem modificações necessárias para dar suporte a necessidades locais específicas. Como as versões customizadas operam dentro da estrutura geral da TEI, elas podem fazer uso de termos e conceitos chave compartilhados, desta forma evitando o trabalho desnecessário de reinventá-los. E, como a TEI oferece uma estrutura comum para a criação e descrição de customizações, elas podem ser compartilhadas com facilidade e coerência. Como resultado, grupos de pesquisadores de disciplinas particulares podem articular metas e métodos específicos para caracterizar seu trabalho, e as diferenças que o distinguem de outros trabalhos de campos relacionados. No lugar de enfoques mutuamente initeligíveis, projetos diferentes podem produzir resultados cujas diferenças resultem de discordâncias reais, em vez de simples divergências acidentais.

                                      A Customização EpiDoc: TEI para epígrafos

                                      Dentro desta estrutura, a Comunidade EpiDoc está trabalhando desde 2000 para desenvolver uma versão customizada das Normas TEI que dê suporte às necessidades particulares dos epígrafos. A ideia foi lançada por Tom Elliott, um historiador da antiguadade na University of North Carolina em Chapel Hill; o objetivo é tanto aproveitar ao máximo o trabalho que já foi feito quanto assegurar que textos que aparecem inscritos sejam tratados de uma maneira consistente com a que foi utilizada por outros textos, e não se distanciar destes. A customização EpiDoc remove os elementos irrelevantes do corpo da TEI, e adiciona provisões para tipos específicos de transcrições, análises, descrições e classificações que são essenciais para o trabalho epigráfico. O resultado é uma linguagem simples mas poderosa que pode ser utilizada para marcar todos os elementos significativos de inscrições e também representar a informação anexa a respeito do objeto epigráfico em si.

                                      Para acompanhar a linguagem de codificação EpiDoc, a comunidade EpiDoc também produziu um conjunto de normas de codificação e ferramentas de software, bem como documentação que descreve como utilizar a linguagem de codificação, as ferramentas e os outros elementos do método EpiDoc. O objetivo é estabelecer uma estrutura que seja fácil de aprender e usar, mesmo para pesquisadores sem experiência ou suporte tecnológico. Pode parecer improvável, mas este empreendimento é da mesma ordem de se aprender a marcação de um texto epigráfico padrão, com as séries de siglas existentes.

                                      O grupo trabalhou para desenvolver expressões para todas as convenções epigráficas aceitas. Ele expandiu este guia para atender os diversos campos que podem estar presentes numa publicação epigráfica, inclusive:

                                      Veja mais em: Estrutura do Documento.

                                      Outras áreas que estão sendo ativamente exploradas incluem o desenvolvimento de interoperabilidade. Uma ferramenta de software para a conversão de textos de marcação epigráfica comum para XML de EpiDoc já foi desenvolvido (o assim chamado Conversor de Texto Eletrônico Chapel Hill (Chapel Hill Electronic Text Converter - CHETC)). Outras áreas envolvem to uso de léxico seguro. Por exemplo, o projeto Inscrições de Aphrodisias está trabalhando em proximidade com o Léxico de Nomes Pessoais Gregos, para assegurar total cobertura e uso consistente.

                                      O trabalho, liderado pelo Dr. Elliott, tem sido desempenhado por vários pesquisadores individuais trabalhando em colaboração e em contato regular com o resto da profissão. Eles fizeram uso da experiência de um projeto EpiDoc já estabelecido, o Tabletes Vindolanda on line, e dois projetos em curso: o US Epigraphy Project (USEP) (que recebe suporte das universidades Brown, Princeton e Rutgers), e o Projeto Inscrições de Aphrodisias (Inscriptions of Aphrodisias Project - InsAph) (que recebe suporte do Conselho de Pesquisa em Artes e Humanidades - AHRC). O apoio generoso do AHRC permitiu o acontecimento do workshop intensivo de março de 2006, onde estas normas foran refinadas.

                                      Responsabilidade por esta seção

                                      1. Charlotte Roueché, autor
                                      2. Julia Flanders, autor
                                      3. Tom Elliott, coagido para longe do TEI-Lite e diversas edições de reforma edits
                                      4. Gabriel Bodard, consertou e atualizou muitos links
                                      5. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-eps.html b/gl/dev/intro-eps.html index a3a8211c6..96cd9c335 100644 --- a/gl/dev/intro-eps.html +++ b/gl/dev/intro-eps.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Gentle Introduction to Mark-up for Epigraphers

                                      2023-04-27

                                      Note: The original version of this chapter written by Julia Flanders and Charlotte Roueché in 2006 has been archived at the Stoa Review.

                                      The concepts behind EpiDoc bring together, for epigraphers, traditional and entirely modern editorial methods and conventions.

                                      Epigraphic conventions

                                      Over the last century, epigraphers have wrestled with the issues involved in representing non-verbal information within their written texts. Until the end of the 19th century publishers could be expected to produce a facsimile of the text, but this became decreasingly common, and publishers did not demonstrate a parallel willingness to provide a full photographic record of every text. The conventions which have been painfully developed to indicate missing text, abbreviations, etc. have been more or less generally agreed since the 1930s and overlap, to some extent, with those used in papyrology and palaeography. All epigraphers have had to deal with the issues involved in moving this to an electronic environment—for example, finding a font which will permit underdotting; but most of us have now adjusted to these new constraints.

                                      The difficulty of rendering such conventions and, in particular, Greek characters in consistent fonts and on the Web has tended to delay the publication of full epigraphic texts online; instead, enormously rich search collections have been created, most notably:

                                      See also: Conformance (EpiDoc Compatibility).

                                      All these developments have therefore been determined by the state of the existing technologies, as these have evolved over the 20th century. The object of EpiDoc is to exploit new and rich technologies for the traditional purposes of epigraphy. Many of the processes described above have involved struggling agaist the technological standards—for example, in print publications—in order to accommodate as many of our requirements as possible. Over the period it has become steadily more difficult to persuade conventional publishers to meet our requirements for inserting meta-textual information, unless at prohibitive expense. At the same time, the expectations as to the volume of information which should accompany a text have risen greatly; as well as information about physical circumstances, photographic illustration has become standard.

                                      In the last 15 years scholars generally have been dealing with similar requirements to incorporate meta-data within texts in their electronic form, and tools have emerged which make this increasingly easy and make the results increasingly valuable. The word-processing software that has been familiar since the 1980s allows us to control the formatting of our texts, using markup which by now is invisibly embedded by the software. The more demanding requirements of large-scale document collections—legal papers, industrial documentation, commercial publishing—led in the 1980s to the investigation of ways to insert a wider range of information and instructions within electronic texts. At first the emphasis was on inserting formatting instructions, but there soon emerged methods of including more complex semantic information concerning document structure and even content. A simple example is marking up a book title as a title, rather than simply marking it as being italicized. The use of this more abstract markup permits a separation of structure and presentation, where structure is comparatively fundamental to the document's genre, while presentation may be varied depending on the form of publication. In a way, this shift represents a return to an earlier mode in which authors dealt with the substance of the text and all details of presentation were handled in the publishing process—a distinction which has been lost in the days of camera-ready copy.

                                      The protocols which emerged from this latter effort were standardized in the late 1980s as the Standard Generalized Markup Language, and more recently were given a simpler and more flexible form for use in the world-wide web as XML: the Extensible Markup Language. XML is now widely used by scholars in a broad range of humanistic disciplines to capture/represent and preserve research materials for a wide range of purposes.

                                      The attractions of XML for epigraphers are therefore considerable. For example: missing material can be marked up as such, and then presented within square brackets; at the same time, a search can be instructed only to interrogate text which has not been marked up as missing (so only definitely attested terms). Uncertain letters can be marked up as such, and a decision made later as to whether to render them with an underdot or in another way. Words can be lemmatised during editing, to create indices which grow as the collection grows. What is important, however, at this juncture is to repeat the 'Leyden' exercise; that is, to agree electronic equivalents of the various sigla that we use. Firstly, this is valuable simply in order to save time and trouble; but also consistency—without imposing uniformity—continues to be valuable. Not only does it support the user, as on the printed page; but documents edited in this way and published electronically will then be exploitable together, even if they have been prepared separately.

                                      The need for agreed standards is not limited to epigraphy. Since 1987 an international consortium of scholars principally in the humanities has been working together to develop and refine a set of guidelines for describing the structure and content of documents. The results of this endeavour have produced an encoding language, realized in XML and described by the name of the group—TEI, the Text Encoding Initiatve.

                                      TEI for Epigraphers: What is it, why use it?

                                      The Text Encoding Initiative is a research effort aimed at defining an encoding language that encompasses the needs of humanities scholars very generally. There are two essential goals motivating the development of the TEI. The first is to enable scholars to represent their research materials in digital form using a descriptive language that mirrors the kinds of analytical terms and concepts that are familiar and essential to humanistic scholarship. The second goal is to enable scholars to share the resulting materials intelligibly, by using a common descriptive language.

                                      We can think of the TEI encoding language as resembling a human language: a core of shared terms at the center, surrounded by less widely shared vocabularies including local usage, specialized terminology, and other variations. At the core of the TEI are the common terms and concepts that are broadly shared by scholars in most disciplines: features like paragraphs, generic textual divisions, headings, lists, and so forth. More specialized elements are grouped together according to their applications: for instance, elements for detailed encoding of names, elements for representing features of manuscripts, elements for capturing the structure of dictionaries, and so forth. The TEI is intentionally organized into modules in this way, so that scholars working in specific disciplinary areas may use only the modules relevant to their work, and omit the others. The TEI can thus achieve a great deal of breadth without burdening individual scholars and projects with the necessity of mastering a very large domain, much of which is only relevant to other disciplines. On the contrary, the TEI encoding language can be very directly targeted at a specific domain or task, and can be limited to what is essential to the individual project's work.

                                      Like a human language, TEI can be used in a way that draws on a rich and nuanced vocabulary, with detailed encoding that describes a great many textual phenomena, but it can also be used very simply, using only a few essential concepts that describe only the most basic textual facts: sections, headings, paragraphs. The more detailed the encoding, the more one can do with it, but factors such as time, cost, available staff, and local expertise may place constraints on the level of detail that is feasible.

                                      In addition to providing an encoding system that scholars can use in its original state, the TEI also provides a way for scholarly projects to define custom versions of the TEI language which include modifications that are necessary to support specific local needs. Because these custom versions operate within the overall TEI framework, they can use its broadly shared core of terms and concepts, thereby avoiding unnecessary work in reinventing these. And because the TEI provides a common framework for creating and describing customizations, these can be shared easily and meaningfully. As a result, groups of scholars in particular disciplines can articulate the specific goals and methods which characterize their work, and the differences which distinguish them from others working in related fields. Instead of mutually unintelligible approaches, different projects can produce results whose differences result from real disagreements rather than simple random divergence.

                                      The EpiDoc Customization: TEI for Epigraphers

                                      Within this framework, the EpiDoc community has been working, since 2000, to develop a custom version of the TEI Guidelines to support the particular needs of epigraphers. The idea was launched by Tom Elliott, an ancient historian at the University of North Carolina at Chapel Hill; the aim is both to make the fullest possible use of the work that has already been done, and also to ensure that texts which happen to be inscribed are handled in a manner consistent with that used for other texts, and not distanced from them. The EpiDoc customization removes irrelevant elements from the main body of the TEI, and it adds provisions for the specific kinds of transcription, analysis, description, and classification that are essential for epigraphic work. The result is a simple yet powerful language which can be used to mark all of the significant features of inscriptions and also represent the accompanying information about the epigraphic object itself.

                                      To accompany the EpiDoc encoding language, the EpiDoc community has also produced a set of encoding guidelines and software tools, as well as documentation which describes how to use the encoding language, the tools, and the other elements of the EpiDoc method. The goal is to establish a framework that is easy to learn and use, even for scholars with no technical background or support. This may sound improbable, but the enterprise is of the same order as learning to mark-up a standard epigraphic text, with the existing series of sigla.

                                      The group has worked to develop expressions for all the agreed epigraphic conventions. They have expanded this guidance to address the various fields which may be presented in an epigraphic publication, including:

                                      See further: Document Structure.

                                      Further areas under active exploration include developing interoperability. A software tool for converting texts in normal epigraphic markup into EpiDoc XML has already been developed (the so-called Chapel Hill Electronic Text Converter (CHETC)). Other areas involve the use of authoritative lexica. For example, the Inscriptions of Aphrodisias project is working closely with the Lexicon of Greek Personal Names, to ensure full coverage and consistent usage.

                                      The work, led by Dr. Elliott, has been undertaken by various individual scholars working in close collaboration, and in regular contact with the wider profession. They have drawn on the experience of an established EpiDoc project, the Vindolanda Tablets on line, and two current projects: the US Epigraphy Project (USEP) (supported by Brown, Princeton and Rutgers Universities), and the Inscriptions of Aphrodisias Project (InsAph) (supported by the Arts and Humanities Research Council). The generous support of the AHRC allowed for the intensive workshop in March 2006 where these guidelines were refined.

                                      Responsibility for this section

                                      1. Charlotte Roueché, author
                                      2. Julia Flanders, author
                                      3. Tom Elliott, coerced from TEI-Lite and various reformatting edits
                                      4. Gabriel Bodard, fixed and updated many links

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Gentle Introduction to Mark-up for Epigraphers

                                      2024-03-05

                                      Note: The original version of this chapter written by Julia Flanders and Charlotte Roueché in 2006 has been archived at the Stoa Review.

                                      The concepts behind EpiDoc bring together, for epigraphers, traditional and entirely modern editorial methods and conventions.

                                      Epigraphic conventions

                                      Over the last century, epigraphers have wrestled with the issues involved in representing non-verbal information within their written texts. Until the end of the 19th century publishers could be expected to produce a facsimile of the text, but this became decreasingly common, and publishers did not demonstrate a parallel willingness to provide a full photographic record of every text. The conventions which have been painfully developed to indicate missing text, abbreviations, etc. have been more or less generally agreed since the 1930s and overlap, to some extent, with those used in papyrology and palaeography. All epigraphers have had to deal with the issues involved in moving this to an electronic environment—for example, finding a font which will permit underdotting; but most of us have now adjusted to these new constraints.

                                      The difficulty of rendering such conventions and, in particular, Greek characters in consistent fonts and on the Web has tended to delay the publication of full epigraphic texts online; instead, enormously rich search collections have been created, most notably:

                                      See also: Conformance (EpiDoc Compatibility).

                                      All these developments have therefore been determined by the state of the existing technologies, as these have evolved over the 20th century. The object of EpiDoc is to exploit new and rich technologies for the traditional purposes of epigraphy. Many of the processes described above have involved struggling agaist the technological standards—for example, in print publications—in order to accommodate as many of our requirements as possible. Over the period it has become steadily more difficult to persuade conventional publishers to meet our requirements for inserting meta-textual information, unless at prohibitive expense. At the same time, the expectations as to the volume of information which should accompany a text have risen greatly; as well as information about physical circumstances, photographic illustration has become standard.

                                      In the last 15 years scholars generally have been dealing with similar requirements to incorporate meta-data within texts in their electronic form, and tools have emerged which make this increasingly easy and make the results increasingly valuable. The word-processing software that has been familiar since the 1980s allows us to control the formatting of our texts, using markup which by now is invisibly embedded by the software. The more demanding requirements of large-scale document collections—legal papers, industrial documentation, commercial publishing—led in the 1980s to the investigation of ways to insert a wider range of information and instructions within electronic texts. At first the emphasis was on inserting formatting instructions, but there soon emerged methods of including more complex semantic information concerning document structure and even content. A simple example is marking up a book title as a title, rather than simply marking it as being italicized. The use of this more abstract markup permits a separation of structure and presentation, where structure is comparatively fundamental to the document's genre, while presentation may be varied depending on the form of publication. In a way, this shift represents a return to an earlier mode in which authors dealt with the substance of the text and all details of presentation were handled in the publishing process—a distinction which has been lost in the days of camera-ready copy.

                                      The protocols which emerged from this latter effort were standardized in the late 1980s as the Standard Generalized Markup Language, and more recently were given a simpler and more flexible form for use in the world-wide web as XML: the Extensible Markup Language. XML is now widely used by scholars in a broad range of humanistic disciplines to capture/represent and preserve research materials for a wide range of purposes.

                                      The attractions of XML for epigraphers are therefore considerable. For example: missing material can be marked up as such, and then presented within square brackets; at the same time, a search can be instructed only to interrogate text which has not been marked up as missing (so only definitely attested terms). Uncertain letters can be marked up as such, and a decision made later as to whether to render them with an underdot or in another way. Words can be lemmatised during editing, to create indices which grow as the collection grows. What is important, however, at this juncture is to repeat the 'Leyden' exercise; that is, to agree electronic equivalents of the various sigla that we use. Firstly, this is valuable simply in order to save time and trouble; but also consistency—without imposing uniformity—continues to be valuable. Not only does it support the user, as on the printed page; but documents edited in this way and published electronically will then be exploitable together, even if they have been prepared separately.

                                      The need for agreed standards is not limited to epigraphy. Since 1987 an international consortium of scholars principally in the humanities has been working together to develop and refine a set of guidelines for describing the structure and content of documents. The results of this endeavour have produced an encoding language, realized in XML and described by the name of the group—TEI, the Text Encoding Initiatve.

                                      TEI for Epigraphers: What is it, why use it?

                                      The Text Encoding Initiative is a research effort aimed at defining an encoding language that encompasses the needs of humanities scholars very generally. There are two essential goals motivating the development of the TEI. The first is to enable scholars to represent their research materials in digital form using a descriptive language that mirrors the kinds of analytical terms and concepts that are familiar and essential to humanistic scholarship. The second goal is to enable scholars to share the resulting materials intelligibly, by using a common descriptive language.

                                      We can think of the TEI encoding language as resembling a human language: a core of shared terms at the center, surrounded by less widely shared vocabularies including local usage, specialized terminology, and other variations. At the core of the TEI are the common terms and concepts that are broadly shared by scholars in most disciplines: features like paragraphs, generic textual divisions, headings, lists, and so forth. More specialized elements are grouped together according to their applications: for instance, elements for detailed encoding of names, elements for representing features of manuscripts, elements for capturing the structure of dictionaries, and so forth. The TEI is intentionally organized into modules in this way, so that scholars working in specific disciplinary areas may use only the modules relevant to their work, and omit the others. The TEI can thus achieve a great deal of breadth without burdening individual scholars and projects with the necessity of mastering a very large domain, much of which is only relevant to other disciplines. On the contrary, the TEI encoding language can be very directly targeted at a specific domain or task, and can be limited to what is essential to the individual project's work.

                                      Like a human language, TEI can be used in a way that draws on a rich and nuanced vocabulary, with detailed encoding that describes a great many textual phenomena, but it can also be used very simply, using only a few essential concepts that describe only the most basic textual facts: sections, headings, paragraphs. The more detailed the encoding, the more one can do with it, but factors such as time, cost, available staff, and local expertise may place constraints on the level of detail that is feasible.

                                      In addition to providing an encoding system that scholars can use in its original state, the TEI also provides a way for scholarly projects to define custom versions of the TEI language which include modifications that are necessary to support specific local needs. Because these custom versions operate within the overall TEI framework, they can use its broadly shared core of terms and concepts, thereby avoiding unnecessary work in reinventing these. And because the TEI provides a common framework for creating and describing customizations, these can be shared easily and meaningfully. As a result, groups of scholars in particular disciplines can articulate the specific goals and methods which characterize their work, and the differences which distinguish them from others working in related fields. Instead of mutually unintelligible approaches, different projects can produce results whose differences result from real disagreements rather than simple random divergence.

                                      The EpiDoc Customization: TEI for Epigraphers

                                      Within this framework, the EpiDoc community has been working, since 2000, to develop a custom version of the TEI Guidelines to support the particular needs of epigraphers. The idea was launched by Tom Elliott, an ancient historian at the University of North Carolina at Chapel Hill; the aim is both to make the fullest possible use of the work that has already been done, and also to ensure that texts which happen to be inscribed are handled in a manner consistent with that used for other texts, and not distanced from them. The EpiDoc customization removes irrelevant elements from the main body of the TEI, and it adds provisions for the specific kinds of transcription, analysis, description, and classification that are essential for epigraphic work. The result is a simple yet powerful language which can be used to mark all of the significant features of inscriptions and also represent the accompanying information about the epigraphic object itself.

                                      To accompany the EpiDoc encoding language, the EpiDoc community has also produced a set of encoding guidelines and software tools, as well as documentation which describes how to use the encoding language, the tools, and the other elements of the EpiDoc method. The goal is to establish a framework that is easy to learn and use, even for scholars with no technical background or support. This may sound improbable, but the enterprise is of the same order as learning to mark-up a standard epigraphic text, with the existing series of sigla.

                                      The group has worked to develop expressions for all the agreed epigraphic conventions. They have expanded this guidance to address the various fields which may be presented in an epigraphic publication, including:

                                      See further: Document Structure.

                                      Further areas under active exploration include developing interoperability. A software tool for converting texts in normal epigraphic markup into EpiDoc XML has already been developed (the so-called Chapel Hill Electronic Text Converter (CHETC)). Other areas involve the use of authoritative lexica. For example, the Inscriptions of Aphrodisias project is working closely with the Lexicon of Greek Personal Names, to ensure full coverage and consistent usage.

                                      The work, led by Dr. Elliott, has been undertaken by various individual scholars working in close collaboration, and in regular contact with the wider profession. They have drawn on the experience of an established EpiDoc project, the Vindolanda Tablets on line, and two current projects: the US Epigraphy Project (USEP) (supported by Brown, Princeton and Rutgers Universities), and the Inscriptions of Aphrodisias Project (InsAph) (supported by the Arts and Humanities Research Council). The generous support of the AHRC allowed for the intensive workshop in March 2006 where these guidelines were refined.

                                      Responsibility for this section

                                      1. Charlotte Roueché, author
                                      2. Julia Flanders, author
                                      3. Tom Elliott, coerced from TEI-Lite and various reformatting edits
                                      4. Gabriel Bodard, fixed and updated many links

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-bg.html b/gl/dev/intro-intro-bg.html index 5ca3770b9..235d04f74 100644 --- a/gl/dev/intro-intro-bg.html +++ b/gl/dev/intro-intro-bg.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Как да използваме Насoките за EpiDoc

                                      2023-04-27

                                      EpiDoc представлява широк спектър от сътрудничество между проекти и учени, които работят с документи от антични източници в Text Encoding Initiative (TEI) XML, и изработват препоръки, инструменти и добри практики за дигитално кодиране, обработка и публикуване на подобни текстове. Главната страница на EpiDoc може да бъде намерена на следния адрес: http://epidoc.sf.net.

                                      Настоящият документ (Насоки за EpiDoc) е текущ продукт от дейността на EpiDoc общността през последните няколко години. Той описва как се кодират разнообразни особености на епиграфските и папироложките документи, въз основа на базови принципи за редактиране на научни текстове (например т. нар. Установени практики по Leiden за особености при транскрибиране, както и модели за данни като Electronic Archive of Greek and Latin Epigraphy (EAGLE) за особености при описателни и исторически елементи). Насоките трябва да бъдат използвани заедно с EpiDoc Schema, според които валидността на документи, маркирани съгласно тези принципи, трябва да бъде потвърдена, както и с EpiDoc Example Stylesheets, чиято главна цел е да предоставят основен израз на всяка от описаните особености.

                                      Насоките за EpiDoc не претендират да дават пълно обяснение на това как се стартира EpiDoc проект, създава уебсайт, изграждат инструменти за търсене, или други подобни технически и съвместни начинания, които публикуването на кодирани текстове онлайн изисква. Нито пък са детайлно въведение към епиграфиката или папирологията; те Насоките предимно представляват ръководство към XML кодирането на особености на издания на антични документи, често използвани в областта на епиграфиката или сродни на нея дисциплини.

                                      Въпреки че няма единна установена практика за структуриране на епиграфско или папироложко издание, Насоките за EpiDocEpiDoc Stylesheets) подемат подход, който е в съответствие с моделите, използвани в проекти и съвместни сътрудничества като Advanced Papyrological Information System (APIS), EAGLE, и Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Предвид факта, че дисциплината епиграфика в общ смисъл и в частност, дигиталната епиграфика, вече имат устойчиви модели на добри практики в структурирането на издания, ние просто препоръчваме кодиране в TEI XML на същите данни и наблюдения, които в своята практиката учените са установили за важни или полезни.

                                      Насоките за EpiDoc са замислени като допълнение към Установените практики на Leiden (оттук-нататък "Leiden"), които повече от 80 години намират приложение в областта на епиграфиката и папирологията и се възприемат от широк спектър науки в областта на филологията и документаристиката. В Насоките е разписано, че Leiden се възриема за безспорна основа за отразяване на различия, регистрирани в дадено издание на предмодерен текст, като техните препоръки и примери се основават на тези различия, без да се изискват специфични типографски установени практики и препоръчани сигли в това отношение. Т.е целта на EpiDoc е ясно да регистрира в XML такива текстови интервенции като редакторска добавка на символи, които са напълно изгубени или с нарушена цялост, без да има нужда тези добавки да бъдат предадени в „квадратни скоби” ("[" и "]") в самия XML или какъвто и да бил производен документ. С други думи, режимът на работа на EpiDoc Example Stylesheets по подразбиране е да произведе предаване в Leiden на кодираните текстове в EpiDoc. За TEI често е възможно да се регистрират разночетения, които са по-прецизни или в дълбочина по-ясни, отколкото при Leiden, като тук са описани подобни възможности. Но настоящите Насоки не препоръчват да се заменя стандартната епиграфска или папироложка практика с такива нови принципи.

                                      Изработените и препоръчани от общността на EpiDoc Насоки представляват подмножество и усъвършенстване на Насоките на TEI, които препоръчват кодиране с XML на широка гама литературни и исторически текстове и лингвистични сборници. Както EpiDoc е специализация на TEI за антични документи и обекти, даващ препоръки единствено за онези елементи, атрибути и обекти от значение за тази специфична под-общност, така в основата на Насоките за EpiDoc се корени идеята да допълват (и в никакъв случай заместват) Насоките на TEI. Предимно разделите, касаещи препратките и техническата част от TEI, остават безценен източник за потребители на EpiDoc, които често ще намират полезни списъци с елементи, обяснения на атрибутите за стойност или видове данни, примери за употреба в широк диапазон от контексти и подробни описания на особеностите при маркирането с XML. Насоките за EpiDoc предлагат доста ограничен набор от TEI елементи, модели за съдържание, атрибути и стойности, така че файл в EpiDoc е винаги валиден TEI файл, но не всеки TEI файл е валиден в EpiDoc. В случаите, в които Насоките за EpiDoc въвеждат повече ограничения, отколкото тези за TEI, следва да се приеме, че първите насоки имат предимство пред вторите; обратно, в тези, в които TEI навлиза в по-големи детайли или предлага по-полезен набор от примери, трябва, разбира се, да се вземе предвид и да се счита за изконен източник за всяка употреба на EpiDoc.

                                      Структура и Особености на Насоките за EpiDoc

                                      Има няколко пътя, които насочват към индивидуалните страници, съставляващи тялото на Насоките за EpiDoc.

                                      • Три основни съдържания събират в едно всички тези страници в категориите: Транскрибиране (особеностите, касаещи съдържанието, изгледа, възстановката и интерпретация на самия текст в основни линни); Спомагателни Данни (те включват описание на обекта или ръкописа, история на обекта и неговото откриване, библиографска и друга редакторска информация); и Речник и Индексиране (термини и особености, които са тагнати в текста с цел контрол върху набора от лексеми или индексиране, търсене и фасетиране).
                                      • Няколко раздела предлагат структурирани и подбрани списъци на страници за ръководство според категориите, обичайно следвани от потребителите, принадлежащи към специализирани общности (например насоките на Krummrey-Panciera за епиграфско транскрибиране; папироложките особености, така както са регистрирани в базата данни на APIS). Тези раздели все още се обработват и затова трябва да се смятат по-скоро за информативни, отколкото носещи нормативен характер. Приемат се предложения за нови раздели от този род.
                                      • И накрая, Насоките съдържат подкрепящи приложения, като речник на технически и сцециализирани термини, и библиография на епиграфски и папироложки авторитети, примери от EpiDoc corpora, и дигитални публикации на антични текстове като цяло. Показалец към Насоките чрез споменаване на TEI елементи позволява на читателите да намерят всички епиграфски особености, при които даденият елемент е част от предложената употреба.

                                      Отделните страници в Насоките са организирани според епиграфска и папироложка концепция, отколкото според наименованието на TEI елемента. Така, например всички страници, в които има съкращения, са групирани заедно (по рубриката Редакторски интервенции), независимо от това какви TEI елементи включват. Всяка страница от Насоките има определена структура: първо, кратко обяснение на заглавието на страницата (например пояснението към страницата, озаглавена „Знаци без тълкувания”, е следното „Ясни, но неразбираеми букви”. Съответният TEI елемент или елементи са показани по-долу в кутия, която включва и линк към страницата за Насоките за TEI за този елемент. След което следва пояснение на EpiDoc препоръките за употребата на тези TEI елементи, включително и детайли за подходящи атрибути и стойности.

                                      Под обяснителната бележка обикновено се намират няколко примери за употреба в контекст. В случай на особености при транскрибиране, Насоките ще дадат списък с общоприети практики за предаване на въпросната особеност според общите епиграфски и папироложки насоки за транскрибиране, по Krummrey-Panciera и Duke Databank.

                                      Примерите на XML показват препоръчителното маркиране на различни видове на всяка от особеностите при транскрибиране, например различни случаи на съкращение, което включва символ. Примерите обикновено изброяват няколко опции за маркиране в зависимост от желаното ниво за детайлизиране. Под тях се намира поредица от варианти (или различни варианти след всеки пример), които представляват съвкупност от няколко резултата за израз на маркиран текст, предоставени в примерите на EpiDoc P5 stylesheets. Крайният резултат по подразбиране следва установените практики на Krummrey-Panciera. Останалите включват стиловете SEG, Лондон и DDbDP. Под всеки пример има препратка към съответния източник. Повечето примери са взети от Надписите от Афродизиас, Надписите от римска Триполитания и Duke Databank of Documentary Papyri.

                                      Обучение, Инструменти и Помощ

                                      По своята същност тези Насоки са източник за референция. При по-задълбочено обучение или подкрепа други ресурси биха били полезни. Членове на EpiDoc общността организират обучителни семинари, понякога финансово подкрепени от големи проекти (по подобие на няколкото уъркшопа, проведени в рамките на проекта Надписи от Афродизиас, 2004-2008); повече информация относно тези обучителни събития може да се намери на страницата за Обучения в EpiDoc Wiki. Тези от вас, които за първи път се сблъскват с EpiDoc и кодиране на текст, биха сметнали също така за полезни общите обучителни сесии, посветени на TEI (някои от тях са включени в списъка за TEI събития).

                                      EpiDoc може да бъде модифициран и редактиран с помощта на всеки стандартен инструмент за XML (няколко от тях са изброени в страницата за Инструменти за редактиране на TEI wiki); базово обучение за употреба на подобни инструменти обикновено е заложено в програмите на обучителните събития и за EpiDoc, и за TEI, или какъвто и да е курс по XML. Други инструменти за публикуване, търсене и обработка на EpiDoc и TEI файлове включват XML езиците за трансформация XSLT и XQuery, и общоприети платформи за търсене като Solr и инструменти за предаване спецификите на TEI като Kiln и Papyrological Navigator.

                                      Както обикновено, първоначално всяка молба за помощ по каквато и да е тема, която настоящите насоки не покрива, трябва да бъде адресирана до Markup list.

                                      Отговорни лица за този раздел

                                      1. Габриел Бодар, автор
                                      2. Лаура Льосер, автор
                                      3. Симона Стоянова, автор
                                      4. Шарлот Тупман, автор
                                      5. Том Елиът, автор
                                      6. Мария Дончева, преведе на български език
                                      7. Полина Йорданова, редактор на превода

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Как да използваме Насoките за EpiDoc

                                      2024-03-05

                                      EpiDoc представлява широк спектър от сътрудничество между проекти и учени, които работят с документи от антични източници в Text Encoding Initiative (TEI) XML, и изработват препоръки, инструменти и добри практики за дигитално кодиране, обработка и публикуване на подобни текстове. Главната страница на EpiDoc може да бъде намерена на следния адрес: http://epidoc.sf.net.

                                      Настоящият документ (Насоки за EpiDoc) е текущ продукт от дейността на EpiDoc общността през последните няколко години. Той описва как се кодират разнообразни особености на епиграфските и папироложките документи, въз основа на базови принципи за редактиране на научни текстове (например т. нар. Установени практики по Leiden за особености при транскрибиране, както и модели за данни като Electronic Archive of Greek and Latin Epigraphy (EAGLE) за особености при описателни и исторически елементи). Насоките трябва да бъдат използвани заедно с EpiDoc Schema, според които валидността на документи, маркирани съгласно тези принципи, трябва да бъде потвърдена, както и с EpiDoc Example Stylesheets, чиято главна цел е да предоставят основен израз на всяка от описаните особености.

                                      Насоките за EpiDoc не претендират да дават пълно обяснение на това как се стартира EpiDoc проект, създава уебсайт, изграждат инструменти за търсене, или други подобни технически и съвместни начинания, които публикуването на кодирани текстове онлайн изисква. Нито пък са детайлно въведение към епиграфиката или папирологията; те Насоките предимно представляват ръководство към XML кодирането на особености на издания на антични документи, често използвани в областта на епиграфиката или сродни на нея дисциплини.

                                      Въпреки че няма единна установена практика за структуриране на епиграфско или папироложко издание, Насоките за EpiDocEpiDoc Stylesheets) подемат подход, който е в съответствие с моделите, използвани в проекти и съвместни сътрудничества като Advanced Papyrological Information System (APIS), EAGLE, и Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Предвид факта, че дисциплината епиграфика в общ смисъл и в частност, дигиталната епиграфика, вече имат устойчиви модели на добри практики в структурирането на издания, ние просто препоръчваме кодиране в TEI XML на същите данни и наблюдения, които в своята практиката учените са установили за важни или полезни.

                                      Насоките за EpiDoc са замислени като допълнение към Установените практики на Leiden (оттук-нататък "Leiden"), които повече от 80 години намират приложение в областта на епиграфиката и папирологията и се възприемат от широк спектър науки в областта на филологията и документаристиката. В Насоките е разписано, че Leiden се възриема за безспорна основа за отразяване на различия, регистрирани в дадено издание на предмодерен текст, като техните препоръки и примери се основават на тези различия, без да се изискват специфични типографски установени практики и препоръчани сигли в това отношение. Т.е целта на EpiDoc е ясно да регистрира в XML такива текстови интервенции като редакторска добавка на символи, които са напълно изгубени или с нарушена цялост, без да има нужда тези добавки да бъдат предадени в „квадратни скоби” ("[" и "]") в самия XML или какъвто и да бил производен документ. С други думи, режимът на работа на EpiDoc Example Stylesheets по подразбиране е да произведе предаване в Leiden на кодираните текстове в EpiDoc. За TEI често е възможно да се регистрират разночетения, които са по-прецизни или в дълбочина по-ясни, отколкото при Leiden, като тук са описани подобни възможности. Но настоящите Насоки не препоръчват да се заменя стандартната епиграфска или папироложка практика с такива нови принципи.

                                      Изработените и препоръчани от общността на EpiDoc Насоки представляват подмножество и усъвършенстване на Насоките на TEI, които препоръчват кодиране с XML на широка гама литературни и исторически текстове и лингвистични сборници. Както EpiDoc е специализация на TEI за антични документи и обекти, даващ препоръки единствено за онези елементи, атрибути и обекти от значение за тази специфична под-общност, така в основата на Насоките за EpiDoc се корени идеята да допълват (и в никакъв случай заместват) Насоките на TEI. Предимно разделите, касаещи препратките и техническата част от TEI, остават безценен източник за потребители на EpiDoc, които често ще намират полезни списъци с елементи, обяснения на атрибутите за стойност или видове данни, примери за употреба в широк диапазон от контексти и подробни описания на особеностите при маркирането с XML. Насоките за EpiDoc предлагат доста ограничен набор от TEI елементи, модели за съдържание, атрибути и стойности, така че файл в EpiDoc е винаги валиден TEI файл, но не всеки TEI файл е валиден в EpiDoc. В случаите, в които Насоките за EpiDoc въвеждат повече ограничения, отколкото тези за TEI, следва да се приеме, че първите насоки имат предимство пред вторите; обратно, в тези, в които TEI навлиза в по-големи детайли или предлага по-полезен набор от примери, трябва, разбира се, да се вземе предвид и да се счита за изконен източник за всяка употреба на EpiDoc.

                                      Структура и Особености на Насоките за EpiDoc

                                      Има няколко пътя, които насочват към индивидуалните страници, съставляващи тялото на Насоките за EpiDoc.

                                      • Три основни съдържания събират в едно всички тези страници в категориите: Транскрибиране (особеностите, касаещи съдържанието, изгледа, възстановката и интерпретация на самия текст в основни линни); Спомагателни Данни (те включват описание на обекта или ръкописа, история на обекта и неговото откриване, библиографска и друга редакторска информация); и Речник и Индексиране (термини и особености, които са тагнати в текста с цел контрол върху набора от лексеми или индексиране, търсене и фасетиране).
                                      • Няколко раздела предлагат структурирани и подбрани списъци на страници за ръководство според категориите, обичайно следвани от потребителите, принадлежащи към специализирани общности (например насоките на Krummrey-Panciera за епиграфско транскрибиране; папироложките особености, така както са регистрирани в базата данни на APIS). Тези раздели все още се обработват и затова трябва да се смятат по-скоро за информативни, отколкото носещи нормативен характер. Приемат се предложения за нови раздели от този род.
                                      • И накрая, Насоките съдържат подкрепящи приложения, като речник на технически и сцециализирани термини, и библиография на епиграфски и папироложки авторитети, примери от EpiDoc corpora, и дигитални публикации на антични текстове като цяло. Показалец към Насоките чрез споменаване на TEI елементи позволява на читателите да намерят всички епиграфски особености, при които даденият елемент е част от предложената употреба.

                                      Отделните страници в Насоките са организирани според епиграфска и папироложка концепция, отколкото според наименованието на TEI елемента. Така, например всички страници, в които има съкращения, са групирани заедно (по рубриката Редакторски интервенции), независимо от това какви TEI елементи включват. Всяка страница от Насоките има определена структура: първо, кратко обяснение на заглавието на страницата (например пояснението към страницата, озаглавена „Знаци без тълкувания”, е следното „Ясни, но неразбираеми букви”. Съответният TEI елемент или елементи са показани по-долу в кутия, която включва и линк към страницата за Насоките за TEI за този елемент. След което следва пояснение на EpiDoc препоръките за употребата на тези TEI елементи, включително и детайли за подходящи атрибути и стойности.

                                      Под обяснителната бележка обикновено се намират няколко примери за употреба в контекст. В случай на особености при транскрибиране, Насоките ще дадат списък с общоприети практики за предаване на въпросната особеност според общите епиграфски и папироложки насоки за транскрибиране, по Krummrey-Panciera и Duke Databank.

                                      Примерите на XML показват препоръчителното маркиране на различни видове на всяка от особеностите при транскрибиране, например различни случаи на съкращение, което включва символ. Примерите обикновено изброяват няколко опции за маркиране в зависимост от желаното ниво за детайлизиране. Под тях се намира поредица от варианти (или различни варианти след всеки пример), които представляват съвкупност от няколко резултата за израз на маркиран текст, предоставени в примерите на EpiDoc P5 stylesheets. Крайният резултат по подразбиране следва установените практики на Krummrey-Panciera. Останалите включват стиловете SEG, Лондон и DDbDP. Под всеки пример има препратка към съответния източник. Повечето примери са взети от Надписите от Афродизиас, Надписите от римска Триполитания и Duke Databank of Documentary Papyri.

                                      Обучение, Инструменти и Помощ

                                      По своята същност тези Насоки са източник за референция. При по-задълбочено обучение или подкрепа други ресурси биха били полезни. Членове на EpiDoc общността организират обучителни семинари, понякога финансово подкрепени от големи проекти (по подобие на няколкото уъркшопа, проведени в рамките на проекта Надписи от Афродизиас, 2004-2008); повече информация относно тези обучителни събития може да се намери на страницата за Обучения в EpiDoc Wiki. Тези от вас, които за първи път се сблъскват с EpiDoc и кодиране на текст, биха сметнали също така за полезни общите обучителни сесии, посветени на TEI (някои от тях са включени в списъка за TEI събития).

                                      EpiDoc може да бъде модифициран и редактиран с помощта на всеки стандартен инструмент за XML (няколко от тях са изброени в страницата за Инструменти за редактиране на TEI wiki); базово обучение за употреба на подобни инструменти обикновено е заложено в програмите на обучителните събития и за EpiDoc, и за TEI, или какъвто и да е курс по XML. Други инструменти за публикуване, търсене и обработка на EpiDoc и TEI файлове включват XML езиците за трансформация XSLT и XQuery, и общоприети платформи за търсене като Solr и инструменти за предаване спецификите на TEI като Kiln и Papyrological Navigator.

                                      Както обикновено, първоначално всяка молба за помощ по каквато и да е тема, която настоящите насоки не покрива, трябва да бъде адресирана до Markup list.

                                      Отговорни лица за този раздел

                                      1. Габриел Бодар, автор
                                      2. Лаура Льосер, автор
                                      3. Симона Стоянова, автор
                                      4. Шарлот Тупман, автор
                                      5. Том Елиът, автор
                                      6. Мария Дончева, преведе на български език
                                      7. Полина Йорданова, редактор на превода

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-de.html b/gl/dev/intro-intro-de.html index ae2a22702..e3eb9afb6 100644 --- a/gl/dev/intro-intro-de.html +++ b/gl/dev/intro-intro-de.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Einführung in die EpiDoc Richtlinien

                                      2023-04-27

                                      EpiDoc ist ein loser Zusammenschluss von Projekten sowie Wissenschaftlerinnen und Wissenschaftler, die antiken Quellen mittels Text Encoding Initiative (TEI) XML erarbeiten und hierzu Empfehlungen ausarbeiten, Werkzeuge identifizieren und „best practice“-Richtlinien in Bezug auf das Encoding, das Verarbeiten sowie das Publizieren dieser Texte formulieren. Die EpiDoc Homepage ist unter http://epidoc.sf.net zu finden.

                                      Das vorliegende Dokument (die EpiDoc Richtlinien) ist ein sich ständig weiterentwickelndes Produkt, dass sich aus der langjährigen Erfahrungen der EpiDoc-Community speist. Die Richtlinien beschreiben, wie charakteristische Phänomene epigraphischer und papyrologischer Dokumente kodieren werden können. Die Richtlinien basieren – was die Transkription anbelangt – auf den allgemein akzeptierten Konventionen des sogenannten Leidener Klammersystems, was die beschreibende und historischen Bestandteile angeht – auf den Datenmodellen des Electronic Archive of Greek and Latin Epigraphy (EAGLE). Die Richtlinien sollten im Zusammenspiel mit dem EpiDoc-Schema verwendet werden. So kann jedes im Entstehen begriffene EpiDoc-XML-Dokument bereits während der Bearbeitung gegen das Schema validiert werden, sodass dessen interne Konsistenz stets gewährleistet ist. Die EpiDoc-Beispiel-Stylesheets enthalten grundlegende Ausgabe-Funktionalitäten (Rendering), mit denen eine erste Lese- oder Druck-Ansicht generiert werden kann.

                                      Dabei sind die EpiDoc-Richtlinien weder eine vollständige noch erschöpfende Einführung in Umsetzung und Planung eines EpiDoc-Projekts, oder die Erstellung einer Webseite mit X-Technologien, die Implementierung eines Such-Werkzeuges oder die Realisierung anders gearteter technischer oder kollaborativer Arbeitsaufgaben. Es wird auch keine erschöpfende Einführung in die epigraphischen Fachdisziplinen oder die Papyrologie gegeben. Die Richtlinien verstehen sich dagegen ausschließlich als Leitfaden zur Kodierung der am häufigsten auftretenden Phänomene antiker Quellendokumente deren Edition und jeweiligen Spezifika in XML.

                                      Da sich Konventionen, Strukturen und Aufbau epigraphischer und papyrologischer Editionen im Detail durchaus voneinander unterscheiden können, orientieren sich die EpiDoc-Richtlinien und die dazugehörigen EpiDoc Stylesheets an Datenmodellen, wie sie beispielsweise in Projekten wie APIS, EAGLE und Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE) erstellt wurden und noch immer eingesetzt werden. Da die Fachdisziplin der Epigraphik im Allgemeinen, und der digitalen Epigraphik im Besonderen, bereits über ein ausgeklügeltes System von Verfahren und Methoden verfügt, mit deren Hilfe eine Edition aufgebaut und strukturiert wird, empfehlen wir im Folgenden nur diejenigen Verfahren, Daten und Beobachtungen in die Praxis der XML-Kodierung zu überführen, deren Nützlichkeit bereits bewiesen ist und die sich in der Praxis als unverzichtbar erwiesen haben.

                                      Die Richtlinien wollen das Leidener Klammersystem (im folgenden "Leiden"), das bereits seit über 80 Jahren in der Epigraphik sowie der Papyrologie Verwendung findet und in vielen philologischen und dokumentatorischen Kontexten verstanden wird, zu ergänzen. Die Richtlinien sehen das Leidener Klammersystem als adäquate Grundlage an, auf der die in vormodernen Texten zu findenden Phänomene sinnvoll kenntlich gemacht und aufgezeichnet werden können. Die Empfehlungen basieren auf dieser Grundlage, ohne sich dabei jedoch auf eine einzige Art der typographischen Repräsentation oder ein spezifisches Set von Siglen festzulegen. EpiDoc versucht, Phänomene – wie beispielsweise Textverlust – in der XML-Kodierung klar und eindeutig abzubilden, ohne jedoch eine spezifische Form der graphischen Repräsentation – beispielsweise in eckigen Klammern „[ ]“ – im XML-kodierten Dokument oder in einer wie auch immer gearteten Repräsentationsschicht zu erzwingen. Nichtsdestoweniger ist es so, dass ein in EpiDoc kodierter Text auf Basis der EpiDoc-Stylesheets standardmäßig auf Basis des Leidener Klammersystems dargestellt wird. Auf der Grundlage von TEI-XML ist es dabei theoretisch häufig möglich, bestimmte textuelle Phänomene feingranularer und tiefergehender zu annotieren, als dies auf Basis des Leidener Klammersystems möglich wäre. Einige dieser Annotationsmöglichkeiten werden zwar im Folgenden innerhalb der Richtlinien dargestellt, dennoch befürworten die Richtlinien in keinster Weise, die etablierte und standardisierte epigraphische sowie papyrologische Praxis durch solche neuartigen Verfahren zu ersetzen.

                                      Die durch die EpiDoc-Community erstellten und empfohlenen Richtlinien sind eine Untermenge sowie spezialisierte Anpassung der TEI-Richtlinien, welche Empfehlungen für die XML-Kodierung einer großen Bandbreite an literarischen und historischen Texten sowie linguistischer Corpora aussprechen. Genauso wie es sich bei EpiDoc um eine Spezialisierung von TEI im Bezug auf antike Dokumente und Texte handelt, die nur diejenigen Elemente, Attribute und Objekte empfiehlt, welche sich als besonders nützlich für die Belange dieser Fachcommunity gezeigt haben, sollen die EpiDoc-Richtlinien die TEI-Richtlinien ergänzen jedoch auf keinen Fall ersetzen. Insbesondere die Referenz sowie das technische Kapitel der TEI bleiben darum stets eine außerordentlich wertvolle Quelle für alle EpiDoc-Nutzer. Dort findet man Listen der Elemente, Erläuterungen der Attributwerte oder der Datentypen sowie Anwendungsbeispiele aus zahlreichen Kontexten. Zusätzlich bieten die TEI-Richtlinien ausführliche Beschreibungen nützlicher Funktionen. Die EpiDoc-Richtlinien empfehlen eine eingeschränkte Untermenge an TEI-Elementen, content models, Attributen und Werten. Daher ist jede EpiDoc-Datei auch stets eine valide TEI-Datei, umgekehrt jedoch ist nicht jede TEI-Datei auch notwendigerweise immer auch eine valide EpiDoc-Datei. Dort wo die EpiDoc-Richtlinien restriktiver sind als die TEI-Richtlinien, sollten erstere an Stelle letzterer genutzt werden; dort hingegen, wo die TEI stärker ins Detail geht, oder ein breiteres Spektrum an Beispielen gibt, sollte ihr gegenüber EpiDoc der Vorzug gegeben werden.

                                      Struktur und Charakteristika der EpiDoc-Richtlinien

                                      Mehrere Einstiegspunkte in die EpiDoc-Richtlinien werden angeboten:

                                      • Inhaltsverzeichnisse strukturieren die Unterseiten nach drei Kategorien: Transkription (Charakteristika, welche sich auf Inhalt, Erscheinung, Wiederherstellung und grundlegende Interpretation des Textes selbst beziehen); Unterstützende Daten (beinhaltet die Beschreibung des Inschriftenträgers bzw. des Manuskriptes); und Vokabular und Indexierung (Begriffe und Charakteristika, welche im Text annotiert werden, um in der Folge zum Zweck der Kontrolle der Vokabular und Indizes, der Suchfunktionalitäten und Facetierung genutzt zu werden).
                                      • Mehrere Abschnitte bieten strukturierte Listen, welche Einstiegspunkte und Lernpfade darstellen, die sich an den Gewohnheiten spezialisierter Fachcommunities orientieren und diese in sinnvoller Weise durch die Richtlinien führen sollen (z.B. die epigraphischen Transkriptions-Richtlinien von Krummrey-Panciera; die papyrologischen Charakteristika wie sie innerhalb der APIS-Datenbank aufgezeichnet wurden).
                                      • Zu guter letzt bieten die Richtlinien ergänzende Anhänge, wie das Glossar technischer und spezialisierter Fachbegriffe, und eine Bibliographie epigraphischer und papyrologischer Autoritäten, beispielhafte EpiDoc-Corpora und digitaler Publikationen antiker Texte im Allgemeinen. Ein Index, bietet einen Zugang zu den Richtlinien auf Basis der TEI-Elementeund ermöglicht, sämtliche epigraphischen Charakteristika zu finden in denen ein bestimmtes Element Teil der empfohlenen Nutzung ist.

                                      Die Unterseiten der Richtlinien sind eher nach epigraphischen oder papyrologischen Konzepten organisiert, weniger nach TEI-Elementnamen. Daher sind beispielsweise alle Seiten, die sich mit Abkürzungen beschäftigen, zusammen gruppiert worden, gleichgültig, ob spezifische TEI-Elemente vorkommen oder nicht (beispielsweise unterhalb der Rubrik „Editorische Eingriffe“). Jede Unterseite weist eine konsistente, wiederkehrende Struktur auf: Am Anfang steht eine knappe Erläuterung des Seitentitels (so wird beispielsweise der Titel der Seite „Uninterpretiertes Zeichen“ durch “Deutlicher aber unverständlicher Buchstabe” erläutert). Darunter werden die relevanten TEI-Elemente in einer Box angezeigt und mit der betreffenden Seite der TEI-Richtlinien verlinkt. Im Anschluss daran folgt eine umgangssprachlicher Erläuterungstext, der die EpiDoc-Empfehlung zur Benutzung des Elements sowie der damit zusammenhängenden Attribute und Werte enthält.

                                      Unter dieser Erläuterung finden sich für gewöhnlich mehrere Anwendungsbeispiele in ihrem jeweiligen Kontext. In den Fällen, die sich auf Besonderheiten der Transkription beziehen, listen die Richtlinien auf, wie das infrage stehenden Phänomen mit den allgemeinen epigraphischen wie papyrologischen Transkriptionsrichtlinien (wie Krummrey-Panciera und die Duke-Datenbank) wiederzugeben wäre.

                                      Die XML-Beispiele zeigen das empfohlene Markup für die einzelnen Varianten jedes Transkriptions-Charakteristikums an, z.B. werden verschiedene Varianten gezeigt, auf welche Weise Abkürzungen, die ein Symbol enthalten, aufgelöst werden können. Die Beispiele listen häufig mehrere Markup-Optionen auf, die sich im Detailgrad unterscheiden. Unterhalb der Beispiele wird gezeigt, wie das jeweilige Markup durch die EpiDoc-Stylesheets dargestellt und ausgegeben werden würde. Der Standard orientiert sich an der Krummrey-Panciera-Konvention. Außerdem stehen der SEG-Stil, der London-Stil und der DdbDP-Stil zur Verfügung. Unter jedem Beispiel findet sich eine Referenz zur Quelle. Die meisten Beispiele stammen aus den Inschriften von Aphrodisias, den Inschriften des römischen Tripolitanien und der Duke Datenbank dokumentarischer Papyri.

                                      Training, Werkzeuge und Unterstützung

                                      Die Richtlinien verstehen sich im Wesentlichen als Referenzwerk. Für tiefergehende Schulung oder weitergehende Unterstützung sind andere Ressourcen verfügbar. So halten Mitglieder der EpiDoc-Community gelegentlich Schulungen ab, die ab und zu von langfristigeren Projekten gefördert oder getragen werden (beispielsweise gab es in den Jahren 2004–2008 mehrere Workshops im Rahmen des Inschriften von Aphrodisias Projektes); mehr Information zu diesen Veranstaltungen findet man auf der Schulungsseite im EpiDoc-Wiki. Für Anfänger im Bereich EpiDoc und Text Encoding kann es sinnvoll sein eine allgemeine TEI-Schulung zu besuchen (siehe TEI Veranstaltungskalender).

                                      EpiDoc kann mit standardmäßigen XML-Werkzeugen geschrieben und bearbeitet werden (für eine Liste siehe Editions Werkzeuge im TEI Wiki). Grundlegende Schulungen zum Umgang mit diesen Werkzeugen finden für gewöhnlich im Rahmen von EpiDoc- und TEI-Schulungen, oder auch allgemeinen XML-Schulungen statt. Andere digitale Werkzeuge mit denen EpiDoc- oder TEI-Dateien publiziert, durchsucht oder anderweitig weiterverarbeitet werden können sind unter anderem XSLT und Xquery sowie einige Suchplattformen wie Solr und die TEI-spezifischen und quelloffenen Werkzeuge Kiln und der Papyrological Navigator.

                                      Wie immer, sollte der erste Anlaufpunkt für Hilfe bezüglich eines Themas, welche nicht in den Richtlinien besprochen wird, die Markup-Mailing-Liste sein.

                                      Verantwortlich für diesen Abschnitt

                                      1. Gabriel Bodard, Autor
                                      2. Laura Löser, Autor
                                      3. Simona Stoyanova, Autor
                                      4. Charlotte Tupman, Autor
                                      5. Tom Elliott, Autor
                                      6. Max Grüntgens, übersetzt ins Deutsche
                                      7. Thomas Kollatz, übersetzt ins Deutsche

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Einführung in die EpiDoc Richtlinien

                                      2024-03-05

                                      EpiDoc ist ein loser Zusammenschluss von Projekten sowie Wissenschaftlerinnen und Wissenschaftler, die antiken Quellen mittels Text Encoding Initiative (TEI) XML erarbeiten und hierzu Empfehlungen ausarbeiten, Werkzeuge identifizieren und „best practice“-Richtlinien in Bezug auf das Encoding, das Verarbeiten sowie das Publizieren dieser Texte formulieren. Die EpiDoc Homepage ist unter http://epidoc.sf.net zu finden.

                                      Das vorliegende Dokument (die EpiDoc Richtlinien) ist ein sich ständig weiterentwickelndes Produkt, dass sich aus der langjährigen Erfahrungen der EpiDoc-Community speist. Die Richtlinien beschreiben, wie charakteristische Phänomene epigraphischer und papyrologischer Dokumente kodieren werden können. Die Richtlinien basieren – was die Transkription anbelangt – auf den allgemein akzeptierten Konventionen des sogenannten Leidener Klammersystems, was die beschreibende und historischen Bestandteile angeht – auf den Datenmodellen des Electronic Archive of Greek and Latin Epigraphy (EAGLE). Die Richtlinien sollten im Zusammenspiel mit dem EpiDoc-Schema verwendet werden. So kann jedes im Entstehen begriffene EpiDoc-XML-Dokument bereits während der Bearbeitung gegen das Schema validiert werden, sodass dessen interne Konsistenz stets gewährleistet ist. Die EpiDoc-Beispiel-Stylesheets enthalten grundlegende Ausgabe-Funktionalitäten (Rendering), mit denen eine erste Lese- oder Druck-Ansicht generiert werden kann.

                                      Dabei sind die EpiDoc-Richtlinien weder eine vollständige noch erschöpfende Einführung in Umsetzung und Planung eines EpiDoc-Projekts, oder die Erstellung einer Webseite mit X-Technologien, die Implementierung eines Such-Werkzeuges oder die Realisierung anders gearteter technischer oder kollaborativer Arbeitsaufgaben. Es wird auch keine erschöpfende Einführung in die epigraphischen Fachdisziplinen oder die Papyrologie gegeben. Die Richtlinien verstehen sich dagegen ausschließlich als Leitfaden zur Kodierung der am häufigsten auftretenden Phänomene antiker Quellendokumente deren Edition und jeweiligen Spezifika in XML.

                                      Da sich Konventionen, Strukturen und Aufbau epigraphischer und papyrologischer Editionen im Detail durchaus voneinander unterscheiden können, orientieren sich die EpiDoc-Richtlinien und die dazugehörigen EpiDoc Stylesheets an Datenmodellen, wie sie beispielsweise in Projekten wie APIS, EAGLE und Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE) erstellt wurden und noch immer eingesetzt werden. Da die Fachdisziplin der Epigraphik im Allgemeinen, und der digitalen Epigraphik im Besonderen, bereits über ein ausgeklügeltes System von Verfahren und Methoden verfügt, mit deren Hilfe eine Edition aufgebaut und strukturiert wird, empfehlen wir im Folgenden nur diejenigen Verfahren, Daten und Beobachtungen in die Praxis der XML-Kodierung zu überführen, deren Nützlichkeit bereits bewiesen ist und die sich in der Praxis als unverzichtbar erwiesen haben.

                                      Die Richtlinien wollen das Leidener Klammersystem (im folgenden "Leiden"), das bereits seit über 80 Jahren in der Epigraphik sowie der Papyrologie Verwendung findet und in vielen philologischen und dokumentatorischen Kontexten verstanden wird, zu ergänzen. Die Richtlinien sehen das Leidener Klammersystem als adäquate Grundlage an, auf der die in vormodernen Texten zu findenden Phänomene sinnvoll kenntlich gemacht und aufgezeichnet werden können. Die Empfehlungen basieren auf dieser Grundlage, ohne sich dabei jedoch auf eine einzige Art der typographischen Repräsentation oder ein spezifisches Set von Siglen festzulegen. EpiDoc versucht, Phänomene – wie beispielsweise Textverlust – in der XML-Kodierung klar und eindeutig abzubilden, ohne jedoch eine spezifische Form der graphischen Repräsentation – beispielsweise in eckigen Klammern „[ ]“ – im XML-kodierten Dokument oder in einer wie auch immer gearteten Repräsentationsschicht zu erzwingen. Nichtsdestoweniger ist es so, dass ein in EpiDoc kodierter Text auf Basis der EpiDoc-Stylesheets standardmäßig auf Basis des Leidener Klammersystems dargestellt wird. Auf der Grundlage von TEI-XML ist es dabei theoretisch häufig möglich, bestimmte textuelle Phänomene feingranularer und tiefergehender zu annotieren, als dies auf Basis des Leidener Klammersystems möglich wäre. Einige dieser Annotationsmöglichkeiten werden zwar im Folgenden innerhalb der Richtlinien dargestellt, dennoch befürworten die Richtlinien in keinster Weise, die etablierte und standardisierte epigraphische sowie papyrologische Praxis durch solche neuartigen Verfahren zu ersetzen.

                                      Die durch die EpiDoc-Community erstellten und empfohlenen Richtlinien sind eine Untermenge sowie spezialisierte Anpassung der TEI-Richtlinien, welche Empfehlungen für die XML-Kodierung einer großen Bandbreite an literarischen und historischen Texten sowie linguistischer Corpora aussprechen. Genauso wie es sich bei EpiDoc um eine Spezialisierung von TEI im Bezug auf antike Dokumente und Texte handelt, die nur diejenigen Elemente, Attribute und Objekte empfiehlt, welche sich als besonders nützlich für die Belange dieser Fachcommunity gezeigt haben, sollen die EpiDoc-Richtlinien die TEI-Richtlinien ergänzen jedoch auf keinen Fall ersetzen. Insbesondere die Referenz sowie das technische Kapitel der TEI bleiben darum stets eine außerordentlich wertvolle Quelle für alle EpiDoc-Nutzer. Dort findet man Listen der Elemente, Erläuterungen der Attributwerte oder der Datentypen sowie Anwendungsbeispiele aus zahlreichen Kontexten. Zusätzlich bieten die TEI-Richtlinien ausführliche Beschreibungen nützlicher Funktionen. Die EpiDoc-Richtlinien empfehlen eine eingeschränkte Untermenge an TEI-Elementen, content models, Attributen und Werten. Daher ist jede EpiDoc-Datei auch stets eine valide TEI-Datei, umgekehrt jedoch ist nicht jede TEI-Datei auch notwendigerweise immer auch eine valide EpiDoc-Datei. Dort wo die EpiDoc-Richtlinien restriktiver sind als die TEI-Richtlinien, sollten erstere an Stelle letzterer genutzt werden; dort hingegen, wo die TEI stärker ins Detail geht, oder ein breiteres Spektrum an Beispielen gibt, sollte ihr gegenüber EpiDoc der Vorzug gegeben werden.

                                      Struktur und Charakteristika der EpiDoc-Richtlinien

                                      Mehrere Einstiegspunkte in die EpiDoc-Richtlinien werden angeboten:

                                      • Inhaltsverzeichnisse strukturieren die Unterseiten nach drei Kategorien: Transkription (Charakteristika, welche sich auf Inhalt, Erscheinung, Wiederherstellung und grundlegende Interpretation des Textes selbst beziehen); Unterstützende Daten (beinhaltet die Beschreibung des Inschriftenträgers bzw. des Manuskriptes); und Vokabular und Indexierung (Begriffe und Charakteristika, welche im Text annotiert werden, um in der Folge zum Zweck der Kontrolle der Vokabular und Indizes, der Suchfunktionalitäten und Facetierung genutzt zu werden).
                                      • Mehrere Abschnitte bieten strukturierte Listen, welche Einstiegspunkte und Lernpfade darstellen, die sich an den Gewohnheiten spezialisierter Fachcommunities orientieren und diese in sinnvoller Weise durch die Richtlinien führen sollen (z.B. die epigraphischen Transkriptions-Richtlinien von Krummrey-Panciera; die papyrologischen Charakteristika wie sie innerhalb der APIS-Datenbank aufgezeichnet wurden).
                                      • Zu guter letzt bieten die Richtlinien ergänzende Anhänge, wie das Glossar technischer und spezialisierter Fachbegriffe, und eine Bibliographie epigraphischer und papyrologischer Autoritäten, beispielhafte EpiDoc-Corpora und digitaler Publikationen antiker Texte im Allgemeinen. Ein Index, bietet einen Zugang zu den Richtlinien auf Basis der TEI-Elementeund ermöglicht, sämtliche epigraphischen Charakteristika zu finden in denen ein bestimmtes Element Teil der empfohlenen Nutzung ist.

                                      Die Unterseiten der Richtlinien sind eher nach epigraphischen oder papyrologischen Konzepten organisiert, weniger nach TEI-Elementnamen. Daher sind beispielsweise alle Seiten, die sich mit Abkürzungen beschäftigen, zusammen gruppiert worden, gleichgültig, ob spezifische TEI-Elemente vorkommen oder nicht (beispielsweise unterhalb der Rubrik „Editorische Eingriffe“). Jede Unterseite weist eine konsistente, wiederkehrende Struktur auf: Am Anfang steht eine knappe Erläuterung des Seitentitels (so wird beispielsweise der Titel der Seite „Uninterpretiertes Zeichen“ durch “Deutlicher aber unverständlicher Buchstabe” erläutert). Darunter werden die relevanten TEI-Elemente in einer Box angezeigt und mit der betreffenden Seite der TEI-Richtlinien verlinkt. Im Anschluss daran folgt eine umgangssprachlicher Erläuterungstext, der die EpiDoc-Empfehlung zur Benutzung des Elements sowie der damit zusammenhängenden Attribute und Werte enthält.

                                      Unter dieser Erläuterung finden sich für gewöhnlich mehrere Anwendungsbeispiele in ihrem jeweiligen Kontext. In den Fällen, die sich auf Besonderheiten der Transkription beziehen, listen die Richtlinien auf, wie das infrage stehenden Phänomen mit den allgemeinen epigraphischen wie papyrologischen Transkriptionsrichtlinien (wie Krummrey-Panciera und die Duke-Datenbank) wiederzugeben wäre.

                                      Die XML-Beispiele zeigen das empfohlene Markup für die einzelnen Varianten jedes Transkriptions-Charakteristikums an, z.B. werden verschiedene Varianten gezeigt, auf welche Weise Abkürzungen, die ein Symbol enthalten, aufgelöst werden können. Die Beispiele listen häufig mehrere Markup-Optionen auf, die sich im Detailgrad unterscheiden. Unterhalb der Beispiele wird gezeigt, wie das jeweilige Markup durch die EpiDoc-Stylesheets dargestellt und ausgegeben werden würde. Der Standard orientiert sich an der Krummrey-Panciera-Konvention. Außerdem stehen der SEG-Stil, der London-Stil und der DdbDP-Stil zur Verfügung. Unter jedem Beispiel findet sich eine Referenz zur Quelle. Die meisten Beispiele stammen aus den Inschriften von Aphrodisias, den Inschriften des römischen Tripolitanien und der Duke Datenbank dokumentarischer Papyri.

                                      Training, Werkzeuge und Unterstützung

                                      Die Richtlinien verstehen sich im Wesentlichen als Referenzwerk. Für tiefergehende Schulung oder weitergehende Unterstützung sind andere Ressourcen verfügbar. So halten Mitglieder der EpiDoc-Community gelegentlich Schulungen ab, die ab und zu von langfristigeren Projekten gefördert oder getragen werden (beispielsweise gab es in den Jahren 2004–2008 mehrere Workshops im Rahmen des Inschriften von Aphrodisias Projektes); mehr Information zu diesen Veranstaltungen findet man auf der Schulungsseite im EpiDoc-Wiki. Für Anfänger im Bereich EpiDoc und Text Encoding kann es sinnvoll sein eine allgemeine TEI-Schulung zu besuchen (siehe TEI Veranstaltungskalender).

                                      EpiDoc kann mit standardmäßigen XML-Werkzeugen geschrieben und bearbeitet werden (für eine Liste siehe Editions Werkzeuge im TEI Wiki). Grundlegende Schulungen zum Umgang mit diesen Werkzeugen finden für gewöhnlich im Rahmen von EpiDoc- und TEI-Schulungen, oder auch allgemeinen XML-Schulungen statt. Andere digitale Werkzeuge mit denen EpiDoc- oder TEI-Dateien publiziert, durchsucht oder anderweitig weiterverarbeitet werden können sind unter anderem XSLT und Xquery sowie einige Suchplattformen wie Solr und die TEI-spezifischen und quelloffenen Werkzeuge Kiln und der Papyrological Navigator.

                                      Wie immer, sollte der erste Anlaufpunkt für Hilfe bezüglich eines Themas, welche nicht in den Richtlinien besprochen wird, die Markup-Mailing-Liste sein.

                                      Verantwortlich für diesen Abschnitt

                                      1. Gabriel Bodard, Autor
                                      2. Laura Löser, Autor
                                      3. Simona Stoyanova, Autor
                                      4. Charlotte Tupman, Autor
                                      5. Tom Elliott, Autor
                                      6. Max Grüntgens, übersetzt ins Deutsche
                                      7. Thomas Kollatz, übersetzt ins Deutsche

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-es.html b/gl/dev/intro-intro-es.html index 69e1f8751..8972aef40 100644 --- a/gl/dev/intro-intro-es.html +++ b/gl/dev/intro-intro-es.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Cómo Utilizar la Guía de Uso de EpiDoc

                                      2023-04-27

                                      EpiDoc es una amplia unión cooperativa y voluntaria de proyectos y estudiosos que trabajan con fuentes epigráficas en Text Encoding Initiative (TEI) XML, que idean y ponen en común consejos, herramientas y soluciones para abordar la codificación (encoding), el procesamiento y la publicación digital de este tipo de textos. La página principal de EpiDoc se encuentra en la siguiente dirección http://epidoc.sf.net.

                                      Este documento (la Guía de uso de EpiDoc) es el producto del trabajo que ha desarrollado la comunidad EpiDoc durante varios años. Describe cómo codificar las diferentes particularidades de los documentos epigráficos y papirológicos, basándose en los principios fundamentales de la edición de textos académicos (por ejemplo, en las llamadas Convenciones de Leiden para cuestiones de transcripción, y en modelos como el Archivo Electrónico de Epigrafía Griega y Latina (EAGLE) para cuestiones descriptivas e históricas). Las presente Guía debería usarse conjuntamente con el Patrón EpiDoc, gracias al cual los documentos marcados según los principios TEI pueden ser validados por el editor de XML y con las hojas de estilo EpiDoc, cuyo fin es proporcionar una representación básica y homogénea de cada rasgo descrito en el texto.

                                      La Guía EpiDoc no pretende ofrecer una explicación pormenorizada de cómo poner en marcha un proyecto EpiDoc, crear una web, diseñar herramientas de búsqueda, u otras tareas técnicas o colaborativas que la publicación online de textos codificados requiere. Tampoco ha de entenderse esta Guía como una introducción detallada y completa a la epigrafía y a la papirología; se trata de una introducción a la codificación XML de ciertos rasgos específicos de los documentos antiguos que tan a menudo se emplean en epigrafía y en otras disciplinas similares.

                                      Aunque no hay una convención única para la estructura de una edición epigráfica y papirológica, el enfoque de la Guía EpiDoc (y de las hojas de estilo EpiDoc ) se ajusta a los modelos empleados por ciertos proyectos y cooperaciones de éstos como Advanced Papyrological Information System (APIS), EAGLE, y Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Puesto que la disciplina epigráfica en general, y la epigrafía digital en particular, ya tienen sólidos modelos de edición, simplemente queremos recomendar la codificación en TEI XML de los datos y de las observaciones que los estudiosos ya hayan encontrado esenciales o útiles.

                                      La Guía de Uso de EpiDoc pretende complementar las Convenciones de Leiden (de aquí en adelante, "Leiden"), que se llevan empleando en epigrafía y papirología durante más de 80 años y es común a muchos campos de la filología y del tratamiento de textos. En la Guía se entiende que Leiden es una base adecuada para recoger y expresar las características de un texto antiguo; y sus recomendaciones y ejemplos están basados en estos detalles sin necesidad de las convenciones tipográficas específicas o de las siglas contenidas en aquélla. Es decir, el objetivo fundamental de EpiDoc es registrar en XML las intervenciones textuales. Se trata de una ayuda para la edición, concretamente para cuando se debe indicar que algún carácter está completamente perdido; pero sin poner esta parte de texto entre "corchetes" ("[" y "]") en el mismo XML o en cualquier otro documento derivado. Dicho esto, la línea habitual de las hojas de estilo EpiDoc es producir una edición Leiden de los textos codificados en EpiDoc. En muchas ocasiones, es posible registrar en TEI particularidades del texto de forma más exacta y detallada que en Leiden, y algunas de estas posibilidades se describen aquí; pero esta Guía no recomienda sustituir los métodos epigráficos y papirológicos habituales por estos nuevos principios.

                                      La Guía creada por la comunidad EpiDoc es una parte de la Guía TEI, así como una especialización de ella, que aconseja la codificación XML de una amplia variedad de textos literarios e históricos y de corpora lingüísticos. Del mismo modo que EpiDoc es una especialización de TEI para documentos y objetos antiguos, que recomienda estos elementos y atributos para este subconjunto en concreto, la Guía EpiDoc pretende complementar (y no substituir) la Guía TEI. La referencia de TEI y sus secciones técnicas son una fuente de incalculable valor para los usuarios de EpiDoc, quienes encontrarán abundantes y útiles listas de elementos, explicaciones sobre la atribución de valores o tipos de datos, ejemplos de uso en una amplia variedad de contextos y extensas explicaciones sobre el registro de particularidades textuales. Sin embargo, la Guía EpiDoc recomienda sólo un restringido conjunto de elementos TEI, modelos de contenidos, atributos y valores, ya que un archivo EpiDoc es siempre un archivo TEI válido, pero no todos los archivos TEI son archivos EpiDoc válidos. En los casos en los que la Guía EpiDoc sea más restringida que la TEI, la primera tiene validez sobre la segunda; a cambio, aquellos casos en los que la Guía TEI profundiza más, u ofrecen mayor cantidad de ejemplos, deberían considerarse como la fuente canónica para su uso EpiDoc.

                                      Estructura y características de la Guía EpiDoc

                                      Hay diversas formas de llegar desde las páginas individuales a la Guía EpiDoc.

                                      • Tres tablas de contenidos recogen todas estas páginas bajo las siguientes categorías: Transcripción (aquellas características relativas al contenido, apariencia, restauración e interpretación básica del texto); Información del soporte (referidas a la descripción del objeto o manuscrito, la historia del objeto y su hallazgo, bibliografía y otra información editorial); y Vocabulario e indexación (términos y características etiquetadas en el texto con fin de indexar y compilar el vocabulario, de cara a las búsquedas).
                                      • Varias secciones ofrecen listas organizadas y seleccionadas de páginas en función de las categorías que usan de manera más frecuente los usuarios de comunidades especializadas (por ejemplo, la guía de transcripción epigráfica de Krummrey-Panciera; las características papirológicas recogidas por la base de datos APIS). Estas secciones están todavía en construcción, y deben entenderse más a título informativo que normativo. Se agradecería la propuesta de nuevas secciones de este tipo.
                                      • Por último, la Guía de Uso contiene anexos de apoyo, como el glosario de términos técnicos y especializados y una bibliografía de autoridades de las disciplinas de la epigrafía y la papirología, especialmente de los corpora EpiDoc y de la publicación digital de textos. Un índice a la Guía de Uso organizado por elementos TEI permite a los lectores encontrar cualquier rasgo epigráfico en los que dicho elemento es parte del uso recomendado.

                                      Las páginas individuales están organizadas en la Guía de Uso por conceptos epigráficos y papirológicos, y no por el nombre de su elemento TEI. Así, por ejemplo, todas las páginas relativas a las abreviaturas están agrupadas (bajo la rúbrica "Intervenciones Editoriales"), independientemente de qué elemento TEI se especifique en ellas. Cada página de la Guía tiene una estructura regular: primero, una breve explicación del título de la página (por ejemplo, en la página titulada "Caracteres no interpretados", se especifica "letras claras pero incomprensibles"). El elemento (o elementos) TEI relevante está dispuesto en una caja en la parte inferior, incluyendo un enlace a la página de la Guía de Uso TEI dirigido hacia dicho elemento. A continuación se expone una explicación a las recomendaciones EpiDoc para el uso de dichos elementos TEI, incluyendo detalles de atributos y valores relevantes.

                                      Bajo esta explicación normalmente hay algunos ejemplos del uso en contexto. Especialmente en el caso de las transcripciones, la Guía de Uso ofrece una lista de las convenciones en cuestión según la transcripción epigráfica o papirológica más habitual, como Krummrey-Panciera y la del Duke Databank.

                                      Los ejemplos XML muestran el registro recomendado para varios tipos de particularidades en la transcripción, por ejemplo, diferentes casos de desarrollo de una abreviatura que incluya un símbolo. Los ejemplos ofrecen habitualmente diferentes opciones de registro, en función del nivel de detalle y profundización deseados. A continuación de los ejemplos hay una serie de variantes (o una variante diferente después de cada ejemplo) que representan las diferentes versiones disponibles en los ejemplos de las hojas de estilo EpiDoc P5. La versión por defecto es la convención Krummrey-Panciera. También están disponibles el estilo SEG, el de Londres y el DDbDP. Junto a cada ejemplo hay una referencia que indica su fuente. La mayoría de ejemplos están tomados de Inscriptions of Aphrodisias, de Inscriptions of Roman Tripolitania y del Duke Databank of Documentary Papyri.

                                      Enseñanza, Herramientas y Soporte

                                      Esta Guía de Uso es básicamente una referencia orientativa. Para profundizar más en cuestiones de aprendizaje o de soporte, están a su disposición otros recursos. Algunos miembros de la comunidad EpiDoc llevan a cabo cursos de aprendizaje, frecuentemente financiados por proyectos de mayor alcance (como los talleres que tuvieron lugar a lo largo del Proyecto de Inscripciones de Afrodisias entre 2004 y 2008). Se puede encontrar información de estas jornadas en la sección de Formación del Wiki de EpiDoc. También los no iniciados a EpiDoc o a la codificación digital de textos pueden encontrar sesiones de introducción a TEI (algunas de ellas están en la lista de eventos TEI).

                                      EpiDoc puede ser modificado y editado usando cualquiera de las herramientas estándar de XML (muchas de las cuales se pueden encontrar en la página de herramientas de edición del Wiki de TEI). Del mismo modo, una introducción al uso de dichas herramientas se incluye a menudo tanto en los encuentros EpiDoc como en los de TEI, o en cualquier tutorial de XML. Otras herramientas de publicación, búsqueda y procesamiento de archivos EpiDoc y TEI incluyen la transformación de lenguajes XML, XSLT y XQuery, y en plataformas de búsqueda generales como Solr y herramientas específicas de TEI como Kiln y Papyrological Navigator.

                                      En cualquier caso, la primera referencia a la que acudir en caso de necesitar ayuda relacionada con alguna cuestión que no esté incluida en esta Guía de Uso debería ser la Markup list , una lista de mensajería vía correo electrónico usada habitualmente por la comunidad EpiDoc.

                                      Responsables de esta sección

                                      1. Gabriel Bodard, Autor
                                      2. Laura Löser, Autora
                                      3. Simona Stoyanova, Autora
                                      4. Charlotte Tupman, Autora
                                      5. Tom Elliott, Autor
                                      6. María José Estarán Tolosa, traducido al español
                                      7. Núria Garcia Casacuberta, traducido al español

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Cómo Utilizar la Guía de Uso de EpiDoc

                                      2024-03-05

                                      EpiDoc es una amplia unión cooperativa y voluntaria de proyectos y estudiosos que trabajan con fuentes epigráficas en Text Encoding Initiative (TEI) XML, que idean y ponen en común consejos, herramientas y soluciones para abordar la codificación (encoding), el procesamiento y la publicación digital de este tipo de textos. La página principal de EpiDoc se encuentra en la siguiente dirección http://epidoc.sf.net.

                                      Este documento (la Guía de uso de EpiDoc) es el producto del trabajo que ha desarrollado la comunidad EpiDoc durante varios años. Describe cómo codificar las diferentes particularidades de los documentos epigráficos y papirológicos, basándose en los principios fundamentales de la edición de textos académicos (por ejemplo, en las llamadas Convenciones de Leiden para cuestiones de transcripción, y en modelos como el Archivo Electrónico de Epigrafía Griega y Latina (EAGLE) para cuestiones descriptivas e históricas). Las presente Guía debería usarse conjuntamente con el Patrón EpiDoc, gracias al cual los documentos marcados según los principios TEI pueden ser validados por el editor de XML y con las hojas de estilo EpiDoc, cuyo fin es proporcionar una representación básica y homogénea de cada rasgo descrito en el texto.

                                      La Guía EpiDoc no pretende ofrecer una explicación pormenorizada de cómo poner en marcha un proyecto EpiDoc, crear una web, diseñar herramientas de búsqueda, u otras tareas técnicas o colaborativas que la publicación online de textos codificados requiere. Tampoco ha de entenderse esta Guía como una introducción detallada y completa a la epigrafía y a la papirología; se trata de una introducción a la codificación XML de ciertos rasgos específicos de los documentos antiguos que tan a menudo se emplean en epigrafía y en otras disciplinas similares.

                                      Aunque no hay una convención única para la estructura de una edición epigráfica y papirológica, el enfoque de la Guía EpiDoc (y de las hojas de estilo EpiDoc ) se ajusta a los modelos empleados por ciertos proyectos y cooperaciones de éstos como Advanced Papyrological Information System (APIS), EAGLE, y Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Puesto que la disciplina epigráfica en general, y la epigrafía digital en particular, ya tienen sólidos modelos de edición, simplemente queremos recomendar la codificación en TEI XML de los datos y de las observaciones que los estudiosos ya hayan encontrado esenciales o útiles.

                                      La Guía de Uso de EpiDoc pretende complementar las Convenciones de Leiden (de aquí en adelante, "Leiden"), que se llevan empleando en epigrafía y papirología durante más de 80 años y es común a muchos campos de la filología y del tratamiento de textos. En la Guía se entiende que Leiden es una base adecuada para recoger y expresar las características de un texto antiguo; y sus recomendaciones y ejemplos están basados en estos detalles sin necesidad de las convenciones tipográficas específicas o de las siglas contenidas en aquélla. Es decir, el objetivo fundamental de EpiDoc es registrar en XML las intervenciones textuales. Se trata de una ayuda para la edición, concretamente para cuando se debe indicar que algún carácter está completamente perdido; pero sin poner esta parte de texto entre "corchetes" ("[" y "]") en el mismo XML o en cualquier otro documento derivado. Dicho esto, la línea habitual de las hojas de estilo EpiDoc es producir una edición Leiden de los textos codificados en EpiDoc. En muchas ocasiones, es posible registrar en TEI particularidades del texto de forma más exacta y detallada que en Leiden, y algunas de estas posibilidades se describen aquí; pero esta Guía no recomienda sustituir los métodos epigráficos y papirológicos habituales por estos nuevos principios.

                                      La Guía creada por la comunidad EpiDoc es una parte de la Guía TEI, así como una especialización de ella, que aconseja la codificación XML de una amplia variedad de textos literarios e históricos y de corpora lingüísticos. Del mismo modo que EpiDoc es una especialización de TEI para documentos y objetos antiguos, que recomienda estos elementos y atributos para este subconjunto en concreto, la Guía EpiDoc pretende complementar (y no substituir) la Guía TEI. La referencia de TEI y sus secciones técnicas son una fuente de incalculable valor para los usuarios de EpiDoc, quienes encontrarán abundantes y útiles listas de elementos, explicaciones sobre la atribución de valores o tipos de datos, ejemplos de uso en una amplia variedad de contextos y extensas explicaciones sobre el registro de particularidades textuales. Sin embargo, la Guía EpiDoc recomienda sólo un restringido conjunto de elementos TEI, modelos de contenidos, atributos y valores, ya que un archivo EpiDoc es siempre un archivo TEI válido, pero no todos los archivos TEI son archivos EpiDoc válidos. En los casos en los que la Guía EpiDoc sea más restringida que la TEI, la primera tiene validez sobre la segunda; a cambio, aquellos casos en los que la Guía TEI profundiza más, u ofrecen mayor cantidad de ejemplos, deberían considerarse como la fuente canónica para su uso EpiDoc.

                                      Estructura y características de la Guía EpiDoc

                                      Hay diversas formas de llegar desde las páginas individuales a la Guía EpiDoc.

                                      • Tres tablas de contenidos recogen todas estas páginas bajo las siguientes categorías: Transcripción (aquellas características relativas al contenido, apariencia, restauración e interpretación básica del texto); Información del soporte (referidas a la descripción del objeto o manuscrito, la historia del objeto y su hallazgo, bibliografía y otra información editorial); y Vocabulario e indexación (términos y características etiquetadas en el texto con fin de indexar y compilar el vocabulario, de cara a las búsquedas).
                                      • Varias secciones ofrecen listas organizadas y seleccionadas de páginas en función de las categorías que usan de manera más frecuente los usuarios de comunidades especializadas (por ejemplo, la guía de transcripción epigráfica de Krummrey-Panciera; las características papirológicas recogidas por la base de datos APIS). Estas secciones están todavía en construcción, y deben entenderse más a título informativo que normativo. Se agradecería la propuesta de nuevas secciones de este tipo.
                                      • Por último, la Guía de Uso contiene anexos de apoyo, como el glosario de términos técnicos y especializados y una bibliografía de autoridades de las disciplinas de la epigrafía y la papirología, especialmente de los corpora EpiDoc y de la publicación digital de textos. Un índice a la Guía de Uso organizado por elementos TEI permite a los lectores encontrar cualquier rasgo epigráfico en los que dicho elemento es parte del uso recomendado.

                                      Las páginas individuales están organizadas en la Guía de Uso por conceptos epigráficos y papirológicos, y no por el nombre de su elemento TEI. Así, por ejemplo, todas las páginas relativas a las abreviaturas están agrupadas (bajo la rúbrica "Intervenciones Editoriales"), independientemente de qué elemento TEI se especifique en ellas. Cada página de la Guía tiene una estructura regular: primero, una breve explicación del título de la página (por ejemplo, en la página titulada "Caracteres no interpretados", se especifica "letras claras pero incomprensibles"). El elemento (o elementos) TEI relevante está dispuesto en una caja en la parte inferior, incluyendo un enlace a la página de la Guía de Uso TEI dirigido hacia dicho elemento. A continuación se expone una explicación a las recomendaciones EpiDoc para el uso de dichos elementos TEI, incluyendo detalles de atributos y valores relevantes.

                                      Bajo esta explicación normalmente hay algunos ejemplos del uso en contexto. Especialmente en el caso de las transcripciones, la Guía de Uso ofrece una lista de las convenciones en cuestión según la transcripción epigráfica o papirológica más habitual, como Krummrey-Panciera y la del Duke Databank.

                                      Los ejemplos XML muestran el registro recomendado para varios tipos de particularidades en la transcripción, por ejemplo, diferentes casos de desarrollo de una abreviatura que incluya un símbolo. Los ejemplos ofrecen habitualmente diferentes opciones de registro, en función del nivel de detalle y profundización deseados. A continuación de los ejemplos hay una serie de variantes (o una variante diferente después de cada ejemplo) que representan las diferentes versiones disponibles en los ejemplos de las hojas de estilo EpiDoc P5. La versión por defecto es la convención Krummrey-Panciera. También están disponibles el estilo SEG, el de Londres y el DDbDP. Junto a cada ejemplo hay una referencia que indica su fuente. La mayoría de ejemplos están tomados de Inscriptions of Aphrodisias, de Inscriptions of Roman Tripolitania y del Duke Databank of Documentary Papyri.

                                      Enseñanza, Herramientas y Soporte

                                      Esta Guía de Uso es básicamente una referencia orientativa. Para profundizar más en cuestiones de aprendizaje o de soporte, están a su disposición otros recursos. Algunos miembros de la comunidad EpiDoc llevan a cabo cursos de aprendizaje, frecuentemente financiados por proyectos de mayor alcance (como los talleres que tuvieron lugar a lo largo del Proyecto de Inscripciones de Afrodisias entre 2004 y 2008). Se puede encontrar información de estas jornadas en la sección de Formación del Wiki de EpiDoc. También los no iniciados a EpiDoc o a la codificación digital de textos pueden encontrar sesiones de introducción a TEI (algunas de ellas están en la lista de eventos TEI).

                                      EpiDoc puede ser modificado y editado usando cualquiera de las herramientas estándar de XML (muchas de las cuales se pueden encontrar en la página de herramientas de edición del Wiki de TEI). Del mismo modo, una introducción al uso de dichas herramientas se incluye a menudo tanto en los encuentros EpiDoc como en los de TEI, o en cualquier tutorial de XML. Otras herramientas de publicación, búsqueda y procesamiento de archivos EpiDoc y TEI incluyen la transformación de lenguajes XML, XSLT y XQuery, y en plataformas de búsqueda generales como Solr y herramientas específicas de TEI como Kiln y Papyrological Navigator.

                                      En cualquier caso, la primera referencia a la que acudir en caso de necesitar ayuda relacionada con alguna cuestión que no esté incluida en esta Guía de Uso debería ser la Markup list , una lista de mensajería vía correo electrónico usada habitualmente por la comunidad EpiDoc.

                                      Responsables de esta sección

                                      1. Gabriel Bodard, Autor
                                      2. Laura Löser, Autora
                                      3. Simona Stoyanova, Autora
                                      4. Charlotte Tupman, Autora
                                      5. Tom Elliott, Autor
                                      6. María José Estarán Tolosa, traducido al español
                                      7. Núria Garcia Casacuberta, traducido al español

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-fi.html b/gl/dev/intro-intro-fi.html index 1423b0f37..4a116663b 100644 --- a/gl/dev/intro-intro-fi.html +++ b/gl/dev/intro-intro-fi.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Kuinka EpiDoc-ohjeistoa käytetään

                                      2023-04-27

                                      EpiDoc on väljä yhteistyöhön perustuva hanke. Siihen osallistuu tutkimusprojekteja ja tutkijoita, jotka työstävät alkuperäislähteitä Text Encoding Initiative (TEI) XML -merkintäkielellä ja jotka pohtivat suosituksia, työkaluja ja hyviä menettelytapoja tekstien koodaamiseen, digitaaliseen käsittelyyn ja tällä tavoin tuotettujen aineistojen julkaisemiseen. EpiDocin kotisivut löytyvät osoitteesta: http://epidoc.sf.net.

                                      Tämä sivusto (EpiDoc Ohjeisto) on EpiDoc-yhteisön monen vuoden työn tulos ja sen työstäminen jatkuu edelleen. Näillä sivuilla kerrotaan, kuinka koodata piirtokirjoituksissa ja papyruksissa ilmeneviä seikkoja. Ohjeet perustuvat tieteellisen tekstieditoimisen keskeisille periaatteille (esimerkiksi ns. Leidenin sopimuksen mukaiseen merkintätapaan tekstin ilmiöiden kuvaamisessa sekä aineistomalleihin, kuten esim. kreikkalaisen ja latinalaisen piirtokirjoitustutkimuksen digitaalinen arkisto (EAGLE), materiaalisten ja historiallisten piirteiden kuvaamisessa). Ohjeisto on tarkoitettu käytettäväksi yhdessä EpiDoc-skeeman ja tyyliarkkimalliston kanssa. EpiDoc-periaatteiden mukaisesti koodattujen dokumenttien tulee olla skeemassa kuvattujen sääntöjen mukaisia. EpiDoc-tyyliarkeissa puolestaan pyritään tarjoamaan perustulkinta kaikille kuvattaville piirteille.

                                      EpiDoc-ohjeistossa ei kerrota kuinka käynnistää EpiDoc-projekti, luoda verkkosivu, rakentaa hakutoiminnot tai muutakaan sellaista teknisiin tai yhteistyöhankkeisiin liittyvää, jota tarvitaan digitaalisten aineistojen julkaisemiseen verkkoympäristössä. Ohjeisto ei ole myöskään johdatus piirtokirjoitus- tai papyrustutkimukseen. EpiDoc-ohjeisto on yksinomaan opas siihen kuinka XML-merkintäkielellä ilmaistaan alkuperäislähteisiin perustuvien tekstieditioiden piirteet, mitä tavallisimmin käytetään piirtokirjoitusten sekä muiden vastaavanlaisten kohteiden tutkimuksessa.

                                      Ei ole olemassa yhtä ainoaa tapaa koostaa piirtokirjoitus- tai papyruseditio. EpiDoc-ohjeistossa (ja EpiDoc-tyyliarkeissa) kuitenkin otetaan suunta sen kaltaisiin aineistomalleihin, joita on käytetty esimerkiksi hankkeissa Advanced Papyrological Information System (APIS), EAGLE ja Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Koska piirtokirjoitustutkimuksessa ylipäätään ja varsinkin digitaalisessa piirtokirjoitustutkimuksessa on jo perusteellisesti toteutettuja esimerkkejä hyvistä menettelytavoista editioiden jäsentämisessä, me yksinkertaisesti vain suosittelemme, että myös TEI XML -merkintäkielellä kirjoitettaessa editiot sisältäisivät sen tietomäärän ja yksityiskohdat, jotka tutkijat ovat jo havainneet keskeisiksi ja hyödyllisiksi käytännössä.

                                      EpiDoc-ohjeiston on tarkoitus täydentää Leidenin merkintätapaa, joka on ollut epigraafikoiden ja papyrologien käytössä jo yli 80 vuotta ja jota osataan lukea monilla filologisilla ja alkuperäisdokumentteihin pohjaavilla tutkimusaloilla. Ohjeistossa oletetaan, että Leidenin merkintätavassa käytetyt käsitteet muodostavat riittävän perustan esimodernien tekstien editioissa ilmenevien piirteiden kuvaamiseen, ja se antaa suosituksia ja esimerkkejä, jotka pohjautuvat näihin käsitteisiin, asettamatta kuitenkaan vaatimusta käyttää jotakin tarkasti määriteltyä typografiaa tai siinä suositeltua lyhennetapaa. Toisin sanoen, EpiDoc pyrkii esitystapaan, jossa XML-merkintäkielellä kuvataan tekstin ominaisuus kuten esim. editoijan täydentämä, alkuperäisdokumentista vaurion vuoksi kadonnut kirjain, mutta EpiDoc ei määrää, että kyseinen kirjain tulisi esittää kulmasulkeissa ([ ja ]) XML:ssä tai jossain tulevassa julkaisussa. EpiDoc-tyyliarkin tehtävä on tulkita EpiDocin mukaisesti koodattu teksti ja kääntää se Leidenin merkintätavan mukaiseksi. TEI-merkintäkielellä on mahdollista kuvata hienovaraisempia ja yksityiskohtaisempia piirteitä kuin Leidenin merkintätavassa. Näillä sivuilla kerrotaan myös joistakin näistä mahdollisuuksista. Ohjeistossa ei kuitenkaan suositella standardin epigrafisen tai papyrologisen käytännön korvaamista sellaisilla uusilla periaatteilla.

                                      EpiDoc-yhteisön tuottama ja suosittelema Ohjeisto on jalostettu TEI-ohjeistosta ja muodostaa näin sen osajoukon. TEI-ohjeistosta löytyy suosituksia XML-koodausta varten monenlaisille kirjallisille ja historiallisille teksteille ja kielellisille kokoelmille. EpiDoc on vanhojen tekstien ja esineiden dokumentointiin erikoistunut TEI:n osa, joka ehdottaa ainoastaan niiden elementtien, attribuuttien ja arvojen käyttöä, joita tässä erikoisryhmässä tarvitaan. EpiDoc-ohjeisto on tarkoitettu täydentämään (eikä missään tapauksessa korvaamaan) TEI-ohjeistoa. Erityisesti TEI:n viite- ja tekniset osiot ovat edelleen korvaamaton lähde myös EpiDocin käyttäjille, jotka monesti kokevat hyödyllisiksi niiden sisältämät luettelot elementeistä, attribuuttien arvojen tai tietotyyppien selityksistä, monenlaisissa ympäristöissä annetuista käyttöesimerkeistä sekä laajoista merkintäkielen piirteiden kuvauksista. EpiDoc-ohjeiston suositukset koostuvat varsin suppeasta määrästä TEI:n elementtejä, sisältömalleja, attribuutteja ja arvoja. Jokainen EpiDoc-tiedosto on myös validi TEI-tiedosto, mutta jokainen TEI-tiedosto ei ole validia EpiDocia. Niissä seikoissa, missä EpiDoc-ohjeisto on rajoittavampi kuin TEI, EpiDocia tulee pitää ensisijaisena ohjeena. Kuitenkin niissä seikoissa, missä TEI on huomattavasti yksityiskohtaisempi tai tarjoaa hyödyllisempiä esimerkkejä, siitä luonnollisestikin tulee hakea neuvoa ja se tulee huomioida kaikenlaisen EpiDocin käytön kanonisena lähteenä.

                                      EpiDoc-ohjeistonrakenne ja ominaispiirteet

                                      EpiDoc-ohjeisto koostuu yksittäisistä sivuista, joille pääsee useampaa reittiä.

                                      • Kaikki sivut on koottu kolmeen pääsisällysluetteloon, jotka jakautuvat seuraavalla tavalla: Transkriptio (piirteet, jotka liittyvät tekstin sisältöön, ulkoasuun, entistämiseen ja tekstin perustulkintaan); Lisätiedot (sisältää esineen tai käsikirjoituksen kuvauksen, sen historian ja löytämiseen liittyvät seikat, bibliografiset ym. toimitukselliset tiedot); Sanasto ja luettelointi (koostuu tekstissä ilmenevän sanaston ja kielellisten piirteiden merkitsemisestä sanastonhallintaa tai luettelointia sekä erilaisten hakujen mahdollistamista varten).
                                      • Useista osioista löytyy jäsennelty ja valikoitu luettelo ohjesivuista. Se on järjestetty erikoistuneiden käyttäjäyhteisöjen yleisesti seuraamien ryhmittelyjen mukaan (esimerkiksi Krummrey-Pancieran ohjeisto piirtokirjoitusten transkriptioihin; APIS-tietokannan käyttämä tapa kuvata papyrologisia ilmiöitä). Nämä osiot ovat vielä rakennusvaiheessa, joten niihin tulee suhtautua enneminkin tiedonlähteinä kuin normatiivisina ohjeina. Ehdotukset mahdollisista uusista samantapaisista osioista ovat erittäin tervetulleita.
                                      • Ohjeisto sisältää myös työskentelyn tueksi tarkoitettuja liitteitä, joista löytyy mm. teknisten- ja erikoistermien sanasto, epigrafisten ja papyrologisten julkaisujen kirjallisuusluettelo, EpiDoc-korpusten ja ylipäätään vanhojen tekstien digitaalisten julkaisujen mallikappaleita. Epidoc-ohjeiston sisältämästä TEI-elementtien luettelosta (Index of TEI elements) lukija löytää kunkin elementin kohdalta myös kaikki sen sisältämät, suositusten mukaiset epigrafisten piirteiden kuvaukset.

                                      Ohjeiston yksittäiset sivut on järjestetty epigrafisten tai papyrologisten käsitteiden perusteella eikä TEI-elementtien nimien mukaisesti. Näin esimerkiksi kaikki sellaiset sivut, joissa käsitellään lyhenteitä, on ryhmitelty yhteen (otsakkeen Editorial Interventions alle) välittämättä siitä, mitä TEI-elementtejä niiden merkitsemisessä käytetään. Ohjeiston jokainen sivu on rakenteeltaan samankaltainen: ensin selitetään lyhyesti sivun otsikon merkitys (esim. sivulla, jonka otsikko on Tulkitsemattomat merkit, selitys on ’Selvästi näkyvät mutta käsittämättömät merkit’). Sen alla esitetään asianmukainen TEI-elementti (tai elementit) sekä annetaan linkki TEI-ohjeiston sivulle, jossa ko. elementti on esitelty yksityiskohtaisesti. Tämän jälkeen kerrotaan EpiDocin mukaiset suositukset kyseisten TEI-elementtien käyttöön sekä niihin yhdistettävissä olevien attribuuttien ja arvojen yksityiskohtia.

                                      Selitysten alapuolelta löytyy yleensä myös muutama esimerkki sen aidosta käyttöympäristöstä. Erityisesti transkriptioiden piirteiden ollessa kyseessä ohjeistossa esitetään kustakin aiheesta yleisten epigrafisten ja papyrologisten transkriptio-ohjeiden mukaisia perinteisiä tulkintoja, esim. Krummrey-Panciera, Duke Databank.

                                      XML-esimerkeistä näkee erilaisille transkriptioiden piirteille soveliaan merkintäkielen, esim. tavat merkitä symbolin sisältävän lyhennyksen avaus. Malliesimerkeissä luetellaan useampia merkintäkielen vaihtoehtoja, joista voi valita sen mukaan, kuinka yksityiskohtaisesti asia halutaan ilmaista. Esimerkkien jälkeen esitetään sarja tulkintoja (tai eri tulkinta jokaisen esimerkin jälkeen), joista näkee, millaisia tulostusvaihtoehtoja EpiDoc P5 -tyyliarkeista kyseiselle merkintäkielen ilmaukselle löytyy. Oletustulostus on Krummrey-Pancieran periaatteiden mukainen. Muita tyylejä ovat mm. SEG, London ja DDbDP. Jokaisessa esimerkissä on lähdeviite. Useimmat piirtokirjoituksiin liittyvät esimerkkitapaukset on poimittu Afrodisiaksen (Inscriptions of Aphrodisias) tai Tripolitanian (Inscriptions of Roman Tripolitania) tekstien joukosta ja papyrologiset puolestaan Duke Databank of Documentary Papyri:n kokoelmista.

                                      Harjoituskurssit, työkalut ja tuki

                                      Tämä Ohjeisto on pohjimmiltaan lähdeteos. Perusteellisempaan harjoitteluun ja tukeen on tarjolla muita keinoja. EpiDoc-yhteisön jäsenet järjestävät ajoittain harjoituskursseja ja saavat niihin toisinaan myös rahoitusta isommilta tutkimushankkeilta (esim. Afrodisiaksen piirtokirjoitusten tutkimusprojekti rahoitti useita EpiDoc-työpajoja vuosina 2004–2008). Tällaisista harjoituskursseista löytyy lisätietoa Koulutus-sivulta EpiDocin wikissä. Ne, joille EpiDoc ja tekstin koodaus on täysin uutta, saattavat hyötyä myös TEI:n yleisluontoisista harjoituskursseista (TEI:n tapahtumalistalta löytyy ainakin osa ko. kursseista).

                                      EpiDoc-merkintäkieltä voi kirjoittaa ja editoida millä tahansa XML-kielelle tarkoitetulla perustyökalulla (luettelo löytyy Editointityökalut-sivulta TEI:n wikissä). Tavallisesti EpiDoc- ja TEI-harjoituskursseilla, tai missä tahansa XML-kurssilla, käydään läpi tällaisten työkalujen peruskäyttöä. Julkaisemiseen, hakujärjestelmien luomiseen ja muuhun EpiDoc ja TEI-tiedostojen työstöön käytetään XML-kielen muuntajana XSLT ja XQuery-kieliä, yleisinä hakualustoina saattaa olla mm. Solr tai TEI:lle erityisesti luotu avoimeen koodiin perustuva työkalu kuten Kiln ja Papyrological Navigator.

                                      Mikäli eteen tulee ongelma, johon ei tunnu löytyvän vastausta näiltä ohjesivuilta, kysymys kannattaa esittää Markup-listalla.

                                      Responsibility for this section

                                      1. Gabriel Bodard, kirjoittaja
                                      2. Laura Löser, kirjoittaja
                                      3. Simona Stoyanova, kirjoittaja
                                      4. Charlotte Tupman, kirjoittaja
                                      5. Tom Elliott, kirjoittaja
                                      6. Katariina Kankaanpää, suomentaja
                                      7. Marja Vierros, suomentaja

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Kuinka EpiDoc-ohjeistoa käytetään

                                      2024-03-05

                                      EpiDoc on väljä yhteistyöhön perustuva hanke. Siihen osallistuu tutkimusprojekteja ja tutkijoita, jotka työstävät alkuperäislähteitä Text Encoding Initiative (TEI) XML -merkintäkielellä ja jotka pohtivat suosituksia, työkaluja ja hyviä menettelytapoja tekstien koodaamiseen, digitaaliseen käsittelyyn ja tällä tavoin tuotettujen aineistojen julkaisemiseen. EpiDocin kotisivut löytyvät osoitteesta: http://epidoc.sf.net.

                                      Tämä sivusto (EpiDoc Ohjeisto) on EpiDoc-yhteisön monen vuoden työn tulos ja sen työstäminen jatkuu edelleen. Näillä sivuilla kerrotaan, kuinka koodata piirtokirjoituksissa ja papyruksissa ilmeneviä seikkoja. Ohjeet perustuvat tieteellisen tekstieditoimisen keskeisille periaatteille (esimerkiksi ns. Leidenin sopimuksen mukaiseen merkintätapaan tekstin ilmiöiden kuvaamisessa sekä aineistomalleihin, kuten esim. kreikkalaisen ja latinalaisen piirtokirjoitustutkimuksen digitaalinen arkisto (EAGLE), materiaalisten ja historiallisten piirteiden kuvaamisessa). Ohjeisto on tarkoitettu käytettäväksi yhdessä EpiDoc-skeeman ja tyyliarkkimalliston kanssa. EpiDoc-periaatteiden mukaisesti koodattujen dokumenttien tulee olla skeemassa kuvattujen sääntöjen mukaisia. EpiDoc-tyyliarkeissa puolestaan pyritään tarjoamaan perustulkinta kaikille kuvattaville piirteille.

                                      EpiDoc-ohjeistossa ei kerrota kuinka käynnistää EpiDoc-projekti, luoda verkkosivu, rakentaa hakutoiminnot tai muutakaan sellaista teknisiin tai yhteistyöhankkeisiin liittyvää, jota tarvitaan digitaalisten aineistojen julkaisemiseen verkkoympäristössä. Ohjeisto ei ole myöskään johdatus piirtokirjoitus- tai papyrustutkimukseen. EpiDoc-ohjeisto on yksinomaan opas siihen kuinka XML-merkintäkielellä ilmaistaan alkuperäislähteisiin perustuvien tekstieditioiden piirteet, mitä tavallisimmin käytetään piirtokirjoitusten sekä muiden vastaavanlaisten kohteiden tutkimuksessa.

                                      Ei ole olemassa yhtä ainoaa tapaa koostaa piirtokirjoitus- tai papyruseditio. EpiDoc-ohjeistossa (ja EpiDoc-tyyliarkeissa) kuitenkin otetaan suunta sen kaltaisiin aineistomalleihin, joita on käytetty esimerkiksi hankkeissa Advanced Papyrological Information System (APIS), EAGLE ja Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Koska piirtokirjoitustutkimuksessa ylipäätään ja varsinkin digitaalisessa piirtokirjoitustutkimuksessa on jo perusteellisesti toteutettuja esimerkkejä hyvistä menettelytavoista editioiden jäsentämisessä, me yksinkertaisesti vain suosittelemme, että myös TEI XML -merkintäkielellä kirjoitettaessa editiot sisältäisivät sen tietomäärän ja yksityiskohdat, jotka tutkijat ovat jo havainneet keskeisiksi ja hyödyllisiksi käytännössä.

                                      EpiDoc-ohjeiston on tarkoitus täydentää Leidenin merkintätapaa, joka on ollut epigraafikoiden ja papyrologien käytössä jo yli 80 vuotta ja jota osataan lukea monilla filologisilla ja alkuperäisdokumentteihin pohjaavilla tutkimusaloilla. Ohjeistossa oletetaan, että Leidenin merkintätavassa käytetyt käsitteet muodostavat riittävän perustan esimodernien tekstien editioissa ilmenevien piirteiden kuvaamiseen, ja se antaa suosituksia ja esimerkkejä, jotka pohjautuvat näihin käsitteisiin, asettamatta kuitenkaan vaatimusta käyttää jotakin tarkasti määriteltyä typografiaa tai siinä suositeltua lyhennetapaa. Toisin sanoen, EpiDoc pyrkii esitystapaan, jossa XML-merkintäkielellä kuvataan tekstin ominaisuus kuten esim. editoijan täydentämä, alkuperäisdokumentista vaurion vuoksi kadonnut kirjain, mutta EpiDoc ei määrää, että kyseinen kirjain tulisi esittää kulmasulkeissa ([ ja ]) XML:ssä tai jossain tulevassa julkaisussa. EpiDoc-tyyliarkin tehtävä on tulkita EpiDocin mukaisesti koodattu teksti ja kääntää se Leidenin merkintätavan mukaiseksi. TEI-merkintäkielellä on mahdollista kuvata hienovaraisempia ja yksityiskohtaisempia piirteitä kuin Leidenin merkintätavassa. Näillä sivuilla kerrotaan myös joistakin näistä mahdollisuuksista. Ohjeistossa ei kuitenkaan suositella standardin epigrafisen tai papyrologisen käytännön korvaamista sellaisilla uusilla periaatteilla.

                                      EpiDoc-yhteisön tuottama ja suosittelema Ohjeisto on jalostettu TEI-ohjeistosta ja muodostaa näin sen osajoukon. TEI-ohjeistosta löytyy suosituksia XML-koodausta varten monenlaisille kirjallisille ja historiallisille teksteille ja kielellisille kokoelmille. EpiDoc on vanhojen tekstien ja esineiden dokumentointiin erikoistunut TEI:n osa, joka ehdottaa ainoastaan niiden elementtien, attribuuttien ja arvojen käyttöä, joita tässä erikoisryhmässä tarvitaan. EpiDoc-ohjeisto on tarkoitettu täydentämään (eikä missään tapauksessa korvaamaan) TEI-ohjeistoa. Erityisesti TEI:n viite- ja tekniset osiot ovat edelleen korvaamaton lähde myös EpiDocin käyttäjille, jotka monesti kokevat hyödyllisiksi niiden sisältämät luettelot elementeistä, attribuuttien arvojen tai tietotyyppien selityksistä, monenlaisissa ympäristöissä annetuista käyttöesimerkeistä sekä laajoista merkintäkielen piirteiden kuvauksista. EpiDoc-ohjeiston suositukset koostuvat varsin suppeasta määrästä TEI:n elementtejä, sisältömalleja, attribuutteja ja arvoja. Jokainen EpiDoc-tiedosto on myös validi TEI-tiedosto, mutta jokainen TEI-tiedosto ei ole validia EpiDocia. Niissä seikoissa, missä EpiDoc-ohjeisto on rajoittavampi kuin TEI, EpiDocia tulee pitää ensisijaisena ohjeena. Kuitenkin niissä seikoissa, missä TEI on huomattavasti yksityiskohtaisempi tai tarjoaa hyödyllisempiä esimerkkejä, siitä luonnollisestikin tulee hakea neuvoa ja se tulee huomioida kaikenlaisen EpiDocin käytön kanonisena lähteenä.

                                      EpiDoc-ohjeistonrakenne ja ominaispiirteet

                                      EpiDoc-ohjeisto koostuu yksittäisistä sivuista, joille pääsee useampaa reittiä.

                                      • Kaikki sivut on koottu kolmeen pääsisällysluetteloon, jotka jakautuvat seuraavalla tavalla: Transkriptio (piirteet, jotka liittyvät tekstin sisältöön, ulkoasuun, entistämiseen ja tekstin perustulkintaan); Lisätiedot (sisältää esineen tai käsikirjoituksen kuvauksen, sen historian ja löytämiseen liittyvät seikat, bibliografiset ym. toimitukselliset tiedot); Sanasto ja luettelointi (koostuu tekstissä ilmenevän sanaston ja kielellisten piirteiden merkitsemisestä sanastonhallintaa tai luettelointia sekä erilaisten hakujen mahdollistamista varten).
                                      • Useista osioista löytyy jäsennelty ja valikoitu luettelo ohjesivuista. Se on järjestetty erikoistuneiden käyttäjäyhteisöjen yleisesti seuraamien ryhmittelyjen mukaan (esimerkiksi Krummrey-Pancieran ohjeisto piirtokirjoitusten transkriptioihin; APIS-tietokannan käyttämä tapa kuvata papyrologisia ilmiöitä). Nämä osiot ovat vielä rakennusvaiheessa, joten niihin tulee suhtautua enneminkin tiedonlähteinä kuin normatiivisina ohjeina. Ehdotukset mahdollisista uusista samantapaisista osioista ovat erittäin tervetulleita.
                                      • Ohjeisto sisältää myös työskentelyn tueksi tarkoitettuja liitteitä, joista löytyy mm. teknisten- ja erikoistermien sanasto, epigrafisten ja papyrologisten julkaisujen kirjallisuusluettelo, EpiDoc-korpusten ja ylipäätään vanhojen tekstien digitaalisten julkaisujen mallikappaleita. Epidoc-ohjeiston sisältämästä TEI-elementtien luettelosta (Index of TEI elements) lukija löytää kunkin elementin kohdalta myös kaikki sen sisältämät, suositusten mukaiset epigrafisten piirteiden kuvaukset.

                                      Ohjeiston yksittäiset sivut on järjestetty epigrafisten tai papyrologisten käsitteiden perusteella eikä TEI-elementtien nimien mukaisesti. Näin esimerkiksi kaikki sellaiset sivut, joissa käsitellään lyhenteitä, on ryhmitelty yhteen (otsakkeen Editorial Interventions alle) välittämättä siitä, mitä TEI-elementtejä niiden merkitsemisessä käytetään. Ohjeiston jokainen sivu on rakenteeltaan samankaltainen: ensin selitetään lyhyesti sivun otsikon merkitys (esim. sivulla, jonka otsikko on Tulkitsemattomat merkit, selitys on ’Selvästi näkyvät mutta käsittämättömät merkit’). Sen alla esitetään asianmukainen TEI-elementti (tai elementit) sekä annetaan linkki TEI-ohjeiston sivulle, jossa ko. elementti on esitelty yksityiskohtaisesti. Tämän jälkeen kerrotaan EpiDocin mukaiset suositukset kyseisten TEI-elementtien käyttöön sekä niihin yhdistettävissä olevien attribuuttien ja arvojen yksityiskohtia.

                                      Selitysten alapuolelta löytyy yleensä myös muutama esimerkki sen aidosta käyttöympäristöstä. Erityisesti transkriptioiden piirteiden ollessa kyseessä ohjeistossa esitetään kustakin aiheesta yleisten epigrafisten ja papyrologisten transkriptio-ohjeiden mukaisia perinteisiä tulkintoja, esim. Krummrey-Panciera, Duke Databank.

                                      XML-esimerkeistä näkee erilaisille transkriptioiden piirteille soveliaan merkintäkielen, esim. tavat merkitä symbolin sisältävän lyhennyksen avaus. Malliesimerkeissä luetellaan useampia merkintäkielen vaihtoehtoja, joista voi valita sen mukaan, kuinka yksityiskohtaisesti asia halutaan ilmaista. Esimerkkien jälkeen esitetään sarja tulkintoja (tai eri tulkinta jokaisen esimerkin jälkeen), joista näkee, millaisia tulostusvaihtoehtoja EpiDoc P5 -tyyliarkeista kyseiselle merkintäkielen ilmaukselle löytyy. Oletustulostus on Krummrey-Pancieran periaatteiden mukainen. Muita tyylejä ovat mm. SEG, London ja DDbDP. Jokaisessa esimerkissä on lähdeviite. Useimmat piirtokirjoituksiin liittyvät esimerkkitapaukset on poimittu Afrodisiaksen (Inscriptions of Aphrodisias) tai Tripolitanian (Inscriptions of Roman Tripolitania) tekstien joukosta ja papyrologiset puolestaan Duke Databank of Documentary Papyri:n kokoelmista.

                                      Harjoituskurssit, työkalut ja tuki

                                      Tämä Ohjeisto on pohjimmiltaan lähdeteos. Perusteellisempaan harjoitteluun ja tukeen on tarjolla muita keinoja. EpiDoc-yhteisön jäsenet järjestävät ajoittain harjoituskursseja ja saavat niihin toisinaan myös rahoitusta isommilta tutkimushankkeilta (esim. Afrodisiaksen piirtokirjoitusten tutkimusprojekti rahoitti useita EpiDoc-työpajoja vuosina 2004–2008). Tällaisista harjoituskursseista löytyy lisätietoa Koulutus-sivulta EpiDocin wikissä. Ne, joille EpiDoc ja tekstin koodaus on täysin uutta, saattavat hyötyä myös TEI:n yleisluontoisista harjoituskursseista (TEI:n tapahtumalistalta löytyy ainakin osa ko. kursseista).

                                      EpiDoc-merkintäkieltä voi kirjoittaa ja editoida millä tahansa XML-kielelle tarkoitetulla perustyökalulla (luettelo löytyy Editointityökalut-sivulta TEI:n wikissä). Tavallisesti EpiDoc- ja TEI-harjoituskursseilla, tai missä tahansa XML-kurssilla, käydään läpi tällaisten työkalujen peruskäyttöä. Julkaisemiseen, hakujärjestelmien luomiseen ja muuhun EpiDoc ja TEI-tiedostojen työstöön käytetään XML-kielen muuntajana XSLT ja XQuery-kieliä, yleisinä hakualustoina saattaa olla mm. Solr tai TEI:lle erityisesti luotu avoimeen koodiin perustuva työkalu kuten Kiln ja Papyrological Navigator.

                                      Mikäli eteen tulee ongelma, johon ei tunnu löytyvän vastausta näiltä ohjesivuilta, kysymys kannattaa esittää Markup-listalla.

                                      Responsibility for this section

                                      1. Gabriel Bodard, kirjoittaja
                                      2. Laura Löser, kirjoittaja
                                      3. Simona Stoyanova, kirjoittaja
                                      4. Charlotte Tupman, kirjoittaja
                                      5. Tom Elliott, kirjoittaja
                                      6. Katariina Kankaanpää, suomentaja
                                      7. Marja Vierros, suomentaja

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-fr.html b/gl/dev/intro-intro-fr.html index e7aa03923..9252f1ee3 100644 --- a/gl/dev/intro-intro-fr.html +++ b/gl/dev/intro-intro-fr.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Introduction générale aux Guidelines EpiDoc

                                      2023-04-27

                                      EpiDoc est un regroupement informel de projets et de chercheurs travaillant sur des sources anciennes retranscrites en XML en utilisant les principes de la Text Encoding Initiative (TEI). Il produit des recommandations, des outils et des suggestions de bonnes pratiques pour l’encodage numérique, le traitement et la publication de tels textes. La page d’accueil d’EpiDoc se trouve à l’adresse http://epidoc.sf.net

                                      Le présent document (les Guidelines EpiDoc) est le résultat du travail encore en cours de la communauté EpiDoc, entammé depuis plusieurs années déjà. Il décrit la manière d’encoder les diverses caractéristiques des documents épigraphiques et papyrologiques, en se basant sur les concepts de base de l’édition scientifique de texte (tels que, par exemple, les conventions de Leyde pour les éléments relatifs à la transcription proprement dite ou un modèle de données comme celui de l’Electronic Archive of Greek and Latin Epigraphy (EAGLE) pour les éléments historiques ou descriptifs). Ces Guidelines doivent être utilisées en conjonction avec le schéma EpiDoc, lequel permet la validation des documents encodés selon les principes décrits dans les Guidelines, et la feuille de style d’exemple EpiDoc, laquelle tente de fournir une mise en page basique de chacune des fonctionnalités décrites.

                                      Les Guidelines EpiDoc ne peuvent prétendre fournir une explication exhaustive de la manière dont doit être établi un projet EpiDoc, mit sur pied un site internet, conçus des outils de recherche ou réalisée tout autre tâche technique ou colaborative requise pour la publication sur internet des textes transcrits. De même ces Guidelines ne constituent pas une introduction complète à la papyrologie ou à l’épigraphie : elles sont uniquement une ressource relative à l’encodage en XML selon le schéma TEI des caractéristiques d’une édition d’un texte documentaire ancien telles quelles sont requises dans le domaine de l’épigraphie ou dans des disciplines similaires.

                                      Même s’il n’existe pas de convention unique pour l’édition d’un document épigraphique ou papyrologique, les Guidelines EpiDoc (et les feuilles de style EpiDoc) adoptent une approche en accord avec les modèles de données utilisés par des projets et des collaborations telles que l’Advanced Papyrological Information System (APIS), EAGLE, et le Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Dans la mesure ou la discipline épigraphique, et en particulier sa version numérique, ont déjà établis de solides modèles de bonnes pratiques en terme d’édition, nous nous contentons de recommander une manière de reproduire en XML structuré TEI les informations et observations que les spécialistes considèrent déjà comme essentielles ou à tout le moins utiles.

                                      Les Guidelines EpiDoc sont donc conçues comme un complément aux conventions de Leyde, lesquelles sont en usage dans le domaine de l’épigraphie et de la papyrologie depuis plus de 80 ans et sont comprises dans de nombreuses disciplines philologiques et documentaires. Les Guidelines partent du principe que ces conventions forment une base adéquate pour représenter les éléments distinctifs nécessaires à l’édition d’un texte pré-moderne, et formulent leurs recommandations et exemples sur ces distinctions sans toutefois avoir besoin des conventions typographique et des sigles définis par ces conventions. Ceci revient à dire que si EpiDoc cherche effectivement à retranscrire en XML les interventions textuelles telles que les interventions éditoriales destinées à marquer la perte complète de caractères, il ne spécifie pas que ces interventions doivent être formellement rendues entre crochets ( “[“ et “]”) dans le XML ou lors de transformations ultérieure. Cela étant, le comportement par défaut des feuilles de style EpiDoc est bien un rendu des textes encodés selon les conventions de Leyde. Il est souvent possible pour le TEI d’enregistrer un niveau plus détaillé d’observations que celui permit par les conventions de Leyde, mais les Guidelines ne recommandent pas le remplacement des pratiques épigraphiques ou papyrologiques classiques par ces nouveaux principes.

                                      Les Guidelines produites et recommandées par la communauté EpiDoc représentent une sélection et une spécialisation des Guidelines TEI, lesquelles recommandent l’encodage en XML d’une large gamme de textes littéraires ou historiques ainsi que de corpus linguistiques. De la même manière qu’EpiDoc est une spécialisation de la TEI pour l’encodage d’objets et documents anciens, ne formulant des recommandations que pour les seuls éléments, attributs et valeurs pertinents pour cette communauté spécifique, les Guidelines EpiDoc sont conçues pour compléter (et non remplacer) les Guidelines TEI. En particulier on notera que les sections techniques et références de la TEI restent une ressource essentielle pour les utilisateurs d’EpiDoc. Ils y trouveront des listes d’éléments, des explications des valeurs des attributs ou des types de données et des exemples d’utilisations dans une large gamme de contextes ainsi qu’une description complète des fonctionnalités d’encodage. Les Guidelines EpiDoc recommandent un ensemble réduit de fonctionnalités de la TEI (éléments, modèles de contenu, attributs et valeurs) de façon à ce qu’un fichier EpiDoc soit toujours un contenu TEI valide même si tous les fichiers TEI ne sont pas valides EpiDoc. Là où les recommandations des Guidelines EpiDoc sont plus restrictives que celles de la TEI, il faut considérer que les premières remplacent les secondes. Mais là où la TEI offre plus de précision, de détails ou d’exemples d’utilisations pertinentes, il va de soit qu’elle doit être considérée comme la source principale pour tous les usages EpiDoc.

                                      Structure and Features of the EpiDoc Guidelines

                                      Il y a plusieurs manières d’accéder aux diverses pages individuelles formant le corps des Guidelines EpiDoc.

                                      • Trois menus principaux rassemblent toutes les pages sous les catégories suivantes : Transcription (les fonctionnalités relatives au contenu, à son apparence, aux restaurations et à l’interprétation basique du texte lui-même); Supporting Data (en ce compris la description du support matériel ou du manuscrit, l’histoire de l’objet et de sa découverte, les informations bibliographiques et tout autre information éditoriale); et Vocabulary and Indexing (mots et caractéristiques marquées dans le texte à des fins de lexicographie, d’indexation, de recherche, …)
                                      • Diverses sections regroupent des pages d’aide destinées à certaines catégories spécifiques d’utilisateurs ou de problématiques (par exemple, les recommandations de Krummerey-Panciera pour la transcription de documents épigraphiques ou l’encodage des caractéristiques papyrologiques telles qu’enregistrées dans la base de données APIS). Ces sections sont encore en cours de construction et toutes vos recommandations pour les améliorer ou en ajouter sont les bienvenues.
                                      • Finalement les Guidelines contiennent un certain nombre d’appendices tels que le glossaire des termes techniques et spécialisés, une bibliographie reprenant des sources relatives aux domaines de la papyrologie et de l’épigraphie, des exemples de corpus EpiDoc et de manière générale sur la publication numérique de textes anciens. Un index des Guidelines classé en fonction des éléments TEI mentionnés permet enfin de retrouver toutes les caractéristiques épigraphiques pour lesquels un élément spécifique fait partie des pratiques recommandées.

                                      Les pages des Guidelines EpiDoc sont organisées sur base des concepts papyrologiques ou épigraphiques plutôt qu’en fonction des éléments TEI. Ainsi toutes les pages relatives aux abréviations sont rassemblées (sous la rubrique (Editorial Interventions) indépendamment des éléments TEI qui y sont définis. Chaque page des Guidelines suit une structure commune qui commence par une brève explication du titre de la page (ainsi, pour la page “Uninterpreted Characters”, sera fournie l’explication “Clear but incomprehensible letters”). Les éléments pertinents sont ensuite affichés dans une case dédiée, avec un lien vers les pages adéquates des TEI Guidelines. Suit alors une description des recommandations d’EpiDoc pour l’utilisation de ces éléments, en ce compris le détail des des attributs et valeurs pertinentes.

                                      Sous cette explication figurent usuellement quelques exemples de l’utilisation des éléments dans leur contexte. Cela est particulièrement vrai en ce qui concerne les fonctionnalités relatives à la transcription du texte, les Guidelines fournissant la liste des retranscriptions usuelles de la problématique concernée selon les usages courants des pratiques épigraphiques et papyrologiques tels que repris dans des guidelines comme celles de Krummrey-Panciera ou de la Duke Databank of Documentary Papyri (DDbDP).

                                      La section des exemples XML présente des recommandations de balisage correspondant aux différentes manières de reproduire une caractéristique spécifique, par exemple différentes manières d’indiquer l’expansion d’une abréviation contenant un symbole. Ces exemples reprennent souvent différentes options de balisages en fonction du degré de détail souhaité. Sous ces exemples sont donnés sont affichées des transcriptions dans les différents styles offerts par les feuilles de styles EpiDoc P5. Le style de transcription repris par défaut est celui des conventions Krummrey-Panciera. Les autres comprennent les styles SEG, Londres et DDbDP. Sous chaque exemple se trouve par ailleurs un lien renvoyant vers sa source. La plupart des exemples sont tirés des Inscriptions Of Aphrodisias, des Inscriptions of Roman Tripolitania et de la Duke Databank of Documentary Papyri .

                                      Formation, outils et support

                                      Les présentes Guidelines sont essentiellement une source de référence. D’autres ressources existent, qu’il s’agisse de formations plus approfondies ou de moyens pour obtenir de l’aide. Les membres de la communauté EpiDoc organisent de manière irrégulière des sessions de formation, parfois financées par des projets majeurs tels que les ateliers organisés entre 2004 et 2008 dans le cadre du projet projet Inscriptions of Aphrodisias. Plus d’informations sur ces sessions de formations sont accessibles sur la page “Training” du Wiki EpiDoc. Celles et ceux débutants dans le domaine de la l’encodage en général ou d’EpiDoc en particulier peuvent également trouver utiles les séances de formation à la TEI, certaines étant reprises sur la liste des évènements TEI.

                                      Il est possible de rédiger ou d’éditer des textes EpiDoc avec n’importe quel outil XML standard (plusieurs étant mentionnés sur la page "Editing Tools" du Wiki TEI). Une formation de base à l’utilisation de ces outils est prévue dans les ateliers de formation TEI et EpiDoc, ainsi que dans tous les tutoriels XML. D’autres outils pour publier, interroger ou appliquer toute autre forme de traitement pour les fichiers EpiDoc comprennent les langages de conversion de l’XML XSLT et XQuery, et des plateformes de recherche génériques telles que Solr ou propres à la TEI comme l’outil open source Kiln ou le Navigateur Papyrologique.

                                      Comme toujours, la première ressource à consulter pour obtenir de l’aide pour tout sujet non couvert par ces Guidelines est et reste la liste de distribution Markup.

                                      Responsables de cette section

                                      1. Gabriel Bodard, Auteur
                                      2. Laura Löser, Auteur
                                      3. Simona Stoyanova, Auteur
                                      4. Charlotte Tupman, Auteur
                                      5. Tom Elliott, Auteur
                                      6. Pascal Lemaire, Traduction française

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Introduction générale aux Guidelines EpiDoc

                                      2024-03-05

                                      EpiDoc est un regroupement informel de projets et de chercheurs travaillant sur des sources anciennes retranscrites en XML en utilisant les principes de la Text Encoding Initiative (TEI). Il produit des recommandations, des outils et des suggestions de bonnes pratiques pour l’encodage numérique, le traitement et la publication de tels textes. La page d’accueil d’EpiDoc se trouve à l’adresse http://epidoc.sf.net

                                      Le présent document (les Guidelines EpiDoc) est le résultat du travail encore en cours de la communauté EpiDoc, entammé depuis plusieurs années déjà. Il décrit la manière d’encoder les diverses caractéristiques des documents épigraphiques et papyrologiques, en se basant sur les concepts de base de l’édition scientifique de texte (tels que, par exemple, les conventions de Leyde pour les éléments relatifs à la transcription proprement dite ou un modèle de données comme celui de l’Electronic Archive of Greek and Latin Epigraphy (EAGLE) pour les éléments historiques ou descriptifs). Ces Guidelines doivent être utilisées en conjonction avec le schéma EpiDoc, lequel permet la validation des documents encodés selon les principes décrits dans les Guidelines, et la feuille de style d’exemple EpiDoc, laquelle tente de fournir une mise en page basique de chacune des fonctionnalités décrites.

                                      Les Guidelines EpiDoc ne peuvent prétendre fournir une explication exhaustive de la manière dont doit être établi un projet EpiDoc, mit sur pied un site internet, conçus des outils de recherche ou réalisée tout autre tâche technique ou colaborative requise pour la publication sur internet des textes transcrits. De même ces Guidelines ne constituent pas une introduction complète à la papyrologie ou à l’épigraphie : elles sont uniquement une ressource relative à l’encodage en XML selon le schéma TEI des caractéristiques d’une édition d’un texte documentaire ancien telles quelles sont requises dans le domaine de l’épigraphie ou dans des disciplines similaires.

                                      Même s’il n’existe pas de convention unique pour l’édition d’un document épigraphique ou papyrologique, les Guidelines EpiDoc (et les feuilles de style EpiDoc) adoptent une approche en accord avec les modèles de données utilisés par des projets et des collaborations telles que l’Advanced Papyrological Information System (APIS), EAGLE, et le Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Dans la mesure ou la discipline épigraphique, et en particulier sa version numérique, ont déjà établis de solides modèles de bonnes pratiques en terme d’édition, nous nous contentons de recommander une manière de reproduire en XML structuré TEI les informations et observations que les spécialistes considèrent déjà comme essentielles ou à tout le moins utiles.

                                      Les Guidelines EpiDoc sont donc conçues comme un complément aux conventions de Leyde, lesquelles sont en usage dans le domaine de l’épigraphie et de la papyrologie depuis plus de 80 ans et sont comprises dans de nombreuses disciplines philologiques et documentaires. Les Guidelines partent du principe que ces conventions forment une base adéquate pour représenter les éléments distinctifs nécessaires à l’édition d’un texte pré-moderne, et formulent leurs recommandations et exemples sur ces distinctions sans toutefois avoir besoin des conventions typographique et des sigles définis par ces conventions. Ceci revient à dire que si EpiDoc cherche effectivement à retranscrire en XML les interventions textuelles telles que les interventions éditoriales destinées à marquer la perte complète de caractères, il ne spécifie pas que ces interventions doivent être formellement rendues entre crochets ( “[“ et “]”) dans le XML ou lors de transformations ultérieure. Cela étant, le comportement par défaut des feuilles de style EpiDoc est bien un rendu des textes encodés selon les conventions de Leyde. Il est souvent possible pour le TEI d’enregistrer un niveau plus détaillé d’observations que celui permit par les conventions de Leyde, mais les Guidelines ne recommandent pas le remplacement des pratiques épigraphiques ou papyrologiques classiques par ces nouveaux principes.

                                      Les Guidelines produites et recommandées par la communauté EpiDoc représentent une sélection et une spécialisation des Guidelines TEI, lesquelles recommandent l’encodage en XML d’une large gamme de textes littéraires ou historiques ainsi que de corpus linguistiques. De la même manière qu’EpiDoc est une spécialisation de la TEI pour l’encodage d’objets et documents anciens, ne formulant des recommandations que pour les seuls éléments, attributs et valeurs pertinents pour cette communauté spécifique, les Guidelines EpiDoc sont conçues pour compléter (et non remplacer) les Guidelines TEI. En particulier on notera que les sections techniques et références de la TEI restent une ressource essentielle pour les utilisateurs d’EpiDoc. Ils y trouveront des listes d’éléments, des explications des valeurs des attributs ou des types de données et des exemples d’utilisations dans une large gamme de contextes ainsi qu’une description complète des fonctionnalités d’encodage. Les Guidelines EpiDoc recommandent un ensemble réduit de fonctionnalités de la TEI (éléments, modèles de contenu, attributs et valeurs) de façon à ce qu’un fichier EpiDoc soit toujours un contenu TEI valide même si tous les fichiers TEI ne sont pas valides EpiDoc. Là où les recommandations des Guidelines EpiDoc sont plus restrictives que celles de la TEI, il faut considérer que les premières remplacent les secondes. Mais là où la TEI offre plus de précision, de détails ou d’exemples d’utilisations pertinentes, il va de soit qu’elle doit être considérée comme la source principale pour tous les usages EpiDoc.

                                      Structure and Features of the EpiDoc Guidelines

                                      Il y a plusieurs manières d’accéder aux diverses pages individuelles formant le corps des Guidelines EpiDoc.

                                      • Trois menus principaux rassemblent toutes les pages sous les catégories suivantes : Transcription (les fonctionnalités relatives au contenu, à son apparence, aux restaurations et à l’interprétation basique du texte lui-même); Supporting Data (en ce compris la description du support matériel ou du manuscrit, l’histoire de l’objet et de sa découverte, les informations bibliographiques et tout autre information éditoriale); et Vocabulary and Indexing (mots et caractéristiques marquées dans le texte à des fins de lexicographie, d’indexation, de recherche, …)
                                      • Diverses sections regroupent des pages d’aide destinées à certaines catégories spécifiques d’utilisateurs ou de problématiques (par exemple, les recommandations de Krummerey-Panciera pour la transcription de documents épigraphiques ou l’encodage des caractéristiques papyrologiques telles qu’enregistrées dans la base de données APIS). Ces sections sont encore en cours de construction et toutes vos recommandations pour les améliorer ou en ajouter sont les bienvenues.
                                      • Finalement les Guidelines contiennent un certain nombre d’appendices tels que le glossaire des termes techniques et spécialisés, une bibliographie reprenant des sources relatives aux domaines de la papyrologie et de l’épigraphie, des exemples de corpus EpiDoc et de manière générale sur la publication numérique de textes anciens. Un index des Guidelines classé en fonction des éléments TEI mentionnés permet enfin de retrouver toutes les caractéristiques épigraphiques pour lesquels un élément spécifique fait partie des pratiques recommandées.

                                      Les pages des Guidelines EpiDoc sont organisées sur base des concepts papyrologiques ou épigraphiques plutôt qu’en fonction des éléments TEI. Ainsi toutes les pages relatives aux abréviations sont rassemblées (sous la rubrique (Editorial Interventions) indépendamment des éléments TEI qui y sont définis. Chaque page des Guidelines suit une structure commune qui commence par une brève explication du titre de la page (ainsi, pour la page “Uninterpreted Characters”, sera fournie l’explication “Clear but incomprehensible letters”). Les éléments pertinents sont ensuite affichés dans une case dédiée, avec un lien vers les pages adéquates des TEI Guidelines. Suit alors une description des recommandations d’EpiDoc pour l’utilisation de ces éléments, en ce compris le détail des des attributs et valeurs pertinentes.

                                      Sous cette explication figurent usuellement quelques exemples de l’utilisation des éléments dans leur contexte. Cela est particulièrement vrai en ce qui concerne les fonctionnalités relatives à la transcription du texte, les Guidelines fournissant la liste des retranscriptions usuelles de la problématique concernée selon les usages courants des pratiques épigraphiques et papyrologiques tels que repris dans des guidelines comme celles de Krummrey-Panciera ou de la Duke Databank of Documentary Papyri (DDbDP).

                                      La section des exemples XML présente des recommandations de balisage correspondant aux différentes manières de reproduire une caractéristique spécifique, par exemple différentes manières d’indiquer l’expansion d’une abréviation contenant un symbole. Ces exemples reprennent souvent différentes options de balisages en fonction du degré de détail souhaité. Sous ces exemples sont donnés sont affichées des transcriptions dans les différents styles offerts par les feuilles de styles EpiDoc P5. Le style de transcription repris par défaut est celui des conventions Krummrey-Panciera. Les autres comprennent les styles SEG, Londres et DDbDP. Sous chaque exemple se trouve par ailleurs un lien renvoyant vers sa source. La plupart des exemples sont tirés des Inscriptions Of Aphrodisias, des Inscriptions of Roman Tripolitania et de la Duke Databank of Documentary Papyri .

                                      Formation, outils et support

                                      Les présentes Guidelines sont essentiellement une source de référence. D’autres ressources existent, qu’il s’agisse de formations plus approfondies ou de moyens pour obtenir de l’aide. Les membres de la communauté EpiDoc organisent de manière irrégulière des sessions de formation, parfois financées par des projets majeurs tels que les ateliers organisés entre 2004 et 2008 dans le cadre du projet projet Inscriptions of Aphrodisias. Plus d’informations sur ces sessions de formations sont accessibles sur la page “Training” du Wiki EpiDoc. Celles et ceux débutants dans le domaine de la l’encodage en général ou d’EpiDoc en particulier peuvent également trouver utiles les séances de formation à la TEI, certaines étant reprises sur la liste des évènements TEI.

                                      Il est possible de rédiger ou d’éditer des textes EpiDoc avec n’importe quel outil XML standard (plusieurs étant mentionnés sur la page "Editing Tools" du Wiki TEI). Une formation de base à l’utilisation de ces outils est prévue dans les ateliers de formation TEI et EpiDoc, ainsi que dans tous les tutoriels XML. D’autres outils pour publier, interroger ou appliquer toute autre forme de traitement pour les fichiers EpiDoc comprennent les langages de conversion de l’XML XSLT et XQuery, et des plateformes de recherche génériques telles que Solr ou propres à la TEI comme l’outil open source Kiln ou le Navigateur Papyrologique.

                                      Comme toujours, la première ressource à consulter pour obtenir de l’aide pour tout sujet non couvert par ces Guidelines est et reste la liste de distribution Markup.

                                      Responsables de cette section

                                      1. Gabriel Bodard, Auteur
                                      2. Laura Löser, Auteur
                                      3. Simona Stoyanova, Auteur
                                      4. Charlotte Tupman, Auteur
                                      5. Tom Elliott, Auteur
                                      6. Pascal Lemaire, Traduction française

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-it.html b/gl/dev/intro-intro-it.html index b3afb796a..bf82ec43b 100644 --- a/gl/dev/intro-intro-it.html +++ b/gl/dev/intro-intro-it.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Come usare le Linee Guida EpiDoc

                                      2023-04-27

                                      EpiDoc è una collaborazione in senso ampio di progetti e studiosi che lavorano su risorse documentarie antiche in XML TEI (Text Encoding Initiative), e progettano raccomandazioni, strumenti e buona pratica per la codifica digitale, il trattamento e la pubblicazione di tali testi. La home page di EpiDoc sul web si trova presso http://EpiDoc.sf.net.

                                      Questo documento (le Linee Guida EpiDoc) è il prodotto in continuo mutamento del lavoro svolto dalla comunità EpiDoc in diversi anni. Descrive come codificare i vari elementi caratteristici dei documenti epigrafici e papirologici, basandosi sui principi base dell'ecdotica dei testi (come per esempio le Convenzioni Leiden per quanto riguarda la trascrizione, e modelli di dati Electronic Archive of Greek and Latin Epigraphy (EAGLE) per quanto riguarda elementi stotici e descrittivi). Le Linee Guida devono essere usate in coppia con lo Schema EpiDoc , con cui i documenti codificati secondo tali principi devono essere validati, e con gli EpiDoc Example Stylesheets (fogli di stile esemplari), che rappresentano un tentativo di resa grafica per ogni elemento caratteristico descritto.

                                      Le Linee Guida EpiDoc non hanno la pretesa di rappresentare una spiegazione esaustiva di come iniziare un progetto EpiDoc, generare un sito web, costruire uno strumento di ricerca, o altri lavori tecnici o collaborativi necessari alla pubblicazione online di testi codificati. Né le Linee Guida rappresentano una introduzione completa all'epigrafia o alla papirologia; esse vogliono esclusivamente essere una guida alla codifica in XML delle caratteristiche dell'edizione di testi documentari antichi, sempre più necessaria nello studio dell'epigrafia.

                                      Anche se non esiste una singola convenzione per la strutturazione di un'edizione epigrafica o papirologica, le Linee Guida EpiDoc (e i Fogli di Stile EpiDoc) adottano una strategia che è in accordo con i modelli di dati impiegati in progetti e collaborazioni quali l'Advanced Papyrological Information System (APIS), EAGLE, e il Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Dato che la disciplina dell'epigrafia in generale, e dell'epigrafia digitale in particolare, possiede già dei modelli rigorosi per una buona pratica nella strutturazione delle edizioni, ci limitiamo a raccomandare la codifica in XML degli stessi dati e delle stesse osservazioni che altri studiosi hanno già stabilito essere essenziali o utili.

                                      Le Linee Guida EpiDoc intendono essere un complemento alle Convenzioni Leiden (da qui in poi "Leiden"), in uso da oltre 80 anni in epigrafia e papirologia, e comunemente usate e comprese in vari campi filologici e documentari. Le Linee Guida danno per scontato che Leiden sia una base adeguata per le distinzioni intellettuali registrate nell'edizione di un testo pre-moderno, e basano le proprie raccomandazioni e esempi su tali distinzioni senza aver bisogno delle specifiche convenzioni tipografiche e sigle raccomandate. Ciò significa che EpiDoc intende chiaramente registrare in XML tali interventi testuali quali i supplimenti di un editore per caratteri persi o danneggiati, ma non specifica, nell'XML o in prodotti susseguenti, che tali supplementi debbano essere resi all'interno di parentesi quadre ("[" e "]"). Detto questo, il comportamento predefinito degli EpiDoc Example Stylesheets è quello di produrre una resa Leiden per i testi codificati con EpiDoc. A volte è possibile per la TEI di registrare distinzioni che sono più sottili o precise di Leiden, e tali possibilità sono descritte qui sotto, ma queste Linee Guida raccomandano di non rimpiazzare pratiche standard di epigrafia e papirologia con suddetti nuovi principi.

                                      Le Linee Guida prodotte e raccomandate dalla comunità EpiDoc rappresentano una sottocategoria e un raffinamento delle Linee Guida TEI , che contengono raccomandazioni sulla codifica in XML di una vasta gamma di testi letterari e storici, e di corpora linguistici. Nello stesso modo in cui EpiDoc è una specializzazione delle raccomandazioni TEI per documenti e oggetti antichi, concentrandosi solo su quegli elementi, attributi e oggetti che abbiano un valore ben preciso per una comunità specifica, le Linee Guida EpiDoc sono da intendersi come supplemento (e non in alcun modo un rimpiazzo) delle Linee Guida TEI. In particolar modo le sezioni tecniche e di referenza della TEI rimangono una risorsa inestimabile per chiunque faccia uso di EpiDoc, vi si potranno trovare liste di elementi, spiegazioni dei valori di attributi o tipologie di dati, esempi in una vasta gamma di contesti e una descrizioni esaustive delle caratteristiche della codifica. Le Linee Guida EpiDoc raccomandano un numero ristretto di elementi, modelli di contenuto, attributi e valori TEI; in questo modo, un documento EpiDoc sarà sempre un documento TEI valido, ma non necessariamente un documento TEI potrà essere un documento EpiDoc valido. Ove le Linee Guida EpiDoc sono più restrittive di quelle TEI, le prime sono intese a sostituire queste ultime, ma nel caso in cui le linee guida TEI vadano più nel dettaglio, o offrano una gamma più vasta di esempi queste dovrebbero ovviamente essere consultate e considerate la risorsa canonica per tutti gli usi EpiDoc.

                                      Struttura e caratteristiche delle Linee Guida EpiDoc

                                      Ci sono diverse strade che portano alle singole pagine che costituiscono il corpo centrale delle Linee Guida EpiDoc .

                                      Le singole pagine delle Linee Guida sono organizzate per concetto epigrafico o papirologico, e non per nome dell'elemento TEI. Per cui, per esempio, tutte le pagine che si occupano di abbreviazioni sono raggruppate sotto la Rubrica degli interventi editoriali (Editorial Interventions rubric)), indipendentemente da quale elemento TEI vi è specificato. Ogni pagina delle Linee Guida è strutturata allo stesso modo: per prima c'è una breve spiegazione del titolo della pagina (per esempio, per la pagina intitolata Caratteri non Interpretati ( ‘Uninterpreted Characters’), vi è una spiegazione “Lettere chiare ma incomprensibili”). L'elemento (o gli elementi) TEI rilevanti sono mostrati in una tavola più sotto, che include un link alle pagine delle Linee Guida TEi relative a quell'elemento. Segue una spiegazione delle raccomandazioni EpiDoc per l'uso dei detti elementi TEI, inclusi dettagli su attributi e valori relativi.

                                      Sotto a queste spiegazioni ci sono in genere una serie di esempi di uso in contesto. Specialmente in caso di caratteristiche di trascrizione, le Linee Guida elencano rese abituali del problema in questione secondo le più comuni convenzioni epigrafiche e papirologiche, quali le Krummrey-Panciera e il Duke Databank.

                                      Gli esempi in XML mostrano la codifica raccomandata per ogni tipo di caratteristica della trascrizione, per essempio i vari casi di espansione di un'abbreviazione che include un simbolo (?). Gli esempi solitamente mostrano varie opzioni di codifica, a seconda del livello di dettaglio desiderato. Sotto gli esempi vi è una serie di rese/esecuzioni/rappresentazioni (o una resa diversa sotto ogni esempio) che rappresentano gli svariati output disponibili nei fogli di stile esemplari di EpiDoc P5. L'output di default segue le convenzioni Krummrey-Panciera. Altri includono lo stile SEG, lo Stile Londra (London style) e lo stile DDbDP. Sotto ad ogni esempio vi è una referenza alla fonte. La maggior parte degli esempi deriva dalle Inscriptions of Aphrodisias (Iscrizioni di Aphrodisia), dalle Inscriptions of Roman Tripolitania (Iscrizioni della Tripolitania romana) e dalla Duke Databank of Documentary Papyri (Databank Duke dei papiri documentari).

                                      Corsi, strumenti e supporto

                                      Queste Linee Guida sono essenzialmente una risorsa di riferimento. Per una formazione più dettagliata o supporto sono disponibili altre risorse. I membri della comunità EpiDoc tengono occasionalmente corsi di formazione, a volte finanziati da vari progetti (come per esempio gli svariati workshop tenuti durante lo sviluppo del progetto Inscriptions of Aphrodisias, 2004-2008); ulteriori informazioni su tali corsi di formazione possono essere trovati presso la Training page nella Wiki di EpiDoc. Coloro che non avessero precedenti conoscenze su EpiDoc e sulla codifica dei testi, possono inoltre trovare utili i corsi generici di formazione TEI (alcuni dei quali elencati nella TEI Events list (lista di eventi TEI)).

                                      I documenti in EpiDoc possono essere creati e modificati usando un qualsiasi strumento standard per (molti dei quali sono elencati nella pagina "Editing Tools" della wiki TEI); un corso base sull'uso di tali strumenti è solitamente incluso sia negli eventi di formazione EpiDoc sia in quelli TEI, o in un qualsiasi tutorial sull'XML. Altri strumenti per la pubblicazione, la ricerca e il trattamento dei documenti EpiDoc e TEI includono i linguaggi di trasformazione XML XSLT e XQuery, e piattaforme di ricerca generiche quali Solr e strumenti open source specifici TEI quali Kiln e il Papyrological Navigator.

                                      Come di consueto, il primo punto di riferimento per ogni questione non coperta da queste linee guida dovrebbe essere la lista di discussione Markup.

                                      Responsibility for this section

                                      1. Gabriel Bodard, autore
                                      2. Laura Löser, autore
                                      3. Simona Stoyanova, autore
                                      4. Charlotte Tupman, autore
                                      5. Tom Elliott, autore
                                      6. Eleonora Litta, traduzione italiana
                                      7. Greta Franzini, correzione traduzione italiana

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Come usare le Linee Guida EpiDoc

                                      2024-03-05

                                      EpiDoc è una collaborazione in senso ampio di progetti e studiosi che lavorano su risorse documentarie antiche in XML TEI (Text Encoding Initiative), e progettano raccomandazioni, strumenti e buona pratica per la codifica digitale, il trattamento e la pubblicazione di tali testi. La home page di EpiDoc sul web si trova presso http://EpiDoc.sf.net.

                                      Questo documento (le Linee Guida EpiDoc) è il prodotto in continuo mutamento del lavoro svolto dalla comunità EpiDoc in diversi anni. Descrive come codificare i vari elementi caratteristici dei documenti epigrafici e papirologici, basandosi sui principi base dell'ecdotica dei testi (come per esempio le Convenzioni Leiden per quanto riguarda la trascrizione, e modelli di dati Electronic Archive of Greek and Latin Epigraphy (EAGLE) per quanto riguarda elementi stotici e descrittivi). Le Linee Guida devono essere usate in coppia con lo Schema EpiDoc , con cui i documenti codificati secondo tali principi devono essere validati, e con gli EpiDoc Example Stylesheets (fogli di stile esemplari), che rappresentano un tentativo di resa grafica per ogni elemento caratteristico descritto.

                                      Le Linee Guida EpiDoc non hanno la pretesa di rappresentare una spiegazione esaustiva di come iniziare un progetto EpiDoc, generare un sito web, costruire uno strumento di ricerca, o altri lavori tecnici o collaborativi necessari alla pubblicazione online di testi codificati. Né le Linee Guida rappresentano una introduzione completa all'epigrafia o alla papirologia; esse vogliono esclusivamente essere una guida alla codifica in XML delle caratteristiche dell'edizione di testi documentari antichi, sempre più necessaria nello studio dell'epigrafia.

                                      Anche se non esiste una singola convenzione per la strutturazione di un'edizione epigrafica o papirologica, le Linee Guida EpiDoc (e i Fogli di Stile EpiDoc) adottano una strategia che è in accordo con i modelli di dati impiegati in progetti e collaborazioni quali l'Advanced Papyrological Information System (APIS), EAGLE, e il Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Dato che la disciplina dell'epigrafia in generale, e dell'epigrafia digitale in particolare, possiede già dei modelli rigorosi per una buona pratica nella strutturazione delle edizioni, ci limitiamo a raccomandare la codifica in XML degli stessi dati e delle stesse osservazioni che altri studiosi hanno già stabilito essere essenziali o utili.

                                      Le Linee Guida EpiDoc intendono essere un complemento alle Convenzioni Leiden (da qui in poi "Leiden"), in uso da oltre 80 anni in epigrafia e papirologia, e comunemente usate e comprese in vari campi filologici e documentari. Le Linee Guida danno per scontato che Leiden sia una base adeguata per le distinzioni intellettuali registrate nell'edizione di un testo pre-moderno, e basano le proprie raccomandazioni e esempi su tali distinzioni senza aver bisogno delle specifiche convenzioni tipografiche e sigle raccomandate. Ciò significa che EpiDoc intende chiaramente registrare in XML tali interventi testuali quali i supplimenti di un editore per caratteri persi o danneggiati, ma non specifica, nell'XML o in prodotti susseguenti, che tali supplementi debbano essere resi all'interno di parentesi quadre ("[" e "]"). Detto questo, il comportamento predefinito degli EpiDoc Example Stylesheets è quello di produrre una resa Leiden per i testi codificati con EpiDoc. A volte è possibile per la TEI di registrare distinzioni che sono più sottili o precise di Leiden, e tali possibilità sono descritte qui sotto, ma queste Linee Guida raccomandano di non rimpiazzare pratiche standard di epigrafia e papirologia con suddetti nuovi principi.

                                      Le Linee Guida prodotte e raccomandate dalla comunità EpiDoc rappresentano una sottocategoria e un raffinamento delle Linee Guida TEI , che contengono raccomandazioni sulla codifica in XML di una vasta gamma di testi letterari e storici, e di corpora linguistici. Nello stesso modo in cui EpiDoc è una specializzazione delle raccomandazioni TEI per documenti e oggetti antichi, concentrandosi solo su quegli elementi, attributi e oggetti che abbiano un valore ben preciso per una comunità specifica, le Linee Guida EpiDoc sono da intendersi come supplemento (e non in alcun modo un rimpiazzo) delle Linee Guida TEI. In particolar modo le sezioni tecniche e di referenza della TEI rimangono una risorsa inestimabile per chiunque faccia uso di EpiDoc, vi si potranno trovare liste di elementi, spiegazioni dei valori di attributi o tipologie di dati, esempi in una vasta gamma di contesti e una descrizioni esaustive delle caratteristiche della codifica. Le Linee Guida EpiDoc raccomandano un numero ristretto di elementi, modelli di contenuto, attributi e valori TEI; in questo modo, un documento EpiDoc sarà sempre un documento TEI valido, ma non necessariamente un documento TEI potrà essere un documento EpiDoc valido. Ove le Linee Guida EpiDoc sono più restrittive di quelle TEI, le prime sono intese a sostituire queste ultime, ma nel caso in cui le linee guida TEI vadano più nel dettaglio, o offrano una gamma più vasta di esempi queste dovrebbero ovviamente essere consultate e considerate la risorsa canonica per tutti gli usi EpiDoc.

                                      Struttura e caratteristiche delle Linee Guida EpiDoc

                                      Ci sono diverse strade che portano alle singole pagine che costituiscono il corpo centrale delle Linee Guida EpiDoc .

                                      Le singole pagine delle Linee Guida sono organizzate per concetto epigrafico o papirologico, e non per nome dell'elemento TEI. Per cui, per esempio, tutte le pagine che si occupano di abbreviazioni sono raggruppate sotto la Rubrica degli interventi editoriali (Editorial Interventions rubric)), indipendentemente da quale elemento TEI vi è specificato. Ogni pagina delle Linee Guida è strutturata allo stesso modo: per prima c'è una breve spiegazione del titolo della pagina (per esempio, per la pagina intitolata Caratteri non Interpretati ( ‘Uninterpreted Characters’), vi è una spiegazione “Lettere chiare ma incomprensibili”). L'elemento (o gli elementi) TEI rilevanti sono mostrati in una tavola più sotto, che include un link alle pagine delle Linee Guida TEi relative a quell'elemento. Segue una spiegazione delle raccomandazioni EpiDoc per l'uso dei detti elementi TEI, inclusi dettagli su attributi e valori relativi.

                                      Sotto a queste spiegazioni ci sono in genere una serie di esempi di uso in contesto. Specialmente in caso di caratteristiche di trascrizione, le Linee Guida elencano rese abituali del problema in questione secondo le più comuni convenzioni epigrafiche e papirologiche, quali le Krummrey-Panciera e il Duke Databank.

                                      Gli esempi in XML mostrano la codifica raccomandata per ogni tipo di caratteristica della trascrizione, per essempio i vari casi di espansione di un'abbreviazione che include un simbolo (?). Gli esempi solitamente mostrano varie opzioni di codifica, a seconda del livello di dettaglio desiderato. Sotto gli esempi vi è una serie di rese/esecuzioni/rappresentazioni (o una resa diversa sotto ogni esempio) che rappresentano gli svariati output disponibili nei fogli di stile esemplari di EpiDoc P5. L'output di default segue le convenzioni Krummrey-Panciera. Altri includono lo stile SEG, lo Stile Londra (London style) e lo stile DDbDP. Sotto ad ogni esempio vi è una referenza alla fonte. La maggior parte degli esempi deriva dalle Inscriptions of Aphrodisias (Iscrizioni di Aphrodisia), dalle Inscriptions of Roman Tripolitania (Iscrizioni della Tripolitania romana) e dalla Duke Databank of Documentary Papyri (Databank Duke dei papiri documentari).

                                      Corsi, strumenti e supporto

                                      Queste Linee Guida sono essenzialmente una risorsa di riferimento. Per una formazione più dettagliata o supporto sono disponibili altre risorse. I membri della comunità EpiDoc tengono occasionalmente corsi di formazione, a volte finanziati da vari progetti (come per esempio gli svariati workshop tenuti durante lo sviluppo del progetto Inscriptions of Aphrodisias, 2004-2008); ulteriori informazioni su tali corsi di formazione possono essere trovati presso la Training page nella Wiki di EpiDoc. Coloro che non avessero precedenti conoscenze su EpiDoc e sulla codifica dei testi, possono inoltre trovare utili i corsi generici di formazione TEI (alcuni dei quali elencati nella TEI Events list (lista di eventi TEI)).

                                      I documenti in EpiDoc possono essere creati e modificati usando un qualsiasi strumento standard per (molti dei quali sono elencati nella pagina "Editing Tools" della wiki TEI); un corso base sull'uso di tali strumenti è solitamente incluso sia negli eventi di formazione EpiDoc sia in quelli TEI, o in un qualsiasi tutorial sull'XML. Altri strumenti per la pubblicazione, la ricerca e il trattamento dei documenti EpiDoc e TEI includono i linguaggi di trasformazione XML XSLT e XQuery, e piattaforme di ricerca generiche quali Solr e strumenti open source specifici TEI quali Kiln e il Papyrological Navigator.

                                      Come di consueto, il primo punto di riferimento per ogni questione non coperta da queste linee guida dovrebbe essere la lista di discussione Markup.

                                      Responsibility for this section

                                      1. Gabriel Bodard, autore
                                      2. Laura Löser, autore
                                      3. Simona Stoyanova, autore
                                      4. Charlotte Tupman, autore
                                      5. Tom Elliott, autore
                                      6. Eleonora Litta, traduzione italiana
                                      7. Greta Franzini, correzione traduzione italiana

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro-pt-br.html b/gl/dev/intro-intro-pt-br.html index 2a5583a2e..c3558a0e8 100644 --- a/gl/dev/intro-intro-pt-br.html +++ b/gl/dev/intro-intro-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Como usar as Normas EpiDoc

                                      2023-04-27

                                      EpiDoc é um colaborativo informal, de projetos e pesquisadores que trabalham com documentos fonte antigos em Text Encoding Initiative (TEI) XML, que produz recomendações, ferramentas e boas práticas para o processamento digital e a publicação de tais textos. A página do EpiDoc na web se encontra em http://epidoc.sf.net.

                                      O presente documento, as Normas EpiDoc, é resultado do trabalho contínuo da comunidade EpiDoc ao longo de diversos anos. Ele descreve a forma de codificar as diversas características de documentos epigráficos e em papiro, baseado nos princípios centrais de edição de textos acadêmicos (por exemplo, as chamadasLeiden Conventions para os elementos de transcrição, e modelos de dados como o Electronic Archive of Greek and Latin Epigraphy (EAGLE) para os elementos descritivos e históricos). As normas devem ser utilizadas em conjunto com o EpiDoc Schema, que valida os documentos marcados de acordo com estes princípios, e os EpiDoc Example Stylesheets, que tentam fornecer uma versão básica de cada elemento descrito.

                                      As Normas EpiDoc não tentam dar a explicação completa de como montar um projeto EpiDoc, como gerar um site, construir mecanismos de busca ou outras tarefas tecnológicas necessárias para a publicação de textos codificados online. EstasNormas também não são uma introdução completa à epigrafia ou papirologia; elas são, exclusivamente, um guia para a codificação XML dos elementos de edição de texto de documentos antigos que são mais frequentemente necessários em epigrafia e pesquisas similares.

                                      Apesar de não existir uma convenção única para a estruturação de edições epigráficas ou em papiro, as Normas EpiDoc (e as EpiDoc Stylesheets - Folhas de Estilo EpiDoc) fazem uso de enfoque utilizado pelos modelos de dados utilizados por projetos e colaborações como o Advanced Papyrological Information System (APIS), EAGLE, e Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Como a área de epigrafia, de um modo geral (e epigrafia digital em particular), já possui modelos rigorosos de boas práticas na estruturação de suas edições, nós simplesmente recomendamos a codificação em TEI XML dos mesmos dados e observações que os pesquisadores já consideraram úteis ou essenciais na prática.

                                      As Normas EpiDoc têm a intenção de complementar as Leiden Conventions (a partir de agora chamadas apenas de "Leiden"), que já estão em uso na epigrafia e papirologia por mais de 80 anos e são conhecidas em muitos campos filológicos e documentais. As Normas partem do princípio que Leiden é uma base adequada para as distinções intelectuais registradas em uma edição de texto pré-moderno, e baseiam suas recomendações e exemplos nestas distinções sem requerer as convenções tipográficas e siglas específicas recomendadas nas Leiden. Isto significa que EpiDoc procura registrar com clareza, em XML, intervenções textuais como um suplemento do editor para caracteres perdidos por dano, mas não especifica que tais suplementos devam ser escritos dentro de "colchetes" ("[" e "]") no próprio XML ou em qualquer outro produto derivado. Dito isto, é o comportamento padrão das Folhas Exemplo de Estilo EpiDoc produzir uma renderização em Leiden de textos codificados em EpiDoc. Muitas vezes, é possível registrar distinções em TEI que sejam mais sutis ou mais profundas que em Leiden, e algumas destas possibilidades estão descritas aqui, mas estas Normas não recomendam substituir práticas padrão de epigrafia ou papirologia por estes novos princípios.

                                      As Normas produzidas e recomendadas pela comunidade EpiDoc representam um subconjunto e um refino das TEI Guidelines (Normas TEI), que recomendam a codificação XML de uma ampla variedade corpos de textos literários e históricos. Da mesma forma que EpiDoc é uma especialização para o TEI de objetos e documentos antigos, recomendando apenas aqueles elementos, atributos e objetos de valor para esta subcomunidade específica, as Normas EpiDoc têm a intenção de complementar (de forma alguma substituir) as Normas TEI . As seções de referência e técnicas do TEI, especialmente, permanecem como recursos valiosos para os usuários do EpiDoc, que muitas vezes vão achar úteis as listas de elementos, as explicações de valores de atributos ou de tipos de dados e os exemplos de uso em uma grande variedade de contextos e a extensa descrição em prosa dos elementos de marcação. As Normas EpiDoc recomendam um conjunto bastante restrito de elementos, modelos de conteúdo, atributos e valores TEI, tanto que um arquivo EpiDoc é também um arquivo válido TEI, mas nem todo arquivo TEI é válido para o EpiDoc. Nas áreas onde as Normas EpiDoc são mais restritivas que as TEI, as primeiras devem suplantar as segundas; mas nas situações onde as TEI entram em maiores detalhes ou oferecem um espectro maior de exemplos, deveriam, é claro, ser consultadas e consideradas a fonte canônica para todo o uso EpiDoc.

                                      Estrutura e Características das Normas EpiDoc

                                      Existem diversas vias de entrada para cada página que compõe o corpus das Normas EpiDoc .

                                      • Três índices principais agrupam todas estas páginas dentro das categorias: Transcrição (os elementos relativos a conteúdo, aparência, restauração e interpretação básica do texto em si);Dados de Suporte (incluindo a descrição do objeto ou manuscrito, a história do objeto e de sua descoberta, informação bibliográfica ou outra informação editorial); e Vocabulário e Indexação (termos e características marcadas no texto com o objetivo de controlar ou indexar vocabulário, busca e faceting).
                                      • Diversas seções oferecem listas selecionadas e organizadas de acordo com as categorias geralmente utilizadas pelos usuários de comunidades especializadas (por exemplo, as normas de transcrição epigráfica de Krummrey-Panciera; as características de papirologia como registradas no APIS ). Estas seções estão em desenvolvimento, e devem ser consideradas informativas em vez de normativas. Sugestões de novas seções deste tipo são bem vindas.
                                      • Finalmente, as Normas contém apêndices de suporte, tais como glosário de termos técnicos e especializados, e uma bibliografia de autoridades de epigrafia e papirologia, por exemplo o EpiDoc corpora, e, em termos gerais, de publicação de textos antigos. Um índice para as Normas organizado por elemento TEI mencionado permite aos leitores encontrar todas as características epigráficas que recomendam o uso de um dado elemento.

                                      Páginas individuais nas Normas são organizadas por conceito epigráfico ou papirológico, não por nome de elemento TEI. Desta forma, por exemplo, todas as páginas que lidam com abreviaturas estão agrupadas, (sob a rubrica Intervenções Editoriais), independente de quais elementos TEI são especificados. Cada página das Normas tem uma estrutura regular: primeiro, uma breve explicação do título da página (para a página entitulada ‘Caracteres Não Interpretados’, por exemplo, existe uma explicação “Letras claras, mas incompreensíveis”). O elemento (ou elementos) TEI relevante(s) fica(m) exposto(s) em uma caixa logo abaixo, com um link para a página das Normas TEI para aquele elemento. A seguir, há uma explicação textual das recomendações EpiDoc para o uso daquele(s) elemento(s) TEI, incluindo detalhes dos valores e atributos relevantes.

                                      Abaixo desta explicação geralmente aparecem alguns exemplos de contexto de uso. As Normas, especialmente nos casos de elementos de transcrição, listam renderizações convencionais da publicação em questão de acordo com normas papirológicas ou epigráficas, como a Krummrey-Panciera e o Duke Databank.

                                      Os exemplos de XML mostram a marcação recomendada para os diversos tipos de elemento de transcrição, como por exemplo os diferentes casos de expansão de uma abreviatura que inclui um símbolo. Os exemplos muitas vezes listam várias opções de marcação, dependendo do nível de detalhamento desejado. Abaixo dos exemplos aparece uma série de renderizações (ou uma renderização diferente depois de cada exemplo) que representa os diversos outputs disponíveis nos exemplos das folhas de estilo EpiDoc P5. O output padrão é seguir as convenções Krummrey-Panciera. Outros output incluem o estilo SEG, o estilo London e o estilo DDbDP. Abaixo de cada exemplo existe uma referênca que aponta sua fonte. A maior parte dos exemplos é tirada das Inscrições de Aphrodisias, das Inscrições da Tripolitania Romana e do Duke Databank de Documentos em Papiro.

                                      Treinamento, Ferramentas e Suporte

                                      Estas Normas são, em essência, uma fonte de referência. Para treinamento e suporte mais aprofundado pode haver outros recursos disponíveis. Membros da comunidade EpiDoc coordenam escolas de treinamento ocasionais, algumas vezes patrocinadas por projetos de grande porte (como os diversos workshops ministrados surante o Projeto Inscrições de Aphrodisias, 2004-2008); maiores informações a respeito destes eventos de treinamento podem ser encontradas naPágina de Treinamento na EpiDoc Wiki. Aqueles que iniciaram recentemente tanto o EpiDoc quanto codificação de texto também podem achar útil diversas sessões de treinamento em TEI (algumas encontradas na lista de Eventos TEI).

                                      EpiDoc pode ser ampliado e editado através do uso de qualquer ferramenta padrão de XML (diversas delas estão listadas na página Ferramentas de Edição do TEI Wiki);treinamento básico no uso destas ferramentas é geralmente incluído tanto nos eventos de treinamento em EpiDoc quanto nos de TEI, ou qualquer tutorial de XML. Outras ferramentas para publicação, busca ou quaisquer outros arquivos de processamento de EpiDoc e TEI incluem as linguagens de transformação de XML XSLT and XQuery, plataformas genéricas de busca, como Solr e ferramentas open source específicas de TEI como Kiln e o Papyrological Navigator.

                                      Como sempre, o ponto de partida para obter ajuda a respeito de qualquer tópico que não seja coberto por estas normas deve ser a lista de Marcação.

                                      Responsabilidade por esta seção

                                      1. Gabriel Bodard, autor
                                      2. Laura Löser, autor
                                      3. Simona Stoyanova, autor
                                      4. Charlotte Tupman, autor
                                      5. Tom Elliott, autor
                                      6. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Como usar as Normas EpiDoc

                                      2024-03-05

                                      EpiDoc é um colaborativo informal, de projetos e pesquisadores que trabalham com documentos fonte antigos em Text Encoding Initiative (TEI) XML, que produz recomendações, ferramentas e boas práticas para o processamento digital e a publicação de tais textos. A página do EpiDoc na web se encontra em http://epidoc.sf.net.

                                      O presente documento, as Normas EpiDoc, é resultado do trabalho contínuo da comunidade EpiDoc ao longo de diversos anos. Ele descreve a forma de codificar as diversas características de documentos epigráficos e em papiro, baseado nos princípios centrais de edição de textos acadêmicos (por exemplo, as chamadasLeiden Conventions para os elementos de transcrição, e modelos de dados como o Electronic Archive of Greek and Latin Epigraphy (EAGLE) para os elementos descritivos e históricos). As normas devem ser utilizadas em conjunto com o EpiDoc Schema, que valida os documentos marcados de acordo com estes princípios, e os EpiDoc Example Stylesheets, que tentam fornecer uma versão básica de cada elemento descrito.

                                      As Normas EpiDoc não tentam dar a explicação completa de como montar um projeto EpiDoc, como gerar um site, construir mecanismos de busca ou outras tarefas tecnológicas necessárias para a publicação de textos codificados online. EstasNormas também não são uma introdução completa à epigrafia ou papirologia; elas são, exclusivamente, um guia para a codificação XML dos elementos de edição de texto de documentos antigos que são mais frequentemente necessários em epigrafia e pesquisas similares.

                                      Apesar de não existir uma convenção única para a estruturação de edições epigráficas ou em papiro, as Normas EpiDoc (e as EpiDoc Stylesheets - Folhas de Estilo EpiDoc) fazem uso de enfoque utilizado pelos modelos de dados utilizados por projetos e colaborações como o Advanced Papyrological Information System (APIS), EAGLE, e Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). Como a área de epigrafia, de um modo geral (e epigrafia digital em particular), já possui modelos rigorosos de boas práticas na estruturação de suas edições, nós simplesmente recomendamos a codificação em TEI XML dos mesmos dados e observações que os pesquisadores já consideraram úteis ou essenciais na prática.

                                      As Normas EpiDoc têm a intenção de complementar as Leiden Conventions (a partir de agora chamadas apenas de "Leiden"), que já estão em uso na epigrafia e papirologia por mais de 80 anos e são conhecidas em muitos campos filológicos e documentais. As Normas partem do princípio que Leiden é uma base adequada para as distinções intelectuais registradas em uma edição de texto pré-moderno, e baseiam suas recomendações e exemplos nestas distinções sem requerer as convenções tipográficas e siglas específicas recomendadas nas Leiden. Isto significa que EpiDoc procura registrar com clareza, em XML, intervenções textuais como um suplemento do editor para caracteres perdidos por dano, mas não especifica que tais suplementos devam ser escritos dentro de "colchetes" ("[" e "]") no próprio XML ou em qualquer outro produto derivado. Dito isto, é o comportamento padrão das Folhas Exemplo de Estilo EpiDoc produzir uma renderização em Leiden de textos codificados em EpiDoc. Muitas vezes, é possível registrar distinções em TEI que sejam mais sutis ou mais profundas que em Leiden, e algumas destas possibilidades estão descritas aqui, mas estas Normas não recomendam substituir práticas padrão de epigrafia ou papirologia por estes novos princípios.

                                      As Normas produzidas e recomendadas pela comunidade EpiDoc representam um subconjunto e um refino das TEI Guidelines (Normas TEI), que recomendam a codificação XML de uma ampla variedade corpos de textos literários e históricos. Da mesma forma que EpiDoc é uma especialização para o TEI de objetos e documentos antigos, recomendando apenas aqueles elementos, atributos e objetos de valor para esta subcomunidade específica, as Normas EpiDoc têm a intenção de complementar (de forma alguma substituir) as Normas TEI . As seções de referência e técnicas do TEI, especialmente, permanecem como recursos valiosos para os usuários do EpiDoc, que muitas vezes vão achar úteis as listas de elementos, as explicações de valores de atributos ou de tipos de dados e os exemplos de uso em uma grande variedade de contextos e a extensa descrição em prosa dos elementos de marcação. As Normas EpiDoc recomendam um conjunto bastante restrito de elementos, modelos de conteúdo, atributos e valores TEI, tanto que um arquivo EpiDoc é também um arquivo válido TEI, mas nem todo arquivo TEI é válido para o EpiDoc. Nas áreas onde as Normas EpiDoc são mais restritivas que as TEI, as primeiras devem suplantar as segundas; mas nas situações onde as TEI entram em maiores detalhes ou oferecem um espectro maior de exemplos, deveriam, é claro, ser consultadas e consideradas a fonte canônica para todo o uso EpiDoc.

                                      Estrutura e Características das Normas EpiDoc

                                      Existem diversas vias de entrada para cada página que compõe o corpus das Normas EpiDoc .

                                      • Três índices principais agrupam todas estas páginas dentro das categorias: Transcrição (os elementos relativos a conteúdo, aparência, restauração e interpretação básica do texto em si);Dados de Suporte (incluindo a descrição do objeto ou manuscrito, a história do objeto e de sua descoberta, informação bibliográfica ou outra informação editorial); e Vocabulário e Indexação (termos e características marcadas no texto com o objetivo de controlar ou indexar vocabulário, busca e faceting).
                                      • Diversas seções oferecem listas selecionadas e organizadas de acordo com as categorias geralmente utilizadas pelos usuários de comunidades especializadas (por exemplo, as normas de transcrição epigráfica de Krummrey-Panciera; as características de papirologia como registradas no APIS ). Estas seções estão em desenvolvimento, e devem ser consideradas informativas em vez de normativas. Sugestões de novas seções deste tipo são bem vindas.
                                      • Finalmente, as Normas contém apêndices de suporte, tais como glosário de termos técnicos e especializados, e uma bibliografia de autoridades de epigrafia e papirologia, por exemplo o EpiDoc corpora, e, em termos gerais, de publicação de textos antigos. Um índice para as Normas organizado por elemento TEI mencionado permite aos leitores encontrar todas as características epigráficas que recomendam o uso de um dado elemento.

                                      Páginas individuais nas Normas são organizadas por conceito epigráfico ou papirológico, não por nome de elemento TEI. Desta forma, por exemplo, todas as páginas que lidam com abreviaturas estão agrupadas, (sob a rubrica Intervenções Editoriais), independente de quais elementos TEI são especificados. Cada página das Normas tem uma estrutura regular: primeiro, uma breve explicação do título da página (para a página entitulada ‘Caracteres Não Interpretados’, por exemplo, existe uma explicação “Letras claras, mas incompreensíveis”). O elemento (ou elementos) TEI relevante(s) fica(m) exposto(s) em uma caixa logo abaixo, com um link para a página das Normas TEI para aquele elemento. A seguir, há uma explicação textual das recomendações EpiDoc para o uso daquele(s) elemento(s) TEI, incluindo detalhes dos valores e atributos relevantes.

                                      Abaixo desta explicação geralmente aparecem alguns exemplos de contexto de uso. As Normas, especialmente nos casos de elementos de transcrição, listam renderizações convencionais da publicação em questão de acordo com normas papirológicas ou epigráficas, como a Krummrey-Panciera e o Duke Databank.

                                      Os exemplos de XML mostram a marcação recomendada para os diversos tipos de elemento de transcrição, como por exemplo os diferentes casos de expansão de uma abreviatura que inclui um símbolo. Os exemplos muitas vezes listam várias opções de marcação, dependendo do nível de detalhamento desejado. Abaixo dos exemplos aparece uma série de renderizações (ou uma renderização diferente depois de cada exemplo) que representa os diversos outputs disponíveis nos exemplos das folhas de estilo EpiDoc P5. O output padrão é seguir as convenções Krummrey-Panciera. Outros output incluem o estilo SEG, o estilo London e o estilo DDbDP. Abaixo de cada exemplo existe uma referênca que aponta sua fonte. A maior parte dos exemplos é tirada das Inscrições de Aphrodisias, das Inscrições da Tripolitania Romana e do Duke Databank de Documentos em Papiro.

                                      Treinamento, Ferramentas e Suporte

                                      Estas Normas são, em essência, uma fonte de referência. Para treinamento e suporte mais aprofundado pode haver outros recursos disponíveis. Membros da comunidade EpiDoc coordenam escolas de treinamento ocasionais, algumas vezes patrocinadas por projetos de grande porte (como os diversos workshops ministrados surante o Projeto Inscrições de Aphrodisias, 2004-2008); maiores informações a respeito destes eventos de treinamento podem ser encontradas naPágina de Treinamento na EpiDoc Wiki. Aqueles que iniciaram recentemente tanto o EpiDoc quanto codificação de texto também podem achar útil diversas sessões de treinamento em TEI (algumas encontradas na lista de Eventos TEI).

                                      EpiDoc pode ser ampliado e editado através do uso de qualquer ferramenta padrão de XML (diversas delas estão listadas na página Ferramentas de Edição do TEI Wiki);treinamento básico no uso destas ferramentas é geralmente incluído tanto nos eventos de treinamento em EpiDoc quanto nos de TEI, ou qualquer tutorial de XML. Outras ferramentas para publicação, busca ou quaisquer outros arquivos de processamento de EpiDoc e TEI incluem as linguagens de transformação de XML XSLT and XQuery, plataformas genéricas de busca, como Solr e ferramentas open source específicas de TEI como Kiln e o Papyrological Navigator.

                                      Como sempre, o ponto de partida para obter ajuda a respeito de qualquer tópico que não seja coberto por estas normas deve ser a lista de Marcação.

                                      Responsabilidade por esta seção

                                      1. Gabriel Bodard, autor
                                      2. Laura Löser, autor
                                      3. Simona Stoyanova, autor
                                      4. Charlotte Tupman, autor
                                      5. Tom Elliott, autor
                                      6. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/intro-intro.html b/gl/dev/intro-intro.html index 2af0abd2f..107a17c08 100644 --- a/gl/dev/intro-intro.html +++ b/gl/dev/intro-intro.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      How to Use the EpiDoc Guidelines

                                      2023-04-27

                                      EpiDoc is a loose collaborative of projects and scholars working with ancient source documents in Text Encoding Initiative (TEI) XML, and devising recommendations, tools, and good practice for the digital encoding, processing and publishing of such texts. EpiDoc's home page on the web may be found at http://epidoc.sf.net.

                                      The present document (the EpiDoc Guidelines) is the on-going product of the EpiDoc community's work over several years. It describes how to encode the various features of epigraphic and papyrological documents, based on the core principles of scholarly text editing (e.g. the so-called Leiden Conventions for transcriptional features, and data models such as Electronic Archive of Greek and Latin Epigraphy (EAGLE) for descriptive and historical elements). The Guidelines should be used in conjunction with the EpiDoc Schema, against which documents marked up according to these principles should validate, and the EpiDoc Example Stylesheets, which attempt to provide a basic rendering for each feature described.

                                      The EpiDoc Guidelines cannot undertake to give full explanation of how to set up an EpiDoc project, generate a website, build search tools, or other technical or collaborative tasks required for the publication of encoded texts online. Neither are the Guidelines a full introduction to epigraphy or papyrology; they are exclusively a guide to the XML encoding of the features of an ancient documentary text edition that are most often needed in epigraphic and similar scholarship.

                                      Although there is no single convention for the structure of an epigraphic or papyrological edition, the EpiDoc Guidelines (and the EpiDoc Stylesheets) take an approach that is in accord with the data models employed by projects and collaborations like the Advanced Papyrological Information System (APIS), EAGLE, and Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). As the discipline of epigraphy in general, and digital epigraphy in particular, already have rigorous models of good practice in structuring editions, we merely recommend the encoding in TEI XML of the same data and observations that scholars have already found essential or useful in practice.

                                      The EpiDoc Guidelines are intended to complement the Leiden Conventions (hereafter "Leiden"), which have been in use in epigraphy and papyrology for over 80 years and are understood in many philological and documentary fields. The Guidelines assume that Leiden is an adequate basis for the intellectual distinctions recorded in an edition of a pre-modern text, and base their recommendations and examples upon these distinctions without requiring the specific typographical conventions and sigla recommended therein. That is, EpiDoc seeks clearly to record in XML such textual interventions as an editor's supplement for characters wholly lost to damage, but does not specify that such supplements must be rendered within "square brackets" ("[" and "]") in the XML itself or in any downstream output. That said, it is the default behaviour of the EpiDoc Example Stylesheets to produce a Leiden rendering of EpiDoc-encoded texts. It is often possible for TEI to record distinctions that are finer or deeper than Leiden, and some such possibilities are described herein, but these Guidelines do not recommend replacing standard epigraphic or papyrological practice with such new principles.

                                      The Guidelines produced and recommended by the EpiDoc community represent a subset of and refinement to the TEI Guidelines, which recommend the XML encoding of a wide range of literary and historical texts and linguistic corpora. Just as EpiDoc is a specialization of the TEI for ancient documents and objects, recommending only those elements, attributes and objects of value for this specific sub-community, the EpiDoc Guidelines are intended to supplement (and by no means replace) the TEI Guidelines. Especially the reference and technical sections of the TEI remain an invaluable resource for users of EpiDoc, who will often find lists of elements, explanations of attribute values or data types, examples of usage in a wide range of contexts and extensive prose descriptions of markup features useful. The EpiDoc Guidelines recommend a rather restricted set of TEI elements, content models, attributes and values, such that an EpiDoc file is always also a valid TEI file, but not every TEI file is valid EpiDoc. Where the EpiDoc Guidelines are more restrictive than the TEI, the former should be considered to supercede the latter; but where the TEI goes into more detail, or offers a more useful range of examples, it should of course be consulted and considered the canonical source for all EpiDoc usage.

                                      Structure and Features of the EpiDoc Guidelines

                                      There are several pathways into the individual pages that make up the body of the EpiDoc Guidelines.

                                      • Three main tables of contents collect together all of these pages under the categories: Transcription (those features relating to the content, appearance, restoration and basic interpretation of the text itself); Supporting Data (including the description of the object or manuscript, the history of the object and its discovery, bibliographical and other editorial information); and Vocabulary and Indexing (terms and features tagged in the text for purpose of vocabulary control or indexing, searching and faceting).
                                      • Several sections offer organized and selected lists of guidance pages according to the categories generally followed by users of specialized communities (for example, the epigraphic transcription guidelines of Krummrey-Panciera; the papyrological features as recorded by the APIS database). These sections are under construction, and should be considered informational rather than normative. Suggestions of new sections of this kind are welcome.
                                      • Finally the Guidelines contain supporting appendices, such as the glossary of technical and specialized terms, and a bibliography of epigraphic and papyrological authorities, example EpiDoc corpora, and on digital publication of ancient texts generally. An index to the Guidelines by TEI elements mentioned allows readers to find all epigraphic features in which a given element is part of the recommended usage.

                                      Individual pages in the Guidelines are organised by epigraphic or papyrological concept, rather than by TEI element name. So, for instance, all pages involving abbreviations are grouped together (under the Editorial Interventions rubric), regardless of what TEI elements are specified. Each Guidelines page has a regular structure: first, a brief explanation of the title of a page (e.g., for the page entitled ‘Uninterpreted Characters’, there is an explanation “Clear but incomprehensible letters”). The relevant TEI element (or elements) are displayed in a box underneath, including a link to the TEI Guidelines page for that element. There then follows a prose explanation of the EpiDoc recommendations for the use of those TEI elements, including details of relevant attributes and values.

                                      Below this explanation there are usually a few examples of the usage in context. Especially in the case of transcriptional features, the Guidelines will list conventional renderings of the issue in question according to common epigraphic or papyrological transcription guidelines, such as Krummrey-Panciera and the Duke Databank.

                                      The XML examples show the recommended markup for the various types of each transcriptional feature, e. g. different cases of expansion of an abbreviation which includes a symbol. The examples often list several markup options depending on the level of detail desired. Below the examples there is a series of renderings (or a different rendering after each example) which represent the several outputs available in the example EpiDoc P5 stylesheets. The default output is following the Krummrey-Panciera conventions. The others include the SEG style, the London style and the DDbDP style. Below each example there is a reference pointing to its source. Most of the examples are taken from the Inscriptions of Aphrodisias, the Inscriptions of Roman Tripolitania and the Duke Databank of Documentary Papyri.

                                      Training, Tools, and Support

                                      These Guidelines are in essence a reference source. For more in-depth training or support, other resources might be available. Members of the EpiDoc community run occasional training schools, sometimes funded by major projects (such as the several workshops run during the Inscriptions of Aphrodisias Project, 2004-2008); more information on these training events can be found on the Training page in the EpiDoc Wiki. Those new to EpiDoc and text encoding might also find general training sessions on TEI (some listed in TEI Events list) useful.

                                      EpiDoc can be authored and edited using any standard tool for XML (several of which are listed on the Editing Tools page of the TEI wiki); basic training in the use of such tools is usually included in both EpiDoc and TEI training events, or any XML tutorial. Other tools for publishing, searching and otherwise processing EpiDoc and TEI files include the XML transformation languages XSLT and XQuery, and general searching platforms such as Solr and TEI-specific open source tools like Kiln and the Papyrological Navigator.

                                      As always, the first port of call for help with any topic not covered by these guidelines should be the Markup list.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Laura Löser, author
                                      3. Simona Stoyanova, author
                                      4. Charlotte Tupman, author
                                      5. Tom Elliott, author

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      How to Use the EpiDoc Guidelines

                                      2024-03-05

                                      EpiDoc is a loose collaborative of projects and scholars working with ancient source documents in Text Encoding Initiative (TEI) XML, and devising recommendations, tools, and good practice for the digital encoding, processing and publishing of such texts. EpiDoc's home page on the web may be found at http://epidoc.sf.net.

                                      The present document (the EpiDoc Guidelines) is the on-going product of the EpiDoc community's work over several years. It describes how to encode the various features of epigraphic and papyrological documents, based on the core principles of scholarly text editing (e.g. the so-called Leiden Conventions for transcriptional features, and data models such as Electronic Archive of Greek and Latin Epigraphy (EAGLE) for descriptive and historical elements). The Guidelines should be used in conjunction with the EpiDoc Schema, against which documents marked up according to these principles should validate, and the EpiDoc Example Stylesheets, which attempt to provide a basic rendering for each feature described.

                                      The EpiDoc Guidelines cannot undertake to give full explanation of how to set up an EpiDoc project, generate a website, build search tools, or other technical or collaborative tasks required for the publication of encoded texts online. Neither are the Guidelines a full introduction to epigraphy or papyrology; they are exclusively a guide to the XML encoding of the features of an ancient documentary text edition that are most often needed in epigraphic and similar scholarship.

                                      Although there is no single convention for the structure of an epigraphic or papyrological edition, the EpiDoc Guidelines (and the EpiDoc Stylesheets) take an approach that is in accord with the data models employed by projects and collaborations like the Advanced Papyrological Information System (APIS), EAGLE, and Programme d’enregistrement, de traitement et de recherche automatique en épigraphie (PETRAE). As the discipline of epigraphy in general, and digital epigraphy in particular, already have rigorous models of good practice in structuring editions, we merely recommend the encoding in TEI XML of the same data and observations that scholars have already found essential or useful in practice.

                                      The EpiDoc Guidelines are intended to complement the Leiden Conventions (hereafter "Leiden"), which have been in use in epigraphy and papyrology for over 80 years and are understood in many philological and documentary fields. The Guidelines assume that Leiden is an adequate basis for the intellectual distinctions recorded in an edition of a pre-modern text, and base their recommendations and examples upon these distinctions without requiring the specific typographical conventions and sigla recommended therein. That is, EpiDoc seeks clearly to record in XML such textual interventions as an editor's supplement for characters wholly lost to damage, but does not specify that such supplements must be rendered within "square brackets" ("[" and "]") in the XML itself or in any downstream output. That said, it is the default behaviour of the EpiDoc Example Stylesheets to produce a Leiden rendering of EpiDoc-encoded texts. It is often possible for TEI to record distinctions that are finer or deeper than Leiden, and some such possibilities are described herein, but these Guidelines do not recommend replacing standard epigraphic or papyrological practice with such new principles.

                                      The Guidelines produced and recommended by the EpiDoc community represent a subset of and refinement to the TEI Guidelines, which recommend the XML encoding of a wide range of literary and historical texts and linguistic corpora. Just as EpiDoc is a specialization of the TEI for ancient documents and objects, recommending only those elements, attributes and objects of value for this specific sub-community, the EpiDoc Guidelines are intended to supplement (and by no means replace) the TEI Guidelines. Especially the reference and technical sections of the TEI remain an invaluable resource for users of EpiDoc, who will often find lists of elements, explanations of attribute values or data types, examples of usage in a wide range of contexts and extensive prose descriptions of markup features useful. The EpiDoc Guidelines recommend a rather restricted set of TEI elements, content models, attributes and values, such that an EpiDoc file is always also a valid TEI file, but not every TEI file is valid EpiDoc. Where the EpiDoc Guidelines are more restrictive than the TEI, the former should be considered to supercede the latter; but where the TEI goes into more detail, or offers a more useful range of examples, it should of course be consulted and considered the canonical source for all EpiDoc usage.

                                      Structure and Features of the EpiDoc Guidelines

                                      There are several pathways into the individual pages that make up the body of the EpiDoc Guidelines.

                                      • Three main tables of contents collect together all of these pages under the categories: Transcription (those features relating to the content, appearance, restoration and basic interpretation of the text itself); Supporting Data (including the description of the object or manuscript, the history of the object and its discovery, bibliographical and other editorial information); and Vocabulary and Indexing (terms and features tagged in the text for purpose of vocabulary control or indexing, searching and faceting).
                                      • Several sections offer organized and selected lists of guidance pages according to the categories generally followed by users of specialized communities (for example, the epigraphic transcription guidelines of Krummrey-Panciera; the papyrological features as recorded by the APIS database). These sections are under construction, and should be considered informational rather than normative. Suggestions of new sections of this kind are welcome.
                                      • Finally the Guidelines contain supporting appendices, such as the glossary of technical and specialized terms, and a bibliography of epigraphic and papyrological authorities, example EpiDoc corpora, and on digital publication of ancient texts generally. An index to the Guidelines by TEI elements mentioned allows readers to find all epigraphic features in which a given element is part of the recommended usage.

                                      Individual pages in the Guidelines are organised by epigraphic or papyrological concept, rather than by TEI element name. So, for instance, all pages involving abbreviations are grouped together (under the Editorial Interventions rubric), regardless of what TEI elements are specified. Each Guidelines page has a regular structure: first, a brief explanation of the title of a page (e.g., for the page entitled ‘Uninterpreted Characters’, there is an explanation “Clear but incomprehensible letters”). The relevant TEI element (or elements) are displayed in a box underneath, including a link to the TEI Guidelines page for that element. There then follows a prose explanation of the EpiDoc recommendations for the use of those TEI elements, including details of relevant attributes and values.

                                      Below this explanation there are usually a few examples of the usage in context. Especially in the case of transcriptional features, the Guidelines will list conventional renderings of the issue in question according to common epigraphic or papyrological transcription guidelines, such as Krummrey-Panciera and the Duke Databank.

                                      The XML examples show the recommended markup for the various types of each transcriptional feature, e. g. different cases of expansion of an abbreviation which includes a symbol. The examples often list several markup options depending on the level of detail desired. Below the examples there is a series of renderings (or a different rendering after each example) which represent the several outputs available in the example EpiDoc P5 stylesheets. The default output is following the Krummrey-Panciera conventions. The others include the SEG style, the London style and the DDbDP style. Below each example there is a reference pointing to its source. Most of the examples are taken from the Inscriptions of Aphrodisias, the Inscriptions of Roman Tripolitania and the Duke Databank of Documentary Papyri.

                                      Training, Tools, and Support

                                      These Guidelines are in essence a reference source. For more in-depth training or support, other resources might be available. Members of the EpiDoc community run occasional training schools, sometimes funded by major projects (such as the several workshops run during the Inscriptions of Aphrodisias Project, 2004-2008); more information on these training events can be found on the Training page in the EpiDoc Wiki. Those new to EpiDoc and text encoding might also find general training sessions on TEI (some listed in TEI Events list) useful.

                                      EpiDoc can be authored and edited using any standard tool for XML (several of which are listed on the Editing Tools page of the TEI wiki); basic training in the use of such tools is usually included in both EpiDoc and TEI training events, or any XML tutorial. Other tools for publishing, searching and otherwise processing EpiDoc and TEI files include the XML transformation languages XSLT and XQuery, and general searching platforms such as Solr and TEI-specific open source tools like Kiln and the Papyrological Navigator.

                                      As always, the first port of call for help with any topic not covered by these guidelines should be the Markup list.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Laura Löser, author
                                      3. Simona Stoyanova, author
                                      4. Charlotte Tupman, author
                                      5. Tom Elliott, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-TEI.html b/gl/dev/ref-TEI.html index d5b858a17..0cf093014 100644 --- a/gl/dev/ref-TEI.html +++ b/gl/dev/ref-TEI.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <TEI>

                                      <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or teiCorpus) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      versionspecifies the version number of the TEI Guidelines against which this document is valid.
                                      Status Optional
                                      Datatype teidata.version
                                      Note

                                      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 releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      header: teiHeader
                                      linking: standOff
                                      textstructure: TEI text
                                      Note

                                      This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

                                      Example
                                      <TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                        <fileDesc>
                                         <titleStmt>
                                          <title>The shortest TEI Document Imaginable</title>
                                         </titleStmt>
                                         <publicationStmt>
                                          <p>First published as part of TEI P2, this is the P5
                                               version using a namespace.</p>
                                         </publicationStmt>
                                         <sourceDesc>
                                          <p>No source: this is an original work.</p>
                                         </sourceDesc>
                                        </fileDesc>
                                       </teiHeader>
                                       <text>
                                        <body>
                                         <p>This is about the shortest TEI document imaginable.</p>
                                        </body>
                                       </text>
                                      </TEI>
                                      Example
                                      <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                        <fileDesc>
                                         <titleStmt>
                                          <title>A TEI Document containing four page images </title>
                                         </titleStmt>
                                         <publicationStmt>
                                          <p>Unpublished demonstration file.</p>
                                         </publicationStmt>
                                         <sourceDesc>
                                          <p>No source: this is an original work.</p>
                                         </sourceDesc>
                                        </fileDesc>
                                       </teiHeader>
                                       <facsimile>
                                        <graphic url="page1.png"/>
                                        <graphic url="page2.png"/>
                                        <graphic url="page3.png"/>
                                        <graphic url="page4.png"/>
                                       </facsimile>
                                      </TEI>
                                      Schematron

                                      <sch:ns prefix="tei"
                                       uri="http://www.tei-c.org/ns/1.0"/>

                                      <sch:ns prefix="xs"
                                       uri="http://www.w3.org/2001/XMLSchema"/>
                                      Schematron

                                      <sch:ns prefix="rng"
                                       uri="http://relaxng.org/ns/structure/1.0"/>

                                      <sch:ns prefix="rna"
                                       uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="teiHeader"/>
                                        <alternate>
                                         <sequence>
                                          <classRef key="model.resource"
                                           minOccurs="1maxOccurs="unbounded"/>

                                          <elementRef key="TEIminOccurs="0"
                                           maxOccurs="unbounded"/>

                                         </sequence>
                                         <elementRef key="TEIminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <TEI>

                                      <TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or teiCorpus) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      versionspecifies the version number of the TEI Guidelines against which this document is valid.
                                      Status Optional
                                      Datatype teidata.version
                                      Note

                                      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 releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      header: teiHeader
                                      linking: standOff
                                      textstructure: TEI text
                                      Note

                                      This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

                                      Example
                                      <TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                        <fileDesc>
                                         <titleStmt>
                                          <title>The shortest TEI Document Imaginable</title>
                                         </titleStmt>
                                         <publicationStmt>
                                          <p>First published as part of TEI P2, this is the P5
                                               version using a namespace.</p>
                                         </publicationStmt>
                                         <sourceDesc>
                                          <p>No source: this is an original work.</p>
                                         </sourceDesc>
                                        </fileDesc>
                                       </teiHeader>
                                       <text>
                                        <body>
                                         <p>This is about the shortest TEI document imaginable.</p>
                                        </body>
                                       </text>
                                      </TEI>
                                      Example
                                      <TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                        <fileDesc>
                                         <titleStmt>
                                          <title>A TEI Document containing four page images </title>
                                         </titleStmt>
                                         <publicationStmt>
                                          <p>Unpublished demonstration file.</p>
                                         </publicationStmt>
                                         <sourceDesc>
                                          <p>No source: this is an original work.</p>
                                         </sourceDesc>
                                        </fileDesc>
                                       </teiHeader>
                                       <facsimile>
                                        <graphic url="page1.png"/>
                                        <graphic url="page2.png"/>
                                        <graphic url="page3.png"/>
                                        <graphic url="page4.png"/>
                                       </facsimile>
                                      </TEI>
                                      Schematron

                                      <sch:ns prefix="tei"
                                       uri="http://www.tei-c.org/ns/1.0"/>

                                      <sch:ns prefix="xs"
                                       uri="http://www.w3.org/2001/XMLSchema"/>
                                      Schematron

                                      <sch:ns prefix="rng"
                                       uri="http://relaxng.org/ns/structure/1.0"/>

                                      <sch:ns prefix="rna"
                                       uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="teiHeader"/>
                                        <alternate>
                                         <sequence>
                                          <classRef key="model.resource"
                                           minOccurs="1maxOccurs="unbounded"/>

                                          <elementRef key="TEIminOccurs="0"
                                           maxOccurs="unbounded"/>

                                         </sequence>
                                         <elementRef key="TEIminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element TEI
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          attribute version { teidata.version }?,
                                          ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-ab.html b/gl/dev/ref-ab.html index 296de9373..2065f0444 100644 --- a/gl/dev/ref-ab.html +++ b/gl/dev/ref-ab.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <ab>

                                      <ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [16.3. Blocks, Segments, and Anchors]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declaring (@decls) att.fragmentable (@part) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      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.

                                      Example
                                      <div type="bookn="Genesis">
                                       <div type="chaptern="1">
                                        <ab>In the beginning God created the heaven and the earth.</ab>
                                        <ab>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.</ab>
                                        <ab>And God said, Let there be light: and there was light.</ab>
                                      <!-- ...-->
                                       </div>
                                      </div>
                                      Schematron

                                      <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText +

                                      <ab>

                                      <ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [16.3. Blocks, Segments, and Anchors]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declaring (@decls) att.fragmentable (@part) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      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.

                                      Example
                                      <div type="bookn="Genesis">
                                       <div type="chaptern="1">
                                        <ab>In the beginning God created the heaven and the earth.</ab>
                                        <ab>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.</ab>
                                        <ab>And God said, Let there be light: and there was light.</ab>
                                      <!-- ...-->
                                       </div>
                                      </div>
                                      Schematron

                                      <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText |parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab, unless ab is a child of figure or note, or is a descendant of floatingText.
                                      </sch:report>
                                      Content model
                                      <content>
                                       <macroRef key="macro.abContent"/>
                                      </content>
                                      Schema Declaration
                                       element ab
                                       {
                                      @@ -31,4 +31,4 @@
                                          tei_att.fragmentable.attributes,
                                          tei_att.written.attributes,
                                          tei_macro.abContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-abbr.html b/gl/dev/ref-abbr.html index 7146967c2..e1dcab7be 100644 --- a/gl/dev/ref-abbr.html +++ b/gl/dev/ref-abbr.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <abbr>

                                      <abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      type(type) allows the encoder to classify the abbreviation according to some convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      suspension
                                      (suspension) the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
                                      contraction
                                      (contraction) the abbreviation omits some letter(s) in the middle.
                                      brevigraph
                                      the abbreviation comprises a special symbol or mark.
                                      superscription
                                      (superscription) the abbreviation includes writing above the line.
                                      acronym
                                      (acronym) the abbreviation comprises the initial letters of the words of a phrase.
                                      title
                                      (title) the abbreviation is for a title of address (Dr, Ms, Mr, …)
                                      organization
                                      (organization) the abbreviation is for the name of an organization.
                                      geographic
                                      (geographic) the abbreviation is for a geographic name.
                                      Note

                                      The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      If abbreviations are expanded silently, this practice should be documented in the editorialDecl, either with a normalization element or a p.

                                      Example
                                      <choice>
                                       <expan>North Atlantic Treaty Organization</expan>
                                       <abbr cert="low">NorATO</abbr>
                                       <abbr cert="high">NATO</abbr>
                                       <abbr cert="highxml:lang="fr">OTAN</abbr>
                                      </choice>
                                      Example
                                      <choice>
                                       <abbr>SPQR</abbr>
                                       <expan>senatus populusque romanorum</expan>
                                      </choice>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <abbr>

                                      <abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      type(type) allows the encoder to classify the abbreviation according to some convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      suspension
                                      (suspension) the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
                                      contraction
                                      (contraction) the abbreviation omits some letter(s) in the middle.
                                      brevigraph
                                      the abbreviation comprises a special symbol or mark.
                                      superscription
                                      (superscription) the abbreviation includes writing above the line.
                                      acronym
                                      (acronym) the abbreviation comprises the initial letters of the words of a phrase.
                                      title
                                      (title) the abbreviation is for a title of address (Dr, Ms, Mr, …)
                                      organization
                                      (organization) the abbreviation is for the name of an organization.
                                      geographic
                                      (geographic) the abbreviation is for a geographic name.
                                      Note

                                      The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      If abbreviations are expanded silently, this practice should be documented in the editorialDecl, either with a normalization element or a p.

                                      Example
                                      <choice>
                                       <expan>North Atlantic Treaty Organization</expan>
                                       <abbr cert="low">NorATO</abbr>
                                       <abbr cert="high">NATO</abbr>
                                       <abbr cert="highxml:lang="fr">OTAN</abbr>
                                      </choice>
                                      Example
                                      <choice>
                                       <abbr>SPQR</abbr>
                                       <expan>senatus populusque romanorum</expan>
                                      </choice>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element abbr
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attribute.subtype,
                                          attribute type { teidata.enumerated }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-abstract.html b/gl/dev/ref-abstract.html index ccff8d67d..f3938cea8 100644 --- a/gl/dev/ref-abstract.html +++ b/gl/dev/ref-abstract.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <abstract>

                                      <abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Note

                                      This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a div within the front, as it should for a born-digital document.

                                      Example
                                      <profileDesc>
                                       <abstract resp="#LB">
                                        <p>Good database design involves the acquisition and deployment of
                                           skills which have a wider relevance to the educational process. From
                                           a set of more or less instinctive rules of thumb a formal discipline
                                           or "methodology" of database design has evolved. Applying that
                                           methodology can be of great benefit to a very wide range of academic
                                           subjects: it requires fundamental skills of abstraction and
                                           generalisation and it provides a simple mechanism whereby complex
                                           ideas and information structures can be represented and manipulated,
                                           even without the use of a computer. </p>
                                       </abstract>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <classRef key="model.listLike"/>
                                        <elementRef key="listBibl"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <abstract>

                                      <abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Note

                                      This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a div within the front, as it should for a born-digital document.

                                      Example
                                      <profileDesc>
                                       <abstract resp="#LB">
                                        <p>Good database design involves the acquisition and deployment of
                                           skills which have a wider relevance to the educational process. From
                                           a set of more or less instinctive rules of thumb a formal discipline
                                           or "methodology" of database design has evolved. Applying that
                                           methodology can be of great benefit to a very wide range of academic
                                           subjects: it requires fundamental skills of abstraction and
                                           generalisation and it provides a simple mechanism whereby complex
                                           ideas and information structures can be represented and manipulated,
                                           even without the use of a computer. </p>
                                       </abstract>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <classRef key="model.listLike"/>
                                        <elementRef key="listBibl"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element abstract
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike | tei_model.listLike | tei_listBibl )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-accMat.html b/gl/dev/ref-accMat.html index 209a2d276..6a044f2b1 100644 --- a/gl/dev/ref-accMat.html +++ b/gl/dev/ref-accMat.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <accMat>

                                      <accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      Example
                                      <accMat>A copy of a tax form from 1947 is included in the envelope
                                      with the letter. It is not catalogued separately.</accMat>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <accMat>

                                      <accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      Example
                                      <accMat>A copy of a tax form from 1947 is included in the envelope
                                      with the letter. It is not catalogued separately.</accMat>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element accMat
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-acquisition.html b/gl/dev/ref-acquisition.html index 504746574..b369e3dc3 100644 --- a/gl/dev/ref-acquisition.html +++ b/gl/dev/ref-acquisition.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <acquisition>

                                      <acquisition> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      msdescription: history
                                      May contain
                                      Example
                                      <acquisition>Left to the <name type="place">Bodleian</name> by
                                      <name type="person">Richard Rawlinson</name> in 1755.
                                      </acquisition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <acquisition>

                                      <acquisition> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      msdescription: history
                                      May contain
                                      Example
                                      <acquisition>Left to the <name type="place">Bodleian</name> by
                                      <name type="person">Richard Rawlinson</name> in 1755.
                                      </acquisition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element acquisition
                                       {
                                          tei_att.global.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-add.html b/gl/dev/ref-add.html index 7639ea65b..ba8b2591a 100644 --- a/gl/dev/ref-add.html +++ b/gl/dev/ref-add.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <add>

                                      <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      place
                                      Status Optional
                                      Legal values are:
                                      above
                                      content added above the line
                                      below
                                      content added below the line
                                      bottom
                                      content added at bottom of page or monument
                                      inline
                                      content added at the same level of the text, e.g. between existing characters
                                      interlinear
                                      content added between two lines of text
                                      left
                                      content added to left of main text
                                      margin
                                      content added in margin of document, i.e. outside of delineated text area
                                      mixed
                                      content added in more that one location, encoded as a single addition
                                      opposite
                                      content added on facing page/surface
                                      overleaf
                                      content added over the page or on reverse of leaf or surface
                                      overstrike
                                      content added directly over existing text, e.g. as erasure or correction
                                      right
                                      content added to right of main text
                                      top
                                      content added at top of page or monument
                                      unspecified
                                      location of addition not specified or not known
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      In a diplomatic edition attempting to represent an original source, the add element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the corr or supplied element are recommended.

                                      In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of add may be appropriate, dependent on the editorial philosophy of the project.

                                      Example
                                      The story I am
                                      going to relate is true as to its main facts, and as to the
                                      consequences <add place="above">of these facts</add> from which
                                      this tale takes its title.
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <add>

                                      <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      place
                                      Status Optional
                                      Legal values are:
                                      above
                                      content added above the line
                                      below
                                      content added below the line
                                      bottom
                                      content added at bottom of page or monument
                                      inline
                                      content added at the same level of the text, e.g. between existing characters
                                      interlinear
                                      content added between two lines of text
                                      left
                                      content added to left of main text
                                      margin
                                      content added in margin of document, i.e. outside of delineated text area
                                      mixed
                                      content added in more that one location, encoded as a single addition
                                      opposite
                                      content added on facing page/surface
                                      overleaf
                                      content added over the page or on reverse of leaf or surface
                                      overstrike
                                      content added directly over existing text, e.g. as erasure or correction
                                      right
                                      content added to right of main text
                                      top
                                      content added at top of page or monument
                                      unspecified
                                      location of addition not specified or not known
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      In a diplomatic edition attempting to represent an original source, the add element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the corr or supplied element are recommended.

                                      In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of add may be appropriate, dependent on the editorial philosophy of the project.

                                      Example
                                      The story I am
                                      going to relate is true as to its main facts, and as to the
                                      consequences <add place="above">of these facts</add> from which
                                      this tale takes its title.
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element add
                                       {
                                          tei_att.global.attributes,
                                      @@ -46,4 +46,4 @@
                                           | "unspecified"
                                          }?,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-addName.html b/gl/dev/ref-addName.html index 7c2874a66..319f41d8b 100644 --- a/gl/dev/ref-addName.html +++ b/gl/dev/ref-addName.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <addName>

                                      <addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <forename>Frederick</forename>
                                       <addName type="epithet">the Great</addName>
                                       <roleName>Emperor of Prussia</roleName>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <addName>

                                      <addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <forename>Frederick</forename>
                                       <addName type="epithet">the Great</addName>
                                       <roleName>Emperor of Prussia</roleName>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element addName
                                       {
                                          tei_att.global.attributes,
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-addSpan.html b/gl/dev/ref-addSpan.html index f04b11a3e..c2322bdad 100644 --- a/gl/dev/ref-addSpan.html +++ b/gl/dev/ref-addSpan.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <addSpan>

                                      <addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also add). [11.3.1.4. Additions and Deletions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.placement (@place) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      Both the beginning and the end of the added material must be marked; the beginning by the addSpan element itself, the end by the spanTo attribute.

                                      Example
                                      <handNote xml:id="HEOL"
                                       scribe="HelgiÓlafsson"/>

                                      <!-- ... -->
                                      <body>
                                       <div>
                                      <!-- text here -->
                                       </div>
                                       <addSpan n="added_gatheringhand="#HEOL"
                                        spanTo="#P025"/>

                                       <div>
                                      <!-- text of first added poem here -->
                                       </div>
                                       <div>
                                      <!-- text of second added poem here -->
                                       </div>
                                       <div>
                                      <!-- text of third added poem here -->
                                       </div>
                                       <div>
                                      <!-- text of fourth added poem here -->
                                       </div>
                                       <anchor xml:id="P025"/>
                                       <div>
                                      <!-- more text here -->
                                       </div>
                                      </body>
                                      Schematron

                                      <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert>
                                      Schematron

                                      <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <addSpan>

                                      <addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also add). [11.3.1.4. Additions and Deletions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.placement (@place) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      Both the beginning and the end of the added material must be marked; the beginning by the addSpan element itself, the end by the spanTo attribute.

                                      Example
                                      <handNote xml:id="HEOL"
                                       scribe="HelgiÓlafsson"/>

                                      <!-- ... -->
                                      <body>
                                       <div>
                                      <!-- text here -->
                                       </div>
                                       <addSpan n="added_gatheringhand="#HEOL"
                                        spanTo="#P025"/>

                                       <div>
                                      <!-- text of first added poem here -->
                                       </div>
                                       <div>
                                      <!-- text of second added poem here -->
                                       </div>
                                       <div>
                                      <!-- text of third added poem here -->
                                       </div>
                                       <div>
                                      <!-- text of fourth added poem here -->
                                       </div>
                                       <anchor xml:id="P025"/>
                                       <div>
                                      <!-- more text here -->
                                       </div>
                                      </body>
                                      Schematron

                                      <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert>
                                      Schematron

                                      <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element addSpan
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.spanning.attributes,
                                          tei_att.dimensions.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-additional.html b/gl/dev/ref-additional.html index de8f1270e..c0986dd4d 100644 --- a/gl/dev/ref-additional.html +++ b/gl/dev/ref-additional.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <additional>

                                      <additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      core: listBibl
                                      msdescription: adminInfo surrogates
                                      Example
                                      <additional>
                                       <adminInfo>
                                        <recordHist>
                                         <p>
                                      <!-- record history here -->
                                         </p>
                                        </recordHist>
                                        <custodialHist>
                                         <p>
                                      <!-- custodial history here -->
                                         </p>
                                        </custodialHist>
                                       </adminInfo>
                                       <surrogates>
                                        <p>
                                      <!-- information about surrogates here -->
                                        </p>
                                       </surrogates>
                                       <listBibl>
                                        <bibl>
                                      <!-- ... -->
                                        </bibl>
                                      <!-- full bibliography here -->
                                       </listBibl>
                                      </additional>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="adminInfominOccurs="0"/>
                                        <elementRef key="surrogates"
                                         minOccurs="0"/>

                                        <elementRef key="listBiblminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <additional>

                                      <additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      core: listBibl
                                      msdescription: adminInfo surrogates
                                      Example
                                      <additional>
                                       <adminInfo>
                                        <recordHist>
                                         <p>
                                      <!-- record history here -->
                                         </p>
                                        </recordHist>
                                        <custodialHist>
                                         <p>
                                      <!-- custodial history here -->
                                         </p>
                                        </custodialHist>
                                       </adminInfo>
                                       <surrogates>
                                        <p>
                                      <!-- information about surrogates here -->
                                        </p>
                                       </surrogates>
                                       <listBibl>
                                        <bibl>
                                      <!-- ... -->
                                        </bibl>
                                      <!-- full bibliography here -->
                                       </listBibl>
                                      </additional>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="adminInfominOccurs="0"/>
                                        <elementRef key="surrogates"
                                         minOccurs="0"/>

                                        <elementRef key="listBiblminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element additional
                                       {
                                          tei_att.global.attributes,
                                          ( tei_adminInfo?, tei_surrogates?, tei_listBibl? )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-additions.html b/gl/dev/ref-additions.html index 463a2d88c..a4d78235b 100644 --- a/gl/dev/ref-additions.html +++ b/gl/dev/ref-additions.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <additions>

                                      <additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      Example
                                      <additions>
                                       <p>There are several marginalia in this manuscript. Some consist of
                                         single characters and others are figurative. On 8v is to be found a drawing of
                                         a mans head wearing a hat. At times sentences occurs: On 5v:
                                       <q xml:lang="is">Her er skrif andres isslendin</q>,
                                         on 19r: <q xml:lang="is">þeim go</q>,
                                         on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad
                                           batar þad mælgi ok mal</q>,
                                         On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p>
                                      </additions>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element additions { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <additions>

                                      <additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      Example
                                      <additions>
                                       <p>There are several marginalia in this manuscript. Some consist of
                                         single characters and others are figurative. On 8v is to be found a drawing of
                                         a mans head wearing a hat. At times sentences occurs: On 5v:
                                       <q xml:lang="is">Her er skrif andres isslendin</q>,
                                         on 19r: <q xml:lang="is">þeim go</q>,
                                         on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad
                                           batar þad mælgi ok mal</q>,
                                         On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p>
                                      </additions>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element additions { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-addrLine.html b/gl/dev/ref-addrLine.html index c47c3fc7e..20d5a1dd3 100644 --- a/gl/dev/ref-addrLine.html +++ b/gl/dev/ref-addrLine.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <addrLine>

                                      <addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May contain
                                      Note

                                      Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text.

                                      Example
                                      <address>
                                       <addrLine>Computing Center, MC 135</addrLine>
                                       <addrLine>P.O. Box 6998</addrLine>
                                       <addrLine>Chicago, IL</addrLine>
                                       <addrLine>60680 USA</addrLine>
                                      </address>
                                      Example
                                      <addrLine>
                                       <ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
                                      </addrLine>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <addrLine>

                                      <addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May contain
                                      Note

                                      Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text.

                                      Example
                                      <address>
                                       <addrLine>Computing Center, MC 135</addrLine>
                                       <addrLine>P.O. Box 6998</addrLine>
                                       <addrLine>Chicago, IL</addrLine>
                                       <addrLine>60680 USA</addrLine>
                                      </address>
                                      Example
                                      <addrLine>
                                       <ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
                                      </addrLine>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-address.html b/gl/dev/ref-address.html index a56deea9b..dc611e02b 100644 --- a/gl/dev/ref-address.html +++ b/gl/dev/ref-address.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <address>

                                      <address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as street, postCode etc.

                                      Example

                                      Using just the elements defined by the core module, an address could be represented as follows:

                                      <address>
                                       <street>via Marsala 24</street>
                                       <postCode>40126</postCode>
                                       <name>Bologna</name>
                                       <name>Italy</name>
                                      </address>
                                      Example

                                      When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name:

                                      <address>
                                       <street>via Marsala 24</street>
                                       <postCode>40126</postCode>
                                       <settlement>Bologna</settlement>
                                       <country>Italy</country>
                                      </address>
                                      Example
                                      <address>
                                       <addrLine>Computing Center, MC 135</addrLine>
                                       <addrLine>P.O. Box 6998</addrLine>
                                       <addrLine>Chicago, IL 60680</addrLine>
                                       <addrLine>USA</addrLine>
                                      </address>
                                      Example
                                      <address>
                                       <country key="FR"/>
                                       <settlement type="city">Lyon</settlement>
                                       <postCode>69002</postCode>
                                       <district type="arrondissement">IIème</district>
                                       <district type="quartier">Perrache</district>
                                       <street>
                                        <num>30</num>, Cours de Verdun</street>
                                      </address>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.addrPart"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <address>

                                      <address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as street, postCode etc.

                                      Example

                                      Using just the elements defined by the core module, an address could be represented as follows:

                                      <address>
                                       <street>via Marsala 24</street>
                                       <postCode>40126</postCode>
                                       <name>Bologna</name>
                                       <name>Italy</name>
                                      </address>
                                      Example

                                      When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name:

                                      <address>
                                       <street>via Marsala 24</street>
                                       <postCode>40126</postCode>
                                       <settlement>Bologna</settlement>
                                       <country>Italy</country>
                                      </address>
                                      Example
                                      <address>
                                       <addrLine>Computing Center, MC 135</addrLine>
                                       <addrLine>P.O. Box 6998</addrLine>
                                       <addrLine>Chicago, IL 60680</addrLine>
                                       <addrLine>USA</addrLine>
                                      </address>
                                      Example
                                      <address>
                                       <country key="FR"/>
                                       <settlement type="city">Lyon</settlement>
                                       <postCode>69002</postCode>
                                       <district type="arrondissement">IIème</district>
                                       <district type="quartier">Perrache</district>
                                       <street>
                                        <num>30</num>, Cours de Verdun</street>
                                      </address>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.addrPart"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element address
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.global*, ( tei_model.addrPart, tei_model.global* )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-adminInfo.html b/gl/dev/ref-adminInfo.html index 7af895b11..c691e0204 100644 --- a/gl/dev/ref-adminInfo.html +++ b/gl/dev/ref-adminInfo.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <adminInfo>

                                      <adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [10.9.1. Administrative Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: additional
                                      May contain
                                      header: availability
                                      msdescription: custodialHist recordHist
                                      Example
                                      <adminInfo>
                                       <recordHist>
                                        <source>Record created <date>1 Aug 2004</date>
                                        </source>
                                       </recordHist>
                                       <availability>
                                        <p>Until 2015 permission to photocopy some materials from this
                                           collection has been limited at the request of the donor. Please ask repository staff for details
                                           if you are interested in obtaining photocopies from Series 1:
                                           Correspondence.</p>
                                       </availability>
                                       <custodialHist>
                                        <p>Collection donated to the Manuscript Library by the Estate of
                                           Edgar Holden in 1993. Donor number: 1993-034.</p>
                                       </custodialHist>
                                      </adminInfo>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="recordHist"
                                         minOccurs="0"/>

                                        <elementRef key="availability"
                                         minOccurs="0"/>

                                        <elementRef key="custodialHist"
                                         minOccurs="0"/>

                                        <classRef key="model.noteLike"
                                         minOccurs="0"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <adminInfo>

                                      <adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [10.9.1. Administrative Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: additional
                                      May contain
                                      header: availability
                                      msdescription: custodialHist recordHist
                                      Example
                                      <adminInfo>
                                       <recordHist>
                                        <source>Record created <date>1 Aug 2004</date>
                                        </source>
                                       </recordHist>
                                       <availability>
                                        <p>Until 2015 permission to photocopy some materials from this
                                           collection has been limited at the request of the donor. Please ask repository staff for details
                                           if you are interested in obtaining photocopies from Series 1:
                                           Correspondence.</p>
                                       </availability>
                                       <custodialHist>
                                        <p>Collection donated to the Manuscript Library by the Estate of
                                           Edgar Holden in 1993. Donor number: 1993-034.</p>
                                       </custodialHist>
                                      </adminInfo>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="recordHist"
                                         minOccurs="0"/>

                                        <elementRef key="availability"
                                         minOccurs="0"/>

                                        <elementRef key="custodialHist"
                                         minOccurs="0"/>

                                        <classRef key="model.noteLike"
                                         minOccurs="0"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element adminInfo
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                             tei_custodialHist?,
                                             tei_model.noteLike?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-altIdentifier.html b/gl/dev/ref-altIdentifier.html index 718a6bc8c..a5e80e6c2 100644 --- a/gl/dev/ref-altIdentifier.html +++ b/gl/dev/ref-altIdentifier.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <altIdentifier>

                                      <altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      msdescription: msFrag msIdentifier
                                      namesdates: objectIdentifier
                                      May contain
                                      Note

                                      An identifying number of some kind must be supplied if known; if it is not known, this should be stated.

                                      Example
                                      <altIdentifier>
                                       <settlement>San Marino</settlement>
                                       <repository>Huntington Library</repository>
                                       <idno>MS.El.26.C.9</idno>
                                      </altIdentifier>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.placeNamePart"
                                         expand="sequenceOptional"/>

                                        <elementRef key="institution"
                                         minOccurs="0"/>

                                        <elementRef key="repository"
                                         minOccurs="0"/>

                                        <elementRef key="collection"
                                         minOccurs="0"/>

                                        <elementRef key="idno"/>
                                        <elementRef key="noteminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <altIdentifier>

                                      <altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      msdescription: msFrag msIdentifier
                                      namesdates: objectIdentifier
                                      May contain
                                      Note

                                      An identifying number of some kind must be supplied if known; if it is not known, this should be stated.

                                      Example
                                      <altIdentifier>
                                       <settlement>San Marino</settlement>
                                       <repository>Huntington Library</repository>
                                       <idno>MS.El.26.C.9</idno>
                                      </altIdentifier>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.placeNamePart"
                                         expand="sequenceOptional"/>

                                        <elementRef key="institution"
                                         minOccurs="0"/>

                                        <elementRef key="repository"
                                         minOccurs="0"/>

                                        <elementRef key="collection"
                                         minOccurs="0"/>

                                        <elementRef key="idno"/>
                                        <elementRef key="noteminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element altIdentifier
                                       {
                                          tei_att.global.attributes,
                                      @@ -41,4 +41,4 @@
                                             tei_idno,
                                             tei_note?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-am.html b/gl/dev/ref-am.html index 9a10edf7b..096d9e587 100644 --- a/gl/dev/ref-am.html +++ b/gl/dev/ref-am.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <am>

                                      <am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      do you <abbr>Mr<am>.</am>
                                      </abbr> Jones?
                                      Example
                                      <choice>
                                       <abbr>Aug<am>g</am>
                                       </abbr>
                                       <expan>Aug<ex>ustorum duo</ex>
                                       </expan>
                                      </choice>
                                      Example
                                      <abbr>eu<am>
                                        <g ref="#b-er"/>
                                       </am>y</abbr>
                                      <abbr>
                                       <am>
                                        <g ref="#b-per"/>
                                       </am>sone

                                      </abbr> ...
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.pPart.transcriptional"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <am>

                                      <am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      do you <abbr>Mr<am>.</am>
                                      </abbr> Jones?
                                      Example
                                      <choice>
                                       <abbr>Aug<am>g</am>
                                       </abbr>
                                       <expan>Aug<ex>ustorum duo</ex>
                                       </expan>
                                      </choice>
                                      Example
                                      <abbr>eu<am>
                                        <g ref="#b-er"/>
                                       </am>y</abbr>
                                      <abbr>
                                       <am>
                                        <g ref="#b-per"/>
                                       </am>sone

                                      </abbr> ...
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.pPart.transcriptional"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element am
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.editLike.attributes,
                                          ( text | tei_model.gLike | tei_model.pPart.transcriptional )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-analytic.html b/gl/dev/ref-analytic.html index 3b62b7672..f95911378 100644 --- a/gl/dev/ref-analytic.html +++ b/gl/dev/ref-analytic.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <analytic>

                                      <analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      May contain titles and statements of responsibility (author, editor, or other), in any order.

                                      The analytic element may only occur within a biblStruct, where its use is mandatory for the description of an analytic level bibliographic item.

                                      Example
                                      <biblStruct>
                                       <analytic>
                                        <author>Chesnutt, David</author>
                                        <title>Historical Editions in the States</title>
                                       </analytic>
                                       <monogr>
                                        <title level="j">Computers and the Humanities</title>
                                        <imprint>
                                         <date when="1991-12">(December, 1991):</date>
                                        </imprint>
                                        <biblScope>25.6</biblScope>
                                        <biblScope>377–380</biblScope>
                                       </monogr>
                                      </biblStruct>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="author"/>
                                        <elementRef key="editor"/>
                                        <elementRef key="respStmt"/>
                                        <elementRef key="title"/>
                                        <classRef key="model.ptrLike"/>
                                        <elementRef key="date"/>
                                        <elementRef key="textLang"/>
                                        <elementRef key="idno"/>
                                        <elementRef key="availability"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <analytic>

                                      <analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      May contain titles and statements of responsibility (author, editor, or other), in any order.

                                      The analytic element may only occur within a biblStruct, where its use is mandatory for the description of an analytic level bibliographic item.

                                      Example
                                      <biblStruct>
                                       <analytic>
                                        <author>Chesnutt, David</author>
                                        <title>Historical Editions in the States</title>
                                       </analytic>
                                       <monogr>
                                        <title level="j">Computers and the Humanities</title>
                                        <imprint>
                                         <date when="1991-12">(December, 1991):</date>
                                        </imprint>
                                        <biblScope>25.6</biblScope>
                                        <biblScope>377–380</biblScope>
                                       </monogr>
                                      </biblStruct>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="author"/>
                                        <elementRef key="editor"/>
                                        <elementRef key="respStmt"/>
                                        <elementRef key="title"/>
                                        <classRef key="model.ptrLike"/>
                                        <elementRef key="date"/>
                                        <elementRef key="textLang"/>
                                        <elementRef key="idno"/>
                                        <elementRef key="availability"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element analytic
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                           | tei_idno
                                           | tei_availability
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-anchor.html b/gl/dev/ref-anchor.html index 7142f9f3f..898c97557 100644 --- a/gl/dev/ref-anchor.html +++ b/gl/dev/ref-anchor.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <anchor>

                                      <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

                                      Example
                                      <s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
                                      <s>Help me find it.<ptr target="#A234"/>
                                      </s>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      -element anchor { tei_att.global.attributes, tei_att.typed.attributes, empty }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <anchor>

                                      <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

                                      Example
                                      <s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
                                      <s>Help me find it.<ptr target="#A234"/>
                                      </s>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +element anchor { tei_att.global.attributes, tei_att.typed.attributes, empty }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-annotation.html b/gl/dev/ref-annotation.html index 8b3f2f5c2..2b588d371 100644 --- a/gl/dev/ref-annotation.html +++ b/gl/dev/ref-annotation.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <annotation>

                                      <annotation> represents an annotation following the Web Annotation Data Model. [16.10. The standOff Container]
                                      Modulelinking
                                      Attributesatt.global (xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source) att.pointing (target, @targetLang, @evaluate)
                                      xml:id(identifier) provides a unique identifier for the element bearing the attribute.
                                      Derived fromatt.global
                                      Status Required
                                      Datatype ID
                                      targetspecifies the destination of the reference by supplying one or more URI References
                                      Derived fromatt.pointing
                                      Status Required
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      motivation
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Legal values are:
                                      assessing
                                      intent is to assess the target resource in some way, rather than simply make a comment about it
                                      bookmarking
                                      intent is to create a bookmark to the target or part thereof
                                      classifying
                                      intent is to classify the target in some way
                                      commenting
                                      intent is to comment about the target
                                      describing
                                      intent is to describe the target, rather than (for example) comment on it
                                      editing
                                      intent is to request an edit or a change to the target resource
                                      highlighting
                                      intent is to highlight the target resource or a segment thereof
                                      identifying
                                      intent is to assign an identity to the target
                                      linking
                                      intent is to link to a resource related to the target
                                      moderating
                                      intent is to assign some value or quality to the target
                                      questioning
                                      intent is to ask a question about the target
                                      replying
                                      intent is to reply to a previous statement, either an annotation or another resource
                                      tagging
                                      intent is to associate a tag with the target
                                      Note

                                      For further detailed explanation of the suggested values, see the Web Annotation Vocabulary (WAV). The motivations described here map to URIs defined by the WAV and when exported to RDF or JSON-LD must have the URI http://www.w3.org/ns/oa# prepended.

                                      As an RDF vocabulary, WADM permits the definition of new motivations (see Appendix C of the WAV). In TEI, new motivations may be defined in a custom ODD (see section 23.3.1.3). New motivations must also map to URIs defined by an RDF ontology extending the WAV.

                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <annotation xml:id="ann1"
                                       motivation="linkingtarget="#Gallia">

                                      <!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and - https://www.w3.org/TR/annotation-model/#agents -->
                                       <respStmt xml:id="fred">
                                        <resp>creator</resp>
                                        <persName>Fred Editor</persName>
                                       </respStmt>
                                       <revisionDesc>
                                        <change status="created"
                                         when="2020-05-21T13:59:00Zwho="#fred"/>

                                        <change status="modified"
                                         when="2020-05-21T19:48:00Zwho="#fred"/>

                                       </revisionDesc>
                                      <!-- See https://www.w3.org/TR/annotation-model/#rights-information -->
                                       <licence target="http://creativecommons.org/licenses/by/3.0/"/>
                                      <!-- Multiple bodies -->
                                      <!-- Pointers to sections of text in the same document -->
                                       <ptr target="#string-range(c1p1s1,0,6)"/>
                                       <ptr target="#string-range(c1p1s6,19,7)"/>
                                      </annotation>
                                      Example
                                      <annotation xml:id="TheCorrectTitle"
                                       motivation="commentingtarget="#line1">

                                       <note>The correct title of this specification, and the correct full name of XML, is
                                         "Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.
                                         However, the abbreviation "XML" is not only correct but, appearing as it does in the title
                                         of the specification, an official name of the Extensible Markup Language. </note>
                                      </annotation>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="respStmtminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="revisionDesc"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="licenceminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.annotationPart.body"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <annotation>

                                      <annotation> represents an annotation following the Web Annotation Data Model. [16.10. The standOff Container]
                                      Modulelinking
                                      Attributesatt.global (xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source) att.pointing (target, @targetLang, @evaluate)
                                      xml:id(identifier) provides a unique identifier for the element bearing the attribute.
                                      Derived fromatt.global
                                      Status Required
                                      Datatype ID
                                      targetspecifies the destination of the reference by supplying one or more URI References
                                      Derived fromatt.pointing
                                      Status Required
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      motivation
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Legal values are:
                                      assessing
                                      intent is to assess the target resource in some way, rather than simply make a comment about it
                                      bookmarking
                                      intent is to create a bookmark to the target or part thereof
                                      classifying
                                      intent is to classify the target in some way
                                      commenting
                                      intent is to comment about the target
                                      describing
                                      intent is to describe the target, rather than (for example) comment on it
                                      editing
                                      intent is to request an edit or a change to the target resource
                                      highlighting
                                      intent is to highlight the target resource or a segment thereof
                                      identifying
                                      intent is to assign an identity to the target
                                      linking
                                      intent is to link to a resource related to the target
                                      moderating
                                      intent is to assign some value or quality to the target
                                      questioning
                                      intent is to ask a question about the target
                                      replying
                                      intent is to reply to a previous statement, either an annotation or another resource
                                      tagging
                                      intent is to associate a tag with the target
                                      Note

                                      For further detailed explanation of the suggested values, see the Web Annotation Vocabulary (WAV). The motivations described here map to URIs defined by the WAV and when exported to RDF or JSON-LD must have the URI http://www.w3.org/ns/oa# prepended.

                                      As an RDF vocabulary, WADM permits the definition of new motivations (see Appendix C of the WAV). In TEI, new motivations may be defined in a custom ODD (see section 23.3.1.3). New motivations must also map to URIs defined by an RDF ontology extending the WAV.

                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <annotation xml:id="ann1"
                                       motivation="linkingtarget="#Gallia">

                                      <!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and + https://www.w3.org/TR/annotation-model/#agents -->
                                       <respStmt xml:id="fred">
                                        <resp>creator</resp>
                                        <persName>Fred Editor</persName>
                                       </respStmt>
                                       <revisionDesc>
                                        <change status="created"
                                         when="2020-05-21T13:59:00Zwho="#fred"/>

                                        <change status="modified"
                                         when="2020-05-21T19:48:00Zwho="#fred"/>

                                       </revisionDesc>
                                      <!-- See https://www.w3.org/TR/annotation-model/#rights-information -->
                                       <licence target="http://creativecommons.org/licenses/by/3.0/"/>
                                      <!-- Multiple bodies -->
                                      <!-- Pointers to sections of text in the same document -->
                                       <ptr target="#string-range(c1p1s1,0,6)"/>
                                       <ptr target="#string-range(c1p1s6,19,7)"/>
                                      </annotation>
                                      Example
                                      <annotation xml:id="TheCorrectTitle"
                                       motivation="commentingtarget="#line1">

                                       <note>The correct title of this specification, and the correct full name of XML, is
                                         "Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.
                                         However, the abbreviation "XML" is not only correct but, appearing as it does in the title
                                         of the specification, an official name of the Extensible Markup Language. </note>
                                      </annotation>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="respStmtminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="revisionDesc"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="licenceminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.annotationPart.body"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element annotation
                                       {
                                          tei_att.global.attribute.n,
                                      @@ -77,4 +77,4 @@
                                             tei_licence*,
                                             tei_model.annotationPart.body*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-annotationBlock.html b/gl/dev/ref-annotationBlock.html index 3a27eb271..74db6294c 100644 --- a/gl/dev/ref-annotationBlock.html +++ b/gl/dev/ref-annotationBlock.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <annotationBlock>

                                      <annotationBlock> groups together various annotations, e.g. for parallel interpretations of a spoken segment. [8.4.6. Analytic Coding]
                                      Modulespoken
                                      Attributesatt.ascribed (@who) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <annotationBlock who="#SPK1start="#T2"
                                       end="#T3xml:id="ag20">

                                       <u xml:id="u20">
                                        <seg xml:id="seg37type="utterance"
                                         subtype="modeless">

                                         <w xml:id="w46">Yeah</w>
                                        </seg>
                                       </u>
                                      </annotationBlock>
                                      <annotationBlock who="#SPK1start="#T5"
                                       end="#T6xml:id="ag21">

                                       <u xml:id="u21">
                                        <seg xml:id="seg38type="utterance"
                                         subtype="modeless">

                                         <w xml:id="w47">Mhm</w>
                                        </seg>
                                       </u>
                                      </annotationBlock>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="u"/>
                                        <elementRef key="spanGrp"/>
                                        <classRef key="model.global.spoken"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <annotationBlock>

                                      <annotationBlock> groups together various annotations, e.g. for parallel interpretations of a spoken segment. [8.4.6. Analytic Coding]
                                      Modulespoken
                                      Attributesatt.ascribed (@who) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <annotationBlock who="#SPK1start="#T2"
                                       end="#T3xml:id="ag20">

                                       <u xml:id="u20">
                                        <seg xml:id="seg37type="utterance"
                                         subtype="modeless">

                                         <w xml:id="w46">Yeah</w>
                                        </seg>
                                       </u>
                                      </annotationBlock>
                                      <annotationBlock who="#SPK1start="#T5"
                                       end="#T6xml:id="ag21">

                                       <u xml:id="u21">
                                        <seg xml:id="seg38type="utterance"
                                         subtype="modeless">

                                         <w xml:id="w47">Mhm</w>
                                        </seg>
                                       </u>
                                      </annotationBlock>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="u"/>
                                        <elementRef key="spanGrp"/>
                                        <classRef key="model.global.spoken"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element annotationBlock
                                       {
                                          tei_att.ascribed.attributes,
                                          tei_att.timed.attributes,
                                          tei_att.global.attributes,
                                          ( u | spanGrp | tei_model.global.spoken )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-app.html b/gl/dev/ref-app.html index e63de4da2..dd250fb0f 100644 --- a/gl/dev/ref-app.html +++ b/gl/dev/ref-app.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <app>

                                      <app> (apparatus entry) contains one entry in a critical apparatus, with an optional lemma and usually one or more readings or notes on the relevant passage. [12.1.1. The Apparatus Entry]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typeclassifies the variation contained in this element according to some convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      fromidentifies the beginning of the lemma in the base text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      This attribute should be used when either the double-end point method of apparatus markup, or the location-referenced method with a URL rather than canonical reference, are used.

                                      toidentifies the endpoint of the lemma in the base text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      This attribute is only used when the double-end point method of apparatus markup is used, when the encoded apparatus is not embedded in-line in the base-text.

                                      loc(location) indicates the location of the variation, when the location-referenced method of apparatus markup is used.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Note

                                      This attribute is used only when the location-referenced encoding method is used. It supplies a string containing a canonical reference for the passage to which the variation applies.

                                      Member of
                                      Contained by
                                      May contain
                                      textcrit: lem rdg rdgGrp wit
                                      Example
                                      <app>
                                       <lem wit="#El #Hg">Experience</lem>
                                       <rdg wit="#Latype="substantive">Experiment</rdg>
                                       <rdg wit="#Ra2type="substantive">Eryment</rdg>
                                      </app>
                                      Example
                                      <app type="substantive">
                                       <rdgGrp type="subvariants">
                                        <lem wit="#El #Hg">Experience</lem>
                                        <rdg wit="#Ha4">Experiens</rdg>
                                       </rdgGrp>
                                       <rdgGrp type="subvariants">
                                        <lem wit="#Cp #Ld1">Experiment</lem>
                                        <rdg wit="#La">Ex<g ref="#per"/>iment</rdg>
                                       </rdgGrp>
                                       <rdgGrp type="subvariants">
                                        <lem resp="#ed2013">Eriment</lem>
                                        <rdg wit="#Ra2">Eryment</rdg>
                                       </rdgGrp>
                                      </app>
                                      Example
                                      <app loc="1">
                                       <rdg resp="#SEG">TIMΩΔA</rdg>
                                      </app>
                                      Example
                                      <app loc="1-6">
                                       <note>Too badly worn to yield a text</note>
                                      </app>
                                      Example
                                      <choice xml:id="choice3">
                                       <reg>σύμπαντα</reg>
                                       <orig>ΣΙΝΠΑΤΑΝ</orig>
                                      </choice>
                                      <!-- ... -->
                                      <app from="#choice3">
                                       <note>Mommsen's fanciful normalization, reproduced here, has not been accepted by all recent editions</note>
                                      </app>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="lemminOccurs="0"/>
                                        <alternate maxOccurs="unbounded"
                                         minOccurs="0">

                                         <classRef key="model.rdgLike"/>
                                         <classRef key="model.noteLike"/>
                                         <elementRef key="witDetail"/>
                                         <elementRef key="wit"/>
                                         <elementRef key="rdgGrp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <app>

                                      <app> (apparatus entry) contains one entry in a critical apparatus, with an optional lemma and usually one or more readings or notes on the relevant passage. [12.1.1. The Apparatus Entry]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typeclassifies the variation contained in this element according to some convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      fromidentifies the beginning of the lemma in the base text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      This attribute should be used when either the double-end point method of apparatus markup, or the location-referenced method with a URL rather than canonical reference, are used.

                                      toidentifies the endpoint of the lemma in the base text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      This attribute is only used when the double-end point method of apparatus markup is used, when the encoded apparatus is not embedded in-line in the base-text.

                                      loc(location) indicates the location of the variation, when the location-referenced method of apparatus markup is used.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Note

                                      This attribute is used only when the location-referenced encoding method is used. It supplies a string containing a canonical reference for the passage to which the variation applies.

                                      Member of
                                      Contained by
                                      May contain
                                      textcrit: lem rdg rdgGrp wit
                                      Example
                                      <app>
                                       <lem wit="#El #Hg">Experience</lem>
                                       <rdg wit="#Latype="substantive">Experiment</rdg>
                                       <rdg wit="#Ra2type="substantive">Eryment</rdg>
                                      </app>
                                      Example
                                      <app type="substantive">
                                       <rdgGrp type="subvariants">
                                        <lem wit="#El #Hg">Experience</lem>
                                        <rdg wit="#Ha4">Experiens</rdg>
                                       </rdgGrp>
                                       <rdgGrp type="subvariants">
                                        <lem wit="#Cp #Ld1">Experiment</lem>
                                        <rdg wit="#La">Ex<g ref="#per"/>iment</rdg>
                                       </rdgGrp>
                                       <rdgGrp type="subvariants">
                                        <lem resp="#ed2013">Eriment</lem>
                                        <rdg wit="#Ra2">Eryment</rdg>
                                       </rdgGrp>
                                      </app>
                                      Example
                                      <app loc="1">
                                       <rdg resp="#SEG">TIMΩΔA</rdg>
                                      </app>
                                      Example
                                      <app loc="1-6">
                                       <note>Too badly worn to yield a text</note>
                                      </app>
                                      Example
                                      <choice xml:id="choice3">
                                       <reg>σύμπαντα</reg>
                                       <orig>ΣΙΝΠΑΤΑΝ</orig>
                                      </choice>
                                      <!-- ... -->
                                      <app from="#choice3">
                                       <note>Mommsen's fanciful normalization, reproduced here, has not been accepted by all recent editions</note>
                                      </app>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="lemminOccurs="0"/>
                                        <alternate maxOccurs="unbounded"
                                         minOccurs="0">

                                         <classRef key="model.rdgLike"/>
                                         <classRef key="model.noteLike"/>
                                         <elementRef key="witDetail"/>
                                         <elementRef key="wit"/>
                                         <elementRef key="rdgGrp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element app
                                       {
                                          tei_att.global.attributes,
                                      @@ -40,4 +40,4 @@
                                              | tei_rdgGrp
                                             )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-application.html b/gl/dev/ref-application.html index 12f7d67cd..dd9e53a17 100644 --- a/gl/dev/ref-application.html +++ b/gl/dev/ref-application.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <application>

                                      <application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      identsupplies an identifier for the application, independent of its version number or display name.
                                      Status Required
                                      Datatype teidata.name
                                      versionsupplies a version number for the application, independent of its identifier or display name.
                                      Status Required
                                      Datatype teidata.versionNumber
                                      Contained by
                                      May contain
                                      linking: ab
                                      Example
                                      <appInfo>
                                       <application version="1.5"
                                        ident="ImageMarkupTool1notAfter="2006-06-01">

                                        <label>Image Markup Tool</label>
                                        <ptr target="#P1"/>
                                        <ptr target="#P2"/>
                                       </application>
                                      </appInfo>

                                      This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application 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.

                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.labelLike"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.ptrLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <application>

                                      <application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      identsupplies an identifier for the application, independent of its version number or display name.
                                      Status Required
                                      Datatype teidata.name
                                      versionsupplies a version number for the application, independent of its identifier or display name.
                                      Status Required
                                      Datatype teidata.versionNumber
                                      Contained by
                                      May contain
                                      linking: ab
                                      Example
                                      <appInfo>
                                       <application version="1.5"
                                        ident="ImageMarkupTool1notAfter="2006-06-01">

                                        <label>Image Markup Tool</label>
                                        <ptr target="#P1"/>
                                        <ptr target="#P2"/>
                                       </application>
                                      </appInfo>

                                      This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application 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.

                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.labelLike"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.ptrLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element application
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute ident { teidata.name },
                                          attribute version { teidata.versionNumber },
                                          ( tei_model.labelLike+, ( tei_model.ptrLike* | tei_model.pLike* ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.anchoring.html b/gl/dev/ref-att.anchoring.html index 25220c557..d0d1c42a5 100644 --- a/gl/dev/ref-att.anchoring.html +++ b/gl/dev/ref-att.anchoring.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.anchoring

                                      att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
                                      Moduletei
                                      Membersnote noteGrp
                                      Attributes
                                      anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Default true
                                      Note

                                      In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

                                      targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      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 means of the range function of XPointer, as further described in 16.2.4.6. range().

                                      Example
                                      <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
                                      necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
                                      <!-- elsewhere in the document -->
                                      <noteGrp targetEnd="#A55234">
                                       <note xml:lang="en"> Quatuor Tempora, so called dry fast days.
                                       </note>
                                       <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
                                       </note>
                                      </noteGrp>

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.anchoring

                                      att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
                                      Moduletei
                                      Membersnote noteGrp
                                      Attributes
                                      anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Default true
                                      Note

                                      In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

                                      targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      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 means of the range function of XPointer, as further described in 16.2.4.6. range().

                                      Example
                                      <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
                                      necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
                                      <!-- elsewhere in the document -->
                                      <noteGrp targetEnd="#A55234">
                                       <note xml:lang="en"> Quatuor Tempora, so called dry fast days.
                                       </note>
                                       <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
                                       </note>
                                      </noteGrp>

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.ascribed.directed.html b/gl/dev/ref-att.ascribed.directed.html index bc4c80a4c..7655f15e7 100644 --- a/gl/dev/ref-att.ascribed.directed.html +++ b/gl/dev/ref-att.ascribed.directed.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.ascribed.directed

                                      att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
                                      Moduletei
                                      Membersq said sp stage
                                      Attributesatt.ascribed (@who)
                                      toWhomindicates the person, or group of people, to whom a speech act or action is directed.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      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.

                                      <castItem type="role">
                                       <role xml:id="emil">Emilius.</role>
                                      </castItem>
                                      <castItem type="role">
                                       <role xml:id="lov">Lovisa</role>
                                      </castItem>
                                      <castItem type="role">
                                       <role xml:id="serv">A servant</role>
                                      </castItem>
                                      <!-- ... -->
                                      <sp who="#emiltoWhom="#lov">
                                       <speaker>Emil.</speaker>
                                       <l n="1">My love!</l>
                                      </sp>
                                      <sp who="#lovtoWhom="#emil">
                                       <speaker>Lov.</speaker>
                                       <l n="2">I have no Witness of my Noble Birth</l>
                                       <stage who="emiltoWhom="#serv">Pointing to her Woman.</stage>
                                       <l>But that poor helpless wretch——</l>
                                      </sp>
                                      Note

                                      To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.ascribed.directed

                                      att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
                                      Moduletei
                                      Membersq said sp stage
                                      Attributesatt.ascribed (@who)
                                      toWhomindicates the person, or group of people, to whom a speech act or action is directed.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      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.

                                      <castItem type="role">
                                       <role xml:id="emil">Emilius.</role>
                                      </castItem>
                                      <castItem type="role">
                                       <role xml:id="lov">Lovisa</role>
                                      </castItem>
                                      <castItem type="role">
                                       <role xml:id="serv">A servant</role>
                                      </castItem>
                                      <!-- ... -->
                                      <sp who="#emiltoWhom="#lov">
                                       <speaker>Emil.</speaker>
                                       <l n="1">My love!</l>
                                      </sp>
                                      <sp who="#lovtoWhom="#emil">
                                       <speaker>Lov.</speaker>
                                       <l n="2">I have no Witness of my Noble Birth</l>
                                       <stage who="emiltoWhom="#serv">Pointing to her Woman.</stage>
                                       <l>But that poor helpless wretch——</l>
                                      </sp>
                                      Note

                                      To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.ascribed.html b/gl/dev/ref-att.ascribed.html index bb14d9282..173b71fc9 100644 --- a/gl/dev/ref-att.ascribed.html +++ b/gl/dev/ref-att.ascribed.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.ascribed

                                      att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
                                      Moduletei
                                      Membersatt.ascribed.directed [q said sp stage] annotationBlock change
                                      Attributes
                                      whoindicates the person, or group of people, to whom the element content is ascribed.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      In the following example from Hamlet, speeches (sp) in the body of the play are linked to <castItem> elements in the <castList> using the who attribute.

                                      <castItem type="role">
                                       <role xml:id="Barnardo">Bernardo</role>
                                      </castItem>
                                      <castItem type="role">
                                       <role xml:id="Francisco">Francisco</role>
                                       <roleDesc>a soldier</roleDesc>
                                      </castItem>
                                      <!-- ... -->
                                      <sp who="#Barnardo">
                                       <speaker>Bernardo</speaker>
                                       <l n="1">Who's there?</l>
                                      </sp>
                                      <sp who="#Francisco">
                                       <speaker>Francisco</speaker>
                                       <l n="2">Nay, answer me: stand, and unfold yourself.</l>
                                      </sp>
                                      Note

                                      For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified person element.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.ascribed

                                      att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
                                      Moduletei
                                      Membersatt.ascribed.directed [q said sp stage] annotationBlock change
                                      Attributes
                                      whoindicates the person, or group of people, to whom the element content is ascribed.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      In the following example from Hamlet, speeches (sp) in the body of the play are linked to <castItem> elements in the <castList> using the who attribute.

                                      <castItem type="role">
                                       <role xml:id="Barnardo">Bernardo</role>
                                      </castItem>
                                      <castItem type="role">
                                       <role xml:id="Francisco">Francisco</role>
                                       <roleDesc>a soldier</roleDesc>
                                      </castItem>
                                      <!-- ... -->
                                      <sp who="#Barnardo">
                                       <speaker>Bernardo</speaker>
                                       <l n="1">Who's there?</l>
                                      </sp>
                                      <sp who="#Francisco">
                                       <speaker>Francisco</speaker>
                                       <l n="2">Nay, answer me: stand, and unfold yourself.</l>
                                      </sp>
                                      Note

                                      For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified person element.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.breaking.html b/gl/dev/ref-att.breaking.html index d129046ac..93f631765 100644 --- a/gl/dev/ref-att.breaking.html +++ b/gl/dev/ref-att.breaking.html @@ -22,4 +22,4 @@ }); });

                                      att.breaking

                                      att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone -Elements]
                                      Moduletei
                                      Memberscb gb lb milestone pb
                                      Attributes
                                      breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Sample values include
                                      yes
                                      the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
                                      no
                                      the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
                                      maybe
                                      the encoding does not take any position on this issue.

                                      In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.

                                      <ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt .
                                      leodum la<lb break="no"/> ðost ærþan ichim lifes
                                      ƿeȝ rihtne ȝerymde reord be<lb break="no"/>
                                      rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer...
                                      </ab>

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Elements]ModuleteiMemberscb gb lb milestone pbAttributes
                                      breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Sample values include
                                      yes
                                      the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
                                      no
                                      the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
                                      maybe
                                      the encoding does not take any position on this issue.

                                      In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.

                                      <ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt .
                                      leodum la<lb break="no"/> ðost ærþan ichim lifes
                                      ƿeȝ rihtne ȝerymde reord be<lb break="no"/>
                                      rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer...
                                      </ab>

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.cReferencing.html b/gl/dev/ref-att.cReferencing.html index 593849275..07e912fa1 100644 --- a/gl/dev/ref-att.cReferencing.html +++ b/gl/dev/ref-att.cReferencing.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.cReferencing

                                      att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
                                      Moduletei
                                      Membersgloss ptr ref term
                                      Attributes
                                      cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a refsDecl element in the TEI header
                                      Status Optional
                                      Datatype teidata.text
                                      Note

                                      The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) 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.

                                      Currently these Guidelines only provide for a single canonical reference to be encoded on any given ptr element.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.cReferencing

                                      att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
                                      Moduletei
                                      Membersgloss ptr ref term
                                      Attributes
                                      cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a refsDecl element in the TEI header
                                      Status Optional
                                      Datatype teidata.text
                                      Note

                                      The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) 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.

                                      Currently these Guidelines only provide for a single canonical reference to be encoded on any given ptr element.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.canonical.html b/gl/dev/ref-att.canonical.html index f21f26e29..1be7eda3b 100644 --- a/gl/dev/ref-att.canonical.html +++ b/gl/dev/ref-att.canonical.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.canonical

                                      att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
                                      Moduletei
                                      Membersatt.naming [att.personal [addName forename genName name objectName orgName persName placeName roleName surname] author birth bloc collection country death district editor event geogFeat geogName institution offset origPlace pubPlace region repository rs settlement state] authority catDesc correspDesc date distributor docAuthor docTitle funder material meeting object objectType principal publisher relation resp respStmt sponsor term time title unitDecl unitDef
                                      Attributes
                                      keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
                                      Status Optional
                                      Datatype teidata.text
                                      <author>
                                       <name key="name 427308"
                                        type="organisation">
                                      [New Zealand Parliament, Legislative Council]</name>
                                      </author>
                                      <author>
                                       <name key="Hugo, Victor (1802-1885)"
                                        ref="http://www.idref.fr/026927608">
                                      Victor Hugo</name>
                                      </author>
                                      Note

                                      The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

                                      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.

                                      ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      <name ref="http://viaf.org/viaf/109557338"
                                       type="person">
                                      Seamus Heaney</name>
                                      Note

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.canonical

                                      att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
                                      Moduletei
                                      Membersatt.naming [att.personal [addName forename genName name objectName orgName persName placeName roleName surname] author birth bloc collection country death district editor event geogFeat geogName institution offset origPlace pubPlace region repository rs settlement state] authority catDesc correspDesc date distributor docAuthor docTitle funder material meeting object objectType principal publisher relation resp respStmt sponsor term time title unitDecl unitDef
                                      Attributes
                                      keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
                                      Status Optional
                                      Datatype teidata.text
                                      <author>
                                       <name key="name 427308"
                                        type="organisation">
                                      [New Zealand Parliament, Legislative Council]</name>
                                      </author>
                                      <author>
                                       <name key="Hugo, Victor (1802-1885)"
                                        ref="http://www.idref.fr/026927608">
                                      Victor Hugo</name>
                                      </author>
                                      Note

                                      The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

                                      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.

                                      ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      <name ref="http://viaf.org/viaf/109557338"
                                       type="person">
                                      Seamus Heaney</name>
                                      Note

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.citeStructurePart.html b/gl/dev/ref-att.citeStructurePart.html index 26e4e89cb..1d5f2c3ea 100644 --- a/gl/dev/ref-att.citeStructurePart.html +++ b/gl/dev/ref-att.citeStructurePart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.citeStructurePart

                                      att.citeStructurePart provides attributes for selecting particular elements within a document.
                                      Moduleheader
                                      MembersciteData citeStructure
                                      Attributes
                                      use(use) supplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines]. The XPath pattern is relative to the context given in match, which will either be a sibling attribute in the case of <citeStructure> or on the parent <citeStructure> in the case of <citeData>.
                                      Status Required
                                      Datatype teidata.xpath

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.citeStructurePart

                                      att.citeStructurePart provides attributes for selecting particular elements within a document.
                                      Moduleheader
                                      MembersciteData citeStructure
                                      Attributes
                                      use(use) supplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines]. The XPath pattern is relative to the context given in match, which will either be a sibling attribute in the case of <citeStructure> or on the parent <citeStructure> in the case of <citeData>.
                                      Status Required
                                      Datatype teidata.xpath

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.citing.html b/gl/dev/ref-att.citing.html index 3646434ac..39c096c56 100644 --- a/gl/dev/ref-att.citing.html +++ b/gl/dev/ref-att.citing.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.citing

                                      att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
                                      Moduletei
                                      MembersbiblScope citedRange
                                      Attributes
                                      unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      volume
                                      (volume) the element contains a volume number.
                                      issue
                                      the element contains an issue number, or volume and issue numbers.
                                      page
                                      (page) the element contains a page number or page range.
                                      line
                                      the element contains a line number or line range.
                                      chapter
                                      (chapter) the element contains a chapter indication (number and/or title)
                                      part
                                      the element identifies a part of a book or collection.
                                      column
                                      the element identifies a column.
                                      entry
                                      the element identifies an entry number or label in a list of entries.
                                      fromspecifies the starting point of the range of units indicated by the unit attribute.
                                      Status Optional
                                      Datatype teidata.word
                                      tospecifies the end-point of the range of units indicated by the unit attribute.
                                      Status Optional
                                      Datatype teidata.word

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.citing

                                      att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
                                      Moduletei
                                      MembersbiblScope citedRange
                                      Attributes
                                      unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      volume
                                      (volume) the element contains a volume number.
                                      issue
                                      the element contains an issue number, or volume and issue numbers.
                                      page
                                      (page) the element contains a page number or page range.
                                      line
                                      the element contains a line number or line range.
                                      chapter
                                      (chapter) the element contains a chapter indication (number and/or title)
                                      part
                                      the element identifies a part of a book or collection.
                                      column
                                      the element identifies a column.
                                      entry
                                      the element identifies an entry number or label in a list of entries.
                                      fromspecifies the starting point of the range of units indicated by the unit attribute.
                                      Status Optional
                                      Datatype teidata.word
                                      tospecifies the end-point of the range of units indicated by the unit attribute.
                                      Status Optional
                                      Datatype teidata.word

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.coordinated.html b/gl/dev/ref-att.coordinated.html index e9c696942..6110d6a64 100644 --- a/gl/dev/ref-att.coordinated.html +++ b/gl/dev/ref-att.coordinated.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.coordinated

                                      att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
                                      Moduletranscr
                                      Membersline path surface zone
                                      Attributes
                                      startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
                                      Status Optional
                                      Datatype teidata.pointer
                                      ulxgives the x coordinate value for the upper left corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      ulygives the y coordinate value for the upper left corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      lrxgives the x coordinate value for the lower right corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      lrygives the y coordinate value for the lower right corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      pointsidentifies 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.
                                      Status Optional
                                      Datatype 3–∞ occurrences of teidata.point separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.coordinated

                                      att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
                                      Moduletranscr
                                      Membersline path surface zone
                                      Attributes
                                      startindicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
                                      Status Optional
                                      Datatype teidata.pointer
                                      ulxgives the x coordinate value for the upper left corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      ulygives the y coordinate value for the upper left corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      lrxgives the x coordinate value for the lower right corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      lrygives the y coordinate value for the lower right corner of a rectangular space.
                                      Status Optional
                                      Datatype teidata.numeric
                                      pointsidentifies 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.
                                      Status Optional
                                      Datatype 3–∞ occurrences of teidata.point separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.damaged.html b/gl/dev/ref-att.damaged.html index 52c6cc7e9..1953d1791 100644 --- a/gl/dev/ref-att.damaged.html +++ b/gl/dev/ref-att.damaged.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.damaged

                                      att.damaged provides attributes describing the nature of any physical damage affecting a reading. [11.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes]
                                      Moduletei
                                      Membersdamage
                                      Attributesatt.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.written (@hand)
                                      agentcategorizes the cause of the damage, if it can be identified.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      rubbing
                                      damage results from rubbing of the leaf edges
                                      mildew
                                      damage results from mildew on the leaf surface
                                      smoke
                                      damage results from smoke
                                      degreeprovides a coded representation of the degree of damage, either as a number between 0 (undamaged) and 1 (very extensively damaged), or as one of the codes high, medium, low, or unknown. The damage element with the degree attribute should only be used where the text may be read with some confidence; text supplied from other sources should be tagged as supplied.
                                      Status Optional
                                      Datatype teidata.probCert
                                      Note

                                      The damage element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the text, for example a weathered inscription. Where the damage has rendered the text more or less illegible either the unclear tag (for partial illegibility) or the gap tag (for complete illegibility, with no text supplied) should be used, with the information concerning the damage given in the attribute values of these tags. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of the use of these tags in particular circumstances.

                                      groupassigns an arbitrary number to each stretch of damage regarded as forming part of the same physical phenomenon.
                                      Status Optional
                                      Datatype teidata.count

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.damaged

                                      att.damaged provides attributes describing the nature of any physical damage affecting a reading. [11.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes]
                                      Moduletei
                                      Membersdamage
                                      Attributesatt.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.written (@hand)
                                      agentcategorizes the cause of the damage, if it can be identified.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      rubbing
                                      damage results from rubbing of the leaf edges
                                      mildew
                                      damage results from mildew on the leaf surface
                                      smoke
                                      damage results from smoke
                                      degreeprovides a coded representation of the degree of damage, either as a number between 0 (undamaged) and 1 (very extensively damaged), or as one of the codes high, medium, low, or unknown. The damage element with the degree attribute should only be used where the text may be read with some confidence; text supplied from other sources should be tagged as supplied.
                                      Status Optional
                                      Datatype teidata.probCert
                                      Note

                                      The damage element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the text, for example a weathered inscription. Where the damage has rendered the text more or less illegible either the unclear tag (for partial illegibility) or the gap tag (for complete illegibility, with no text supplied) should be used, with the information concerning the damage given in the attribute values of these tags. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of the use of these tags in particular circumstances.

                                      groupassigns an arbitrary number to each stretch of damage regarded as forming part of the same physical phenomenon.
                                      Status Optional
                                      Datatype teidata.count

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.datable.custom.html b/gl/dev/ref-att.datable.custom.html index 8f1a2bd4e..03cbdf3cc 100644 --- a/gl/dev/ref-att.datable.custom.html +++ b/gl/dev/ref-att.datable.custom.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.datable.custom

                                      att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
                                      Modulenamesdates
                                      Membersatt.datable [acquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef]
                                      Attributes
                                      when-customsupplies the value of a date or time in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace

                                      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

                                      <p>Alhazen died in Cairo on the
                                      <date when="1040-03-06"
                                        when-custom="431-06-12">
                                      12th day of Jumada t-Tania, 430 AH
                                       </date>.</p>
                                      <p>The current world will end at the
                                      <date when="2012-12-21"
                                        when-custom="13.0.0.0.0">
                                      end of B'ak'tun 13</date>.</p>
                                      <p>The Battle of Meggidu
                                      (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
                                      <p>Esidorus bixit in pace annos LXX plus minus sub
                                      <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
                                      </p>

                                      Not all custom date formulations will have Gregorian equivalents.

                                      The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.

                                      notBefore-customspecifies the earliest possible date for the event in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      notAfter-customspecifies the latest possible date for the event in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      from-customindicates the starting point of the period in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      <event xml:id="FIRE1"
                                       datingMethod="#julianfrom-custom="1666-09-02"
                                       to-custom="1666-09-05">

                                       <head>The Great Fire of London</head>
                                       <p>The Great Fire of London burned through a large part
                                         of the city of London.</p>
                                      </event>
                                      to-customindicates the ending point of the period in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
                                      Status Optional
                                      Datatype teidata.pointer
                                      datingMethodsupplies a pointer to a calendar element or other means of interpreting the values of the custom dating attributes.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Contayning the Originall, Antiquity, Increaſe, Moderne
                                      eſtate, and deſcription of that Citie, written in the yeare
                                      <date when-custom="1598calendar="#julian"
                                       datingMethod="#julian">
                                      1598</date>. by Iohn Stow
                                      Citizen of London.

                                      In this example, the calendar attribute points to a calendar element for the Julian calendar, specifying that the text content of the date element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.

                                      <date when="1382-06-28"
                                       when-custom="6890-06-20datingMethod="#creationOfWorld">
                                      μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
                                      </date>

                                      In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (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

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.datable.custom

                                      att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
                                      Modulenamesdates
                                      Membersatt.datable [acquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef]
                                      Attributes
                                      when-customsupplies the value of a date or time in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace

                                      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

                                      <p>Alhazen died in Cairo on the
                                      <date when="1040-03-06"
                                        when-custom="431-06-12">
                                      12th day of Jumada t-Tania, 430 AH
                                       </date>.</p>
                                      <p>The current world will end at the
                                      <date when="2012-12-21"
                                        when-custom="13.0.0.0.0">
                                      end of B'ak'tun 13</date>.</p>
                                      <p>The Battle of Meggidu
                                      (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
                                      <p>Esidorus bixit in pace annos LXX plus minus sub
                                      <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
                                      </p>

                                      Not all custom date formulations will have Gregorian equivalents.

                                      The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.

                                      notBefore-customspecifies the earliest possible date for the event in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      notAfter-customspecifies the latest possible date for the event in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      from-customindicates the starting point of the period in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      <event xml:id="FIRE1"
                                       datingMethod="#julianfrom-custom="1666-09-02"
                                       to-custom="1666-09-05">

                                       <head>The Great Fire of London</head>
                                       <p>The Great Fire of London burned through a large part
                                         of the city of London.</p>
                                      </event>
                                      to-customindicates the ending point of the period in some custom standard form.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
                                      Status Optional
                                      Datatype teidata.pointer
                                      datingMethodsupplies a pointer to a calendar element or other means of interpreting the values of the custom dating attributes.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Contayning the Originall, Antiquity, Increaſe, Moderne
                                      eſtate, and deſcription of that Citie, written in the yeare
                                      <date when-custom="1598calendar="#julian"
                                       datingMethod="#julian">
                                      1598</date>. by Iohn Stow
                                      Citizen of London.

                                      In this example, the calendar attribute points to a calendar element for the Julian calendar, specifying that the text content of the date element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.

                                      <date when="1382-06-28"
                                       when-custom="6890-06-20datingMethod="#creationOfWorld">
                                      μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
                                      </date>

                                      In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (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

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.datable.html b/gl/dev/ref-att.datable.html index bb7cf93bd..7dec0c986 100644 --- a/gl/dev/ref-att.datable.html +++ b/gl/dev/ref-att.datable.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.datable

                                      att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersacquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef
                                      Attributesatt.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
                                      calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Schematron

                                      <sch:rule context="tei:*[@calendar]">
                                      <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
                                      systems or calendars to which the date represented by the content of this element belongs,
                                      but this <sch:name/> element has no textual content.</sch:assert>
                                      </sch:rule>
                                      He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julianwhen="1732-02-22">Feb. 11, 1731/32,
                                      O.S.</date>).
                                      He was born on <date calendar="#gregorian #julian"
                                       when="1732-02-22">
                                      Feb. 22, 1732
                                      (Feb. 11, 1731/32, O.S.)</date>.
                                      Note

                                      Note that 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.

                                      periodsupplies pointers to one or more definitions of named periods of time (typically categorys or calendars) within which the datable item is understood to have occurred.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.datable

                                      att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersacquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef
                                      Attributesatt.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
                                      calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Schematron

                                      <sch:rule context="tei:*[@calendar]">
                                      <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
                                      systems or calendars to which the date represented by the content of this element belongs,
                                      but this <sch:name/> element has no textual content.</sch:assert>
                                      </sch:rule>
                                      He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julianwhen="1732-02-22">Feb. 11, 1731/32,
                                      O.S.</date>).
                                      He was born on <date calendar="#gregorian #julian"
                                       when="1732-02-22">
                                      Feb. 22, 1732
                                      (Feb. 11, 1731/32, O.S.)</date>.
                                      Note

                                      Note that 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.

                                      periodsupplies pointers to one or more definitions of named periods of time (typically categorys or calendars) within which the datable item is understood to have occurred.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.datable.iso.html b/gl/dev/ref-att.datable.iso.html index 5e67a4bd6..74b4fea4b 100644 --- a/gl/dev/ref-att.datable.iso.html +++ b/gl/dev/ref-att.datable.iso.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.datable.iso

                                      att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
                                      Modulenamesdates
                                      Membersatt.datable [acquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef]
                                      Attributes
                                      when-isosupplies the value of a date or time in a standard form.
                                      Status Optional
                                      Datatype teidata.temporal.iso

                                      The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.

                                      <date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
                                      <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
                                      <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
                                      <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
                                      <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
                                      <time when-iso="03:00">3 A.M.</time>
                                      <time when-iso="14">around two</time>
                                      <time when-iso="15,5">half past three</time>

                                      All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.

                                      He likes to be punctual. I said <q>
                                       <time when-iso="12">around noon</time>
                                      </q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.

                                      The second occurence of time could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.

                                      notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      from-isoindicates the starting point of the period in standard form.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      to-isoindicates the ending point of the period in standard form.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      Note

                                      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 ISO 8601:2004, using the Gregorian calendar.

                                      If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
                                      <date when-iso="2007-06-01dur-iso="P8D"/>
                                      indicates the same time period as
                                      <date when-iso="2007-06-01/P8D"/>

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.datable.iso

                                      att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
                                      Modulenamesdates
                                      Membersatt.datable [acquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef]
                                      Attributes
                                      when-isosupplies the value of a date or time in a standard form.
                                      Status Optional
                                      Datatype teidata.temporal.iso

                                      The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.

                                      <date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
                                      <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
                                      <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
                                      <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
                                      <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
                                      <time when-iso="03:00">3 A.M.</time>
                                      <time when-iso="14">around two</time>
                                      <time when-iso="15,5">half past three</time>

                                      All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.

                                      He likes to be punctual. I said <q>
                                       <time when-iso="12">around noon</time>
                                      </q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.

                                      The second occurence of time could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.

                                      notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      from-isoindicates the starting point of the period in standard form.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      to-isoindicates the ending point of the period in standard form.
                                      Status Optional
                                      Datatype teidata.temporal.iso
                                      Note

                                      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 ISO 8601:2004, using the Gregorian calendar.

                                      If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
                                      <date when-iso="2007-06-01dur-iso="P8D"/>
                                      indicates the same time period as
                                      <date when-iso="2007-06-01/P8D"/>

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.datable.w3c.html b/gl/dev/ref-att.datable.w3c.html index 47a5f1bb1..8b2927c8f 100644 --- a/gl/dev/ref-att.datable.w3c.html +++ b/gl/dev/ref-att.datable.w3c.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.datable.w3c

                                      att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersatt.datable [acquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef]
                                      Attributes
                                      whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c

                                      Examples of W3C date, time, and date & time formats.

                                      <p>
                                       <date when="1945-10-24">24 Oct 45</date>
                                       <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
                                       <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
                                       <time when="14:12:38">fourteen twelve and 38 seconds</time>
                                       <date when="1962-10">October of 1962</date>
                                       <date when="--06-12">June 12th</date>
                                       <date when="---01">the first of the month</date>
                                       <date when="--08">August</date>
                                       <date when="2006">MMVI</date>
                                       <date when="0056">AD 56</date>
                                       <date when="-0056">56 BC</date>
                                      </p>
                                      This list begins in
                                      the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
                                      Pentecost, in that year the
                                      <date calendar="#julianwhen="1632-06-06">27th of May (old style)</date>.
                                      <opener>
                                       <dateline>
                                        <placeName>Dorchester, Village,</placeName>
                                        <date when="1828-03-02">March 2d. 1828.</date>
                                       </dateline>
                                       <salute>To
                                         Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time>
                                      </opener>
                                      notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      Schematron

                                      <sch:rule context="tei:*[@when]">
                                      <sch:report test="@notBefore|@notAfter|@from|@to"
                                       role="nonfatal">
                                      The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
                                      </sch:rule>
                                      Schematron

                                      <sch:rule context="tei:*[@from]">
                                      <sch:report test="@notBefore"
                                       role="nonfatal">
                                      The @from and @notBefore attributes cannot be used together.</sch:report>
                                      </sch:rule>
                                      Schematron

                                      <sch:rule context="tei:*[@to]">
                                      <sch:report test="@notAfter"
                                       role="nonfatal">
                                      The @to and @notAfter attributes cannot be used together.</sch:report>
                                      </sch:rule>
                                      Example
                                      <date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
                                      Note

                                      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 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 value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.datable.w3c

                                      att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersatt.datable [acquisition altIdentifier application author binding birth bloc change conversion country creation custEvent date death district editor event floruit funder gender geogFeat geogName idno licence location meeting name objectName offset orgName origDate origPlace origin persName persPronouns placeName precision principal provenance region relation resp seal settlement sponsor stamp state time title unitDecl unitDef]
                                      Attributes
                                      whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c

                                      Examples of W3C date, time, and date & time formats.

                                      <p>
                                       <date when="1945-10-24">24 Oct 45</date>
                                       <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
                                       <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
                                       <time when="14:12:38">fourteen twelve and 38 seconds</time>
                                       <date when="1962-10">October of 1962</date>
                                       <date when="--06-12">June 12th</date>
                                       <date when="---01">the first of the month</date>
                                       <date when="--08">August</date>
                                       <date when="2006">MMVI</date>
                                       <date when="0056">AD 56</date>
                                       <date when="-0056">56 BC</date>
                                      </p>
                                      This list begins in
                                      the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
                                      Pentecost, in that year the
                                      <date calendar="#julianwhen="1632-06-06">27th of May (old style)</date>.
                                      <opener>
                                       <dateline>
                                        <placeName>Dorchester, Village,</placeName>
                                        <date when="1828-03-02">March 2d. 1828.</date>
                                       </dateline>
                                       <salute>To
                                         Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time>
                                      </opener>
                                      notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      Schematron

                                      <sch:rule context="tei:*[@when]">
                                      <sch:report test="@notBefore|@notAfter|@from|@to"
                                       role="nonfatal">
                                      The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
                                      </sch:rule>
                                      Schematron

                                      <sch:rule context="tei:*[@from]">
                                      <sch:report test="@notBefore"
                                       role="nonfatal">
                                      The @from and @notBefore attributes cannot be used together.</sch:report>
                                      </sch:rule>
                                      Schematron

                                      <sch:rule context="tei:*[@to]">
                                      <sch:report test="@notAfter"
                                       role="nonfatal">
                                      The @to and @notAfter attributes cannot be used together.</sch:report>
                                      </sch:rule>
                                      Example
                                      <date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
                                      Note

                                      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 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 value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.datcat.html b/gl/dev/ref-att.datcat.html index 0cadd7261..97a0300d6 100644 --- a/gl/dev/ref-att.datcat.html +++ b/gl/dev/ref-att.datcat.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.datcat

                                      att.datcat 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. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
                                      Moduletei
                                      Membersatt.lexicographic [form gen lang] att.segLike [c m pc phr s seg w] tagUsage
                                      Attributes
                                      datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an 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).
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      valueDatcatprovides a definition of, and/or general 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.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Example

                                      The example below presents the TEI encoding of the name-value pair <part of speech, common 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 should be defined in an external and preferably open reference taxonomy or ontology.

                                      <fs>
                                       <f name="POS"
                                        datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">

                                        <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
                                         value="NN"/>

                                       </f>
                                      <!-- ... -->
                                      </fs>

                                      ‘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 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 English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of 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 [ID FS in TEI Guidelines].
                                      <fs>
                                       <f name="POSfVal="#commonNoun"/>
                                      <!-- ... -->
                                      </fs>

                                      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 child of encodingDesc; a taxonomy available resource-wide (e.g., in a shared header) is also an option.

                                      The example below presents an <fvLib> element that collects the relevant feature values (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.
                                      <fvLib n="POS values">
                                       <symbol xml:id="commonNounvalue="NN"
                                        datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>

                                       <symbol xml:id="properNounvalue="NP"
                                        datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>

                                      <!-- ... -->
                                      </fvLib>

                                      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 represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.

                                      Example

                                      In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.

                                      <gramGrp>
                                       <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
                                        valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">
                                      NN</pos>
                                      </gramGrp>
                                      Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single 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:
                                      <tagsDecl partial="true">
                                      <!-- ... -->
                                       <namespace name="http://www.tei-c.org/ns/1.0">
                                        <tagUsage gi="pos"
                                         targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
                                      Contains the part of speech.</tagUsage>
                                        <tagUsage gi="case"
                                         targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">
                                      Contains information about the grammatical case that the described form is inflected for.</tagUsage>
                                      <!-- ... -->
                                       </namespace>
                                      </tagsDecl>
                                      Another possibility is to shorten the URIs by means of the prefixDef mechanism, as illustrated below:
                                      <listPrefixDef>
                                       <prefixDef ident="ccrmatchPattern="pos"
                                        replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>

                                       <prefixDef ident="ccrmatchPattern="adj"
                                        replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/>

                                      </listPrefixDef>
                                      <!-- ... -->
                                      <entry>
                                      <!--...-->
                                       <form>
                                        <orth>isotope</orth>
                                       </form>
                                       <gramGrp>
                                        <pos datcat="ccr:pos"
                                         valueDatcat="ccr:adj">
                                      adj</pos>
                                       </gramGrp>
                                      <!--...-->
                                      </entry>

                                      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 mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.

                                      Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in <equiv> element that is a child of <elementSpec> or <attDef>.

                                      Example

                                      The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.

                                      <fDecl name="POS"
                                       targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">

                                       <fDescr>part of speech (morphosyntactic category)</fDescr>
                                       <vRange>
                                        <vAlt>
                                         <symbol value="NN"
                                          datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>

                                         <symbol value="NP"
                                          datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>

                                      <!-- ... -->
                                        </vAlt>
                                       </vRange>
                                      </fDecl>

                                      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 its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.

                                      Note

                                      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 the most abstract level, an AVM consists of an information container and the value (contents) of that container.

                                      A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed 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 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 content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

                                      The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

                                      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 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.

                                      Historically, datcat and valueDatcat originate from the (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.

                                      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 attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.datcat

                                      att.datcat 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. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
                                      Moduletei
                                      Membersatt.lexicographic [form gen lang] att.segLike [c m pc phr s seg w] tagUsage
                                      Attributes
                                      datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an 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).
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      valueDatcatprovides a definition of, and/or general 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.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Example

                                      The example below presents the TEI encoding of the name-value pair <part of speech, common 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 should be defined in an external and preferably open reference taxonomy or ontology.

                                      <fs>
                                       <f name="POS"
                                        datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">

                                        <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
                                         value="NN"/>

                                       </f>
                                      <!-- ... -->
                                      </fs>

                                      ‘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 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 English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of 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 [ID FS in TEI Guidelines].
                                      <fs>
                                       <f name="POSfVal="#commonNoun"/>
                                      <!-- ... -->
                                      </fs>

                                      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 child of encodingDesc; a taxonomy available resource-wide (e.g., in a shared header) is also an option.

                                      The example below presents an <fvLib> element that collects the relevant feature values (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.
                                      <fvLib n="POS values">
                                       <symbol xml:id="commonNounvalue="NN"
                                        datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>

                                       <symbol xml:id="properNounvalue="NP"
                                        datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>

                                      <!-- ... -->
                                      </fvLib>

                                      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 represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.

                                      Example

                                      In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.

                                      <gramGrp>
                                       <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
                                        valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">
                                      NN</pos>
                                      </gramGrp>
                                      Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single 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:
                                      <tagsDecl partial="true">
                                      <!-- ... -->
                                       <namespace name="http://www.tei-c.org/ns/1.0">
                                        <tagUsage gi="pos"
                                         targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
                                      Contains the part of speech.</tagUsage>
                                        <tagUsage gi="case"
                                         targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">
                                      Contains information about the grammatical case that the described form is inflected for.</tagUsage>
                                      <!-- ... -->
                                       </namespace>
                                      </tagsDecl>
                                      Another possibility is to shorten the URIs by means of the prefixDef mechanism, as illustrated below:
                                      <listPrefixDef>
                                       <prefixDef ident="ccrmatchPattern="pos"
                                        replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>

                                       <prefixDef ident="ccrmatchPattern="adj"
                                        replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/>

                                      </listPrefixDef>
                                      <!-- ... -->
                                      <entry>
                                      <!--...-->
                                       <form>
                                        <orth>isotope</orth>
                                       </form>
                                       <gramGrp>
                                        <pos datcat="ccr:pos"
                                         valueDatcat="ccr:adj">
                                      adj</pos>
                                       </gramGrp>
                                      <!--...-->
                                      </entry>

                                      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 mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.

                                      Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in <equiv> element that is a child of <elementSpec> or <attDef>.

                                      Example

                                      The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.

                                      <fDecl name="POS"
                                       targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">

                                       <fDescr>part of speech (morphosyntactic category)</fDescr>
                                       <vRange>
                                        <vAlt>
                                         <symbol value="NN"
                                          datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>

                                         <symbol value="NP"
                                          datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/>

                                      <!-- ... -->
                                        </vAlt>
                                       </vRange>
                                      </fDecl>

                                      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 its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.

                                      Note

                                      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 the most abstract level, an AVM consists of an information container and the value (contents) of that container.

                                      A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed 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 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 content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

                                      The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

                                      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 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.

                                      Historically, datcat and valueDatcat originate from the (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.

                                      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 attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.declarable.html b/gl/dev/ref-att.declarable.html index 7e0368ffc..3b7fa40d8 100644 --- a/gl/dev/ref-att.declarable.html +++ b/gl/dev/ref-att.declarable.html @@ -22,4 +22,4 @@ }); });

                                      att.declarable

                                      att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual -Information with a Text]
                                      Moduletei
                                      Membersavailability bibl biblFull biblStruct correction correspDesc editorialDecl geoDecl hyphenation interpretation langUsage listApp listBibl listEvent listNym listObject listOrg listPerson listPlace normalization particDesc projectDesc punctuation quotation refsDecl samplingDecl segmentation seriesStmt settingDesc sourceDesc stdVals styleDefDecl textClass xenoData
                                      Attributes
                                      defaultindicates whether or not this element is selected by default when its parent is selected.
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Legal values are:
                                      true
                                      This element is selected if its parent is selected
                                      false
                                      This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected. [Default]
                                      Note

                                      The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Information with a Text]ModuleteiMembersavailability bibl biblFull biblStruct correction correspDesc editorialDecl geoDecl hyphenation interpretation langUsage listApp listBibl listEvent listNym listObject listOrg listPerson listPlace normalization particDesc projectDesc punctuation quotation refsDecl samplingDecl segmentation seriesStmt settingDesc sourceDesc stdVals styleDefDecl textClass xenoDataAttributes
                                      defaultindicates whether or not this element is selected by default when its parent is selected.
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Legal values are:
                                      true
                                      This element is selected if its parent is selected
                                      false
                                      This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected. [Default]
                                      Note

                                      The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.declaring.html b/gl/dev/ref-att.declaring.html index 07f2b61f0..91cb9774d 100644 --- a/gl/dev/ref-att.declaring.html +++ b/gl/dev/ref-att.declaring.html @@ -22,4 +22,4 @@ }); });

                                      att.declaring

                                      att.declaring 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. [15.3. Associating Contextual -Information with a Text]
                                      Moduletei
                                      Membersab back body div facsimile floatingText front geo gloss graphic group lg listAnnotation media msDesc object p ptr ref sourceDoc standOff surface surfaceGrp term text
                                      Attributes
                                      decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Information with a Text]ModuleteiMembersab back body div facsimile floatingText front geo gloss graphic group lg listAnnotation media msDesc object p ptr ref sourceDoc standOff surface surfaceGrp term textAttributes
                                      decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.dimensions.html b/gl/dev/ref-att.dimensions.html index 0226a3ed8..d8d6fb450 100644 --- a/gl/dev/ref-att.dimensions.html +++ b/gl/dev/ref-att.dimensions.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.dimensions

                                      att.dimensions provides attributes for describing the size of physical objects.
                                      Moduletei
                                      Membersatt.damaged [damage] add addSpan birth date death del delSpan depth dim dimensions ellipsis ex floruit gap geogFeat height mod offset origDate redo retrace secl space state subst substJoin supplied surplus time unclear undo width
                                      Attributesatt.ranging (@atLeast, @atMost, @min, @max, @confidence)
                                      precision
                                      Status Optional
                                      Legal values are:
                                      low
                                      medium
                                      high
                                      unitnames the unit used for the measurement
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      character
                                      line
                                      metre
                                      cm
                                      mm
                                      quantityspecifies the length in the units specified
                                      Status Optional
                                      Datatype teidata.numeric
                                      extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
                                      Status Optional
                                      Datatype teidata.text
                                      Suggested values include:
                                      unknown
                                      <gap extent="5 words"/>
                                      <height extent="half the page"/>
                                      scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      all
                                      measurement applies to all instances.
                                      most
                                      measurement applies to most of the instances inspected.
                                      range
                                      measurement applies to only the specified range of instances.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.dimensions

                                      att.dimensions provides attributes for describing the size of physical objects.
                                      Moduletei
                                      Membersatt.damaged [damage] add addSpan birth date death del delSpan depth dim dimensions ellipsis ex floruit gap geogFeat height mod offset origDate redo retrace secl space state subst substJoin supplied surplus time unclear undo width
                                      Attributesatt.ranging (@atLeast, @atMost, @min, @max, @confidence)
                                      precision
                                      Status Optional
                                      Legal values are:
                                      low
                                      medium
                                      high
                                      unitnames the unit used for the measurement
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      character
                                      line
                                      metre
                                      cm
                                      mm
                                      quantityspecifies the length in the units specified
                                      Status Optional
                                      Datatype teidata.numeric
                                      extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
                                      Status Optional
                                      Datatype teidata.text
                                      Suggested values include:
                                      unknown
                                      <gap extent="5 words"/>
                                      <height extent="half the page"/>
                                      scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      all
                                      measurement applies to all instances.
                                      most
                                      measurement applies to most of the instances inspected.
                                      range
                                      measurement applies to only the specified range of instances.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.divLike.html b/gl/dev/ref-att.divLike.html index cbfe2604f..239897caa 100644 --- a/gl/dev/ref-att.divLike.html +++ b/gl/dev/ref-att.divLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.divLike

                                      att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
                                      Moduletei
                                      Membersdiv lg
                                      Attributesatt.metrical (@met, @real, @rhyme) att.fragmentable (@part)
                                      org(organization) specifies how the content of the division is organized.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      composite
                                      no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
                                      uniform
                                      the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence. [Default]
                                      sampleindicates whether this division is a sample of the original source and if so, from which part.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      initial
                                      division lacks material present at end in source.
                                      medial
                                      division lacks material at start and end.
                                      final
                                      division lacks material at start.
                                      unknown
                                      position of sampled material within original unknown.
                                      complete
                                      division is not a sample. [Default]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.divLike

                                      att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
                                      Moduletei
                                      Membersdiv lg
                                      Attributesatt.metrical (@met, @real, @rhyme) att.fragmentable (@part)
                                      org(organization) specifies how the content of the division is organized.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      composite
                                      no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
                                      uniform
                                      the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence. [Default]
                                      sampleindicates whether this division is a sample of the original source and if so, from which part.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      initial
                                      division lacks material present at end in source.
                                      medial
                                      division lacks material at start and end.
                                      final
                                      division lacks material at start.
                                      unknown
                                      position of sampled material within original unknown.
                                      complete
                                      division is not a sample. [Default]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.docStatus.html b/gl/dev/ref-att.docStatus.html index e560917f8..0aaf350c1 100644 --- a/gl/dev/ref-att.docStatus.html +++ b/gl/dev/ref-att.docStatus.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.docStatus

                                      att.docStatus provides attributes for use on metadata elements describing the status of a document.
                                      Moduletei
                                      Membersbibl biblFull biblStruct change msDesc object revisionDesc
                                      Attributes
                                      statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      approved
                                      candidate
                                      cleared
                                      deprecated
                                      draft
                                      [Default]
                                      embargoed
                                      expired
                                      frozen
                                      galley
                                      proposed
                                      published
                                      recommendation
                                      submitted
                                      unfinished
                                      withdrawn
                                      Example
                                      <revisionDesc status="published">
                                       <change when="2010-10-21"
                                        status="published"/>

                                       <change when="2010-10-02status="cleared"/>
                                       <change when="2010-08-02"
                                        status="embargoed"/>

                                       <change when="2010-05-01status="frozen"
                                        who="#MSM"/>

                                       <change when="2010-03-01status="draft"
                                        who="#LB"/>

                                      </revisionDesc>

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.docStatus

                                      att.docStatus provides attributes for use on metadata elements describing the status of a document.
                                      Moduletei
                                      Membersbibl biblFull biblStruct change msDesc object revisionDesc
                                      Attributes
                                      statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      approved
                                      candidate
                                      cleared
                                      deprecated
                                      draft
                                      [Default]
                                      embargoed
                                      expired
                                      frozen
                                      galley
                                      proposed
                                      published
                                      recommendation
                                      submitted
                                      unfinished
                                      withdrawn
                                      Example
                                      <revisionDesc status="published">
                                       <change when="2010-10-21"
                                        status="published"/>

                                       <change when="2010-10-02status="cleared"/>
                                       <change when="2010-08-02"
                                        status="embargoed"/>

                                       <change when="2010-05-01status="frozen"
                                        who="#MSM"/>

                                       <change when="2010-03-01status="draft"
                                        who="#LB"/>

                                      </revisionDesc>

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.duration.html b/gl/dev/ref-att.duration.html index aef8d52c4..d11a3e1eb 100644 --- a/gl/dev/ref-att.duration.html +++ b/gl/dev/ref-att.duration.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.duration

                                      att.duration provides attributes for normalization of elements that contain datable events.
                                      Modulespoken
                                      Membersatt.timed [annotationBlock binaryObject ellipsis gap media] date time
                                      Attributesatt.duration.w3c (@dur) att.duration.iso (@dur-iso)
                                      Note

                                      This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.duration.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.duration.iso class. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes is rarely needed, and there exists much greater software support for the W3C datatypes.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.duration

                                      att.duration provides attributes for normalization of elements that contain datable events.
                                      Modulespoken
                                      Membersatt.timed [annotationBlock binaryObject ellipsis gap media] date time
                                      Attributesatt.duration.w3c (@dur) att.duration.iso (@dur-iso)
                                      Note

                                      This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.duration.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.duration.iso class. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes is rarely needed, and there exists much greater software support for the W3C datatypes.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.duration.iso.html b/gl/dev/ref-att.duration.iso.html index aa4d5385a..df1a1a286 100644 --- a/gl/dev/ref-att.duration.iso.html +++ b/gl/dev/ref-att.duration.iso.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.duration.iso

                                      att.duration.iso provides attributes for recording normalized temporal durations. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersatt.duration [att.timed [annotationBlock binaryObject ellipsis gap media] date time]
                                      Attributes
                                      dur-iso(duration) indicates the length of this element in time.
                                      Status Optional
                                      Datatype teidata.duration.iso
                                      Note

                                      If both when and dur or dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.duration.iso

                                      att.duration.iso provides attributes for recording normalized temporal durations. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersatt.duration [att.timed [annotationBlock binaryObject ellipsis gap media] date time]
                                      Attributes
                                      dur-iso(duration) indicates the length of this element in time.
                                      Status Optional
                                      Datatype teidata.duration.iso
                                      Note

                                      If both when and dur or dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.duration.w3c.html b/gl/dev/ref-att.duration.w3c.html index 73bf8bfbc..020f20240 100644 --- a/gl/dev/ref-att.duration.w3c.html +++ b/gl/dev/ref-att.duration.w3c.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.duration.w3c

                                      att.duration.w3c provides attributes for recording normalized temporal durations. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersatt.duration [att.timed [annotationBlock binaryObject ellipsis gap media] date time]
                                      Attributes
                                      dur(duration) indicates the length of this element in time.
                                      Status Optional
                                      Datatype teidata.duration.w3c
                                      Note

                                      If both when and dur are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.duration.w3c

                                      att.duration.w3c provides attributes for recording normalized temporal durations. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Membersatt.duration [att.timed [annotationBlock binaryObject ellipsis gap media] date time]
                                      Attributes
                                      dur(duration) indicates the length of this element in time.
                                      Status Optional
                                      Datatype teidata.duration.w3c
                                      Note

                                      If both when and dur are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.editLike.html b/gl/dev/ref-att.editLike.html index 30256335a..e13739ab3 100644 --- a/gl/dev/ref-att.editLike.html +++ b/gl/dev/ref-att.editLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.editLike

                                      att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
                                      Moduletei
                                      Membersatt.transcriptional [add addSpan del delSpan mod redo retrace rt subst substJoin undo] am birth corr date death event ex expan floruit gap gender geogFeat geogName location name objectName offset org orgName origDate origPlace origin persName persPronouns person persona place placeName reg relation secl state supplied surplus time unclear
                                      Attributes
                                      evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      internal
                                      there is internal evidence to support the intervention.
                                      external
                                      there is external evidence to support the intervention.
                                      conjecture
                                      the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
                                      instantindicates whether this is an instant revision or not.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Default false
                                      Note

                                      The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

                                      Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, msDesc, or bibl element, or another external bibliographic citation, documenting the source concerned.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.editLike

                                      att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
                                      Moduletei
                                      Membersatt.transcriptional [add addSpan del delSpan mod redo retrace rt subst substJoin undo] am birth corr date death event ex expan floruit gap gender geogFeat geogName location name objectName offset org orgName origDate origPlace origin persName persPronouns person persona place placeName reg relation secl state supplied surplus time unclear
                                      Attributes
                                      evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      internal
                                      there is internal evidence to support the intervention.
                                      external
                                      there is external evidence to support the intervention.
                                      conjecture
                                      the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
                                      instantindicates whether this is an instant revision or not.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Default false
                                      Note

                                      The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

                                      Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, msDesc, or bibl element, or another external bibliographic citation, documenting the source concerned.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.edition.html b/gl/dev/ref-att.edition.html index 190c1ba35..151518cc7 100644 --- a/gl/dev/ref-att.edition.html +++ b/gl/dev/ref-att.edition.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.edition

                                      att.edition provides attributes identifying the source edition from which some encoded feature derives.
                                      Moduletei
                                      Memberscb gb lb milestone pb refState
                                      Attributes
                                      ed(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Example
                                      <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
                                      <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
                                      <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
                                      Example
                                      <listBibl>
                                       <bibl xml:id="stapledon1937">
                                        <author>Olaf Stapledon</author>,
                                       <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
                                       </bibl>
                                       <bibl xml:id="stapledon1968">
                                        <author>Olaf Stapledon</author>,
                                       <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
                                       </bibl>
                                      </listBibl>
                                      <!-- ... -->
                                      <p>Looking into the future aeons from the supreme moment of
                                      the cosmos, I saw the populations still with all their
                                      strength maintaining the<pb n="411edRef="#stapledon1968"/>essentials of their ancient culture,
                                      still living their personal lives in zest and endless
                                      novelty of action, … I saw myself still
                                      preserving, though with increasing difficulty, my lucid
                                      con-<pb n="291edRef="#stapledon1937"/>sciousness;</p>

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.edition

                                      att.edition provides attributes identifying the source edition from which some encoded feature derives.
                                      Moduletei
                                      Memberscb gb lb milestone pb refState
                                      Attributes
                                      ed(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Example
                                      <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
                                      <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
                                      <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
                                      Example
                                      <listBibl>
                                       <bibl xml:id="stapledon1937">
                                        <author>Olaf Stapledon</author>,
                                       <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
                                       </bibl>
                                       <bibl xml:id="stapledon1968">
                                        <author>Olaf Stapledon</author>,
                                       <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
                                       </bibl>
                                      </listBibl>
                                      <!-- ... -->
                                      <p>Looking into the future aeons from the supreme moment of
                                      the cosmos, I saw the populations still with all their
                                      strength maintaining the<pb n="411edRef="#stapledon1968"/>essentials of their ancient culture,
                                      still living their personal lives in zest and endless
                                      novelty of action, … I saw myself still
                                      preserving, though with increasing difficulty, my lucid
                                      con-<pb n="291edRef="#stapledon1937"/>sciousness;</p>

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.enjamb.html b/gl/dev/ref-att.enjamb.html index b87fc0320..28df7cdeb 100644 --- a/gl/dev/ref-att.enjamb.html +++ b/gl/dev/ref-att.enjamb.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.enjamb

                                      att.enjamb (enjambement) provides attributes that may be used to indicate enjambement of the parent element. [6.2. Components of the Verse Line]
                                      Moduleverse
                                      Membersl
                                      Attributes
                                      enjamb(enjambement) indicates that the end of a verse line is marked by enjambement.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      no
                                      the line is end-stopped
                                      yes
                                      the line in question runs on into the next
                                      weak
                                      the line is weakly enjambed
                                      strong
                                      the line is strongly enjambed
                                      Note

                                      The usual practice will be to give the value ‘yes’ to this attribute when enjambement is being marked, or the values ‘weak’ and ‘strong’ if degrees of enjambement are of interest; if no value is given, however, the attribute does not default to a value of ‘no’; this allows the attribute to be omitted entirely when enjambement is not of particular interest.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.enjamb

                                      att.enjamb (enjambement) provides attributes that may be used to indicate enjambement of the parent element. [6.2. Components of the Verse Line]
                                      Moduleverse
                                      Membersl
                                      Attributes
                                      enjamb(enjambement) indicates that the end of a verse line is marked by enjambement.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      no
                                      the line is end-stopped
                                      yes
                                      the line in question runs on into the next
                                      weak
                                      the line is weakly enjambed
                                      strong
                                      the line is strongly enjambed
                                      Note

                                      The usual practice will be to give the value ‘yes’ to this attribute when enjambement is being marked, or the values ‘weak’ and ‘strong’ if degrees of enjambement are of interest; if no value is given, however, the attribute does not default to a value of ‘no’; this allows the attribute to be omitted entirely when enjambement is not of particular interest.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.formula.html b/gl/dev/ref-att.formula.html index cffc9189c..992c717db 100644 --- a/gl/dev/ref-att.formula.html +++ b/gl/dev/ref-att.formula.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.formula

                                      att.formula provides attributes for defining a mathematical formula. [2.3.9. The Unit Declaration]
                                      Moduletei
                                      Membersconversion
                                      Attributes
                                      formulaA formula is provided to describe a mathematical calculation such as a conversion between measurement systems.
                                      Status Optional
                                      Datatype teidata.xpath
                                      Example
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="stadiumtype="linear">
                                         <label>stadium</label>
                                         <placeName ref="#rome"/>
                                         <conversion fromUnit="#pes"
                                          toUnit="#stadiumformula="$fromUnit * 625"/>

                                         <desc>The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="wmwtype="power">
                                         <label>whatmeworry</label>
                                         <conversion fromUnit="#hpk"
                                          toUnit="#wmwformula="$fromUnit * 1"/>

                                         <desc>In the Potrzebie system of measures as introduced by Donald Knuth, the whatmeworry unit of power is equivalent to one hah per kovac.</desc>
                                        </unitDef>
                                        <unitDef xml:id="kwmwtype="power">
                                         <label>kilowhatmeworry</label>
                                         <conversion fromUnit="#wmw"
                                          toUnit="#kwmwformula="$fromUnit div 1000"/>

                                         <desc>The kilowhatmeworry is equivalent to 1000 whatmeworries.</desc>
                                        </unitDef>
                                        <unitDef xml:id="aptype="power">
                                         <label>kilowhatmeworry</label>
                                         <conversion fromUnit="#kwmw"
                                          toUnit="#apformula="$fromUnit div 100"/>

                                         <desc>One unit of aeolipower (A.P.) is equivalent to 100 kilowhatmeworries.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <conversion fromUnit="#furlongsPerFortnight"
                                       toUnit="#milesPerHour"
                                       formula="$fromUnit cast as xs:decimal * 0.000372"/>
                                      Example
                                      <conversion fromUnit="#deciday"
                                       toUnit="hour"
                                       formula="$fromUnit cast as xs:decimal * 144 div 60"/>
                                      Note

                                      This attribute class provides formula for use in defining a value used in mathematical calculation. It can be used to store a mathematical operation needed to convert from one system of measurement to another. We use the teidata.xpath datatype to express this value in order to communicate mathematical operations on an XML node or nodes. The $fromUnit variable notation simplifies referencing of the fromUnit attribute on the parent conversion element. Note that ‘div’ is required to express the division operator in XPath.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.formula

                                      att.formula provides attributes for defining a mathematical formula. [2.3.9. The Unit Declaration]
                                      Moduletei
                                      Membersconversion
                                      Attributes
                                      formulaA formula is provided to describe a mathematical calculation such as a conversion between measurement systems.
                                      Status Optional
                                      Datatype teidata.xpath
                                      Example
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="stadiumtype="linear">
                                         <label>stadium</label>
                                         <placeName ref="#rome"/>
                                         <conversion fromUnit="#pes"
                                          toUnit="#stadiumformula="$fromUnit * 625"/>

                                         <desc>The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="wmwtype="power">
                                         <label>whatmeworry</label>
                                         <conversion fromUnit="#hpk"
                                          toUnit="#wmwformula="$fromUnit * 1"/>

                                         <desc>In the Potrzebie system of measures as introduced by Donald Knuth, the whatmeworry unit of power is equivalent to one hah per kovac.</desc>
                                        </unitDef>
                                        <unitDef xml:id="kwmwtype="power">
                                         <label>kilowhatmeworry</label>
                                         <conversion fromUnit="#wmw"
                                          toUnit="#kwmwformula="$fromUnit div 1000"/>

                                         <desc>The kilowhatmeworry is equivalent to 1000 whatmeworries.</desc>
                                        </unitDef>
                                        <unitDef xml:id="aptype="power">
                                         <label>kilowhatmeworry</label>
                                         <conversion fromUnit="#kwmw"
                                          toUnit="#apformula="$fromUnit div 100"/>

                                         <desc>One unit of aeolipower (A.P.) is equivalent to 100 kilowhatmeworries.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <conversion fromUnit="#furlongsPerFortnight"
                                       toUnit="#milesPerHour"
                                       formula="$fromUnit cast as xs:decimal * 0.000372"/>
                                      Example
                                      <conversion fromUnit="#deciday"
                                       toUnit="hour"
                                       formula="$fromUnit cast as xs:decimal * 144 div 60"/>
                                      Note

                                      This attribute class provides formula for use in defining a value used in mathematical calculation. It can be used to store a mathematical operation needed to convert from one system of measurement to another. We use the teidata.xpath datatype to express this value in order to communicate mathematical operations on an XML node or nodes. The $fromUnit variable notation simplifies referencing of the fromUnit attribute on the parent conversion element. Note that ‘div’ is required to express the division operator in XPath.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.fragmentable.html b/gl/dev/ref-att.fragmentable.html index 27f33b6e6..f996086d1 100644 --- a/gl/dev/ref-att.fragmentable.html +++ b/gl/dev/ref-att.fragmentable.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.fragmentable

                                      att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
                                      Moduletei
                                      Membersatt.divLike [div lg] att.segLike [c m pc phr s seg w] ab l p
                                      Attributes
                                      partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      Y
                                      (yes) the element is fragmented in some (unspecified) respect
                                      N
                                      (no) the element is not fragmented, or no claim is made as to its completeness [Default]
                                      I
                                      (initial) this is the initial part of a fragmented element
                                      M
                                      (medial) this is a medial part of a fragmented element
                                      F
                                      (final) this is the final part of a fragmented element
                                      Note

                                      The values I, M, or F should be used only where it is clear how the element may be reconstituted.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.fragmentable

                                      att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
                                      Moduletei
                                      Membersatt.divLike [div lg] att.segLike [c m pc phr s seg w] ab l p
                                      Attributes
                                      partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      Y
                                      (yes) the element is fragmented in some (unspecified) respect
                                      N
                                      (no) the element is not fragmented, or no claim is made as to its completeness [Default]
                                      I
                                      (initial) this is the initial part of a fragmented element
                                      M
                                      (medial) this is a medial part of a fragmented element
                                      F
                                      (final) this is the final part of a fragmented element
                                      Note

                                      The values I, M, or F should be used only where it is clear how the element may be reconstituted.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.gaijiProp.html b/gl/dev/ref-att.gaijiProp.html index 6559c1922..7aef45c21 100644 --- a/gl/dev/ref-att.gaijiProp.html +++ b/gl/dev/ref-att.gaijiProp.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.gaijiProp

                                      att.gaijiProp provides attributes for defining the properties of non-standard characters or glyphs. [5. Characters, Glyphs, and Writing Modes]
                                      Modulegaiji
                                      MemberslocalProp unicodeProp unihanProp
                                      Attributes
                                      nameprovides the name of the character or glyph property being defined.
                                      Status Required
                                      Datatype teidata.xmlName
                                      valueprovides the value of the character or glyph property being defined.
                                      Status Required
                                      Datatype teidata.text
                                      versionspecifies the version number of the Unicode Standard in which this property name is defined.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      1.0.1
                                      1.1
                                      2.0
                                      2.1
                                      3.0
                                      3.1
                                      3.2
                                      4.0
                                      4.1
                                      5.0
                                      5.1
                                      5.2
                                      6.0
                                      6.1
                                      6.2
                                      6.3
                                      7.0
                                      8.0
                                      9.0
                                      10.0
                                      11.0
                                      12.0
                                      12.1
                                      unassigned
                                      Example

                                      In this example a definition for the Unicode property Decomposition Mapping is provided.

                                      <unicodeProp name="Decomposition_Mapping"
                                       value="circle"/>
                                      Note

                                      All name-only attributes need an xs:boolean attribute value inside value.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.gaijiProp

                                      att.gaijiProp provides attributes for defining the properties of non-standard characters or glyphs. [5. Characters, Glyphs, and Writing Modes]
                                      Modulegaiji
                                      MemberslocalProp unicodeProp unihanProp
                                      Attributes
                                      nameprovides the name of the character or glyph property being defined.
                                      Status Required
                                      Datatype teidata.xmlName
                                      valueprovides the value of the character or glyph property being defined.
                                      Status Required
                                      Datatype teidata.text
                                      versionspecifies the version number of the Unicode Standard in which this property name is defined.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      1.0.1
                                      1.1
                                      2.0
                                      2.1
                                      3.0
                                      3.1
                                      3.2
                                      4.0
                                      4.1
                                      5.0
                                      5.1
                                      5.2
                                      6.0
                                      6.1
                                      6.2
                                      6.3
                                      7.0
                                      8.0
                                      9.0
                                      10.0
                                      11.0
                                      12.0
                                      12.1
                                      unassigned
                                      Example

                                      In this example a definition for the Unicode property Decomposition Mapping is provided.

                                      <unicodeProp name="Decomposition_Mapping"
                                       value="circle"/>
                                      Note

                                      All name-only attributes need an xs:boolean attribute value inside value.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.analytic.html b/gl/dev/ref-att.global.analytic.html index 3a5ba3bc8..1c2c8cdca 100644 --- a/gl/dev/ref-att.global.analytic.html +++ b/gl/dev/ref-att.global.analytic.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global.analytic

                                      att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]
                                      Moduleanalysis
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global.analytic

                                      att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]
                                      Moduleanalysis
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.change.html b/gl/dev/ref-att.global.change.html index 4f2948660..26b1c7c26 100644 --- a/gl/dev/ref-att.global.change.html +++ b/gl/dev/ref-att.global.change.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global.change

                                      att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
                                      Moduletranscr
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      changepoints to one or more change elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global.change

                                      att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
                                      Moduletranscr
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      changepoints to one or more change elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.facs.html b/gl/dev/ref-att.global.facs.html index e4f071c7c..50594dae1 100644 --- a/gl/dev/ref-att.global.facs.html +++ b/gl/dev/ref-att.global.facs.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global.facs

                                      att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
                                      Moduletranscr
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global.facs

                                      att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
                                      Moduletranscr
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.html b/gl/dev/ref-att.global.html index dddf29612..12266d7ec 100644 --- a/gl/dev/ref-att.global.html +++ b/gl/dev/ref-att.global.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global

                                      att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
                                      Moduletei
                                      MembersTEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone
                                      Attributesatt.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
                                      xml:id(identifier) provides a unique identifier for the element bearing the attribute.
                                      Status Optional
                                      Datatype ID
                                      Note

                                      The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

                                      n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
                                      Status Optional
                                      Datatype teidata.text
                                      Note

                                      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 for the text.

                                      xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
                                      Status Optional
                                      Datatype teidata.language
                                      <p> … The consequences of
                                      this rapid depopulation were the loss of the last
                                      <foreign xml:lang="rap">ariki</foreign> or chief
                                      (Routledge 1920:205,210) and their connections to
                                      ancestral territorial organization.</p>
                                      Note

                                      The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

                                      Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

                                      The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

                                      The value used must conform with 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 the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

                                      xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
                                      Status Optional
                                      Datatype teidata.pointer
                                      <div type="bibl">
                                       <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>
                                       </head>
                                       <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">
                                        <bibl>
                                         <ref target="letterEEd.26.3.xml">
                                          <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.
                                         </ref>
                                        </bibl>
                                        <bibl>
                                         <ref target="letterEEd.26.57.xml">
                                          <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.
                                         </ref>
                                        </bibl>
                                        <bibl>
                                         <ref target="letterEEd.26.85.xml">
                                          <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05to="1794-04-06">5-6 April, 1794</date>.
                                         </ref>
                                        </bibl>
                                       </listBibl>
                                      </div>
                                      xml:spacesignals an intention about how white space should be managed by applications.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      default
                                      signals that the application's default white-space processing modes are acceptable
                                      preserve
                                      indicates the intent that applications preserve all white space
                                      Note

                                      The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global

                                      att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
                                      Moduletei
                                      MembersTEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone
                                      Attributesatt.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
                                      xml:id(identifier) provides a unique identifier for the element bearing the attribute.
                                      Status Optional
                                      Datatype ID
                                      Note

                                      The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

                                      n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
                                      Status Optional
                                      Datatype teidata.text
                                      Note

                                      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 for the text.

                                      xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
                                      Status Optional
                                      Datatype teidata.language
                                      <p> … The consequences of
                                      this rapid depopulation were the loss of the last
                                      <foreign xml:lang="rap">ariki</foreign> or chief
                                      (Routledge 1920:205,210) and their connections to
                                      ancestral territorial organization.</p>
                                      Note

                                      The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

                                      Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

                                      The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

                                      The value used must conform with 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 the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

                                      xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
                                      Status Optional
                                      Datatype teidata.pointer
                                      <div type="bibl">
                                       <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>
                                       </head>
                                       <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">
                                        <bibl>
                                         <ref target="letterEEd.26.3.xml">
                                          <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.
                                         </ref>
                                        </bibl>
                                        <bibl>
                                         <ref target="letterEEd.26.57.xml">
                                          <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.
                                         </ref>
                                        </bibl>
                                        <bibl>
                                         <ref target="letterEEd.26.85.xml">
                                          <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05to="1794-04-06">5-6 April, 1794</date>.
                                         </ref>
                                        </bibl>
                                       </listBibl>
                                      </div>
                                      xml:spacesignals an intention about how white space should be managed by applications.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      default
                                      signals that the application's default white-space processing modes are acceptable
                                      preserve
                                      indicates the intent that applications preserve all white space
                                      Note

                                      The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.linking.html b/gl/dev/ref-att.global.linking.html index 6b404d796..0609a60b2 100644 --- a/gl/dev/ref-att.global.linking.html +++ b/gl/dev/ref-att.global.linking.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global.linking

                                      att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
                                      Modulelinking
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      corresp(corresponds) points to elements that correspond to the current element in some way.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      <group>
                                       <text xml:id="t1-g1-t1xml:lang="mi">
                                        <body xml:id="t1-g1-t1-body1">
                                         <div type="chapter">
                                          <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
                                          <p></p>
                                         </div>
                                        </body>
                                       </text>
                                       <text xml:id="t1-g1-t2xml:lang="en">
                                        <body xml:id="t1-g1-t2-body1"
                                         corresp="#t1-g1-t1-body1">

                                         <div type="chapter">
                                          <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
                                          <p></p>
                                         </div>
                                        </body>
                                       </text>
                                      </group>

                                      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.


                                      <!-- In a placeography called "places.xml" --><place xml:id="LOND1"
                                       corresp="people.xml#LOND2 people.xml#GENI1">

                                       <placeName>London</placeName>
                                       <desc>The city of London...</desc>
                                      </place>
                                      <!-- In a literary personography called "people.xml" -->
                                      <person xml:id="LOND2"
                                       corresp="places.xml#LOND1 #GENI1">

                                       <persName type="lit">London</persName>
                                       <note>
                                        <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
                                       </note>
                                      </person>
                                      <person xml:id="GENI1"
                                       corresp="places.xml#LOND1 #LOND2">

                                       <persName type="lit">London’s Genius</persName>
                                       <note>
                                        <p>Personification of London’s genius. Appears as an
                                           allegorical character in mayoral shows.
                                        </p>
                                       </note>
                                      </person>

                                      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 preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

                                      synch(synchronous) points to elements that are synchronous with the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      sameAspoints to an element that is the same as the current element.
                                      Status Optional
                                      Datatype teidata.pointer
                                      copyOfpoints to an element of which the current element is a copy.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      Any content of the current element should be ignored. Its true content is that of the element being pointed at.

                                      nextpoints to the next element of a virtual aggregate of which the current element is part.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      It is recommended that the element indicated be of the same type as the element bearing this attribute.

                                      prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      It is recommended that the element indicated be of the same type as the element bearing this attribute.

                                      excludepoints to elements that are in exclusive alternation with the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global.linking

                                      att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
                                      Modulelinking
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      corresp(corresponds) points to elements that correspond to the current element in some way.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      <group>
                                       <text xml:id="t1-g1-t1xml:lang="mi">
                                        <body xml:id="t1-g1-t1-body1">
                                         <div type="chapter">
                                          <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
                                          <p></p>
                                         </div>
                                        </body>
                                       </text>
                                       <text xml:id="t1-g1-t2xml:lang="en">
                                        <body xml:id="t1-g1-t2-body1"
                                         corresp="#t1-g1-t1-body1">

                                         <div type="chapter">
                                          <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
                                          <p></p>
                                         </div>
                                        </body>
                                       </text>
                                      </group>

                                      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.


                                      <!-- In a placeography called "places.xml" --><place xml:id="LOND1"
                                       corresp="people.xml#LOND2 people.xml#GENI1">

                                       <placeName>London</placeName>
                                       <desc>The city of London...</desc>
                                      </place>
                                      <!-- In a literary personography called "people.xml" -->
                                      <person xml:id="LOND2"
                                       corresp="places.xml#LOND1 #GENI1">

                                       <persName type="lit">London</persName>
                                       <note>
                                        <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
                                       </note>
                                      </person>
                                      <person xml:id="GENI1"
                                       corresp="places.xml#LOND1 #LOND2">

                                       <persName type="lit">London’s Genius</persName>
                                       <note>
                                        <p>Personification of London’s genius. Appears as an
                                           allegorical character in mayoral shows.
                                        </p>
                                       </note>
                                      </person>

                                      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 preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

                                      synch(synchronous) points to elements that are synchronous with the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      sameAspoints to an element that is the same as the current element.
                                      Status Optional
                                      Datatype teidata.pointer
                                      copyOfpoints to an element of which the current element is a copy.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      Any content of the current element should be ignored. Its true content is that of the element being pointed at.

                                      nextpoints to the next element of a virtual aggregate of which the current element is part.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      It is recommended that the element indicated be of the same type as the element bearing this attribute.

                                      prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      It is recommended that the element indicated be of the same type as the element bearing this attribute.

                                      excludepoints to elements that are in exclusive alternation with the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      selectselects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.rendition.html b/gl/dev/ref-att.global.rendition.html index f50cbb410..996aad339 100644 --- a/gl/dev/ref-att.global.rendition.html +++ b/gl/dev/ref-att.global.rendition.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global.rendition

                                      att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
                                      Moduletei
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      rend(rendition) indicates how the element in question was rendered or presented in the source text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      <head rend="align(center) case(allcaps)">
                                       <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
                                      <lb/>On Her <lb/>
                                       <hi rend="case(mixed)">New Blazing-World</hi>.
                                      </head>
                                      Note

                                      These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

                                      stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
                                      Status Optional
                                      Datatype teidata.text
                                      <head style="text-align: center; font-variant: small-caps">
                                       <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
                                      <lb/>
                                       <hi style="font-variant: normal">New Blazing-World</hi>.
                                      </head>
                                      Note

                                      Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

                                      The formal language in which values for this attribute are expressed may be specified using the styleDefDecl element in the TEI header.

                                      If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

                                      renditionpoints to a description of the rendering or presentation used for this element in the source text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      <head rendition="#ac #sc">
                                       <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
                                      <lb/>
                                       <hi rendition="#normal">New Blazing-World</hi>.
                                      </head>
                                      <!-- elsewhere... -->
                                      <rendition xml:id="scscheme="css">font-variant: small-caps</rendition>
                                      <rendition xml:id="normalscheme="css">font-variant: normal</rendition>
                                      <rendition xml:id="acscheme="css">text-align: center</rendition>
                                      Note

                                      The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

                                      If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

                                      Each URI provided should indicate a rendition element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global.rendition

                                      att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
                                      Moduletei
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      rend(rendition) indicates how the element in question was rendered or presented in the source text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      <head rend="align(center) case(allcaps)">
                                       <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
                                      <lb/>On Her <lb/>
                                       <hi rend="case(mixed)">New Blazing-World</hi>.
                                      </head>
                                      Note

                                      These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

                                      stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
                                      Status Optional
                                      Datatype teidata.text
                                      <head style="text-align: center; font-variant: small-caps">
                                       <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
                                      <lb/>
                                       <hi style="font-variant: normal">New Blazing-World</hi>.
                                      </head>
                                      Note

                                      Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

                                      The formal language in which values for this attribute are expressed may be specified using the styleDefDecl element in the TEI header.

                                      If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

                                      renditionpoints to a description of the rendering or presentation used for this element in the source text.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      <head rendition="#ac #sc">
                                       <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
                                      <lb/>
                                       <hi rendition="#normal">New Blazing-World</hi>.
                                      </head>
                                      <!-- elsewhere... -->
                                      <rendition xml:id="scscheme="css">font-variant: small-caps</rendition>
                                      <rendition xml:id="normalscheme="css">font-variant: normal</rendition>
                                      <rendition xml:id="acscheme="css">text-align: center</rendition>
                                      Note

                                      The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

                                      If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

                                      Each URI provided should indicate a rendition element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.responsibility.html b/gl/dev/ref-att.global.responsibility.html index b9cc96e0d..65e722783 100644 --- a/gl/dev/ref-att.global.responsibility.html +++ b/gl/dev/ref-att.global.responsibility.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.global.responsibility

                                      att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
                                      Moduletei
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
                                      Status Optional
                                      Datatype teidata.probCert
                                      resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (person or org) but to a respStmt, author, editor or similar 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.).

                                      Example
                                      Blessed are the
                                      <choice>
                                       <sic>cheesemakers</sic>
                                       <corr resp="#editorcert="high">peacemakers</corr>
                                      </choice>: for they shall be called the children of God.
                                      Example

                                      <!-- in the <text> ... --><lg>
                                      <!-- ... -->
                                       <l>Punkes, Panders, baſe extortionizing
                                         sla<choice>
                                         <sic>n</sic>
                                         <corr resp="#JENS1_transcriber">u</corr>
                                        </choice>es,</l>
                                      <!-- ... -->
                                      </lg>
                                      <!-- in the <teiHeader> ... -->
                                      <!-- ... -->
                                      <respStmt xml:id="JENS1_transcriber">
                                       <resp when="2014">Transcriber</resp>
                                       <name>Janelle Jenstad</name>
                                      </respStmt>

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.global.responsibility

                                      att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
                                      Moduletei
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
                                      Status Optional
                                      Datatype teidata.probCert
                                      resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (person or org) but to a respStmt, author, editor or similar 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.).

                                      Example
                                      Blessed are the
                                      <choice>
                                       <sic>cheesemakers</sic>
                                       <corr resp="#editorcert="high">peacemakers</corr>
                                      </choice>: for they shall be called the children of God.
                                      Example

                                      <!-- in the <text> ... --><lg>
                                      <!-- ... -->
                                       <l>Punkes, Panders, baſe extortionizing
                                         sla<choice>
                                         <sic>n</sic>
                                         <corr resp="#JENS1_transcriber">u</corr>
                                        </choice>es,</l>
                                      <!-- ... -->
                                      </lg>
                                      <!-- in the <teiHeader> ... -->
                                      <!-- ... -->
                                      <respStmt xml:id="JENS1_transcriber">
                                       <resp when="2014">Transcriber</resp>
                                       <name>Janelle Jenstad</name>
                                      </respStmt>

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.global.source.html b/gl/dev/ref-att.global.source.html index 54c034fdd..26747abd9 100644 --- a/gl/dev/ref-att.global.source.html +++ b/gl/dev/ref-att.global.source.html @@ -23,4 +23,4 @@ });

                                      att.global.source

                                      att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
                                      Moduletei
                                      Membersatt.global [TEI ab abbr abstract accMat acquisition add addName addSpan additional additions addrLine address adminInfo altIdentifier am analytic anchor annotation annotationBlock app application author authority availability back bibl biblFull biblScope biblStruct binaryObject binding bindingDesc birth bloc body c cRefPattern calendar calendarDesc catDesc catRef catchwords category cb cell certainty change charDecl choice cit citeData citeStructure citedRange classCode classDecl collation collection colophon condition conversion corr correction correspAction correspContext correspDesc country creation custEvent custodialHist damage date dateline death decoDesc decoNote del delSpan depth desc dim dimensions distinct distributor district div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl ellipsis email emph encodingDesc epigraph event ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric floatingText floruit foliation foreign forename form front funder fw g gap gb gen genName gender geo geoDecl geogFeat geogName gloss glyph graphic group handDesc handNote handNotes handShift head headItem headLabel height heraldry hi history hyphenation idno imprint incipit index institution interp interpGrp interpretation item join keywords l label lang langUsage language layout layoutDesc lb lem lg licence line link linkGrp list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRelation listTranspose localProp location locus locusGrp m mapping material measure measureGrp media meeting mentioned metamark milestone mod monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name namespace normalization notatedMusic note noteGrp notesStmt num nym object objectDesc objectIdentifier objectName objectType offset org orgName orig origDate origPlace origin p particDesc path pb pc persName persPronouns person personGrp persona phr physDesc place placeName postBox postCode precision prefixDef principal profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher punctuation q quotation quote rb rdg rdgGrp recordHist redo ref refState refsDecl reg region relatedItem relation rendition repository resp respStmt retrace revisionDesc roleName row rs rt rubric ruby s said samplingDecl schemaRef scriptDesc scriptNote seal sealDesc secFol secl seg segmentation series seriesStmt settingDesc settlement sic signatures soCalled source sourceDesc sourceDoc sp space speaker sponsor stage stamp standOff state stdVals street styleDefDecl subst substJoin summary supplied support supportDesc surface surfaceGrp surname surplus surrogates table tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textLang time title titleStmt transcriptionDesc transpose typeDesc typeNote unclear undo unicodeProp unihanProp unit unitDecl unitDef variantEncoding w watermark width wit xenoData zone]
                                      Attributes
                                      sourcespecifies the source from which some aspect of this element is drawn.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Schematron

                                      <sch:rule context="tei:*[@source]">
                                      <sch:let name="srcs"
                                       value="tokenize( normalize-space(@source),' ')"/>

                                      <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) - and $srcs[2]"> When used on a schema description element (like
                                      <sch:value-of select="name(.)"/>), the @source attribute
                                      should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.)
                                      </sch:report>
                                      </sch:rule>
                                      Note

                                      The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

                                      On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

                                      In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a prefixDef.

                                      When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

                                      Example
                                      <p>
                                      <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
                                         term.</quote>
                                      <!-- ... -->
                                      </p>
                                      Example
                                      <p>
                                      <!-- ... -->
                                       <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
                                         less we seem to know.</quote>
                                      <!-- ... -->
                                      </p>
                                      <!-- ... -->
                                      <bibl xml:id="chicago_15_ed">
                                       <title level="m">The Chicago Manual of Style</title>,
                                      <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
                                         Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.

                                      </bibl>
                                      Example
                                      <elementRef key="psource="tei:2.0.1"/>

                                      Include in the schema an element named p available from the TEI P5 2.0.1 release.

                                      Example
                                      <schemaSpec ident="myODD"
                                       source="mycompiledODD.xml">

                                      <!-- further declarations specifying the components required -->
                                      </schemaSpec>

                                      Create a schema using components taken from the file mycompiledODD.xml.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file + and $srcs[2]"> When used on a schema description element (like
                                      <sch:value-of select="name(.)"/>), the @source attribute
                                      should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.)
                                      </sch:report>
                                      </sch:rule>Note

                                      The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

                                      On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

                                      In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a prefixDef.

                                      When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

                                      Example
                                      <p>
                                      <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
                                         term.</quote>
                                      <!-- ... -->
                                      </p>
                                      Example
                                      <p>
                                      <!-- ... -->
                                       <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
                                         less we seem to know.</quote>
                                      <!-- ... -->
                                      </p>
                                      <!-- ... -->
                                      <bibl xml:id="chicago_15_ed">
                                       <title level="m">The Chicago Manual of Style</title>,
                                      <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
                                         Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.

                                      </bibl>
                                      Example
                                      <elementRef key="psource="tei:2.0.1"/>

                                      Include in the schema an element named p available from the TEI P5 2.0.1 release.

                                      Example
                                      <schemaSpec ident="myODD"
                                       source="mycompiledODD.xml">

                                      <!-- further declarations specifying the components required -->
                                      </schemaSpec>

                                      Create a schema using components taken from the file mycompiledODD.xml.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.handFeatures.html b/gl/dev/ref-att.handFeatures.html index e324af477..490b3acbc 100644 --- a/gl/dev/ref-att.handFeatures.html +++ b/gl/dev/ref-att.handFeatures.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.handFeatures

                                      att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands]
                                      Moduletei
                                      MembershandNote handShift scriptNote typeNote
                                      Attributes
                                      scribegives a name or other identifier for the scribe believed to be responsible for this hand.
                                      Status Optional
                                      Datatype teidata.name
                                      scribeRefpoints to a full description of the scribe concerned, typically supplied by a person element elsewhere in the description.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.name separated by whitespace
                                      scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a scriptNote element elsewhere in the description.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      scopespecifies how widely this hand is used in the manuscript.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      sole
                                      only this hand is used throughout the manuscript
                                      major
                                      this hand is used through most of the manuscript
                                      minor
                                      this hand is used occasionally in the manuscript
                                      Note

                                      Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.handFeatures

                                      att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands]
                                      Moduletei
                                      MembershandNote handShift scriptNote typeNote
                                      Attributes
                                      scribegives a name or other identifier for the scribe believed to be responsible for this hand.
                                      Status Optional
                                      Datatype teidata.name
                                      scribeRefpoints to a full description of the scribe concerned, typically supplied by a person element elsewhere in the description.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.name separated by whitespace
                                      scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a scriptNote element elsewhere in the description.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      scopespecifies how widely this hand is used in the manuscript.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      sole
                                      only this hand is used throughout the manuscript
                                      major
                                      this hand is used through most of the manuscript
                                      minor
                                      this hand is used occasionally in the manuscript
                                      Note

                                      Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.internetMedia.html b/gl/dev/ref-att.internetMedia.html index 262474026..8889cd40f 100644 --- a/gl/dev/ref-att.internetMedia.html +++ b/gl/dev/ref-att.internetMedia.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.internetMedia

                                      att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
                                      Moduletei
                                      Membersatt.media [binaryObject graphic media] ptr ref
                                      Attributes
                                      mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Example

                                      In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.

                                      <ref mimeType="application/tei+xml; charset=UTF-8"
                                       target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
                                      Note

                                      This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.internetMedia

                                      att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
                                      Moduletei
                                      Membersatt.media [binaryObject graphic media] ptr ref
                                      Attributes
                                      mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Example

                                      In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.

                                      <ref mimeType="application/tei+xml; charset=UTF-8"
                                       target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
                                      Note

                                      This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.interpLike.html b/gl/dev/ref-att.interpLike.html index 4c183007b..586e94fe9 100644 --- a/gl/dev/ref-att.interpLike.html +++ b/gl/dev/ref-att.interpLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.interpLike

                                      att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [17.2. Global Attributes for Simple Analyses]
                                      Moduletei
                                      Membersinterp interpGrp
                                      Attributes
                                      typeindicates what kind of phenomenon is being noted in the passage.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      image
                                      identifies an image in the passage.
                                      character
                                      identifies a character associated with the passage.
                                      theme
                                      identifies a theme in the passage.
                                      allusion
                                      identifies an allusion to another text.
                                      subtype(subtype) provides a sub-categorization of the phenomenon is being noted in the passage, if needed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

                                      inst(instances) points to instances of the analysis or interpretation represented by the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The current element should be an analytic one. The element pointed at should be a textual one.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.interpLike

                                      att.interpLike provides attributes for elements which represent a formal analysis or interpretation. [17.2. Global Attributes for Simple Analyses]
                                      Moduletei
                                      Membersinterp interpGrp
                                      Attributes
                                      typeindicates what kind of phenomenon is being noted in the passage.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      image
                                      identifies an image in the passage.
                                      character
                                      identifies a character associated with the passage.
                                      theme
                                      identifies a theme in the passage.
                                      allusion
                                      identifies an allusion to another text.
                                      subtype(subtype) provides a sub-categorization of the phenomenon is being noted in the passage, if needed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

                                      inst(instances) points to instances of the analysis or interpretation represented by the current element.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The current element should be an analytic one. The element pointed at should be a textual one.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.lexicographic.html b/gl/dev/ref-att.lexicographic.html index 8c3aa222c..c5432ed98 100644 --- a/gl/dev/ref-att.lexicographic.html +++ b/gl/dev/ref-att.lexicographic.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.lexicographic

                                      att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. [9.2. The Structure of Dictionary Entries]
                                      Moduledictionaries
                                      Membersform gen lang
                                      Attributesatt.datcat (@datcat, @valueDatcat, @targetDatcat) att.lexicographic.normalized (@norm, @orig)
                                      expand(expand) gives an expanded form of information presented more concisely in the dictionary
                                      Status Optional
                                      Datatype teidata.text
                                      <gramGrp>
                                       <pos expand="noun">n</pos>
                                      </gramGrp>
                                      split(split) gives the list of split values for a merged form
                                      Status Optional
                                      Datatype teidata.text
                                      value(value) gives a value which lacks any realization in the printed source text.
                                      Status Optional
                                      Datatype teidata.text
                                      location(location) indicates an anchor element typically elsewhere in the document, but possibly in another document, which is the original location of this component.
                                      Status Optional
                                      Datatype teidata.pointer
                                      mergedIn(merged into) gives a reference to another element, where the original appears as a merged form.
                                      Status Optional
                                      Datatype teidata.pointer
                                      opt(optional) indicates whether the element is optional or not
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Default false

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.lexicographic

                                      att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. [9.2. The Structure of Dictionary Entries]
                                      Moduledictionaries
                                      Membersform gen lang
                                      Attributesatt.datcat (@datcat, @valueDatcat, @targetDatcat) att.lexicographic.normalized (@norm, @orig)
                                      expand(expand) gives an expanded form of information presented more concisely in the dictionary
                                      Status Optional
                                      Datatype teidata.text
                                      <gramGrp>
                                       <pos expand="noun">n</pos>
                                      </gramGrp>
                                      split(split) gives the list of split values for a merged form
                                      Status Optional
                                      Datatype teidata.text
                                      value(value) gives a value which lacks any realization in the printed source text.
                                      Status Optional
                                      Datatype teidata.text
                                      location(location) indicates an anchor element typically elsewhere in the document, but possibly in another document, which is the original location of this component.
                                      Status Optional
                                      Datatype teidata.pointer
                                      mergedIn(merged into) gives a reference to another element, where the original appears as a merged form.
                                      Status Optional
                                      Datatype teidata.pointer
                                      opt(optional) indicates whether the element is optional or not
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Default false

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.lexicographic.normalized.html b/gl/dev/ref-att.lexicographic.normalized.html index 82227ca35..299918870 100644 --- a/gl/dev/ref-att.lexicographic.normalized.html +++ b/gl/dev/ref-att.lexicographic.normalized.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.lexicographic.normalized

                                      att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.
                                      Moduleanalysis
                                      Membersatt.lexicographic [form gen lang] att.linguistic [pc w]
                                      Attributes
                                      norm(normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form
                                      Status Optional
                                      Datatype teidata.text

                                      Normalization of part-of-speech information within a dictionary entry.

                                      <gramGrp>
                                       <pos norm="noun">n</pos>
                                      </gramGrp>

                                      Normalization of a source form in a tokenized historical corpus.

                                      <s>
                                       <w>for</w>
                                       <w norm="virtue's">vertues</w>
                                       <w>sake</w>
                                      </s>
                                      <s>
                                       <w norm="persuasion">perswasion</w>
                                       <w>of</w>
                                       <w norm="Unity">Vnitie</w>
                                      </s>

                                      Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.

                                      <s>
                                       <w norm="freiwillig">freywillig</w>
                                       <pc norm=",join="left">/</pc>
                                       <w norm="unbedrängt">vnbedraͤngt</w>
                                       <w norm="und">vnd</w>
                                       <w norm="unverhindert">vnuerhindert</w>
                                      </s>
                                      <w norm="Teil">Theyll</w>
                                      <w norm="Freude">Frewde</w>
                                      orig(original) gives the original string or is the empty string when the element does not appear in the source text.
                                      Status Optional
                                      Datatype teidata.text

                                      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 like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:

                                      <w orig="ntsa sia'i">ntsasia'i</w>

                                      Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:

                                      <w lemma="hepos="pns"
                                       xml:id="b1afj-003-a-0950">
                                      he</w>
                                      <w lemma="havepos="vvz"
                                       xml:id="b1afj-003-a-0960">
                                      hath</w>
                                      <w lemma="bringpos="vvn"
                                       xml:id="b1afj-003-a-0970">
                                      brought</w>
                                      <w lemma="forthpos="av"
                                       xml:id="b1afj-003-a-0980orig="sorth">
                                      forth</w>

                                      An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:

                                      <w lemma="commandmentpos="n1"
                                       norm="commandmentxml:id="b9avr-018-a-7720"
                                       orig="commandemēt">
                                      commandement</w>
                                      Note

                                      It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on choice, orig, and reg needs to be employed.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.lexicographic.normalized

                                      att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.
                                      Moduleanalysis
                                      Membersatt.lexicographic [form gen lang] att.linguistic [pc w]
                                      Attributes
                                      norm(normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form
                                      Status Optional
                                      Datatype teidata.text

                                      Normalization of part-of-speech information within a dictionary entry.

                                      <gramGrp>
                                       <pos norm="noun">n</pos>
                                      </gramGrp>

                                      Normalization of a source form in a tokenized historical corpus.

                                      <s>
                                       <w>for</w>
                                       <w norm="virtue's">vertues</w>
                                       <w>sake</w>
                                      </s>
                                      <s>
                                       <w norm="persuasion">perswasion</w>
                                       <w>of</w>
                                       <w norm="Unity">Vnitie</w>
                                      </s>

                                      Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.

                                      <s>
                                       <w norm="freiwillig">freywillig</w>
                                       <pc norm=",join="left">/</pc>
                                       <w norm="unbedrängt">vnbedraͤngt</w>
                                       <w norm="und">vnd</w>
                                       <w norm="unverhindert">vnuerhindert</w>
                                      </s>
                                      <w norm="Teil">Theyll</w>
                                      <w norm="Freude">Frewde</w>
                                      orig(original) gives the original string or is the empty string when the element does not appear in the source text.
                                      Status Optional
                                      Datatype teidata.text

                                      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 like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:

                                      <w orig="ntsa sia'i">ntsasia'i</w>

                                      Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:

                                      <w lemma="hepos="pns"
                                       xml:id="b1afj-003-a-0950">
                                      he</w>
                                      <w lemma="havepos="vvz"
                                       xml:id="b1afj-003-a-0960">
                                      hath</w>
                                      <w lemma="bringpos="vvn"
                                       xml:id="b1afj-003-a-0970">
                                      brought</w>
                                      <w lemma="forthpos="av"
                                       xml:id="b1afj-003-a-0980orig="sorth">
                                      forth</w>

                                      An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:

                                      <w lemma="commandmentpos="n1"
                                       norm="commandmentxml:id="b9avr-018-a-7720"
                                       orig="commandemēt">
                                      commandement</w>
                                      Note

                                      It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on choice, orig, and reg needs to be employed.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.linguistic.html b/gl/dev/ref-att.linguistic.html index 1674bc324..16294813e 100644 --- a/gl/dev/ref-att.linguistic.html +++ b/gl/dev/ref-att.linguistic.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.linguistic

                                      att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and pc in the analysis module. [17.4.2. Lightweight Linguistic Annotation]
                                      Moduleanalysis
                                      Memberspc w
                                      Attributesatt.lexicographic.normalized (@norm, @orig)
                                      lemmaprovides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
                                      Status Optional
                                      Datatype teidata.text
                                      <w lemma="wife">wives</w>
                                      <w lemma="Arznei">Artzeneyen</w>
                                      lemmaRefprovides a pointer to a definition of the lemma for the word, for example in an online lexicon.
                                      Status Optional
                                      Datatype teidata.pointer
                                      <w type="verblemma="hit"
                                       lemmaRef="http://www.example.com/lexicon/hitvb.xml">
                                      hitt<m type="suffix">ing</m>
                                      </w>
                                      pos(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.).
                                      Status Optional
                                      Datatype teidata.text

                                      The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).

                                      <s>
                                       <w pos="PPER">Wir</w>
                                       <w pos="VVFIN">fahren</w>
                                       <w pos="APPR">in</w>
                                       <w pos="ART">den</w>
                                       <w pos="NN">Urlaub</w>
                                       <w pos="$.">.</w>
                                      </s>

                                      The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).

                                      <p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p> -        

                                      The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.

                                      <p>
                                       <w pos="PPIS2">We</w>
                                       <w pos="VBR">'re</w>
                                       <w pos="VVG">going</w>
                                       <w pos="II">on</w>
                                       <w pos="NN1">vacation</w>
                                       <w pos="II">to</w>
                                       <w pos="NP1">Brazil</w>
                                       <w pos="IF">for</w>
                                       <w pos="AT1">a</w>
                                       <w pos="NNT1">month</w>
                                       <pc pos="!">!</pc>
                                      </p>
                                      msd(morphosyntactic description) supplies 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).
                                      Status Optional
                                      Datatype teidata.text
                                      <ab>
                                       <w pos="PPERmsd="1.Pl.*.Nom">Wir</w>
                                       <w pos="VVFINmsd="1.Pl.Pres.Ind">fahren</w>
                                       <w pos="APPRmsd="--">in</w>
                                       <w pos="ARTmsd="Def.Masc.Akk.Sg">den</w>
                                       <w pos="NNmsd="Masc.Akk.Sg">Urlaub</w>
                                       <pc pos="$.msd="--">.</pc>
                                      </ab>
                                      joinwhen present, provides information on whether the token in question is adjacent to another, and if so, on which side.
                                      Status Optional
                                      Datatype teidata.text
                                      Legal values are:
                                      no
                                      the token is not adjacent to another
                                      left
                                      there is no whitespace on the left side of the token
                                      right
                                      there is no whitespace on the right side of the token
                                      both
                                      there is no whitespace on either side of the token
                                      overlap
                                      the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream

                                      The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.

                                      <s>
                                       <pc join="right">"</pc>
                                       <w join="left">Friends</w>
                                       <w>will</w>
                                       <w>be</w>
                                       <w join="right">friends</w>
                                       <pc join="both">.</pc>
                                       <pc join="left">"</pc>
                                      </s>

                                      Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.

                                      The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.

                                      <p>
                                       <w pos="PNP">We</w>
                                       <w pos="VBBjoin="left">'re</w>
                                       <w pos="VVG">going</w>
                                       <w pos="PRP">on</w>
                                       <w pos="NN1">vacation</w>
                                       <pc pos="PUNjoin="left">.</pc>
                                      </p>
                                      Note

                                      The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.

                                      Note

                                      These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.linguistic

                                      att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and pc in the analysis module. [17.4.2. Lightweight Linguistic Annotation]
                                      Moduleanalysis
                                      Memberspc w
                                      Attributesatt.lexicographic.normalized (@norm, @orig)
                                      lemmaprovides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
                                      Status Optional
                                      Datatype teidata.text
                                      <w lemma="wife">wives</w>
                                      <w lemma="Arznei">Artzeneyen</w>
                                      lemmaRefprovides a pointer to a definition of the lemma for the word, for example in an online lexicon.
                                      Status Optional
                                      Datatype teidata.pointer
                                      <w type="verblemma="hit"
                                       lemmaRef="http://www.example.com/lexicon/hitvb.xml">
                                      hitt<m type="suffix">ing</m>
                                      </w>
                                      pos(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.).
                                      Status Optional
                                      Datatype teidata.text

                                      The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).

                                      <s>
                                       <w pos="PPER">Wir</w>
                                       <w pos="VVFIN">fahren</w>
                                       <w pos="APPR">in</w>
                                       <w pos="ART">den</w>
                                       <w pos="NN">Urlaub</w>
                                       <w pos="$.">.</w>
                                      </s>

                                      The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).

                                      <p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p> +        

                                      The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.

                                      <p>
                                       <w pos="PPIS2">We</w>
                                       <w pos="VBR">'re</w>
                                       <w pos="VVG">going</w>
                                       <w pos="II">on</w>
                                       <w pos="NN1">vacation</w>
                                       <w pos="II">to</w>
                                       <w pos="NP1">Brazil</w>
                                       <w pos="IF">for</w>
                                       <w pos="AT1">a</w>
                                       <w pos="NNT1">month</w>
                                       <pc pos="!">!</pc>
                                      </p>
                                      msd(morphosyntactic description) supplies 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).
                                      Status Optional
                                      Datatype teidata.text
                                      <ab>
                                       <w pos="PPERmsd="1.Pl.*.Nom">Wir</w>
                                       <w pos="VVFINmsd="1.Pl.Pres.Ind">fahren</w>
                                       <w pos="APPRmsd="--">in</w>
                                       <w pos="ARTmsd="Def.Masc.Akk.Sg">den</w>
                                       <w pos="NNmsd="Masc.Akk.Sg">Urlaub</w>
                                       <pc pos="$.msd="--">.</pc>
                                      </ab>
                                      joinwhen present, provides information on whether the token in question is adjacent to another, and if so, on which side.
                                      Status Optional
                                      Datatype teidata.text
                                      Legal values are:
                                      no
                                      the token is not adjacent to another
                                      left
                                      there is no whitespace on the left side of the token
                                      right
                                      there is no whitespace on the right side of the token
                                      both
                                      there is no whitespace on either side of the token
                                      overlap
                                      the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream

                                      The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.

                                      <s>
                                       <pc join="right">"</pc>
                                       <w join="left">Friends</w>
                                       <w>will</w>
                                       <w>be</w>
                                       <w join="right">friends</w>
                                       <pc join="both">.</pc>
                                       <pc join="left">"</pc>
                                      </s>

                                      Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.

                                      The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.

                                      <p>
                                       <w pos="PNP">We</w>
                                       <w pos="VBBjoin="left">'re</w>
                                       <w pos="VVG">going</w>
                                       <w pos="PRP">on</w>
                                       <w pos="NN1">vacation</w>
                                       <pc pos="PUNjoin="left">.</pc>
                                      </p>
                                      Note

                                      The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.

                                      Note

                                      These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 17.4.2. Lightweight Linguistic Annotation for discussion.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.locatable.html b/gl/dev/ref-att.locatable.html index cfee38982..f44083268 100644 --- a/gl/dev/ref-att.locatable.html +++ b/gl/dev/ref-att.locatable.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.locatable

                                      att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 13.3.4.3. States, Traits, and Events]
                                      Moduletei
                                      Membersconversion event
                                      Attributes
                                      whereindicates one or more locations by pointing to a place element or other canonical description.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.locatable

                                      att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 13.3.4.3. States, Traits, and Events]
                                      Moduletei
                                      Membersconversion event
                                      Attributes
                                      whereindicates one or more locations by pointing to a place element or other canonical description.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.measurement.html b/gl/dev/ref-att.measurement.html index c58420eec..c77199633 100644 --- a/gl/dev/ref-att.measurement.html +++ b/gl/dev/ref-att.measurement.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.measurement

                                      att.measurement provides attributes to represent a regularized or normalized measurement.
                                      Moduletei
                                      Membersmeasure measureGrp unit
                                      Attributes
                                      unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      m
                                      (metre) SI base unit of length
                                      kg
                                      (kilogram) SI base unit of mass
                                      s
                                      (second) SI base unit of time
                                      Hz
                                      (hertz) SI unit of frequency
                                      Pa
                                      (pascal) SI unit of pressure or stress
                                      Ω
                                      (ohm) SI unit of electric resistance
                                      L
                                      (litre) 1 dm³
                                      t
                                      (tonne) 10³ kg
                                      ha
                                      (hectare) 1 hm²
                                      Å
                                      (ångström) 10⁻¹⁰ m
                                      mL
                                      (millilitre)
                                      cm
                                      (centimetre)
                                      dB
                                      (decibel) see remarks, below
                                      kbit
                                      (kilobit) 10³ or 1000 bits
                                      Kibit
                                      (kibibit) 2¹⁰ or 1024 bits
                                      kB
                                      (kilobyte) 10³ or 1000 bytes
                                      KiB
                                      (kibibyte) 2¹⁰ or 1024 bytes
                                      MB
                                      (megabyte) 10⁶ or 1 000 000 bytes
                                      MiB
                                      (mebibyte) 2²⁰ or 1 048 576 bytes
                                      Note

                                      If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

                                      Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

                                      unitRefpoints to a unique identifier stored in the xml:id of a unitDef element that defines a unit of measure.
                                      Status Optional
                                      Datatype teidata.pointer
                                      quantity(quantity) specifies the number of the specified units that comprise the measurement
                                      Status Optional
                                      Datatype teidata.numeric
                                      commodity(commodity) indicates the substance that is being measured
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Note

                                      In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

                                      Schematron

                                      <sch:rule context="tei:*[@unitRef]">
                                      <sch:report test="@unitrole="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report>
                                      </sch:rule>
                                      Note
                                      This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
                                      <l>So weren't you gonna buy <measure quantity="0.5unit="gal"
                                        commodity="ice cream">
                                      half
                                         a gallon</measure>, baby</l>
                                      <l>So won't you go and buy <measure quantity="1.893unit="L"
                                        commodity="ice cream">
                                      half
                                         a gallon</measure>, baby?</l>

                                      The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.measurement

                                      att.measurement provides attributes to represent a regularized or normalized measurement.
                                      Moduletei
                                      Membersmeasure measureGrp unit
                                      Attributes
                                      unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      m
                                      (metre) SI base unit of length
                                      kg
                                      (kilogram) SI base unit of mass
                                      s
                                      (second) SI base unit of time
                                      Hz
                                      (hertz) SI unit of frequency
                                      Pa
                                      (pascal) SI unit of pressure or stress
                                      Ω
                                      (ohm) SI unit of electric resistance
                                      L
                                      (litre) 1 dm³
                                      t
                                      (tonne) 10³ kg
                                      ha
                                      (hectare) 1 hm²
                                      Å
                                      (ångström) 10⁻¹⁰ m
                                      mL
                                      (millilitre)
                                      cm
                                      (centimetre)
                                      dB
                                      (decibel) see remarks, below
                                      kbit
                                      (kilobit) 10³ or 1000 bits
                                      Kibit
                                      (kibibit) 2¹⁰ or 1024 bits
                                      kB
                                      (kilobyte) 10³ or 1000 bytes
                                      KiB
                                      (kibibyte) 2¹⁰ or 1024 bytes
                                      MB
                                      (megabyte) 10⁶ or 1 000 000 bytes
                                      MiB
                                      (mebibyte) 2²⁰ or 1 048 576 bytes
                                      Note

                                      If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

                                      Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

                                      unitRefpoints to a unique identifier stored in the xml:id of a unitDef element that defines a unit of measure.
                                      Status Optional
                                      Datatype teidata.pointer
                                      quantity(quantity) specifies the number of the specified units that comprise the measurement
                                      Status Optional
                                      Datatype teidata.numeric
                                      commodity(commodity) indicates the substance that is being measured
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Note

                                      In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

                                      Schematron

                                      <sch:rule context="tei:*[@unitRef]">
                                      <sch:report test="@unitrole="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report>
                                      </sch:rule>
                                      Note
                                      This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
                                      <l>So weren't you gonna buy <measure quantity="0.5unit="gal"
                                        commodity="ice cream">
                                      half
                                         a gallon</measure>, baby</l>
                                      <l>So won't you go and buy <measure quantity="1.893unit="L"
                                        commodity="ice cream">
                                      half
                                         a gallon</measure>, baby?</l>

                                      The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.media.html b/gl/dev/ref-att.media.html index ad64ab2fc..45b461c6d 100644 --- a/gl/dev/ref-att.media.html +++ b/gl/dev/ref-att.media.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.media

                                      att.media provides attributes for specifying display and related properties of external media.
                                      Moduletei
                                      MembersbinaryObject graphic media
                                      Attributesatt.internetMedia (@mimeType)
                                      widthWhere the media are displayed, indicates the display width
                                      Status Optional
                                      Datatype teidata.outputMeasurement
                                      heightWhere the media are displayed, indicates the display height
                                      Status Optional
                                      Datatype teidata.outputMeasurement
                                      scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
                                      Status Optional
                                      Datatype teidata.numeric

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.media

                                      att.media provides attributes for specifying display and related properties of external media.
                                      Moduletei
                                      MembersbinaryObject graphic media
                                      Attributesatt.internetMedia (@mimeType)
                                      widthWhere the media are displayed, indicates the display width
                                      Status Optional
                                      Datatype teidata.outputMeasurement
                                      heightWhere the media are displayed, indicates the display height
                                      Status Optional
                                      Datatype teidata.outputMeasurement
                                      scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
                                      Status Optional
                                      Datatype teidata.numeric

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.metrical.html b/gl/dev/ref-att.metrical.html index 5308f74fc..1d3fe95bb 100644 --- a/gl/dev/ref-att.metrical.html +++ b/gl/dev/ref-att.metrical.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.metrical

                                      att.metrical defines a set of attributes that certain elements may use to represent metrical information. [6.4. Rhyme and Metrical Analysis]
                                      Moduleverse
                                      Membersatt.divLike [div lg] att.segLike [c m pc phr s seg w] l
                                      Attributes
                                      met(metrical structure, conventional) contains a user-specified encoding for the conventional metrical structure of the element.
                                      Status Recommended
                                      Datatype token
                                      Note

                                      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 notation used should be documented by a <metDecl> element within the encodingDesc of the associated header.

                                      Where this attribute is not specified, the metrical pattern for the element concerned is understood to be inherited from its parent.

                                      real(metrical structure, realized) contains a user-specified encoding for the actual realization of the conventional metrical structure applicable to the element.
                                      Status Optional
                                      Datatype token
                                      Note

                                      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 notation used should be documented by a <metDecl> element within the encodingDesc of the associated header.

                                      Where this attribute is not specified, the metrical realization for the element concerned is understood to be identical to that specified or implied for the met attribute.

                                      rhyme(rhyme scheme) specifies the rhyme scheme applicable to a group of verse lines.
                                      Status Recommended
                                      Datatype token
                                      Note

                                      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 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 user-defined alternative notations.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.metrical

                                      att.metrical defines a set of attributes that certain elements may use to represent metrical information. [6.4. Rhyme and Metrical Analysis]
                                      Moduleverse
                                      Membersatt.divLike [div lg] att.segLike [c m pc phr s seg w] l
                                      Attributes
                                      met(metrical structure, conventional) contains a user-specified encoding for the conventional metrical structure of the element.
                                      Status Recommended
                                      Datatype token
                                      Note

                                      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 notation used should be documented by a <metDecl> element within the encodingDesc of the associated header.

                                      Where this attribute is not specified, the metrical pattern for the element concerned is understood to be inherited from its parent.

                                      real(metrical structure, realized) contains a user-specified encoding for the actual realization of the conventional metrical structure applicable to the element.
                                      Status Optional
                                      Datatype token
                                      Note

                                      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 notation used should be documented by a <metDecl> element within the encodingDesc of the associated header.

                                      Where this attribute is not specified, the metrical realization for the element concerned is understood to be identical to that specified or implied for the met attribute.

                                      rhyme(rhyme scheme) specifies the rhyme scheme applicable to a group of verse lines.
                                      Status Recommended
                                      Datatype token
                                      Note

                                      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 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 user-defined alternative notations.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.milestoneUnit.html b/gl/dev/ref-att.milestoneUnit.html index 460267946..df1331777 100644 --- a/gl/dev/ref-att.milestoneUnit.html +++ b/gl/dev/ref-att.milestoneUnit.html @@ -22,4 +22,4 @@ }); });

                                      att.milestoneUnit

                                      att.milestoneUnit provides attributes to indicate the type of section which is changing at a specific milestone. [3.11.3. Milestone -Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
                                      Modulecore
                                      Membersmilestone refState
                                      Attributes
                                      unitprovides a conventional name for the kind of section changing at this milestone.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      page
                                      physical page breaks (synonymous with the pb element).
                                      column
                                      column breaks.
                                      line
                                      line breaks (synonymous with the lb element).
                                      book
                                      any units termed book, liber, etc.
                                      poem
                                      individual poems in a collection.
                                      canto
                                      cantos or other major sections of a poem.
                                      speaker
                                      changes of speaker or narrator.
                                      stanza
                                      stanzas within a poem, book, or canto.
                                      act
                                      acts within a play.
                                      scene
                                      scenes within a play or act.
                                      section
                                      sections of any kind.
                                      absent
                                      passages not present in the reference edition.
                                      unnumbered
                                      passages present in the text, but not to be included as part of the reference.
                                      <milestone n="23ed="Launit="Dreissiger"/>
                                      ... <milestone n="24ed="AVunit="verse"/> ...
                                      Note

                                      If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next milestone tag for the edition in question 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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]ModulecoreMembersmilestone refStateAttributes
                                      unitprovides a conventional name for the kind of section changing at this milestone.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      page
                                      physical page breaks (synonymous with the pb element).
                                      column
                                      column breaks.
                                      line
                                      line breaks (synonymous with the lb element).
                                      book
                                      any units termed book, liber, etc.
                                      poem
                                      individual poems in a collection.
                                      canto
                                      cantos or other major sections of a poem.
                                      speaker
                                      changes of speaker or narrator.
                                      stanza
                                      stanzas within a poem, book, or canto.
                                      act
                                      acts within a play.
                                      scene
                                      scenes within a play or act.
                                      section
                                      sections of any kind.
                                      absent
                                      passages not present in the reference edition.
                                      unnumbered
                                      passages present in the text, but not to be included as part of the reference.
                                      <milestone n="23ed="Launit="Dreissiger"/>
                                      ... <milestone n="24ed="AVunit="verse"/> ...
                                      Note

                                      If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next milestone tag for the edition in question 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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.msClass.html b/gl/dev/ref-att.msClass.html index 2c71d534b..f32dc47b9 100644 --- a/gl/dev/ref-att.msClass.html +++ b/gl/dev/ref-att.msClass.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.msClass

                                      att.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      MembersmsContents msItem msItemStruct
                                      Attributes
                                      classidentifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.msClass

                                      att.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      MembersmsContents msItem msItemStruct
                                      Attributes
                                      classidentifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.msExcerpt.html b/gl/dev/ref-att.msExcerpt.html index 6ac912b41..0722ef747 100644 --- a/gl/dev/ref-att.msExcerpt.html +++ b/gl/dev/ref-att.msExcerpt.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.msExcerpt

                                      att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content]
                                      Modulemsdescription
                                      Memberscolophon explicit finalRubric incipit msContents msItem msItemStruct quote rubric
                                      Attributes
                                      defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Note

                                      In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.msExcerpt

                                      att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content]
                                      Modulemsdescription
                                      Memberscolophon explicit finalRubric incipit msContents msItem msItemStruct quote rubric
                                      Attributes
                                      defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Note

                                      In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.naming.html b/gl/dev/ref-att.naming.html index 7371f221f..f1dbb61fb 100644 --- a/gl/dev/ref-att.naming.html +++ b/gl/dev/ref-att.naming.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.naming

                                      att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms]
                                      Moduletei
                                      Membersatt.personal [addName forename genName name objectName orgName persName placeName roleName surname] author birth bloc collection country death district editor event geogFeat geogName institution offset origPlace pubPlace region repository rs settlement state
                                      Attributesatt.canonical (@key, @ref)
                                      rolemay 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.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.naming

                                      att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms]
                                      Moduletei
                                      Membersatt.personal [addName forename genName name objectName orgName persName placeName roleName surname] author birth bloc collection country death district editor event geogFeat geogName institution offset origPlace pubPlace region repository rs settlement state
                                      Attributesatt.canonical (@key, @ref)
                                      rolemay 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.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.notated.html b/gl/dev/ref-att.notated.html index 83d04de81..48e775684 100644 --- a/gl/dev/ref-att.notated.html +++ b/gl/dev/ref-att.notated.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.notated

                                      att.notated provides attributes to indicate any specialised notation used for element content.
                                      Moduletei
                                      Membersc listAnnotation m phr quote s seg w
                                      Attributes
                                      notationnames the notation used for the content of the element.
                                      Status Optional
                                      Datatype teidata.enumerated

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.notated

                                      att.notated provides attributes to indicate any specialised notation used for element content.
                                      Moduletei
                                      Membersc listAnnotation m phr quote s seg w
                                      Attributes
                                      notationnames the notation used for the content of the element.
                                      Status Optional
                                      Datatype teidata.enumerated

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.patternReplacement.html b/gl/dev/ref-att.patternReplacement.html index e1a0d84bd..bee06bcb6 100644 --- a/gl/dev/ref-att.patternReplacement.html +++ b/gl/dev/ref-att.patternReplacement.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.patternReplacement

                                      att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
                                      Moduleheader
                                      MemberscRefPattern prefixDef
                                      Attributes
                                      matchPatternspecifies a regular expression against which the values of other attributes can be matched.
                                      Status Required
                                      Datatype teidata.pattern
                                      Note

                                      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 replacementPattern attribute.

                                      replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
                                      Status Required
                                      Datatype teidata.replacement
                                      Note

                                      The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

                                      If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.patternReplacement

                                      att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
                                      Moduleheader
                                      MemberscRefPattern prefixDef
                                      Attributes
                                      matchPatternspecifies a regular expression against which the values of other attributes can be matched.
                                      Status Required
                                      Datatype teidata.pattern
                                      Note

                                      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 replacementPattern attribute.

                                      replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
                                      Status Required
                                      Datatype teidata.replacement
                                      Note

                                      The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

                                      If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.personal.html b/gl/dev/ref-att.personal.html index 0f6e4ab3d..e5cc61873 100644 --- a/gl/dev/ref-att.personal.html +++ b/gl/dev/ref-att.personal.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.personal

                                      att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
                                      Moduletei
                                      MembersaddName forename genName name objectName orgName persName placeName roleName surname
                                      Attributesatt.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      yes
                                      (yes) the name component is spelled out in full. [Default]
                                      abb
                                      (abbreviated) the name component is given in an abbreviated form.
                                      init
                                      (initial letter) the name component is indicated only by one initial.
                                      sort(sort) specifies the sort order of the name component in relation to others within the name.
                                      Status Optional
                                      Datatype teidata.count

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.personal

                                      att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
                                      Moduletei
                                      MembersaddName forename genName name objectName orgName persName placeName roleName surname
                                      Attributesatt.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      yes
                                      (yes) the name component is spelled out in full. [Default]
                                      abb
                                      (abbreviated) the name component is given in an abbreviated form.
                                      init
                                      (initial letter) the name component is indicated only by one initial.
                                      sort(sort) specifies the sort order of the name component in relation to others within the name.
                                      Status Optional
                                      Datatype teidata.count

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.placement.html b/gl/dev/ref-att.placement.html index 2267f5c16..cb5bf7f2d 100644 --- a/gl/dev/ref-att.placement.html +++ b/gl/dev/ref-att.placement.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.placement

                                      att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]
                                      Moduletei
                                      Membersadd addSpan figure fw head label metamark notatedMusic note noteGrp rt stage
                                      Attributes
                                      placespecifies where this item is placed.
                                      Status Recommended
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      top
                                      at the top of the page
                                      bottom
                                      at the foot of the page
                                      margin
                                      in the margin (left, right, or both)
                                      opposite
                                      on the opposite, i.e. facing, page
                                      overleaf
                                      on the other side of the leaf
                                      above
                                      above the line
                                      right
                                      to the right, e.g. to the right of a vertical line of text, or to the right of a figure
                                      below
                                      below the line
                                      left
                                      to the left, e.g. to the left of a vertical line of text, or to the left of a figure
                                      end
                                      at the end of e.g. chapter or volume.
                                      inline
                                      within the body of the text.
                                      inspace
                                      in a predefined space, for example left by an earlier scribe.
                                      <add place="margin">[An addition written in the margin]</add>
                                      <add place="bottom opposite">[An addition written at the
                                      foot of the current page and also on the facing page]</add>
                                      <note place="bottom">Ibid, p.7</note>

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.placement

                                      att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]
                                      Moduletei
                                      Membersadd addSpan figure fw head label metamark notatedMusic note noteGrp rt stage
                                      Attributes
                                      placespecifies where this item is placed.
                                      Status Recommended
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      top
                                      at the top of the page
                                      bottom
                                      at the foot of the page
                                      margin
                                      in the margin (left, right, or both)
                                      opposite
                                      on the opposite, i.e. facing, page
                                      overleaf
                                      on the other side of the leaf
                                      above
                                      above the line
                                      right
                                      to the right, e.g. to the right of a vertical line of text, or to the right of a figure
                                      below
                                      below the line
                                      left
                                      to the left, e.g. to the left of a vertical line of text, or to the left of a figure
                                      end
                                      at the end of e.g. chapter or volume.
                                      inline
                                      within the body of the text.
                                      inspace
                                      in a predefined space, for example left by an earlier scribe.
                                      <add place="margin">[An addition written in the margin]</add>
                                      <add place="bottom opposite">[An addition written at the
                                      foot of the current page and also on the facing page]</add>
                                      <note place="bottom">Ibid, p.7</note>

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.pointing.group.html b/gl/dev/ref-att.pointing.group.html index d32381a9e..ee51dfb41 100644 --- a/gl/dev/ref-att.pointing.group.html +++ b/gl/dev/ref-att.pointing.group.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.pointing.group

                                      att.pointing.group provides a set of attributes common to all elements which enclose groups of pointer elements. [16. Linking, Segmentation, and Alignment]
                                      Moduletei
                                      MemberslinkGrp
                                      Attributesatt.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      domainsoptionally specifies the identifiers of the elements within which all elements indicated by the contents of this element lie.
                                      Status Optional
                                      Datatype 2–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      If this attribute is supplied every element specified as a target must be contained within the element or elements named by it. An application may choose whether or not to report failures to satisfy this constraint as errors, but may not access an element of the right identifier but in the wrong context. If this attribute is not supplied, then target elements may appear anywhere within the target document.

                                      targFunc(target function) describes the function of each of the values of the target attribute of the enclosed link, join, or <alt> tags.
                                      Status Optional
                                      Datatype 2–∞ occurrences of teidata.word separated by whitespace
                                      Note

                                      The number of separate values must match the number of values in the target attribute in the enclosed link, join, or <alt> tags (an intermediate ptr element may be needed to accomplish this). It should also match the number of values in the domains attribute, of the current element, if one has been specified.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.pointing.group

                                      att.pointing.group provides a set of attributes common to all elements which enclose groups of pointer elements. [16. Linking, Segmentation, and Alignment]
                                      Moduletei
                                      MemberslinkGrp
                                      Attributesatt.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      domainsoptionally specifies the identifiers of the elements within which all elements indicated by the contents of this element lie.
                                      Status Optional
                                      Datatype 2–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      If this attribute is supplied every element specified as a target must be contained within the element or elements named by it. An application may choose whether or not to report failures to satisfy this constraint as errors, but may not access an element of the right identifier but in the wrong context. If this attribute is not supplied, then target elements may appear anywhere within the target document.

                                      targFunc(target function) describes the function of each of the values of the target attribute of the enclosed link, join, or <alt> tags.
                                      Status Optional
                                      Datatype 2–∞ occurrences of teidata.word separated by whitespace
                                      Note

                                      The number of separate values must match the number of values in the target attribute in the enclosed link, join, or <alt> tags (an intermediate ptr element may be needed to accomplish this). It should also match the number of values in the domains attribute, of the current element, if one has been specified.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.pointing.html b/gl/dev/ref-att.pointing.html index fe297e45d..a4437b5ec 100644 --- a/gl/dev/ref-att.pointing.html +++ b/gl/dev/ref-att.pointing.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.pointing

                                      att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
                                      Moduletei
                                      Membersatt.pointing.group [linkGrp] annotation calendar catRef citedRange gloss join licence link locus note noteGrp ptr ref substJoin term
                                      Attributes
                                      targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
                                      Status Optional
                                      Datatype teidata.language
                                      Schematron

                                      <sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
                                      <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
                                      </sch:rule>
                                      <linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
                                       <ptr xml:id="pol-swh_aln_2.1.1-ptr"
                                        target="pol/UDHR/text.xml#pol_txt_1-headtype="tuvtargetLang="pl"/>

                                       <ptr xml:id="pol-swh_aln_2.1.2-ptr"
                                        target="swh/UDHR/text.xml#swh_txt_1-headtype="tuvtargetLang="sw"/>

                                      </linkGrp>

                                      In the example above, the linkGrp combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.

                                      Note

                                      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 the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

                                      targetspecifies the destination of the reference by supplying one or more URI References
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      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.

                                      evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      all
                                      if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
                                      one
                                      if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
                                      none
                                      no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
                                      Note

                                      If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.pointing

                                      att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
                                      Moduletei
                                      Membersatt.pointing.group [linkGrp] annotation calendar catRef citedRange gloss join licence link locus note noteGrp ptr ref substJoin term
                                      Attributes
                                      targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
                                      Status Optional
                                      Datatype teidata.language
                                      Schematron

                                      <sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
                                      <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
                                      </sch:rule>
                                      <linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
                                       <ptr xml:id="pol-swh_aln_2.1.1-ptr"
                                        target="pol/UDHR/text.xml#pol_txt_1-headtype="tuvtargetLang="pl"/>

                                       <ptr xml:id="pol-swh_aln_2.1.2-ptr"
                                        target="swh/UDHR/text.xml#swh_txt_1-headtype="tuvtargetLang="sw"/>

                                      </linkGrp>

                                      In the example above, the linkGrp combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.

                                      Note

                                      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 the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

                                      targetspecifies the destination of the reference by supplying one or more URI References
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      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.

                                      evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      all
                                      if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
                                      one
                                      if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
                                      none
                                      no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
                                      Note

                                      If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.ranging.html b/gl/dev/ref-att.ranging.html index 5ca022daa..56fd7d03f 100644 --- a/gl/dev/ref-att.ranging.html +++ b/gl/dev/ref-att.ranging.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.ranging

                                      att.ranging provides attributes for describing numerical ranges.
                                      Moduletei
                                      Membersatt.dimensions [att.damaged [damage] add addSpan birth date death del delSpan depth dim dimensions ellipsis ex floruit gap geogFeat height mod offset origDate redo retrace secl space state subst substJoin supplied surplus time unclear undo width] measure num precision
                                      Attributes
                                      atLeastgives a minimum estimated value for the approximate measurement.
                                      Status Optional
                                      Datatype teidata.numeric
                                      atMostgives a maximum estimated value for the approximate measurement.
                                      Status Optional
                                      Datatype teidata.numeric
                                      minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
                                      Status Optional
                                      Datatype teidata.numeric
                                      maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
                                      Status Optional
                                      Datatype teidata.numeric
                                      confidencespecifies 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.
                                      Status Optional
                                      Datatype teidata.probability
                                      Example
                                      The MS. was lost in transmission by mail from <del rend="overstrike">
                                       <gap reason="illegible"
                                        extent="one or two lettersatLeast="1atMost="2unit="chars"/>

                                      </del> Philadelphia to the Graphic office, New York.
                                      Example
                                      Americares has been supporting the health sector in Eastern
                                      Europe since 1986, and since 1992 has provided <measure atLeast="120000000unit="USD"
                                       commodity="currency">
                                      more than
                                      $120m</measure> in aid to Ukrainians.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.ranging

                                      att.ranging provides attributes for describing numerical ranges.
                                      Moduletei
                                      Membersatt.dimensions [att.damaged [damage] add addSpan birth date death del delSpan depth dim dimensions ellipsis ex floruit gap geogFeat height mod offset origDate redo retrace secl space state subst substJoin supplied surplus time unclear undo width] measure num precision
                                      Attributes
                                      atLeastgives a minimum estimated value for the approximate measurement.
                                      Status Optional
                                      Datatype teidata.numeric
                                      atMostgives a maximum estimated value for the approximate measurement.
                                      Status Optional
                                      Datatype teidata.numeric
                                      minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
                                      Status Optional
                                      Datatype teidata.numeric
                                      maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
                                      Status Optional
                                      Datatype teidata.numeric
                                      confidencespecifies 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.
                                      Status Optional
                                      Datatype teidata.probability
                                      Example
                                      The MS. was lost in transmission by mail from <del rend="overstrike">
                                       <gap reason="illegible"
                                        extent="one or two lettersatLeast="1atMost="2unit="chars"/>

                                      </del> Philadelphia to the Graphic office, New York.
                                      Example
                                      Americares has been supporting the health sector in Eastern
                                      Europe since 1986, and since 1992 has provided <measure atLeast="120000000unit="USD"
                                       commodity="currency">
                                      more than
                                      $120m</measure> in aid to Ukrainians.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.rdgPart.html b/gl/dev/ref-att.rdgPart.html index 602eaada8..cbab38557 100644 --- a/gl/dev/ref-att.rdgPart.html +++ b/gl/dev/ref-att.rdgPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.rdgPart

                                      att.rdgPart provides attributes to mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. Fragmentary Witnesses]
                                      Moduletextcrit
                                      Memberswit
                                      Attributes
                                      wit(witness or witnesses) contains a space-delimited list of one or more sigla indicating the witnesses to this reading beginning or ending at this point.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      These elements may appear anywhere within the elements lem and rdg, and also within any of their constituent elements.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.rdgPart

                                      att.rdgPart provides attributes to mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. Fragmentary Witnesses]
                                      Moduletextcrit
                                      Memberswit
                                      Attributes
                                      wit(witness or witnesses) contains a space-delimited list of one or more sigla indicating the witnesses to this reading beginning or ending at this point.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      These elements may appear anywhere within the elements lem and rdg, and also within any of their constituent elements.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.resourced.html b/gl/dev/ref-att.resourced.html index 660464582..ff5b838d3 100644 --- a/gl/dev/ref-att.resourced.html +++ b/gl/dev/ref-att.resourced.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.resourced

                                      att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
                                      Moduletei
                                      Membersgraphic media schemaRef
                                      Attributes
                                      url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
                                      Status Required
                                      Datatype teidata.pointer

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.resourced

                                      att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
                                      Moduletei
                                      Membersgraphic media schemaRef
                                      Attributes
                                      url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
                                      Status Required
                                      Datatype teidata.pointer

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.scoping.html b/gl/dev/ref-att.scoping.html index def5f976e..38a1b5845 100644 --- a/gl/dev/ref-att.scoping.html +++ b/gl/dev/ref-att.scoping.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.scoping

                                      att.scoping provides attributes for selecting particular elements within a document.
                                      Moduletei
                                      Memberscertainty precision
                                      Attributes
                                      targetpoints at one or more sets of zero or more elements each.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Elizabeth went to <persName xml:id="ESSEX">Essex</persName>
                                      <certainty target="#ESSEXlocus="name"
                                       degree="0.6"/>
                                      matchsupplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines] 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.
                                      Status Optional
                                      Datatype teidata.xpath
                                      <gap reason="cancelled">
                                       <certainty match="@reasonlocus="value"
                                        cert="low"/>

                                      </gap>
                                      Note

                                      The semantics of this element apply to the nodeset identified by the value of the target attribute, possibly modified by the value of the match attribute. If more than one identifier is given, the implication is that all elements (or nodesets) are intended. The match attribute may also be used as a means of identifying groups of elements.

                                      If target and match are present, target selects an element and the XPath expression in match is evaluated in the context of that element. If neither attribute is present, the expression applies to its parent element. If only target is given, the expression refers to the selected element or nodeset. If only match is given, the XPath expression is evaluated in the context of the parent element of the bearing element.

                                      Note that the value of the target attribute may include an XPointer expression including an XPath expression (see 16.2.4. TEI XPointer Schemes).

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.scoping

                                      att.scoping provides attributes for selecting particular elements within a document.
                                      Moduletei
                                      Memberscertainty precision
                                      Attributes
                                      targetpoints at one or more sets of zero or more elements each.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Elizabeth went to <persName xml:id="ESSEX">Essex</persName>
                                      <certainty target="#ESSEXlocus="name"
                                       degree="0.6"/>
                                      matchsupplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines] 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.
                                      Status Optional
                                      Datatype teidata.xpath
                                      <gap reason="cancelled">
                                       <certainty match="@reasonlocus="value"
                                        cert="low"/>

                                      </gap>
                                      Note

                                      The semantics of this element apply to the nodeset identified by the value of the target attribute, possibly modified by the value of the match attribute. If more than one identifier is given, the implication is that all elements (or nodesets) are intended. The match attribute may also be used as a means of identifying groups of elements.

                                      If target and match are present, target selects an element and the XPath expression in match is evaluated in the context of that element. If neither attribute is present, the expression applies to its parent element. If only target is given, the expression refers to the selected element or nodeset. If only match is given, the XPath expression is evaluated in the context of the parent element of the bearing element.

                                      Note that the value of the target attribute may include an XPointer expression including an XPath expression (see 16.2.4. TEI XPointer Schemes).

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.segLike.html b/gl/dev/ref-att.segLike.html index 41d21ff59..f142727a7 100644 --- a/gl/dev/ref-att.segLike.html +++ b/gl/dev/ref-att.segLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.segLike

                                      att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
                                      Moduletei
                                      Membersc m pc phr s seg w
                                      Attributesatt.metrical (@met, @real, @rhyme) att.datcat (@datcat, @valueDatcat, @targetDatcat) att.fragmentable (@part)
                                      function(function) characterizes the function of the segment.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.segLike

                                      att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
                                      Moduletei
                                      Membersc m pc phr s seg w
                                      Attributesatt.metrical (@met, @real, @rhyme) att.datcat (@datcat, @valueDatcat, @targetDatcat) att.fragmentable (@part)
                                      function(function) characterizes the function of the segment.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.sortable.html b/gl/dev/ref-att.sortable.html index 8a2ae3438..69dc010ad 100644 --- a/gl/dev/ref-att.sortable.html +++ b/gl/dev/ref-att.sortable.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.sortable

                                      att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
                                      Moduletei
                                      Membersbibl biblFull biblStruct correspAction event idno item list listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listRelation msDesc nym object org person personGrp persona place relation term
                                      Attributes
                                      sortKeysupplies the sort key for this element in an index, list or group which contains it.
                                      Status Optional
                                      Datatype teidata.word
                                      David's other principal backer, Josiah
                                      ha-Kohen <index indexName="NAMES">
                                       <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
                                      </index> b. Azarya, son of one of the last gaons of Sura was David's own first
                                      cousin.
                                      Note

                                      The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

                                      Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.sortable

                                      att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
                                      Moduletei
                                      Membersbibl biblFull biblStruct correspAction event idno item list listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listRelation msDesc nym object org person personGrp persona place relation term
                                      Attributes
                                      sortKeysupplies the sort key for this element in an index, list or group which contains it.
                                      Status Optional
                                      Datatype teidata.word
                                      David's other principal backer, Josiah
                                      ha-Kohen <index indexName="NAMES">
                                       <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
                                      </index> b. Azarya, son of one of the last gaons of Sura was David's own first
                                      cousin.
                                      Note

                                      The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

                                      Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.spanning.html b/gl/dev/ref-att.spanning.html index 9d8efd589..c1be43be1 100644 --- a/gl/dev/ref-att.spanning.html +++ b/gl/dev/ref-att.spanning.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.spanning

                                      att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
                                      Moduletei
                                      MembersaddSpan cb delSpan gb index lb metamark milestone mod pb redo retrace undo
                                      Attributes
                                      spanToindicates the end of a span initiated by the element bearing this attribute.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronThe @spanTo attribute must point to an element following the current element

                                      <sch:rule context="tei:*[@spanTo]">
                                      <sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/>
                                      </sch:assert>
                                      </sch:rule>
                                      Note

                                      The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.spanning

                                      att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
                                      Moduletei
                                      MembersaddSpan cb delSpan gb index lb metamark milestone mod pb redo retrace undo
                                      Attributes
                                      spanToindicates the end of a span initiated by the element bearing this attribute.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronThe @spanTo attribute must point to an element following the current element

                                      <sch:rule context="tei:*[@spanTo]">
                                      <sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/>
                                      </sch:assert>
                                      </sch:rule>
                                      Note

                                      The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.styleDef.html b/gl/dev/ref-att.styleDef.html index bf22d2f35..fd06febfa 100644 --- a/gl/dev/ref-att.styleDef.html +++ b/gl/dev/ref-att.styleDef.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.styleDef

                                      att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.
                                      Moduletei
                                      Membersrendition styleDefDecl
                                      Attributes
                                      schemeidentifies the language used to describe the rendition.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      css
                                      Cascading Stylesheet Language
                                      xslfo
                                      Extensible Stylesheet Language Formatting Objects
                                      free
                                      Informal free text description
                                      other
                                      A user-defined rendition description language
                                      Note

                                      If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

                                      schemeVersionsupplies a version number for the style language provided in scheme.
                                      Status Optional
                                      Datatype teidata.versionNumber
                                      Schematron

                                      <sch:rule context="tei:*[@schemeVersion]">
                                      <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified.
                                      </sch:assert>
                                      </sch:rule>
                                      Note

                                      If schemeVersion is used, then scheme should also appear, with a value other than free.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.styleDef

                                      att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.
                                      Moduletei
                                      Membersrendition styleDefDecl
                                      Attributes
                                      schemeidentifies the language used to describe the rendition.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      css
                                      Cascading Stylesheet Language
                                      xslfo
                                      Extensible Stylesheet Language Formatting Objects
                                      free
                                      Informal free text description
                                      other
                                      A user-defined rendition description language
                                      Note

                                      If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

                                      schemeVersionsupplies a version number for the style language provided in scheme.
                                      Status Optional
                                      Datatype teidata.versionNumber
                                      Schematron

                                      <sch:rule context="tei:*[@schemeVersion]">
                                      <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified.
                                      </sch:assert>
                                      </sch:rule>
                                      Note

                                      If schemeVersion is used, then scheme should also appear, with a value other than free.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.tableDecoration.html b/gl/dev/ref-att.tableDecoration.html index 3ba96f7dd..1084c76e0 100644 --- a/gl/dev/ref-att.tableDecoration.html +++ b/gl/dev/ref-att.tableDecoration.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.tableDecoration

                                      att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music]
                                      Modulefigures
                                      Memberscell row
                                      Attributes
                                      role(role) indicates the kind of information held in this cell or in each cell of this row.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      label
                                      labelling or descriptive information only.
                                      data
                                      data values. [Default]
                                      Note

                                      When this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent row element.

                                      rows(rows) indicates the number of rows occupied by this cell or row.
                                      Status Optional
                                      Datatype teidata.count
                                      Default 1
                                      Note

                                      A value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.

                                      cols(columns) indicates the number of columns occupied by this cell or row.
                                      Status Optional
                                      Datatype teidata.count
                                      Default 1
                                      Note

                                      A value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.tableDecoration

                                      att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. Tables, Formulæ, Graphics, and Notated Music]
                                      Modulefigures
                                      Memberscell row
                                      Attributes
                                      role(role) indicates the kind of information held in this cell or in each cell of this row.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      label
                                      labelling or descriptive information only.
                                      data
                                      data values. [Default]
                                      Note

                                      When this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent row element.

                                      rows(rows) indicates the number of rows occupied by this cell or row.
                                      Status Optional
                                      Datatype teidata.count
                                      Default 1
                                      Note

                                      A value greater than one indicates that this cell spans several rows. Where several cells span multiple rows, it may be more convenient to use nested tables.

                                      cols(columns) indicates the number of columns occupied by this cell or row.
                                      Status Optional
                                      Datatype teidata.count
                                      Default 1
                                      Note

                                      A value greater than one indicates that this cell or row spans several columns. Where an initial cell spans an entire row, it may be better treated as a heading.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.textCritical.html b/gl/dev/ref-att.textCritical.html index 6dca6913e..f1659b5b2 100644 --- a/gl/dev/ref-att.textCritical.html +++ b/gl/dev/ref-att.textCritical.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.textCritical

                                      att.textCritical defines a set of attributes common to all elements representing variant readings in text critical work. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Memberslem rdg rdgGrp
                                      Attributesatt.written (@hand) att.typed (type, @subtype)
                                      typeclassifies the reading according to some useful typology.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      substantive
                                      (substantive) the reading offers a substantive variant.
                                      orthographic
                                      (orthographic) the reading differs only orthographically, not in substance, from other readings.
                                      causeclassifies the cause for the variant reading, according to any appropriate typology of possible origins.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      homeoteleuton
                                      homeoarchy
                                      paleographicConfusion
                                      haplography
                                      dittography
                                      falseEmendation
                                      varSeq(variant sequence) provides a number indicating the position of this reading in a sequence, when there is reason to presume a sequence to the variants.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      Different variant sequences could be coded with distinct number trails: 1-2-3 for one sequence, 5-6-7 for another. More complex variant sequences, with (for example) multiple branchings from single readings, may be expressed through the join element.

                                      requirepoints to other readings that are required when adopting the current reading or lemma.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      This element class defines attributes inherited by rdg, lem, and rdgGrp.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.textCritical

                                      att.textCritical defines a set of attributes common to all elements representing variant readings in text critical work. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Memberslem rdg rdgGrp
                                      Attributesatt.written (@hand) att.typed (type, @subtype)
                                      typeclassifies the reading according to some useful typology.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      substantive
                                      (substantive) the reading offers a substantive variant.
                                      orthographic
                                      (orthographic) the reading differs only orthographically, not in substance, from other readings.
                                      causeclassifies the cause for the variant reading, according to any appropriate typology of possible origins.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      homeoteleuton
                                      homeoarchy
                                      paleographicConfusion
                                      haplography
                                      dittography
                                      falseEmendation
                                      varSeq(variant sequence) provides a number indicating the position of this reading in a sequence, when there is reason to presume a sequence to the variants.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      Different variant sequences could be coded with distinct number trails: 1-2-3 for one sequence, 5-6-7 for another. More complex variant sequences, with (for example) multiple branchings from single readings, may be expressed through the join element.

                                      requirepoints to other readings that are required when adopting the current reading or lemma.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      This element class defines attributes inherited by rdg, lem, and rdgGrp.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.timed.html b/gl/dev/ref-att.timed.html index fcc6bd406..60cd491d5 100644 --- a/gl/dev/ref-att.timed.html +++ b/gl/dev/ref-att.timed.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.timed

                                      att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
                                      Moduletei
                                      MembersannotationBlock binaryObject ellipsis gap media
                                      Attributesatt.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso))
                                      startindicates the location within a temporal alignment at which this element begins.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.

                                      endindicates the location within a temporal alignment at which this element ends.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.timed

                                      att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
                                      Moduletei
                                      MembersannotationBlock binaryObject ellipsis gap media
                                      Attributesatt.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso))
                                      startindicates the location within a temporal alignment at which this element begins.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.

                                      endindicates the location within a temporal alignment at which this element ends.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Note

                                      If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.transcriptional.html b/gl/dev/ref-att.transcriptional.html index a09173410..558659298 100644 --- a/gl/dev/ref-att.transcriptional.html +++ b/gl/dev/ref-att.transcriptional.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.transcriptional

                                      att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions]
                                      Moduletei
                                      Membersadd addSpan del delSpan mod redo retrace rt subst substJoin undo
                                      Attributesatt.editLike (@evidence, @instant) att.written (@hand)
                                      statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      duplicate
                                      all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
                                      duplicate-partial
                                      part of the text indicated as an addition duplicates some text that is in the original
                                      excessStart
                                      some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
                                      excessEnd
                                      some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
                                      shortStart
                                      some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
                                      shortEnd
                                      some text at the end of the deletion is not marked as deleted even though it clearly should be.
                                      partial
                                      some text in the deletion is not marked as deleted even though it clearly should be.
                                      unremarkable
                                      the deletion is not faulty. [Default]
                                      Note

                                      Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

                                      Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

                                      causedocuments the presumed cause for the intervention.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
                                      Status Optional
                                      Datatype teidata.count

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.transcriptional

                                      att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions]
                                      Moduletei
                                      Membersadd addSpan del delSpan mod redo retrace rt subst substJoin undo
                                      Attributesatt.editLike (@evidence, @instant) att.written (@hand)
                                      statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      duplicate
                                      all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
                                      duplicate-partial
                                      part of the text indicated as an addition duplicates some text that is in the original
                                      excessStart
                                      some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
                                      excessEnd
                                      some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
                                      shortStart
                                      some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
                                      shortEnd
                                      some text at the end of the deletion is not marked as deleted even though it clearly should be.
                                      partial
                                      some text in the deletion is not marked as deleted even though it clearly should be.
                                      unremarkable
                                      the deletion is not faulty. [Default]
                                      Note

                                      Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

                                      Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

                                      causedocuments the presumed cause for the intervention.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
                                      Status Optional
                                      Datatype teidata.count

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.typed.html b/gl/dev/ref-att.typed.html index 1928d658c..d138459e2 100644 --- a/gl/dev/ref-att.typed.html +++ b/gl/dev/ref-att.typed.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.typed

                                      att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
                                      Moduletei
                                      Membersatt.pointing.group [linkGrp] TEI ab abbr accMat add addName addSpan altIdentifier am anchor app application bibl biblStruct binaryObject birth bloc c calendar cb certainty change cit collection corr correspAction correspDesc country custEvent damage date death decoNote del delSpan desc dim dimensions distinct district div divGen event explicit figure filiation finalRubric floatingText forename form fw g gb genName gender geogFeat geogName gloss graphic group head idno incipit join label lb lg line link list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listRelation location locus m mapping material measure measureGrp media milestone mod msDesc msFrag msName msPart name notatedMusic note noteGrp num nym object objectName offset org orgName origDate origPlace path pb pc persName persPronouns phr place placeName provenance ptr quote rb ref reg region relatedItem relation roleName rs rt rubric ruby s schemaRef seal seg settlement space stamp standOff state surface surfaceGrp surname table teiCorpus term text time title unit unitDef w xenoData zone
                                      Attributes
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      <div type="verse">
                                       <head>Night in Tarras</head>
                                       <lg type="stanza">
                                        <l>At evening tramping on the hot white road</l>
                                        <l></l>
                                       </lg>
                                       <lg type="stanza">
                                        <l>A wind sprang up from nowhere as the sky</l>
                                        <l></l>
                                       </lg>
                                      </div>
                                      Note

                                      The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

                                      subtype(subtype) provides a sub-categorization of the element, if needed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

                                      Schematron

                                      <sch:rule context="tei:*[@subtype]">
                                      <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
                                      </sch:rule>
                                      Note

                                      When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.typed

                                      att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
                                      Moduletei
                                      Membersatt.pointing.group [linkGrp] TEI ab abbr accMat add addName addSpan altIdentifier am anchor app application bibl biblStruct binaryObject birth bloc c calendar cb certainty change cit collection corr correspAction correspDesc country custEvent damage date death decoNote del delSpan desc dim dimensions distinct district div divGen event explicit figure filiation finalRubric floatingText forename form fw g gb genName gender geogFeat geogName gloss graphic group head idno incipit join label lb lg line link list listAnnotation listApp listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listRelation location locus m mapping material measure measureGrp media milestone mod msDesc msFrag msName msPart name notatedMusic note noteGrp num nym object objectName offset org orgName origDate origPlace path pb pc persName persPronouns phr place placeName provenance ptr quote rb ref reg region relatedItem relation roleName rs rt rubric ruby s schemaRef seal seg settlement space stamp standOff state surface surfaceGrp surname table teiCorpus term text time title unit unitDef w xenoData zone
                                      Attributes
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      <div type="verse">
                                       <head>Night in Tarras</head>
                                       <lg type="stanza">
                                        <l>At evening tramping on the hot white road</l>
                                        <l></l>
                                       </lg>
                                       <lg type="stanza">
                                        <l>A wind sprang up from nowhere as the sky</l>
                                        <l></l>
                                       </lg>
                                      </div>
                                      Note

                                      The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

                                      subtype(subtype) provides a sub-categorization of the element, if needed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

                                      Schematron

                                      <sch:rule context="tei:*[@subtype]">
                                      <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
                                      </sch:rule>
                                      Note

                                      When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.witnessed.html b/gl/dev/ref-att.witnessed.html index a4f7fd32c..b9d877129 100644 --- a/gl/dev/ref-att.witnessed.html +++ b/gl/dev/ref-att.witnessed.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.witnessed

                                      att.witnessed provides attributes used to identify the witnesses supporting a particular reading in a critical apparatus. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Memberslem rdg
                                      Attributes
                                      wit(witness or witnesses) contains a space-delimited list of one or more pointers indicating the witnesses which attest to a given reading.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      If the apparatus contains readings only for a single witness, this attribute may be consistently omitted.

                                      This attribute may occur both within an apparatus gathering variant readings in the transcription of an individual witness and within an apparatus gathering readings from different witnesses.

                                      Additional descriptions or alternative versions of the sigla referenced may be supplied as the content of a child wit element.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.witnessed

                                      att.witnessed provides attributes used to identify the witnesses supporting a particular reading in a critical apparatus. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Memberslem rdg
                                      Attributes
                                      wit(witness or witnesses) contains a space-delimited list of one or more pointers indicating the witnesses which attest to a given reading.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      If the apparatus contains readings only for a single witness, this attribute may be consistently omitted.

                                      This attribute may occur both within an apparatus gathering variant readings in the transcription of an individual witness and within an apparatus gathering readings from different witnesses.

                                      Additional descriptions or alternative versions of the sigla referenced may be supplied as the content of a child wit element.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-att.written.html b/gl/dev/ref-att.written.html index 24d8ca470..175b1a974 100644 --- a/gl/dev/ref-att.written.html +++ b/gl/dev/ref-att.written.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      att.written

                                      att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
                                      Moduletei
                                      Membersatt.damaged [damage] att.textCritical [lem rdg rdgGrp] att.transcriptional [add addSpan del delSpan mod redo retrace rt subst substJoin undo] ab div figure fw head hi label line note noteGrp p path seg stage text zone
                                      Attributes
                                      handpoints to a handNote element describing the hand considered responsible for the content of the element concerned.
                                      Status Optional
                                      Datatype teidata.pointer

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      att.written

                                      att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
                                      Moduletei
                                      Membersatt.damaged [damage] att.textCritical [lem rdg rdgGrp] att.transcriptional [add addSpan del delSpan mod redo retrace rt subst substJoin undo] ab div figure fw head hi label line note noteGrp p path seg stage text zone
                                      Attributes
                                      handpoints to a handNote element describing the hand considered responsible for the content of the element concerned.
                                      Status Optional
                                      Datatype teidata.pointer

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-author.html b/gl/dev/ref-author.html index 19ca248b2..f5d7b23bf 100644 --- a/gl/dev/ref-author.html +++ b/gl/dev/ref-author.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <author>

                                      <author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

                                      In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

                                      Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

                                      Example
                                      <author>British Broadcasting Corporation</author>
                                      <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
                                      <author>Anonymous</author>
                                      <author>Bill and Melinda Gates Foundation</author>
                                      <author>
                                       <persName>Beaumont, Francis</persName> and
                                      <persName>John Fletcher</persName>
                                      </author>
                                      <author>
                                       <orgName key="BBC">British Broadcasting
                                         Corporation</orgName>: Radio 3 Network
                                      </author>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <author>

                                      <author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

                                      In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

                                      Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

                                      Example
                                      <author>British Broadcasting Corporation</author>
                                      <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
                                      <author>Anonymous</author>
                                      <author>Bill and Melinda Gates Foundation</author>
                                      <author>
                                       <persName>Beaumont, Francis</persName> and
                                      <persName>John Fletcher</persName>
                                      </author>
                                      <author>
                                       <orgName key="BBC">British Broadcasting
                                         Corporation</orgName>: Radio 3 Network
                                      </author>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element author
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-authority.html b/gl/dev/ref-authority.html index b446b6e98..01849d76a 100644 --- a/gl/dev/ref-authority.html +++ b/gl/dev/ref-authority.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <authority>

                                      <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      core: monogr
                                      May contain
                                      Example
                                      <authority>John Smith</authority>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <authority>

                                      <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      core: monogr
                                      May contain
                                      Example
                                      <authority>John Smith</authority>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element authority
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-availability.html b/gl/dev/ref-availability.html index f24d989cf..0b7c327aa 100644 --- a/gl/dev/ref-availability.html +++ b/gl/dev/ref-availability.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <availability>

                                      <availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      status(status) supplies a code identifying the current availability of the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      free
                                      (free) the text is freely available.
                                      unknown
                                      (unknown) the status of the text is unknown.
                                      restricted
                                      (restricted) the text is not freely available.
                                      Member of
                                      Contained by
                                      msdescription: adminInfo
                                      May contain
                                      core: p
                                      header: licence
                                      linking: ab
                                      Note

                                      A consistent format should be adopted

                                      Example
                                      <availability status="restricted">
                                       <p>Available for academic research purposes only.</p>
                                      </availability>
                                      <availability status="free">
                                       <p>In the public domain</p>
                                      </availability>
                                      <availability status="restricted">
                                       <p>Available under licence from the publishers.</p>
                                      </availability>
                                      Example
                                      <availability>
                                       <licence target="http://opensource.org/licenses/MIT">
                                        <p>The MIT License
                                           applies to this document.</p>
                                        <p>Copyright (C) 2011 by The University of Victoria</p>
                                        <p>Permission is hereby granted, free of charge, to any person obtaining a copy
                                           of this software and associated documentation files (the "Software"), to deal
                                           in the Software without restriction, including without limitation the rights
                                           to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
                                           copies of the Software, and to permit persons to whom the Software is
                                           furnished to do so, subject to the following conditions:</p>
                                        <p>The above copyright notice and this permission notice shall be included in
                                           all copies or substantial portions of the Software.</p>
                                        <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
                                           IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
                                           FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
                                           AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
                                           LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
                                           OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
                                           THE SOFTWARE.</p>
                                       </licence>
                                      </availability>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.availabilityPart"/>
                                        <classRef key="model.pLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <availability>

                                      <availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      status(status) supplies a code identifying the current availability of the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      free
                                      (free) the text is freely available.
                                      unknown
                                      (unknown) the status of the text is unknown.
                                      restricted
                                      (restricted) the text is not freely available.
                                      Member of
                                      Contained by
                                      msdescription: adminInfo
                                      May contain
                                      core: p
                                      header: licence
                                      linking: ab
                                      Note

                                      A consistent format should be adopted

                                      Example
                                      <availability status="restricted">
                                       <p>Available for academic research purposes only.</p>
                                      </availability>
                                      <availability status="free">
                                       <p>In the public domain</p>
                                      </availability>
                                      <availability status="restricted">
                                       <p>Available under licence from the publishers.</p>
                                      </availability>
                                      Example
                                      <availability>
                                       <licence target="http://opensource.org/licenses/MIT">
                                        <p>The MIT License
                                           applies to this document.</p>
                                        <p>Copyright (C) 2011 by The University of Victoria</p>
                                        <p>Permission is hereby granted, free of charge, to any person obtaining a copy
                                           of this software and associated documentation files (the "Software"), to deal
                                           in the Software without restriction, including without limitation the rights
                                           to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
                                           copies of the Software, and to permit persons to whom the Software is
                                           furnished to do so, subject to the following conditions:</p>
                                        <p>The above copyright notice and this permission notice shall be included in
                                           all copies or substantial portions of the Software.</p>
                                        <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
                                           IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
                                           FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
                                           AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
                                           LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
                                           OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
                                           THE SOFTWARE.</p>
                                       </licence>
                                      </availability>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.availabilityPart"/>
                                        <classRef key="model.pLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element availability
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          attribute status { "free" | "unknown" | "restricted" }?,
                                          ( tei_model.availabilityPart | tei_model.pLike )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-back.html b/gl/dev/ref-back.html index d162be7ac..00441a76c 100644 --- a/gl/dev/ref-back.html +++ b/gl/dev/ref-back.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <back>

                                      <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Contained by
                                      textstructure: floatingText text
                                      transcr: facsimile
                                      May contain
                                      Note

                                      Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and front elements are identical.

                                      Example
                                      <back>
                                       <div type="appendix">
                                        <head>The Golden Dream or, the Ingenuous Confession</head>
                                        <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets
                                           and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she
                                           had like to have been, too fond of Money
                                      <!-- .... -->
                                        </p>
                                       </div>
                                      <!-- ... -->
                                       <div type="epistle">
                                        <head>A letter from the Printer, which he desires may be inserted</head>
                                        <salute>Sir.</salute>
                                        <p>I have done with your Copy, so you may return it to the Vatican, if you please;
                                        
                                      <!-- ... -->
                                        </p>
                                       </div>
                                       <div type="advert">
                                        <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
                                           Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
                                        <list>
                                         <item n="1">The Christmas Box, Price 1d.</item>
                                         <item n="2">The History of Giles Gingerbread, 1d.</item>
                                      <!-- ... -->
                                         <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
                                             10 Vol, Pr. bound 1l.</item>
                                        </list>
                                       </div>
                                       <div type="advert">
                                        <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.
                                           Paul's Church-Yard.</head>
                                        <list>
                                         <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.
                                             6d</item>
                                         <item n="2">Dr. Hooper's Female Pills, 1s.</item>
                                      <!-- ... -->
                                        </list>
                                       </div>
                                      </back>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.frontPart"/>
                                         <classRef key="model.pLike.front"/>
                                         <classRef key="model.pLike"/>
                                         <classRef key="model.listLike"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <alternate minOccurs="0">
                                         <sequence>
                                          <classRef key="model.div1Like"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.frontPart"/>
                                           <classRef key="model.div1Like"/>
                                           <classRef key="model.global"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <classRef key="model.divLike"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.frontPart"/>
                                           <classRef key="model.divLike"/>
                                           <classRef key="model.global"/>
                                          </alternate>
                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0">
                                         <classRef key="model.divBottomPart"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.divBottomPart"/>
                                          <classRef key="model.global"/>
                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <back>

                                      <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Contained by
                                      textstructure: floatingText text
                                      transcr: facsimile
                                      May contain
                                      Note

                                      Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the back and front elements are identical.

                                      Example
                                      <back>
                                       <div type="appendix">
                                        <head>The Golden Dream or, the Ingenuous Confession</head>
                                        <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets
                                           and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she
                                           had like to have been, too fond of Money
                                      <!-- .... -->
                                        </p>
                                       </div>
                                      <!-- ... -->
                                       <div type="epistle">
                                        <head>A letter from the Printer, which he desires may be inserted</head>
                                        <salute>Sir.</salute>
                                        <p>I have done with your Copy, so you may return it to the Vatican, if you please;
                                        
                                      <!-- ... -->
                                        </p>
                                       </div>
                                       <div type="advert">
                                        <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
                                           Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
                                        <list>
                                         <item n="1">The Christmas Box, Price 1d.</item>
                                         <item n="2">The History of Giles Gingerbread, 1d.</item>
                                      <!-- ... -->
                                         <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
                                             10 Vol, Pr. bound 1l.</item>
                                        </list>
                                       </div>
                                       <div type="advert">
                                        <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.
                                           Paul's Church-Yard.</head>
                                        <list>
                                         <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.
                                             6d</item>
                                         <item n="2">Dr. Hooper's Female Pills, 1s.</item>
                                      <!-- ... -->
                                        </list>
                                       </div>
                                      </back>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.frontPart"/>
                                         <classRef key="model.pLike.front"/>
                                         <classRef key="model.pLike"/>
                                         <classRef key="model.listLike"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <alternate minOccurs="0">
                                         <sequence>
                                          <classRef key="model.div1Like"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.frontPart"/>
                                           <classRef key="model.div1Like"/>
                                           <classRef key="model.global"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <classRef key="model.divLike"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.frontPart"/>
                                           <classRef key="model.divLike"/>
                                           <classRef key="model.global"/>
                                          </alternate>
                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0">
                                         <classRef key="model.divBottomPart"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.divBottomPart"/>
                                          <classRef key="model.global"/>
                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element back
                                       {
                                          tei_att.global.attributes,
                                      @@ -49,4 +49,4 @@
                                                ( tei_model.divBottomPart | tei_model.global )*
                                             )?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-bibl.html b/gl/dev/ref-bibl.html index 58c817a9d..decae55ca 100644 --- a/gl/dev/ref-bibl.html +++ b/gl/dev/ref-bibl.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <bibl>

                                      <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Contains phrase-level elements, together with any combination of elements from the model.biblPart class

                                      Example
                                      <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
                                      1990)</bibl>
                                      Example
                                      <bibl>
                                       <title level="a">The Interesting story of the Children in the Wood</title>. In
                                      <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
                                      <publisher>OUP</publisher>
                                       <date>1968</date>.
                                      </bibl>
                                      Example
                                      <bibl type="articlesubtype="book_chapter"
                                       xml:id="carlin_2003">

                                       <author>
                                        <name>
                                         <surname>Carlin</surname>
                                           (<forename>Claire</forename>)</name>
                                       </author>,
                                      <title level="a">The Staging of Impotence : France’s last
                                         congrès</title> dans
                                      <bibl type="monogr">
                                        <title level="m">Theatrum mundi : studies in honor of Ronald W.
                                           Tobin</title>, éd.
                                       <editor>
                                         <name>
                                          <forename>Claire</forename>
                                          <surname>Carlin</surname>
                                         </name>
                                        </editor> et
                                       <editor>
                                         <name>
                                          <forename>Kathleen</forename>
                                          <surname>Wine</surname>
                                         </name>
                                        </editor>,
                                       <pubPlace>Charlottesville, Va.</pubPlace>,
                                       <publisher>Rookwood Press</publisher>,
                                       <date when="2003">2003</date>.
                                       </bibl>
                                      </bibl>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.highlighted"/>
                                        <classRef key="model.pPart.data"/>
                                        <classRef key="model.pPart.edit"/>
                                        <classRef key="model.segLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <classRef key="model.biblPart"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <bibl>

                                      <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Contains phrase-level elements, together with any combination of elements from the model.biblPart class

                                      Example
                                      <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
                                      1990)</bibl>
                                      Example
                                      <bibl>
                                       <title level="a">The Interesting story of the Children in the Wood</title>. In
                                      <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
                                      <publisher>OUP</publisher>
                                       <date>1968</date>.
                                      </bibl>
                                      Example
                                      <bibl type="articlesubtype="book_chapter"
                                       xml:id="carlin_2003">

                                       <author>
                                        <name>
                                         <surname>Carlin</surname>
                                           (<forename>Claire</forename>)</name>
                                       </author>,
                                      <title level="a">The Staging of Impotence : France’s last
                                         congrès</title> dans
                                      <bibl type="monogr">
                                        <title level="m">Theatrum mundi : studies in honor of Ronald W.
                                           Tobin</title>, éd.
                                       <editor>
                                         <name>
                                          <forename>Claire</forename>
                                          <surname>Carlin</surname>
                                         </name>
                                        </editor> et
                                       <editor>
                                         <name>
                                          <forename>Kathleen</forename>
                                          <surname>Wine</surname>
                                         </name>
                                        </editor>,
                                       <pubPlace>Charlottesville, Va.</pubPlace>,
                                       <publisher>Rookwood Press</publisher>,
                                       <date when="2003">2003</date>.
                                       </bibl>
                                      </bibl>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.highlighted"/>
                                        <classRef key="model.pPart.data"/>
                                        <classRef key="model.pPart.edit"/>
                                        <classRef key="model.segLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <classRef key="model.biblPart"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element bibl
                                       {
                                          tei_att.global.attributes,
                                      @@ -40,4 +40,4 @@
                                           | tei_model.biblPart
                                           | tei_model.global
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-biblFull.html b/gl/dev/ref-biblFull.html index a7268436c..21ff207ab 100644 --- a/gl/dev/ref-biblFull.html +++ b/gl/dev/ref-biblFull.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <biblFull>

                                      <biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.sortable (@sortKey) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <biblFull>
                                       <titleStmt>
                                        <title>The Feminist Companion to Literature in English: women writers from the middle ages
                                           to the present</title>
                                        <author>Blain, Virginia</author>
                                        <author>Clements, Patricia</author>
                                        <author>Grundy, Isobel</author>
                                       </titleStmt>
                                       <editionStmt>
                                        <edition>UK edition</edition>
                                       </editionStmt>
                                       <extent>1231 pp</extent>
                                       <publicationStmt>
                                        <publisher>Yale University Press</publisher>
                                        <pubPlace>New Haven and London</pubPlace>
                                        <date>1990</date>
                                       </publicationStmt>
                                       <sourceDesc>
                                        <p>No source: this is an original work</p>
                                       </sourceDesc>
                                      </biblFull>
                                      Content model
                                      <content>
                                       <alternate>
                                        <sequence>
                                         <sequence>
                                          <elementRef key="titleStmt"/>
                                          <elementRef key="editionStmt"
                                           minOccurs="0"/>

                                          <elementRef key="extentminOccurs="0"/>
                                          <elementRef key="publicationStmt"/>
                                          <elementRef key="seriesStmt"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="notesStmt"
                                           minOccurs="0"/>

                                         </sequence>
                                         <elementRef key="sourceDesc"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <sequence>
                                         <elementRef key="fileDesc"/>
                                         <elementRef key="profileDesc"/>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <biblFull>

                                      <biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.sortable (@sortKey) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <biblFull>
                                       <titleStmt>
                                        <title>The Feminist Companion to Literature in English: women writers from the middle ages
                                           to the present</title>
                                        <author>Blain, Virginia</author>
                                        <author>Clements, Patricia</author>
                                        <author>Grundy, Isobel</author>
                                       </titleStmt>
                                       <editionStmt>
                                        <edition>UK edition</edition>
                                       </editionStmt>
                                       <extent>1231 pp</extent>
                                       <publicationStmt>
                                        <publisher>Yale University Press</publisher>
                                        <pubPlace>New Haven and London</pubPlace>
                                        <date>1990</date>
                                       </publicationStmt>
                                       <sourceDesc>
                                        <p>No source: this is an original work</p>
                                       </sourceDesc>
                                      </biblFull>
                                      Content model
                                      <content>
                                       <alternate>
                                        <sequence>
                                         <sequence>
                                          <elementRef key="titleStmt"/>
                                          <elementRef key="editionStmt"
                                           minOccurs="0"/>

                                          <elementRef key="extentminOccurs="0"/>
                                          <elementRef key="publicationStmt"/>
                                          <elementRef key="seriesStmt"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="notesStmt"
                                           minOccurs="0"/>

                                         </sequence>
                                         <elementRef key="sourceDesc"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <sequence>
                                         <elementRef key="fileDesc"/>
                                         <elementRef key="profileDesc"/>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element biblFull
                                       {
                                          tei_att.global.attributes,
                                      @@ -42,4 +42,4 @@
                                             )
                                           | ( tei_fileDesc, tei_profileDesc )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-biblScope.html b/gl/dev/ref-biblScope.html index 5fb685e99..eb79e4305 100644 --- a/gl/dev/ref-biblScope.html +++ b/gl/dev/ref-biblScope.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <biblScope>

                                      <biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (unit, @from, @to)
                                      unit
                                      Status Optional
                                      Datatype 1–6 occurrences of teidata.word separated by whitespace
                                      Suggested values include:
                                      appendix
                                      the element identifies an appendix.
                                      book
                                      the element contains a book number.
                                      chapter
                                      the element contains a chapter indication (number and/or title)
                                      column
                                      the element identifies a column.
                                      database-id
                                      the element contains an identifier from a database.
                                      entry
                                      the element identifies an entry number or label in a list of entries.
                                      fascicle
                                      the element identifies a fascicle.
                                      figure
                                      the element contains a numbered figure or other illustration.
                                      folio
                                      the element contains a folio number, e.g., from a manuscript.
                                      issue
                                      the element contains an issue number, or volume and issue numbers.
                                      item
                                      the element identifies an item.
                                      line
                                      the element contains a line number or line range.
                                      note
                                      the element identifies a note.
                                      page
                                      the element contains a page number or page range.
                                      part
                                      the element identifies a part of a book or collection.
                                      plate
                                      the element contains a plate.
                                      section
                                      the element contains a section reference.
                                      verse
                                      the element identifies a verse.
                                      volume
                                      the element contains a volume number.
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When a single page is being cited, use the from and to attributes with 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 <biblScope from="3">p. 3ff</biblScope>.

                                      It is now considered good practice to supply this element as a sibling (rather than a child) of imprint, since it supplies information which does not constitute part of the imprint.

                                      Example
                                      <biblScope>pp 12–34</biblScope>
                                      <biblScope unit="pagefrom="12to="34"/>
                                      <biblScope unit="volume">II</biblScope>
                                      <biblScope unit="page">12</biblScope>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <biblScope>

                                      <biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (unit, @from, @to)
                                      unit
                                      Status Optional
                                      Datatype 1–6 occurrences of teidata.word separated by whitespace
                                      Suggested values include:
                                      appendix
                                      the element identifies an appendix.
                                      book
                                      the element contains a book number.
                                      chapter
                                      the element contains a chapter indication (number and/or title)
                                      column
                                      the element identifies a column.
                                      database-id
                                      the element contains an identifier from a database.
                                      entry
                                      the element identifies an entry number or label in a list of entries.
                                      fascicle
                                      the element identifies a fascicle.
                                      figure
                                      the element contains a numbered figure or other illustration.
                                      folio
                                      the element contains a folio number, e.g., from a manuscript.
                                      issue
                                      the element contains an issue number, or volume and issue numbers.
                                      item
                                      the element identifies an item.
                                      line
                                      the element contains a line number or line range.
                                      note
                                      the element identifies a note.
                                      page
                                      the element contains a page number or page range.
                                      part
                                      the element identifies a part of a book or collection.
                                      plate
                                      the element contains a plate.
                                      section
                                      the element contains a section reference.
                                      verse
                                      the element identifies a verse.
                                      volume
                                      the element contains a volume number.
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When a single page is being cited, use the from and to attributes with 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 <biblScope from="3">p. 3ff</biblScope>.

                                      It is now considered good practice to supply this element as a sibling (rather than a child) of imprint, since it supplies information which does not constitute part of the imprint.

                                      Example
                                      <biblScope>pp 12–34</biblScope>
                                      <biblScope unit="pagefrom="12to="34"/>
                                      <biblScope unit="volume">II</biblScope>
                                      <biblScope unit="page">12</biblScope>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element biblScope
                                       {
                                          tei_att.global.attributes,
                                      @@ -166,4 +166,4 @@
                                             }
                                          }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-biblStruct.html b/gl/dev/ref-biblStruct.html index 631a9c578..acd41e6b8 100644 --- a/gl/dev/ref-biblStruct.html +++ b/gl/dev/ref-biblStruct.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <biblStruct>

                                      <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <biblStruct>
                                       <monogr>
                                        <author>Blain, Virginia</author>
                                        <author>Clements, Patricia</author>
                                        <author>Grundy, Isobel</author>
                                        <title>The Feminist Companion to Literature in English: women writers from the middle ages
                                           to the present</title>
                                        <edition>first edition</edition>
                                        <imprint>
                                         <publisher>Yale University Press</publisher>
                                         <pubPlace>New Haven and London</pubPlace>
                                         <date>1990</date>
                                        </imprint>
                                       </monogr>
                                      </biblStruct>
                                      Example
                                      <biblStruct type="newspaper">
                                       <analytic>
                                        <author>
                                         <forename>David</forename>
                                         <surname>Barstow</surname>
                                        </author>
                                        <author>
                                         <forename>Susanne</forename>
                                         <surname>Craig</surname>
                                        </author>
                                        <author>
                                         <forename>Russ</forename>
                                         <surname>Buettner</surname>
                                        </author>
                                        <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
                                        <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
                                       </analytic>
                                       <monogr>
                                        <title level="j">The New York Times</title>
                                        <imprint>
                                         <pubPlace>New York</pubPlace>
                                         <publisher>A. G. Sulzberger</publisher>
                                         <date when="2018-10-03">Wednesday, October 3, 2018</date>
                                        </imprint>
                                        <biblScope unit="volume">CLXVIII</biblScope>
                                        <biblScope unit="issue">58,104</biblScope>
                                        <biblScope unit="page">1</biblScope>
                                       </monogr>
                                      </biblStruct>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="analyticminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="monogr"/>
                                         <elementRef key="seriesminOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.ptrLike"/>
                                         <elementRef key="relatedItem"/>
                                         <elementRef key="citedRange"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <biblStruct>

                                      <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <biblStruct>
                                       <monogr>
                                        <author>Blain, Virginia</author>
                                        <author>Clements, Patricia</author>
                                        <author>Grundy, Isobel</author>
                                        <title>The Feminist Companion to Literature in English: women writers from the middle ages
                                           to the present</title>
                                        <edition>first edition</edition>
                                        <imprint>
                                         <publisher>Yale University Press</publisher>
                                         <pubPlace>New Haven and London</pubPlace>
                                         <date>1990</date>
                                        </imprint>
                                       </monogr>
                                      </biblStruct>
                                      Example
                                      <biblStruct type="newspaper">
                                       <analytic>
                                        <author>
                                         <forename>David</forename>
                                         <surname>Barstow</surname>
                                        </author>
                                        <author>
                                         <forename>Susanne</forename>
                                         <surname>Craig</surname>
                                        </author>
                                        <author>
                                         <forename>Russ</forename>
                                         <surname>Buettner</surname>
                                        </author>
                                        <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
                                        <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
                                       </analytic>
                                       <monogr>
                                        <title level="j">The New York Times</title>
                                        <imprint>
                                         <pubPlace>New York</pubPlace>
                                         <publisher>A. G. Sulzberger</publisher>
                                         <date when="2018-10-03">Wednesday, October 3, 2018</date>
                                        </imprint>
                                        <biblScope unit="volume">CLXVIII</biblScope>
                                        <biblScope unit="issue">58,104</biblScope>
                                        <biblScope unit="page">1</biblScope>
                                       </monogr>
                                      </biblStruct>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="analyticminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="monogr"/>
                                         <elementRef key="seriesminOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.ptrLike"/>
                                         <elementRef key="relatedItem"/>
                                         <elementRef key="citedRange"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element biblStruct
                                       {
                                          tei_att.global.attributes,
                                      @@ -39,4 +39,4 @@
                                              | tei_citedRange
                                             )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-binaryObject.html b/gl/dev/ref-binaryObject.html index 2a3e52b90..1b00378e6 100644 --- a/gl/dev/ref-binaryObject.html +++ b/gl/dev/ref-binaryObject.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <binaryObject>

                                      <binaryObject> provides encoded binary data representing an inline graphic, audio, video or other object. [3.10. Graphics and Other Non-textual Components]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.typed (@type, @subtype)
                                      encodingThe encoding used to encode the binary data. If not specified, this is assumed to be Base64.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May containCharacter data only
                                      Example
                                      <binaryObject mimeType="image/gif"> R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAwAAAC8IyPqcvt3wCcDkiLc7C0qwy
                                      GHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFzByTB10QgxOR0TqBQejhRNzOfkVJ
                                      +5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSpa/TPg7JpJHxyendzWTBfX0cxOnK
                                      PjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJlZeGl9i2icVqaNVailT6F5iJ90m6
                                      mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uisF81M1OIcR7lEewwcLp7tuNNkM3u
                                      Nna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH hhx4dbgYKAAA7</binaryObject>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <binaryObject>

                                      <binaryObject> provides encoded binary data representing an inline graphic, audio, video or other object. [3.10. Graphics and Other Non-textual Components]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.typed (@type, @subtype)
                                      encodingThe encoding used to encode the binary data. If not specified, this is assumed to be Base64.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May containCharacter data only
                                      Example
                                      <binaryObject mimeType="image/gif"> R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAwAAAC8IyPqcvt3wCcDkiLc7C0qwy
                                      GHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFzByTB10QgxOR0TqBQejhRNzOfkVJ
                                      +5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSpa/TPg7JpJHxyendzWTBfX0cxOnK
                                      PjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJlZeGl9i2icVqaNVailT6F5iJ90m6
                                      mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uisF81M1OIcR7lEewwcLp7tuNNkM3u
                                      Nna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH hhx4dbgYKAAA7</binaryObject>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                       element binaryObject
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.typed.attributes,
                                          attribute encoding { list { teidata.word+ } }?,
                                          text
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-binding.html b/gl/dev/ref-binding.html index 19bb463bb..941da599b 100644 --- a/gl/dev/ref-binding.html +++ b/gl/dev/ref-binding.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <binding>

                                      <binding> (binding) contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [10.7.3.1. Binding Descriptions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      contemporary(contemporary) specifies whether or not the binding is contemporary with the majority of its contents
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Note

                                      The value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should be used when the date of either binding or manuscript is unknown

                                      Contained by
                                      msdescription: bindingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: condition decoNote
                                      Example
                                      <binding contemporary="true">
                                       <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp
                                         closing to the back cover.</p>
                                      </binding>
                                      Example
                                      <bindingDesc>
                                       <binding contemporary="false">
                                        <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front
                                           pastedown.</p>
                                       </binding>
                                       <binding contemporary="false">
                                        <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>
                                       </binding>
                                      </bindingDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <elementRef key="condition"/>
                                        <elementRef key="decoNote"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <binding>

                                      <binding> (binding) contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [10.7.3.1. Binding Descriptions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      contemporary(contemporary) specifies whether or not the binding is contemporary with the majority of its contents
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Note

                                      The value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should be used when the date of either binding or manuscript is unknown

                                      Contained by
                                      msdescription: bindingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: condition decoNote
                                      Example
                                      <binding contemporary="true">
                                       <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp
                                         closing to the back cover.</p>
                                      </binding>
                                      Example
                                      <bindingDesc>
                                       <binding contemporary="false">
                                        <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front
                                           pastedown.</p>
                                       </binding>
                                       <binding contemporary="false">
                                        <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>
                                       </binding>
                                      </bindingDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <elementRef key="condition"/>
                                        <elementRef key="decoNote"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element binding
                                       {
                                          tei_att.global.attributes,
                                          tei_att.datable.attributes,
                                          attribute contemporary { teidata.xTruthValue }?,
                                          ( tei_model.pLike | tei_condition | tei_decoNote )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-bindingDesc.html b/gl/dev/ref-bindingDesc.html index 06f2aed4a..753bef4a9 100644 --- a/gl/dev/ref-bindingDesc.html +++ b/gl/dev/ref-bindingDesc.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <bindingDesc>

                                      <bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, either as a series of paragraphs or as a series of distinct binding elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: binding condition decoNote
                                      Example
                                      <bindingDesc>
                                       <p>Sewing not visible; tightly rebound over
                                         19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with
                                         gilt tooling à la fanfare, Paris c. 1580-90, the centre of each
                                         cover inlaid with a 17th-cent. 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.</p>
                                      </bindingDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.pLike"/>
                                         <elementRef key="decoNote"/>
                                         <elementRef key="condition"/>
                                        </alternate>
                                        <elementRef key="bindingminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <bindingDesc>

                                      <bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, either as a series of paragraphs or as a series of distinct binding elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: binding condition decoNote
                                      Example
                                      <bindingDesc>
                                       <p>Sewing not visible; tightly rebound over
                                         19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with
                                         gilt tooling à la fanfare, Paris c. 1580-90, the centre of each
                                         cover inlaid with a 17th-cent. 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.</p>
                                      </bindingDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.pLike"/>
                                         <elementRef key="decoNote"/>
                                         <elementRef key="condition"/>
                                        </alternate>
                                        <elementRef key="bindingminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element bindingDesc
                                       {
                                          tei_att.global.attributes,
                                          ( ( tei_model.pLike | tei_decoNote | tei_condition )+ | tei_binding+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-birth.html b/gl/dev/ref-birth.html index f1d050d39..5843e56cf 100644 --- a/gl/dev/ref-birth.html +++ b/gl/dev/ref-birth.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <birth>

                                      <birth> (birth) contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (type, @subtype)
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      caesarean
                                      (caesarean section)
                                      vaginal
                                      (vaginal delivery)
                                      exNihilo
                                      (ex nihilo)
                                      incorporated
                                      founded
                                      established
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <birth>Before 1920, Midlands region.</birth>
                                      Example
                                      <birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>,
                                      early in the morning of <date>10 Dec 1960</date>
                                      </birth>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <birth>

                                      <birth> (birth) contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (type, @subtype)
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      caesarean
                                      (caesarean section)
                                      vaginal
                                      (vaginal delivery)
                                      exNihilo
                                      (ex nihilo)
                                      incorporated
                                      founded
                                      established
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <birth>Before 1920, Midlands region.</birth>
                                      Example
                                      <birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>,
                                      early in the morning of <date>10 Dec 1960</date>
                                      </birth>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element birth
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          tei_att.typed.attribute.subtype,
                                          attribute type { teidata.enumerated }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-bloc.html b/gl/dev/ref-bloc.html index 88278755b..c2a207b9a 100644 --- a/gl/dev/ref-bloc.html +++ b/gl/dev/ref-bloc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <bloc>

                                      <bloc> (bloc) contains the name of a geo-political unit consisting of two or more nation states or countries. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <bloc type="union">the European Union</bloc>
                                      <bloc type="continent">Africa</bloc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <bloc>

                                      <bloc> (bloc) contains the name of a geo-political unit consisting of two or more nation states or countries. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <bloc type="union">the European Union</bloc>
                                      <bloc type="continent">Africa</bloc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element bloc
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-body.html b/gl/dev/ref-body.html index 9e2c7867d..ac9145b78 100644 --- a/gl/dev/ref-body.html +++ b/gl/dev/ref-body.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <body>

                                      <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Contained by
                                      textstructure: floatingText text
                                      May contain
                                      Example
                                      <body>
                                       <l>Nu scylun hergan hefaenricaes uard</l>
                                       <l>metudæs maecti end his modgidanc</l>
                                       <l>uerc uuldurfadur sue he uundra gihuaes</l>
                                       <l>eci dryctin or astelidæ</l>
                                       <l>he aerist scop aelda barnum</l>
                                       <l>heben til hrofe haleg scepen.</l>
                                       <l>tha middungeard moncynnæs uard</l>
                                       <l>eci dryctin æfter tiadæ</l>
                                       <l>firum foldu frea allmectig</l>
                                       <trailer>primo cantauit Cædmon istud carmen.</trailer>
                                      </body>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <classRef key="model.divTop"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.global"/>
                                          <classRef key="model.divTop"/>
                                         </alternate>
                                        </sequence>
                                        <sequence minOccurs="0">
                                         <classRef key="model.divGenLike"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.global"/>
                                          <classRef key="model.divGenLike"/>
                                         </alternate>
                                        </sequence>
                                        <alternate>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.divLike"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.global"/>
                                           <classRef key="model.divGenLike"/>
                                          </alternate>
                                         </sequence>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.div1Like"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.global"/>
                                           <classRef key="model.divGenLike"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <sequence minOccurs="1"
                                           maxOccurs="unbounded">

                                           <alternate minOccurs="1maxOccurs="1">
                                            <elementRef key="schemaSpec"/>
                                            <classRef key="model.common"/>
                                           </alternate>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                          </sequence>
                                          <alternate minOccurs="0">
                                           <sequence minOccurs="1"
                                            maxOccurs="unbounded">

                                            <classRef key="model.divLike"/>
                                            <alternate minOccurs="0"
                                             maxOccurs="unbounded">

                                             <classRef key="model.global"/>
                                             <classRef key="model.divGenLike"/>
                                            </alternate>
                                           </sequence>
                                           <sequence minOccurs="1"
                                            maxOccurs="unbounded">

                                            <classRef key="model.div1Like"/>
                                            <alternate minOccurs="0"
                                             maxOccurs="unbounded">

                                             <classRef key="model.global"/>
                                             <classRef key="model.divGenLike"/>
                                            </alternate>
                                           </sequence>
                                          </alternate>
                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <body>

                                      <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Contained by
                                      textstructure: floatingText text
                                      May contain
                                      Example
                                      <body>
                                       <l>Nu scylun hergan hefaenricaes uard</l>
                                       <l>metudæs maecti end his modgidanc</l>
                                       <l>uerc uuldurfadur sue he uundra gihuaes</l>
                                       <l>eci dryctin or astelidæ</l>
                                       <l>he aerist scop aelda barnum</l>
                                       <l>heben til hrofe haleg scepen.</l>
                                       <l>tha middungeard moncynnæs uard</l>
                                       <l>eci dryctin æfter tiadæ</l>
                                       <l>firum foldu frea allmectig</l>
                                       <trailer>primo cantauit Cædmon istud carmen.</trailer>
                                      </body>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <classRef key="model.divTop"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.global"/>
                                          <classRef key="model.divTop"/>
                                         </alternate>
                                        </sequence>
                                        <sequence minOccurs="0">
                                         <classRef key="model.divGenLike"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.global"/>
                                          <classRef key="model.divGenLike"/>
                                         </alternate>
                                        </sequence>
                                        <alternate>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.divLike"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.global"/>
                                           <classRef key="model.divGenLike"/>
                                          </alternate>
                                         </sequence>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.div1Like"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.global"/>
                                           <classRef key="model.divGenLike"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <sequence minOccurs="1"
                                           maxOccurs="unbounded">

                                           <alternate minOccurs="1maxOccurs="1">
                                            <elementRef key="schemaSpec"/>
                                            <classRef key="model.common"/>
                                           </alternate>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                          </sequence>
                                          <alternate minOccurs="0">
                                           <sequence minOccurs="1"
                                            maxOccurs="unbounded">

                                            <classRef key="model.divLike"/>
                                            <alternate minOccurs="0"
                                             maxOccurs="unbounded">

                                             <classRef key="model.global"/>
                                             <classRef key="model.divGenLike"/>
                                            </alternate>
                                           </sequence>
                                           <sequence minOccurs="1"
                                            maxOccurs="unbounded">

                                            <classRef key="model.div1Like"/>
                                            <alternate minOccurs="0"
                                             maxOccurs="unbounded">

                                             <classRef key="model.global"/>
                                             <classRef key="model.divGenLike"/>
                                            </alternate>
                                           </sequence>
                                          </alternate>
                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element body
                                       {
                                          tei_att.global.attributes,
                                      @@ -49,4 +49,4 @@
                                             ),
                                             ( tei_model.divBottom, tei_model.global* )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-c.html b/gl/dev/ref-c.html index 367c2d2be..deaf8fa55 100644 --- a/gl/dev/ref-c.html +++ b/gl/dev/ref-c.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <c>

                                      <c> (character) represents a character. [17.1. Linguistic Segment Categories]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      Contains a single character, a g element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc.

                                      Example
                                      <phr>
                                       <c>M</c>
                                       <c>O</c>
                                       <c>A</c>
                                       <c>I</c>
                                       <w>doth</w>
                                       <w>sway</w>
                                       <w>my</w>
                                       <w>life</w>
                                      </phr>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <c>

                                      <c> (character) represents a character. [17.1. Linguistic Segment Categories]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      Contains a single character, a g element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc.

                                      Example
                                      <phr>
                                       <c>M</c>
                                       <c>O</c>
                                       <c>A</c>
                                       <c>I</c>
                                       <w>doth</w>
                                       <w>sway</w>
                                       <w>my</w>
                                       <w>life</w>
                                      </phr>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element c
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.notated.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-cRefPattern.html b/gl/dev/ref-cRefPattern.html index 8719b9cde..671be0f35 100644 --- a/gl/dev/ref-cRefPattern.html +++ b/gl/dev/ref-cRefPattern.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <cRefPattern>

                                      <cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.patternReplacement (@matchPattern, @replacementPattern)
                                      Contained by
                                      header: refsDecl
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

                                      Example
                                      <cRefPattern matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"
                                       replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <cRefPattern>

                                      <cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.patternReplacement (@matchPattern, @replacementPattern)
                                      Contained by
                                      header: refsDecl
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

                                      Example
                                      <cRefPattern matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"
                                       replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element cRefPattern
                                       {
                                          tei_att.global.attributes,
                                          tei_att.patternReplacement.attributes,
                                          tei_model.pLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-calendar.html b/gl/dev/ref-calendar.html index fd6e49204..7422c519d 100644 --- a/gl/dev/ref-calendar.html +++ b/gl/dev/ref-calendar.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <calendar>

                                      <calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Contained by
                                      header: calendarDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="julianEngland">
                                        <p>Julian Calendar (including proleptic)</p>
                                       </calendar>
                                      </calendarDesc>
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="egyptian"
                                        target="http://en.wikipedia.org/wiki/Egyptian_calendar">

                                        <p>Egyptian calendar (as defined by Wikipedia)</p>
                                       </calendar>
                                      </calendarDesc>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <calendar>

                                      <calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Contained by
                                      header: calendarDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="julianEngland">
                                        <p>Julian Calendar (including proleptic)</p>
                                       </calendar>
                                      </calendarDesc>
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="egyptian"
                                        target="http://en.wikipedia.org/wiki/Egyptian_calendar">

                                        <p>Egyptian calendar (as defined by Wikipedia)</p>
                                       </calendar>
                                      </calendarDesc>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element calendar
                                       {
                                          tei_att.global.attributes,
                                          tei_att.pointing.attributes,
                                          tei_att.typed.attributes,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-calendarDesc.html b/gl/dev/ref-calendarDesc.html index 2843552b1..3977b5b6f 100644 --- a/gl/dev/ref-calendarDesc.html +++ b/gl/dev/ref-calendarDesc.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <calendarDesc>

                                      <calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      header: calendar
                                      Note

                                      In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="cal_AD">
                                        <p>Anno Domini (Christian Era)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AH">
                                        <p>Anno Hegirae (Muhammedan Era)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AME">
                                        <p>Mauludi Era (solar years since Mohammed's birth)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AM">
                                        <p>Anno Mundi (Jewish Calendar)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AP">
                                        <p>Anno Persici</p>
                                       </calendar>
                                       <calendar xml:id="cal_AS">
                                        <p>Aji Saka Era (Java)</p>
                                       </calendar>
                                       <calendar xml:id="cal_BE">
                                        <p>Buddhist Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CB">
                                        <p>Cooch Behar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CE">
                                        <p>Common Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CL">
                                        <p>Chinese Lunar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CS">
                                        <p>Chula Sakarat Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_EE">
                                        <p>Ethiopian Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_FE">
                                        <p>Fasli Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_ISO">
                                        <p>ISO 8601 calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_JE">
                                        <p>Japanese Calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_KE">
                                        <p>Khalsa Era (Sikh calendar)</p>
                                       </calendar>
                                       <calendar xml:id="cal_KY">
                                        <p>Kali Yuga</p>
                                       </calendar>
                                       <calendar xml:id="cal_ME">
                                        <p>Malabar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_MS">
                                        <p>Monarchic Solar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_NS">
                                        <p>Nepal Samwat Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_OS">
                                        <p>Old Style (Julian Calendar)</p>
                                       </calendar>
                                       <calendar xml:id="cal_RS">
                                        <p>Rattanakosin (Bangkok) Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_SE">
                                        <p>Saka Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_SH">
                                        <p>Mohammedan Solar Era (Iran)</p>
                                       </calendar>
                                       <calendar xml:id="cal_SS">
                                        <p>Saka Samvat</p>
                                       </calendar>
                                       <calendar xml:id="cal_TE">
                                        <p>Tripurabda Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_VE">
                                        <p>Vikrama Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_VS">
                                        <p>Vikrama Samvat Era</p>
                                       </calendar>
                                      </calendarDesc>
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="cal_Gregorian">
                                        <p>Gregorian calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Julian">
                                        <p>Julian calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Islamic">
                                        <p>Islamic or Muslim (hijri) lunar calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Hebrew">
                                        <p>Hebrew or Jewish lunisolar calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Revolutionary">
                                        <p>French Revolutionary calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Iranian">
                                        <p>Iranian or Persian (Jalaali) solar calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Coptic">
                                        <p>Coptic or Alexandrian calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Chinese">
                                        <p>Chinese lunisolar calendar</p>
                                       </calendar>
                                      </calendarDesc>
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="cal_Egyptian"
                                        target="http://en.wikipedia.org/wiki/Egyptian_calendar">

                                        <p>Egyptian calendar (as defined by Wikipedia)</p>
                                       </calendar>
                                      </calendarDesc>
                                      Content model
                                      <content>
                                       <elementRef key="calendarminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      -element calendarDesc { tei_att.global.attributes, tei_calendar+ }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <calendarDesc>

                                      <calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      header: calendar
                                      Note

                                      In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="cal_AD">
                                        <p>Anno Domini (Christian Era)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AH">
                                        <p>Anno Hegirae (Muhammedan Era)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AME">
                                        <p>Mauludi Era (solar years since Mohammed's birth)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AM">
                                        <p>Anno Mundi (Jewish Calendar)</p>
                                       </calendar>
                                       <calendar xml:id="cal_AP">
                                        <p>Anno Persici</p>
                                       </calendar>
                                       <calendar xml:id="cal_AS">
                                        <p>Aji Saka Era (Java)</p>
                                       </calendar>
                                       <calendar xml:id="cal_BE">
                                        <p>Buddhist Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CB">
                                        <p>Cooch Behar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CE">
                                        <p>Common Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CL">
                                        <p>Chinese Lunar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_CS">
                                        <p>Chula Sakarat Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_EE">
                                        <p>Ethiopian Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_FE">
                                        <p>Fasli Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_ISO">
                                        <p>ISO 8601 calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_JE">
                                        <p>Japanese Calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_KE">
                                        <p>Khalsa Era (Sikh calendar)</p>
                                       </calendar>
                                       <calendar xml:id="cal_KY">
                                        <p>Kali Yuga</p>
                                       </calendar>
                                       <calendar xml:id="cal_ME">
                                        <p>Malabar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_MS">
                                        <p>Monarchic Solar Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_NS">
                                        <p>Nepal Samwat Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_OS">
                                        <p>Old Style (Julian Calendar)</p>
                                       </calendar>
                                       <calendar xml:id="cal_RS">
                                        <p>Rattanakosin (Bangkok) Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_SE">
                                        <p>Saka Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_SH">
                                        <p>Mohammedan Solar Era (Iran)</p>
                                       </calendar>
                                       <calendar xml:id="cal_SS">
                                        <p>Saka Samvat</p>
                                       </calendar>
                                       <calendar xml:id="cal_TE">
                                        <p>Tripurabda Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_VE">
                                        <p>Vikrama Era</p>
                                       </calendar>
                                       <calendar xml:id="cal_VS">
                                        <p>Vikrama Samvat Era</p>
                                       </calendar>
                                      </calendarDesc>
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="cal_Gregorian">
                                        <p>Gregorian calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Julian">
                                        <p>Julian calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Islamic">
                                        <p>Islamic or Muslim (hijri) lunar calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Hebrew">
                                        <p>Hebrew or Jewish lunisolar calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Revolutionary">
                                        <p>French Revolutionary calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Iranian">
                                        <p>Iranian or Persian (Jalaali) solar calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Coptic">
                                        <p>Coptic or Alexandrian calendar</p>
                                       </calendar>
                                       <calendar xml:id="cal_Chinese">
                                        <p>Chinese lunisolar calendar</p>
                                       </calendar>
                                      </calendarDesc>
                                      Example
                                      <calendarDesc>
                                       <calendar xml:id="cal_Egyptian"
                                        target="http://en.wikipedia.org/wiki/Egyptian_calendar">

                                        <p>Egyptian calendar (as defined by Wikipedia)</p>
                                       </calendar>
                                      </calendarDesc>
                                      Content model
                                      <content>
                                       <elementRef key="calendarminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +element calendarDesc { tei_att.global.attributes, tei_calendar+ }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-catDesc.html b/gl/dev/ref-catDesc.html index 039796acf..70e6e26ed 100644 --- a/gl/dev/ref-catDesc.html +++ b/gl/dev/ref-catDesc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <catDesc>

                                      <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Contained by
                                      header: category
                                      May contain
                                      Example
                                      <catDesc>Prose reportage</catDesc>
                                      Example
                                      <catDesc>
                                       <textDesc n="novel">
                                        <channel mode="w">print; part issues</channel>
                                        <constitution type="single"/>
                                        <derivation type="original"/>
                                        <domain type="art"/>
                                        <factuality type="fiction"/>
                                        <interaction type="none"/>
                                        <preparedness type="prepared"/>
                                        <purpose type="entertaindegree="high"/>
                                        <purpose type="informdegree="medium"/>
                                       </textDesc>
                                      </catDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.limitedPhrase"/>
                                        <classRef key="model.catDescPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <catDesc>

                                      <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Contained by
                                      header: category
                                      May contain
                                      Example
                                      <catDesc>Prose reportage</catDesc>
                                      Example
                                      <catDesc>
                                       <textDesc n="novel">
                                        <channel mode="w">print; part issues</channel>
                                        <constitution type="single"/>
                                        <derivation type="original"/>
                                        <domain type="art"/>
                                        <factuality type="fiction"/>
                                        <interaction type="none"/>
                                        <preparedness type="prepared"/>
                                        <purpose type="entertaindegree="high"/>
                                        <purpose type="informdegree="medium"/>
                                       </textDesc>
                                      </catDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.limitedPhrase"/>
                                        <classRef key="model.catDescPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element catDesc
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          ( text | tei_model.limitedPhrase | tei_model.catDescPart )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-catRef.html b/gl/dev/ref-catRef.html index 0cee6f861..628f0582a 100644 --- a/gl/dev/ref-catRef.html +++ b/gl/dev/ref-catRef.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <catRef>

                                      <catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate)
                                      schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a taxonomy element, or by some other resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Contained by
                                      core: imprint
                                      header: textClass
                                      May containEmpty element
                                      Note

                                      The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

                                      Example
                                      <catRef scheme="#myTopics"
                                       target="#news #prov #sales2"/>

                                      <!-- elsewhere -->
                                      <taxonomy xml:id="myTopics">
                                       <category xml:id="news">
                                        <catDesc>Newspapers</catDesc>
                                       </category>
                                       <category xml:id="prov">
                                        <catDesc>Provincial</catDesc>
                                       </category>
                                       <category xml:id="sales2">
                                        <catDesc>Low to average annual sales</catDesc>
                                       </category>
                                      </taxonomy>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <catRef>

                                      <catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate)
                                      schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a taxonomy element, or by some other resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Contained by
                                      core: imprint
                                      header: textClass
                                      May containEmpty element
                                      Note

                                      The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

                                      Example
                                      <catRef scheme="#myTopics"
                                       target="#news #prov #sales2"/>

                                      <!-- elsewhere -->
                                      <taxonomy xml:id="myTopics">
                                       <category xml:id="news">
                                        <catDesc>Newspapers</catDesc>
                                       </category>
                                       <category xml:id="prov">
                                        <catDesc>Provincial</catDesc>
                                       </category>
                                       <category xml:id="sales2">
                                        <catDesc>Low to average annual sales</catDesc>
                                       </category>
                                      </taxonomy>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element catRef
                                       {
                                          tei_att.global.attributes,
                                          tei_att.pointing.attributes,
                                          attribute scheme { teidata.pointer }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-catchwords.html b/gl/dev/ref-catchwords.html index 39d8999ca..797a9e013 100644 --- a/gl/dev/ref-catchwords.html +++ b/gl/dev/ref-catchwords.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <catchwords>

                                      <catchwords> (catchwords) describes the system used to ensure correct ordering of the quires or similar making up a codex, incunable, or other object typically by means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <catchwords>Vertical catchwords in the hand of the scribe placed along
                                      the inner bounding line, reading from top to bottom.</catchwords>
                                      Schematron

                                      <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element catchwords { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <catchwords>

                                      <catchwords> (catchwords) describes the system used to ensure correct ordering of the quires or similar making up a codex, incunable, or other object typically by means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <catchwords>Vertical catchwords in the hand of the scribe placed along
                                      the inner bounding line, reading from top to bottom.</catchwords>
                                      Schematron

                                      <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element catchwords { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-category.html b/gl/dev/ref-category.html index f0e46663c..d5da557ac 100644 --- a/gl/dev/ref-category.html +++ b/gl/dev/ref-category.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <category>

                                      <category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      core: desc gloss
                                      Example
                                      <category xml:id="b1">
                                       <catDesc>Prose reportage</catDesc>
                                      </category>
                                      Example
                                      <category xml:id="b2">
                                       <catDesc>Prose </catDesc>
                                       <category xml:id="b11">
                                        <catDesc>journalism</catDesc>
                                       </category>
                                       <category xml:id="b12">
                                        <catDesc>fiction</catDesc>
                                       </category>
                                      </category>
                                      Example
                                      <category xml:id="LIT">
                                       <catDesc xml:lang="pl">literatura piękna</catDesc>
                                       <catDesc xml:lang="en">fiction</catDesc>
                                       <category xml:id="LPROSE">
                                        <catDesc xml:lang="pl">proza</catDesc>
                                        <catDesc xml:lang="en">prose</catDesc>
                                       </category>
                                       <category xml:id="LPOETRY">
                                        <catDesc xml:lang="pl">poezja</catDesc>
                                        <catDesc xml:lang="en">poetry</catDesc>
                                       </category>
                                       <category xml:id="LDRAMA">
                                        <catDesc xml:lang="pl">dramat</catDesc>
                                        <catDesc xml:lang="en">drama</catDesc>
                                       </category>
                                      </category>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate>
                                         <elementRef key="catDescminOccurs="1"
                                          maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.descLike"/>
                                          <elementRef key="equiv"/>
                                          <elementRef key="gloss"/>
                                         </alternate>
                                        </alternate>
                                        <elementRef key="categoryminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <category>

                                      <category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      core: desc gloss
                                      Example
                                      <category xml:id="b1">
                                       <catDesc>Prose reportage</catDesc>
                                      </category>
                                      Example
                                      <category xml:id="b2">
                                       <catDesc>Prose </catDesc>
                                       <category xml:id="b11">
                                        <catDesc>journalism</catDesc>
                                       </category>
                                       <category xml:id="b12">
                                        <catDesc>fiction</catDesc>
                                       </category>
                                      </category>
                                      Example
                                      <category xml:id="LIT">
                                       <catDesc xml:lang="pl">literatura piękna</catDesc>
                                       <catDesc xml:lang="en">fiction</catDesc>
                                       <category xml:id="LPROSE">
                                        <catDesc xml:lang="pl">proza</catDesc>
                                        <catDesc xml:lang="en">prose</catDesc>
                                       </category>
                                       <category xml:id="LPOETRY">
                                        <catDesc xml:lang="pl">poezja</catDesc>
                                        <catDesc xml:lang="en">poetry</catDesc>
                                       </category>
                                       <category xml:id="LDRAMA">
                                        <catDesc xml:lang="pl">dramat</catDesc>
                                        <catDesc xml:lang="en">drama</catDesc>
                                       </category>
                                      </category>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate>
                                         <elementRef key="catDescminOccurs="1"
                                          maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.descLike"/>
                                          <elementRef key="equiv"/>
                                          <elementRef key="gloss"/>
                                         </alternate>
                                        </alternate>
                                        <elementRef key="categoryminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element category
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                             ( tei_catDesc+ | ( tei_model.descLike | equiv | tei_gloss )* ),
                                             tei_category*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-cb.html b/gl/dev/ref-cb.html index ec02b99f1..0b5b96e77 100644 --- a/gl/dev/ref-cb.html +++ b/gl/dev/ref-cb.html @@ -22,7 +22,7 @@ }); });

                                      <cb>

                                      <cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone -Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this cb element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The cb element is placed at the head of the column to which it refers.

                                      Example

                                      Markup of an early English dictionary printed in two columns:

                                      <pb/>
                                      <cb n="1"/>
                                      <entryFree>
                                       <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
                                      <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
                                         sinks into the Ground, to find out and disappoint the Enemies Mines,
                                         or to prepare one</sense>.
                                      </entryFree>
                                      <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
                                      <sense>lie groveling</sense>.</entryFree>
                                      <!-- remainder of column -->
                                      <cb n="2"/>
                                      <entryFree>
                                       <form>Wey</form>, <sense>the greatest Measure for dry Things,
                                         containing five Chaldron</sense>.
                                      </entryFree>
                                      <entryFree>
                                       <form>Whale</form>, <sense>the greatest of
                                         Sea-Fishes</sense>.
                                      </entryFree>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this cb element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The cb element is placed at the head of the column to which it refers.

                                      Example

                                      Markup of an early English dictionary printed in two columns:

                                      <pb/>
                                      <cb n="1"/>
                                      <entryFree>
                                       <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
                                      <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
                                         sinks into the Ground, to find out and disappoint the Enemies Mines,
                                         or to prepare one</sense>.
                                      </entryFree>
                                      <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
                                      <sense>lie groveling</sense>.</entryFree>
                                      <!-- remainder of column -->
                                      <cb n="2"/>
                                      <entryFree>
                                       <form>Wey</form>, <sense>the greatest Measure for dry Things,
                                         containing five Chaldron</sense>.
                                      </entryFree>
                                      <entryFree>
                                       <form>Whale</form>, <sense>the greatest of
                                         Sea-Fishes</sense>.
                                      </entryFree>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element cb
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.spanning.attributes,
                                          tei_att.breaking.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-cell.html b/gl/dev/ref-cell.html index 53084efa9..3a3de9cc3 100644 --- a/gl/dev/ref-cell.html +++ b/gl/dev/ref-cell.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <cell>

                                      <cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.tableDecoration (@role, @rows, @cols)
                                      Contained by
                                      figures: row
                                      May contain
                                      Example
                                      <row>
                                       <cell role="label">General conduct</cell>
                                       <cell role="data">Not satisfactory, on account of his great unpunctuality
                                         and inattention to duties</cell>
                                      </row>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <cell>

                                      <cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.tableDecoration (@role, @rows, @cols)
                                      Contained by
                                      figures: row
                                      May contain
                                      Example
                                      <row>
                                       <cell role="label">General conduct</cell>
                                       <cell role="data">Not satisfactory, on account of his great unpunctuality
                                         and inattention to duties</cell>
                                      </row>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element cell
                                       {
                                          tei_att.global.attributes,
                                          tei_att.tableDecoration.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-certainty.html b/gl/dev/ref-certainty.html index 3dc62ac82..f9b77fc3c 100644 --- a/gl/dev/ref-certainty.html +++ b/gl/dev/ref-certainty.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <certainty>

                                      <certainty> indicates the degree of certainty associated with some aspect of the text markup. [21.1.2. Structured Indications of Uncertainty]
                                      Modulecertainty
                                      Attributesatt.scoping (@target, @match) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (cert, @resp) att.global.source (@source) att.typed (type, @subtype)
                                      cert(certainty) signifies the degree of certainty associated with the object pointed to by the certainty element.
                                      Derived fromatt.global.responsibility
                                      Status Optional
                                      Datatype teidata.certainty
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology; sample categorization of annotations of uncertainty might use following values:
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      ignorance
                                      incompleteness
                                      credibility
                                      imprecision
                                      locusindicates more exactly the aspect concerning which certainty is being expressed: specifically, whether the markup is correctly located, whether the correct element or attribute name has been used, or whether the content of the element or attribute is correct, etc.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      name
                                      uncertainty concerns whether the name of the element or attribute used is correctly applied.
                                      start
                                      uncertainty concerns whether the start of the element is correctly identified.
                                      end
                                      uncertainty concerns whether the end of the element is correctly identified.
                                      location
                                      uncertainty concerns both the start and the end of the element.
                                      value
                                      uncertainty concerns the content (for an element) or the value (for an attribute)
                                      assertedValueprovides an alternative value for the aspect of the markup in question—an alternative generic identifier, transcription, or attribute value, or the identifier of an anchor element (to indicate an alternative starting or ending location). If an assertedValue is given, the confidence level specified by degree applies to the alternative markup specified by assertedValue; if none is given, it applies to the markup in the text.
                                      Status Recommended
                                      Datatype teidata.word
                                      <certainty target="#ESXlocus="name"
                                       assertedValue="placeNamecert="low">

                                       <desc>It is unlikely, but possible, that this refers to the place
                                         rather than the person.</desc>
                                      </certainty>
                                      Note

                                      This attribute makes it possible to indicate the degree of confidence in a specific alternative to some aspect of the markup. In the first example above the encoder is expressing the likelihood (.2) that the generic identifier should be placeName rather than persName, which is the coded element.

                                      givenindicates one or more element(s) characterizing the conditions which are assumed in the assignment of a degree of confidence.
                                      Status Recommended
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The envisioned typical value of this attribute would be the identifier of another certainty element or a list of such identifiers. It may thus be possible to construct probability networks by chaining certainty elements together. Such networks would ultimately be grounded in unconditional certainty elements (with no value for given). The semantics of this chaining would be understood in this way: if a certainty element is specified, via a reference, as the assumption, then it is not the attribution of uncertainty that is the assumption, but rather the assertion itself. For instance, in the example above, the first certainty element indicates that the confidence in the identification of the new scribe as msm. The second indicates the degree of confidence that Essex is a personal name, given that the new scribe is msm. Note that the given in the second certainty element is not the assertion that the likelihood that msm is the new scribe is 0.6, but simply the assertion that msm is the new scribe; this is a recommended convention to facilitate building networks.

                                      The ambitious encoder may wish to attempt complex networks or probability assertions, experimenting with references to other elements or prose assertions, and deploying feature structure connectives such as <alt>, join, and note. However, we do not believe that the certainty element gives, at this time, a comprehensive ambiguity-free system for indicating certainty.

                                      degreeindicates the degree of confidence assigned to the aspect of the markup named by the locus attribute.
                                      Status Optional
                                      Datatype teidata.probability
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example

                                      (For discussion of this example, see section [ID CEconcon in TEI Guidelines])

                                      Ernest went to <anchor xml:id="A1"/> old
                                      <persName xml:id="SYB">Saybrook</persName>.

                                      <certainty xml:id="c1target="#SYB"
                                       locus="namedegree="0.6"/>

                                      <certainty target="#SYBlocus="start"
                                       given="#c1degree="0.9"/>

                                      <certainty xml:id="C-c2target="#SYB"
                                       locus="nameassertedValue="persNamedegree="0.4"/>

                                      <certainty target="#SYBlocus="start"
                                       given="#C-c2degree="0.5"/>

                                      <certainty target="#SYBlocus="start"
                                       assertedValue="#a1given="#c1degree="0.5"/>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <certainty>

                                      <certainty> indicates the degree of certainty associated with some aspect of the text markup. [21.1.2. Structured Indications of Uncertainty]
                                      Modulecertainty
                                      Attributesatt.scoping (@target, @match) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (cert, @resp) att.global.source (@source) att.typed (type, @subtype)
                                      cert(certainty) signifies the degree of certainty associated with the object pointed to by the certainty element.
                                      Derived fromatt.global.responsibility
                                      Status Optional
                                      Datatype teidata.certainty
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology; sample categorization of annotations of uncertainty might use following values:
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      ignorance
                                      incompleteness
                                      credibility
                                      imprecision
                                      locusindicates more exactly the aspect concerning which certainty is being expressed: specifically, whether the markup is correctly located, whether the correct element or attribute name has been used, or whether the content of the element or attribute is correct, etc.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      name
                                      uncertainty concerns whether the name of the element or attribute used is correctly applied.
                                      start
                                      uncertainty concerns whether the start of the element is correctly identified.
                                      end
                                      uncertainty concerns whether the end of the element is correctly identified.
                                      location
                                      uncertainty concerns both the start and the end of the element.
                                      value
                                      uncertainty concerns the content (for an element) or the value (for an attribute)
                                      assertedValueprovides an alternative value for the aspect of the markup in question—an alternative generic identifier, transcription, or attribute value, or the identifier of an anchor element (to indicate an alternative starting or ending location). If an assertedValue is given, the confidence level specified by degree applies to the alternative markup specified by assertedValue; if none is given, it applies to the markup in the text.
                                      Status Recommended
                                      Datatype teidata.word
                                      <certainty target="#ESXlocus="name"
                                       assertedValue="placeNamecert="low">

                                       <desc>It is unlikely, but possible, that this refers to the place
                                         rather than the person.</desc>
                                      </certainty>
                                      Note

                                      This attribute makes it possible to indicate the degree of confidence in a specific alternative to some aspect of the markup. In the first example above the encoder is expressing the likelihood (.2) that the generic identifier should be placeName rather than persName, which is the coded element.

                                      givenindicates one or more element(s) characterizing the conditions which are assumed in the assignment of a degree of confidence.
                                      Status Recommended
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Note

                                      The envisioned typical value of this attribute would be the identifier of another certainty element or a list of such identifiers. It may thus be possible to construct probability networks by chaining certainty elements together. Such networks would ultimately be grounded in unconditional certainty elements (with no value for given). The semantics of this chaining would be understood in this way: if a certainty element is specified, via a reference, as the assumption, then it is not the attribution of uncertainty that is the assumption, but rather the assertion itself. For instance, in the example above, the first certainty element indicates that the confidence in the identification of the new scribe as msm. The second indicates the degree of confidence that Essex is a personal name, given that the new scribe is msm. Note that the given in the second certainty element is not the assertion that the likelihood that msm is the new scribe is 0.6, but simply the assertion that msm is the new scribe; this is a recommended convention to facilitate building networks.

                                      The ambitious encoder may wish to attempt complex networks or probability assertions, experimenting with references to other elements or prose assertions, and deploying feature structure connectives such as <alt>, join, and note. However, we do not believe that the certainty element gives, at this time, a comprehensive ambiguity-free system for indicating certainty.

                                      degreeindicates the degree of confidence assigned to the aspect of the markup named by the locus attribute.
                                      Status Optional
                                      Datatype teidata.probability
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example

                                      (For discussion of this example, see section [ID CEconcon in TEI Guidelines])

                                      Ernest went to <anchor xml:id="A1"/> old
                                      <persName xml:id="SYB">Saybrook</persName>.

                                      <certainty xml:id="c1target="#SYB"
                                       locus="namedegree="0.6"/>

                                      <certainty target="#SYBlocus="start"
                                       given="#c1degree="0.9"/>

                                      <certainty xml:id="C-c2target="#SYB"
                                       locus="nameassertedValue="persNamedegree="0.4"/>

                                      <certainty target="#SYBlocus="start"
                                       given="#C-c2degree="0.5"/>

                                      <certainty target="#SYBlocus="start"
                                       assertedValue="#a1given="#c1degree="0.5"/>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element certainty
                                       {
                                          tei_att.global.attribute.xmlid,
                                      @@ -54,4 +54,4 @@
                                          attribute given { list { teidata.pointer+ } }?,
                                          attribute degree { teidata.probability }?,
                                          ( tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-change.html b/gl/dev/ref-change.html index 08ad16df2..02dd9d5f6 100644 --- a/gl/dev/ref-change.html +++ b/gl/dev/ref-change.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <change>

                                      <change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
                                      Moduleheader
                                      Attributesatt.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      target(target) points to one or more elements that belong to this change.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Contained by
                                      msdescription: recordHist
                                      May contain
                                      Note

                                      The who attribute may be used to point to any other element, but will typically specify a respStmt or person element elsewhere in the header, identifying the person responsible for the change and their role in making it.

                                      It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

                                      Example
                                      <titleStmt>
                                       <title> ... </title>
                                       <editor xml:id="LDB">Lou Burnard</editor>
                                       <respStmt xml:id="BZ">
                                        <resp>copy editing</resp>
                                        <name>Brett Zamir</name>
                                       </respStmt>
                                      </titleStmt>
                                      <!-- ... -->
                                      <revisionDesc status="published">
                                       <change who="#BZwhen="2008-02-02"
                                        status="public">
                                      Finished chapter 23</change>
                                       <change who="#BZwhen="2008-01-02"
                                        status="draft">
                                      Finished chapter 2</change>
                                       <change n="P2.2when="1991-12-21"
                                        who="#LDB">
                                      Added examples to section 3</change>
                                       <change when="1991-11-11who="#MSM">Deleted chapter 10</change>
                                      </revisionDesc>
                                      Example
                                      <profileDesc>
                                       <creation>
                                        <listChange>
                                         <change xml:id="DRAFT1">First draft in pencil</change>
                                         <change xml:id="DRAFT2"
                                          notBefore="1880-12-09">
                                      First revision, mostly
                                             using green ink</change>
                                         <change xml:id="DRAFT3"
                                          notBefore="1881-02-13">
                                      Final corrections as
                                             supplied to printer.</change>
                                        </listChange>
                                       </creation>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <change>

                                      <change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
                                      Moduleheader
                                      Attributesatt.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      target(target) points to one or more elements that belong to this change.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Contained by
                                      msdescription: recordHist
                                      May contain
                                      Note

                                      The who attribute may be used to point to any other element, but will typically specify a respStmt or person element elsewhere in the header, identifying the person responsible for the change and their role in making it.

                                      It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

                                      Example
                                      <titleStmt>
                                       <title> ... </title>
                                       <editor xml:id="LDB">Lou Burnard</editor>
                                       <respStmt xml:id="BZ">
                                        <resp>copy editing</resp>
                                        <name>Brett Zamir</name>
                                       </respStmt>
                                      </titleStmt>
                                      <!-- ... -->
                                      <revisionDesc status="published">
                                       <change who="#BZwhen="2008-02-02"
                                        status="public">
                                      Finished chapter 23</change>
                                       <change who="#BZwhen="2008-01-02"
                                        status="draft">
                                      Finished chapter 2</change>
                                       <change n="P2.2when="1991-12-21"
                                        who="#LDB">
                                      Added examples to section 3</change>
                                       <change when="1991-11-11who="#MSM">Deleted chapter 10</change>
                                      </revisionDesc>
                                      Example
                                      <profileDesc>
                                       <creation>
                                        <listChange>
                                         <change xml:id="DRAFT1">First draft in pencil</change>
                                         <change xml:id="DRAFT2"
                                          notBefore="1880-12-09">
                                      First revision, mostly
                                             using green ink</change>
                                         <change xml:id="DRAFT3"
                                          notBefore="1881-02-13">
                                      Final corrections as
                                             supplied to printer.</change>
                                        </listChange>
                                       </creation>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element change
                                       {
                                          tei_att.ascribed.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.typed.attributes,
                                          attribute target { list { teidata.pointer+ } }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-charDecl.html b/gl/dev/ref-charDecl.html index 75c372376..66356d019 100644 --- a/gl/dev/ref-charDecl.html +++ b/gl/dev/ref-charDecl.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <charDecl>

                                      <charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: desc
                                      gaiji: glyph
                                      Example
                                      <charDecl>
                                       <char xml:id="aENL">
                                        <unicodeProp name="Name"
                                         value="LATIN LETTER ENLARGED SMALL A"/>

                                        <mapping type="standard">a</mapping>
                                       </char>
                                      </charDecl>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"/>
                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="char"/>
                                         <elementRef key="glyph"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <charDecl>

                                      <charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: desc
                                      gaiji: glyph
                                      Example
                                      <charDecl>
                                       <char xml:id="aENL">
                                        <unicodeProp name="Name"
                                         value="LATIN LETTER ENLARGED SMALL A"/>

                                        <mapping type="standard">a</mapping>
                                       </char>
                                      </charDecl>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"/>
                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="char"/>
                                         <elementRef key="glyph"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element charDecl
                                       {
                                          tei_att.global.attributes,
                                          ( tei_desc?, ( char | tei_glyph )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-choice.html b/gl/dev/ref-choice.html index 9e4470ad2..82f6dd723 100644 --- a/gl/dev/ref-choice.html +++ b/gl/dev/ref-choice.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <choice>

                                      <choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Because the children of a choice element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

                                      Note also that choice elements may self-nest.

                                      Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the app element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

                                      Example

                                      An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.

                                      <p>Lastly, That, upon his solemn oath to observe all the above
                                      articles, the said man-mountain shall have a daily allowance of
                                      meat and drink sufficient for the support of <choice>
                                        <sic>1724</sic>
                                        <corr>1728</corr>
                                       </choice> of our subjects,
                                      with free access to our royal person, and other marks of our
                                      <choice>
                                        <orig>favour</orig>
                                        <reg>favor</reg>
                                       </choice>.</p>
                                      Content model
                                      <content>
                                       <alternate minOccurs="2"
                                        maxOccurs="unbounded">

                                        <classRef key="model.choicePart"/>
                                        <elementRef key="choice"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <choice>

                                      <choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Because the children of a choice element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

                                      Note also that choice elements may self-nest.

                                      Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the app element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

                                      Example

                                      An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.

                                      <p>Lastly, That, upon his solemn oath to observe all the above
                                      articles, the said man-mountain shall have a daily allowance of
                                      meat and drink sufficient for the support of <choice>
                                        <sic>1724</sic>
                                        <corr>1728</corr>
                                       </choice> of our subjects,
                                      with free access to our royal person, and other marks of our
                                      <choice>
                                        <orig>favour</orig>
                                        <reg>favor</reg>
                                       </choice>.</p>
                                      Content model
                                      <content>
                                       <alternate minOccurs="2"
                                        maxOccurs="unbounded">

                                        <classRef key="model.choicePart"/>
                                        <elementRef key="choice"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element choice
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.choicePart | tei_choice )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-cit.html b/gl/dev/ref-cit.html index 8cb2293aa..763569deb 100644 --- a/gl/dev/ref-cit.html +++ b/gl/dev/ref-cit.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <cit>

                                      <cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <cit>
                                       <quote>and the breath of the whale is frequently attended with such an insupportable smell,
                                         as to bring on disorder of the brain.</quote>
                                       <bibl>Ulloa's South America</bibl>
                                      </cit>
                                      Example
                                      <entry>
                                       <form>
                                        <orth>horrifier</orth>
                                       </form>
                                       <cit type="translationxml:lang="en">
                                        <quote>to horrify</quote>
                                       </cit>
                                       <cit type="example">
                                        <quote>elle était horrifiée par la dépense</quote>
                                        <cit type="translationxml:lang="en">
                                         <quote>she was horrified at the expense.</quote>
                                        </cit>
                                       </cit>
                                      </entry>
                                      Example
                                      <cit type="example">
                                       <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
                                       <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
                                        mimeType="audio/wav"/>

                                       <cit type="translation">
                                        <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
                                       </cit>
                                       <cit type="translation">
                                        <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
                                       </cit>
                                      </cit>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.biblLike"/>
                                        <classRef key="model.egLike"/>
                                        <classRef key="model.entryPart"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <classRef key="model.attributable"/>
                                        <elementRef key="pc"/>
                                        <elementRef key="q"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <cit>

                                      <cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <cit>
                                       <quote>and the breath of the whale is frequently attended with such an insupportable smell,
                                         as to bring on disorder of the brain.</quote>
                                       <bibl>Ulloa's South America</bibl>
                                      </cit>
                                      Example
                                      <entry>
                                       <form>
                                        <orth>horrifier</orth>
                                       </form>
                                       <cit type="translationxml:lang="en">
                                        <quote>to horrify</quote>
                                       </cit>
                                       <cit type="example">
                                        <quote>elle était horrifiée par la dépense</quote>
                                        <cit type="translationxml:lang="en">
                                         <quote>she was horrified at the expense.</quote>
                                        </cit>
                                       </cit>
                                      </entry>
                                      Example
                                      <cit type="example">
                                       <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
                                       <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
                                        mimeType="audio/wav"/>

                                       <cit type="translation">
                                        <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
                                       </cit>
                                       <cit type="translation">
                                        <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
                                       </cit>
                                      </cit>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.biblLike"/>
                                        <classRef key="model.egLike"/>
                                        <classRef key="model.entryPart"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <classRef key="model.attributable"/>
                                        <elementRef key="pc"/>
                                        <elementRef key="q"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element cit
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                           | tei_pc
                                           | tei_q
                                          )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-citeData.html b/gl/dev/ref-citeData.html index e2e6cdaf1..eec560eaa 100644 --- a/gl/dev/ref-citeData.html +++ b/gl/dev/ref-citeData.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <citeData>

                                      <citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citeStructurePart (@use)
                                      property(property) A URI indicating a property definition.
                                      Status Required
                                      Datatype teidata.pointer
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <citeStructure unit="book"
                                       match="//body/divuse="@n">

                                       <citeData property="http://purl.org/dc/terms/title"
                                        use="head"/>

                                      </citeStructure>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <citeData>

                                      <citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citeStructurePart (@use)
                                      property(property) A URI indicating a property definition.
                                      Status Required
                                      Datatype teidata.pointer
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <citeStructure unit="book"
                                       match="//body/divuse="@n">

                                       <citeData property="http://purl.org/dc/terms/title"
                                        use="head"/>

                                      </citeStructure>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element citeData
                                       {
                                          tei_att.global.attributes,
                                          tei_att.citeStructurePart.attributes,
                                          attribute property { teidata.pointer },
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-citeStructure.html b/gl/dev/ref-citeStructure.html index a6b1b7357..61564a73b 100644 --- a/gl/dev/ref-citeStructure.html +++ b/gl/dev/ref-citeStructure.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <citeStructure>

                                      <citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citeStructurePart (@use)
                                      delim(delimiter) supplies a delimiting string preceding the structural component.
                                      Status Optional
                                      Datatype string
                                      Note

                                      delim must contain at least one character.

                                      match(match) supplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a citeStructure without a citeStructure parent must be an absolute XPath. If it is relative, its context is set by the match of the parent citeStructure.
                                      Status Required
                                      Datatype teidata.xpath
                                      Schematron

                                      <s:rule context="tei:citeStructure[not(parent::tei:citeStructure)]">
                                      <s:assert test="starts-with(@match,'/')">An XPath in @match on the outer <s:name/> must start with '/'.</s:assert>
                                      </s:rule>
                                      Schematron

                                      <s:rule context="tei:citeStructure[parent::tei:citeStructure]">
                                      <s:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <s:name/>.</s:assert>
                                      </s:rule>
                                      unit(unit) describes the structural unit indicated by the citeStructure.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      book
                                      chapter
                                      entry
                                      poem
                                      letter
                                      line
                                      section
                                      verse
                                      volume
                                      Contained by
                                      May contain
                                      Example
                                      <citeStructure unit="book"
                                       match="//body/divuse="@n">

                                       <citeStructure unit="chaptermatch="div"
                                        use="position()delim=" ">

                                        <citeStructure unit="versematch="div"
                                         use="position()delim=":"/>

                                       </citeStructure>
                                      </citeStructure>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="citeDataminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="citeStructure"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <citeStructure>

                                      <citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 16.2.5.4. Citation Structures]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citeStructurePart (@use)
                                      delim(delimiter) supplies a delimiting string preceding the structural component.
                                      Status Optional
                                      Datatype string
                                      Note

                                      delim must contain at least one character.

                                      match(match) supplies an XPath selection pattern using the syntax defined in [ID XSLT3 in TEI Guidelines] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a citeStructure without a citeStructure parent must be an absolute XPath. If it is relative, its context is set by the match of the parent citeStructure.
                                      Status Required
                                      Datatype teidata.xpath
                                      Schematron

                                      <s:rule context="tei:citeStructure[not(parent::tei:citeStructure)]">
                                      <s:assert test="starts-with(@match,'/')">An XPath in @match on the outer <s:name/> must start with '/'.</s:assert>
                                      </s:rule>
                                      Schematron

                                      <s:rule context="tei:citeStructure[parent::tei:citeStructure]">
                                      <s:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <s:name/>.</s:assert>
                                      </s:rule>
                                      unit(unit) describes the structural unit indicated by the citeStructure.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      book
                                      chapter
                                      entry
                                      poem
                                      letter
                                      line
                                      section
                                      verse
                                      volume
                                      Contained by
                                      May contain
                                      Example
                                      <citeStructure unit="book"
                                       match="//body/divuse="@n">

                                       <citeStructure unit="chaptermatch="div"
                                        use="position()delim=" ">

                                        <citeStructure unit="versematch="div"
                                         use="position()delim=":"/>

                                       </citeStructure>
                                      </citeStructure>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="citeDataminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="citeStructure"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element citeStructure
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute match { teidata.xpath },
                                          attribute unit { teidata.enumerated }?,
                                          ( tei_citeData*, tei_citeStructure*, tei_model.descLike* )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-citedRange.html b/gl/dev/ref-citedRange.html index 53ea22a07..27670177b 100644 --- a/gl/dev/ref-citedRange.html +++ b/gl/dev/ref-citedRange.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <citedRange>

                                      <citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When a single page is being cited, use the from and to attributes with 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>.

                                      Example
                                      <citedRange>pp 12–13</citedRange>
                                      <citedRange unit="pagefrom="12to="13"/>
                                      <citedRange unit="volume">II</citedRange>
                                      <citedRange unit="page">12</citedRange>
                                      Example
                                      <bibl>
                                       <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.
                                         4-5</citedRange>
                                      </bibl>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <citedRange>

                                      <citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When a single page is being cited, use the from and to attributes with 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>.

                                      Example
                                      <citedRange>pp 12–13</citedRange>
                                      <citedRange unit="pagefrom="12to="13"/>
                                      <citedRange unit="volume">II</citedRange>
                                      <citedRange unit="page">12</citedRange>
                                      Example
                                      <bibl>
                                       <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.
                                         4-5</citedRange>
                                      </bibl>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element citedRange
                                       {
                                          tei_att.global.attributes,
                                          tei_att.pointing.attributes,
                                          tei_att.citing.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-classCode.html b/gl/dev/ref-classCode.html index 5e9029a00..8098389b1 100644 --- a/gl/dev/ref-classCode.html +++ b/gl/dev/ref-classCode.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <classCode>

                                      <classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      schemeidentifies the classification system in use, as defined by, e.g. a taxonomy element, or some other resource.
                                      Status Required
                                      Datatype teidata.pointer
                                      Contained by
                                      core: imprint
                                      header: textClass
                                      May contain
                                      Example
                                      <classCode scheme="http://www.udc.org">410</classCode>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <classCode>

                                      <classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      schemeidentifies the classification system in use, as defined by, e.g. a taxonomy element, or some other resource.
                                      Status Required
                                      Datatype teidata.pointer
                                      Contained by
                                      core: imprint
                                      header: textClass
                                      May contain
                                      Example
                                      <classCode scheme="http://www.udc.org">410</classCode>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element classCode
                                       {
                                          tei_att.global.attributes,
                                          attribute scheme { teidata.pointer },
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-classDecl.html b/gl/dev/ref-classDecl.html index 373e7258e..158352ff8 100644 --- a/gl/dev/ref-classDecl.html +++ b/gl/dev/ref-classDecl.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <classDecl>

                                      <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      header: taxonomy
                                      Example
                                      <classDecl>
                                       <taxonomy xml:id="LCSH">
                                        <bibl>Library of Congress Subject Headings</bibl>
                                       </taxonomy>
                                      </classDecl>
                                      <!-- ... -->
                                      <textClass>
                                       <keywords scheme="#LCSH">
                                        <term>Political science</term>
                                        <term>United States -- Politics and government —
                                           Revolution, 1775-1783</term>
                                       </keywords>
                                      </textClass>
                                      Content model
                                      <content>
                                       <elementRef key="taxonomyminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      -element classDecl { tei_att.global.attributes, tei_taxonomy+ }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <classDecl>

                                      <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      header: taxonomy
                                      Example
                                      <classDecl>
                                       <taxonomy xml:id="LCSH">
                                        <bibl>Library of Congress Subject Headings</bibl>
                                       </taxonomy>
                                      </classDecl>
                                      <!-- ... -->
                                      <textClass>
                                       <keywords scheme="#LCSH">
                                        <term>Political science</term>
                                        <term>United States -- Politics and government —
                                           Revolution, 1775-1783</term>
                                       </keywords>
                                      </textClass>
                                      Content model
                                      <content>
                                       <elementRef key="taxonomyminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +element classDecl { tei_att.global.attributes, tei_taxonomy+ }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-collation.html b/gl/dev/ref-collation.html index d0ca2559c..5f24fe6ad 100644 --- a/gl/dev/ref-collation.html +++ b/gl/dev/ref-collation.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <collation>

                                      <collation> (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <collation>The written leaves preceded by an original flyleaf,
                                      conjoint with the pastedown.</collation>
                                      Example
                                      <collation>
                                       <p>
                                        <formula>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)</formula>
                                        <catchwords>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.</catchwords>
                                       </p>
                                      </collation>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element collation { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <collation>

                                      <collation> (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <collation>The written leaves preceded by an original flyleaf,
                                      conjoint with the pastedown.</collation>
                                      Example
                                      <collation>
                                       <p>
                                        <formula>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)</formula>
                                        <catchwords>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.</catchwords>
                                       </p>
                                      </collation>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element collation { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-collection.html b/gl/dev/ref-collection.html index 217119964..41d446111 100644 --- a/gl/dev/ref-collection.html +++ b/gl/dev/ref-collection.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <collection>

                                      <collection> (collection) contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
                                      Contained by
                                      namesdates: objectIdentifier
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <country>USA</country>
                                       <region>California</region>
                                       <settlement>San Marino</settlement>
                                       <repository>Huntington Library</repository>
                                       <collection>Ellesmere</collection>
                                       <idno>El 26 C 9</idno>
                                       <msName>The Ellesmere Chaucer</msName>
                                      </msIdentifier>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <collection>

                                      <collection> (collection) contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
                                      Contained by
                                      namesdates: objectIdentifier
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <country>USA</country>
                                       <region>California</region>
                                       <settlement>San Marino</settlement>
                                       <repository>Huntington Library</repository>
                                       <collection>Ellesmere</collection>
                                       <idno>El 26 C 9</idno>
                                       <msName>The Ellesmere Chaucer</msName>
                                      </msIdentifier>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element collection
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-colophon.html b/gl/dev/ref-colophon.html index bc3f8bb42..ec0471937 100644 --- a/gl/dev/ref-colophon.html +++ b/gl/dev/ref-colophon.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <colophon>

                                      <colophon> (colophon) contains the colophon of an item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript or other object. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <colophon>Ricardus Franciscus Scripsit Anno Domini
                                      1447.</colophon>
                                      Example
                                      <colophon>Explicit expliceat/scriptor ludere eat.</colophon>
                                      Example
                                      <colophon>Explicit venenum viciorum domini illius, qui comparavit Anno
                                      domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo
                                      sancte Marthe virginis gloriose. Laus tibi criste quia finitur
                                      libellus iste.</colophon>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <colophon>

                                      <colophon> (colophon) contains the colophon of an item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript or other object. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <colophon>Ricardus Franciscus Scripsit Anno Domini
                                      1447.</colophon>
                                      Example
                                      <colophon>Explicit expliceat/scriptor ludere eat.</colophon>
                                      Example
                                      <colophon>Explicit venenum viciorum domini illius, qui comparavit Anno
                                      domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo
                                      sancte Marthe virginis gloriose. Laus tibi criste quia finitur
                                      libellus iste.</colophon>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element colophon
                                       {
                                          tei_att.global.attributes,
                                          tei_att.msExcerpt.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-condition.html b/gl/dev/ref-condition.html index 0566382b4..b1c6bc42d 100644 --- a/gl/dev/ref-condition.html +++ b/gl/dev/ref-condition.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <condition>

                                      <condition> (condition) contains a description of the physical condition of the manuscript or object. [10.7.1.5. Condition]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <condition>
                                       <p>There are lacunae in three places in this
                                         manuscript. After 14v two
                                         leaves has been cut out and narrow strips leaves remains in the spine. After
                                         68v one gathering is missing and after 101v at least one gathering of 8 leaves
                                         has been lost. </p>
                                       <p>Several leaves are damaged with tears or holes or have a
                                         irregular shape. Some of the damages do not allow the lines to be of full
                                         length and they are apparently older than the script. There are tears on fol.
                                         2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,
                                         37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,
                                         74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98
                                         the corner has been torn off. Several leaves are in a bad condition due to
                                         moist and wear, and have become dark, bleached or
                                         wrinkled. </p>
                                       <p>The script has been
                                         touched up in the 17th century with black ink. The touching up on the following
                                         fols. was done by
                                       <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,
                                         6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An
                                         AM-note says according to the lawman
                                       <name>Sigurður Björnsson</name> that the rest of the
                                         touching up was done by himself and another lawman
                                       <name>Sigurður Jónsson</name>.
                                       <name>Sigurður Björnsson</name> did the touching up
                                         on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.
                                       <name>Sigurður Jónsson</name> did the rest of the
                                         touching up in the section 36r-59r containing
                                       <title>Bretasögur</title>
                                       </p>
                                      </condition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element condition { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <condition>

                                      <condition> (condition) contains a description of the physical condition of the manuscript or object. [10.7.1.5. Condition]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <condition>
                                       <p>There are lacunae in three places in this
                                         manuscript. After 14v two
                                         leaves has been cut out and narrow strips leaves remains in the spine. After
                                         68v one gathering is missing and after 101v at least one gathering of 8 leaves
                                         has been lost. </p>
                                       <p>Several leaves are damaged with tears or holes or have a
                                         irregular shape. Some of the damages do not allow the lines to be of full
                                         length and they are apparently older than the script. There are tears on fol.
                                         2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,
                                         37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,
                                         74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98
                                         the corner has been torn off. Several leaves are in a bad condition due to
                                         moist and wear, and have become dark, bleached or
                                         wrinkled. </p>
                                       <p>The script has been
                                         touched up in the 17th century with black ink. The touching up on the following
                                         fols. was done by
                                       <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,
                                         6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An
                                         AM-note says according to the lawman
                                       <name>Sigurður Björnsson</name> that the rest of the
                                         touching up was done by himself and another lawman
                                       <name>Sigurður Jónsson</name>.
                                       <name>Sigurður Björnsson</name> did the touching up
                                         on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.
                                       <name>Sigurður Jónsson</name> did the rest of the
                                         touching up in the section 36r-59r containing
                                       <title>Bretasögur</title>
                                       </p>
                                      </condition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element condition { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-conversion.html b/gl/dev/ref-conversion.html index 1e2ba8e06..c9a80d991 100644 --- a/gl/dev/ref-conversion.html +++ b/gl/dev/ref-conversion.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <conversion>

                                      <conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.formula (@formula) att.locatable (@where)
                                      fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
                                      Status Required
                                      Datatype teidata.pointer
                                      toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
                                      Status Required
                                      Datatype teidata.pointer
                                      Contained by
                                      header: unitDef
                                      May containEmpty element
                                      Note

                                      The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.

                                      Example
                                      <conversion fromUnit="#shilling"
                                       toUnit="#penceformula="$fromUnit * 12from="1707"
                                       to="1971"/>
                                      Example
                                      <conversion fromUnit="#pound"
                                       toUnit="#shillingformula="$fromUnit * 20from="1701"
                                       to="1971"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <conversion>

                                      <conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.formula (@formula) att.locatable (@where)
                                      fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
                                      Status Required
                                      Datatype teidata.pointer
                                      toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
                                      Status Required
                                      Datatype teidata.pointer
                                      Contained by
                                      header: unitDef
                                      May containEmpty element
                                      Note

                                      The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.

                                      Example
                                      <conversion fromUnit="#shilling"
                                       toUnit="#penceformula="$fromUnit * 12from="1707"
                                       to="1971"/>
                                      Example
                                      <conversion fromUnit="#pound"
                                       toUnit="#shillingformula="$fromUnit * 20from="1701"
                                       to="1971"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element conversion
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          attribute fromUnit { teidata.pointer },
                                          attribute toUnit { teidata.pointer },
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-corr.html b/gl/dev/ref-corr.html index aeab71ac5..80d57953b 100644 --- a/gl/dev/ref-corr.html +++ b/gl/dev/ref-corr.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <corr>

                                      <corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      If all that is desired is to call attention to the fact that the copy text has been corrected, corr may be used alone:

                                      I don't know,
                                      Juan. It's so far in the past now — how <corr>can we</corr> prove
                                      or disprove anyone's theories?
                                      Example

                                      It is also possible, using the choice and sic elements, to provide an uncorrected reading:

                                      I don't know, Juan. It's so far in the past now —
                                      how <choice>
                                       <sic>we can</sic>
                                       <corr>can we</corr>
                                      </choice> prove or
                                      disprove anyone's theories?
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <corr>

                                      <corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      If all that is desired is to call attention to the fact that the copy text has been corrected, corr may be used alone:

                                      I don't know,
                                      Juan. It's so far in the past now — how <corr>can we</corr> prove
                                      or disprove anyone's theories?
                                      Example

                                      It is also possible, using the choice and sic elements, to provide an uncorrected reading:

                                      I don't know, Juan. It's so far in the past now —
                                      how <choice>
                                       <sic>we can</sic>
                                       <corr>can we</corr>
                                      </choice> prove or
                                      disprove anyone's theories?
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element corr
                                       {
                                          tei_att.global.attributes,
                                          tei_att.editLike.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-correction.html b/gl/dev/ref-correction.html index eea750d58..ced6c83bc 100644 --- a/gl/dev/ref-correction.html +++ b/gl/dev/ref-correction.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <correction>

                                      <correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      statusindicates the degree of correction applied to the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      high
                                      the text has been thoroughly checked and proofread.
                                      medium
                                      the text has been checked at least once.
                                      low
                                      the text has not been checked.
                                      unknown
                                      the correction status of the text is unknown.
                                      methodindicates the method adopted to indicate corrections within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      silent
                                      corrections have been made silently [Default]
                                      markup
                                      corrections have been represented using markup
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes.

                                      Example
                                      <correction>
                                       <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user
                                         defined dictionary of 500 extra words taken from Chambers Twentieth Century
                                         Dictionary.</p>
                                      </correction>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <correction>

                                      <correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      statusindicates the degree of correction applied to the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      high
                                      the text has been thoroughly checked and proofread.
                                      medium
                                      the text has been checked at least once.
                                      low
                                      the text has not been checked.
                                      unknown
                                      the correction status of the text is unknown.
                                      methodindicates the method adopted to indicate corrections within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      silent
                                      corrections have been made silently [Default]
                                      markup
                                      corrections have been represented using markup
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes.

                                      Example
                                      <correction>
                                       <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user
                                         defined dictionary of 500 extra words taken from Chambers Twentieth Century
                                         Dictionary.</p>
                                      </correction>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element correction
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          attribute status { "high" | "medium" | "low" | "unknown" }?,
                                          attribute method { "silent" | "markup" }?,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-correspAction.html b/gl/dev/ref-correspAction.html index 772f2ebb1..03c78e1cc 100644 --- a/gl/dev/ref-correspAction.html +++ b/gl/dev/ref-correspAction.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <correspAction>

                                      <correspAction> (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. [2.4.6. Correspondence Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
                                      typedescribes the nature of the action.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      sent
                                      information concerning the sending or dispatch of a message.
                                      received
                                      information concerning the receipt of a message.
                                      transmitted
                                      information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
                                      redirected
                                      information concerning the redirection of an unread message.
                                      forwarded
                                      information concerning the forwarding of a message.
                                      Member of
                                      Contained by
                                      header: correspDesc
                                      May contain
                                      Example
                                      <correspAction type="sent">
                                       <persName>Adelbert von Chamisso</persName>
                                       <settlement>Vertus</settlement>
                                       <date when="1807-01-29"/>
                                      </correspAction>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.correspActionPart"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <correspAction>

                                      <correspAction> (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. [2.4.6. Correspondence Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
                                      typedescribes the nature of the action.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      sent
                                      information concerning the sending or dispatch of a message.
                                      received
                                      information concerning the receipt of a message.
                                      transmitted
                                      information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
                                      redirected
                                      information concerning the redirection of an unread message.
                                      forwarded
                                      information concerning the forwarding of a message.
                                      Member of
                                      Contained by
                                      header: correspDesc
                                      May contain
                                      Example
                                      <correspAction type="sent">
                                       <persName>Adelbert von Chamisso</persName>
                                       <settlement>Vertus</settlement>
                                       <date when="1807-01-29"/>
                                      </correspAction>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.correspActionPart"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element correspAction
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                           | teidata.enumerated
                                          }?,
                                          ( tei_model.correspActionPart+ | tei_model.pLike+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-correspContext.html b/gl/dev/ref-correspContext.html index c6ae19ba9..213612edb 100644 --- a/gl/dev/ref-correspContext.html +++ b/gl/dev/ref-correspContext.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <correspContext>

                                      <correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: correspDesc
                                      May contain
                                      linking: ab
                                      Example
                                      <correspContext>
                                       <ptr type="nextsubtype="toAuthor"
                                        target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>

                                       <ptr type="prevsubtype="fromAuthor"
                                        target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/>

                                      </correspContext>
                                      Example
                                      <correspContext>
                                       <ref type="prev"
                                        target="http://weber-gesamtausgabe.de/A040962">
                                      Previous letter of
                                       <persName>Carl Maria von Weber</persName> to
                                       <persName>Caroline Brandt</persName>:
                                       <date when="1816-12-30">December 30, 1816</date>
                                       </ref>
                                       <ref type="next"
                                        target="http://weber-gesamtausgabe.de/A041003">
                                      Next letter of
                                       <persName>Carl Maria von Weber</persName> to
                                       <persName>Caroline Brandt</persName>:
                                       <date when="1817-01-05">January 5, 1817</date>
                                       </ref>
                                      </correspContext>
                                      Content model
                                      <content>
                                       <classRef key="model.correspContextPart"
                                        minOccurs="1maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <correspContext>

                                      <correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: correspDesc
                                      May contain
                                      linking: ab
                                      Example
                                      <correspContext>
                                       <ptr type="nextsubtype="toAuthor"
                                        target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>

                                       <ptr type="prevsubtype="fromAuthor"
                                        target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/>

                                      </correspContext>
                                      Example
                                      <correspContext>
                                       <ref type="prev"
                                        target="http://weber-gesamtausgabe.de/A040962">
                                      Previous letter of
                                       <persName>Carl Maria von Weber</persName> to
                                       <persName>Caroline Brandt</persName>:
                                       <date when="1816-12-30">December 30, 1816</date>
                                       </ref>
                                       <ref type="next"
                                        target="http://weber-gesamtausgabe.de/A041003">
                                      Next letter of
                                       <persName>Carl Maria von Weber</persName> to
                                       <persName>Caroline Brandt</persName>:
                                       <date when="1817-01-05">January 5, 1817</date>
                                       </ref>
                                      </correspContext>
                                      Content model
                                      <content>
                                       <classRef key="model.correspContextPart"
                                        minOccurs="1maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element correspContext
                                       {
                                          tei_att.global.attributes,
                                          tei_model.correspContextPart+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-correspDesc.html b/gl/dev/ref-correspDesc.html index 4cbd92026..f62fa5b2a 100644 --- a/gl/dev/ref-correspDesc.html +++ b/gl/dev/ref-correspDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <correspDesc>

                                      <correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
                                      Moduleheader
                                      Attributesatt.declarable (@default) att.canonical (@key, @ref) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Example
                                      <correspDesc>
                                       <correspAction type="sent">
                                        <persName>Carl Maria von Weber</persName>
                                        <settlement>Dresden</settlement>
                                        <date when="1817-06-23">23 June 1817</date>
                                       </correspAction>
                                       <correspAction type="received">
                                        <persName>Caroline Brandt</persName>
                                        <settlement>Prag</settlement>
                                       </correspAction>
                                       <correspContext>
                                        <ref type="prev"
                                         target="http://www.weber-gesamtausgabe.de/A041209">
                                      Previous letter of
                                        <persName>Carl Maria von Weber</persName>
                                           to <persName>Caroline Brandt</persName>:
                                        <date from="1817-06-19to="1817-06-20">June 19/20, 1817</date>
                                        </ref>
                                        <ref type="next"
                                         target="http://www.weber-gesamtausgabe.de/A041217">
                                      Next letter of
                                        <persName>Carl Maria von Weber</persName> to
                                        <persName>Caroline Brandt</persName>:
                                        <date when="1817-06-27">June 27, 1817</date>
                                        </ref>
                                       </correspContext>
                                      </correspDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.correspDescPart"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <correspDesc>

                                      <correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
                                      Moduleheader
                                      Attributesatt.declarable (@default) att.canonical (@key, @ref) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Example
                                      <correspDesc>
                                       <correspAction type="sent">
                                        <persName>Carl Maria von Weber</persName>
                                        <settlement>Dresden</settlement>
                                        <date when="1817-06-23">23 June 1817</date>
                                       </correspAction>
                                       <correspAction type="received">
                                        <persName>Caroline Brandt</persName>
                                        <settlement>Prag</settlement>
                                       </correspAction>
                                       <correspContext>
                                        <ref type="prev"
                                         target="http://www.weber-gesamtausgabe.de/A041209">
                                      Previous letter of
                                        <persName>Carl Maria von Weber</persName>
                                           to <persName>Caroline Brandt</persName>:
                                        <date from="1817-06-19to="1817-06-20">June 19/20, 1817</date>
                                        </ref>
                                        <ref type="next"
                                         target="http://www.weber-gesamtausgabe.de/A041217">
                                      Next letter of
                                        <persName>Carl Maria von Weber</persName> to
                                        <persName>Caroline Brandt</persName>:
                                        <date when="1817-06-27">June 27, 1817</date>
                                        </ref>
                                       </correspContext>
                                      </correspDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.correspDescPart"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element correspDesc
                                       {
                                          tei_att.declarable.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          ( tei_model.correspDescPart+ | tei_model.pLike+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-country.html b/gl/dev/ref-country.html index 4f3add35a..a42455956 100644 --- a/gl/dev/ref-country.html +++ b/gl/dev/ref-country.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <country>

                                      <country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The recommended source for codes to represent coded country names is ISO 3166.

                                      Example
                                      <country key="DK">Denmark</country>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <country>

                                      <country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The recommended source for codes to represent coded country names is ISO 3166.

                                      Example
                                      <country key="DK">Denmark</country>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element country
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-creation.html b/gl/dev/ref-creation.html index c32738f81..9d0167dc8 100644 --- a/gl/dev/ref-creation.html +++ b/gl/dev/ref-creation.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <creation>

                                      <creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Note

                                      The creation element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.

                                      It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the listChange element. It should not be confused with the publicationStmt element, which records date and place of publication.

                                      Example
                                      <creation>
                                       <date>Before 1987</date>
                                      </creation>
                                      Example
                                      <creation>
                                       <date when="1988-07-10">10 July 1988</date>
                                      </creation>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.limitedPhrase"/>
                                        <elementRef key="listChange"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <creation>

                                      <creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Note

                                      The creation element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.

                                      It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the listChange element. It should not be confused with the publicationStmt element, which records date and place of publication.

                                      Example
                                      <creation>
                                       <date>Before 1987</date>
                                      </creation>
                                      Example
                                      <creation>
                                       <date when="1988-07-10">10 July 1988</date>
                                      </creation>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.limitedPhrase"/>
                                        <elementRef key="listChange"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element creation
                                       {
                                          tei_att.global.attributes,
                                          tei_att.datable.attributes,
                                          ( text | tei_model.limitedPhrase | tei_listChange )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-custEvent.html b/gl/dev/ref-custEvent.html index fcd7c0330..3ffec6212 100644 --- a/gl/dev/ref-custEvent.html +++ b/gl/dev/ref-custEvent.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <custEvent>

                                      <custEvent> (custodial event) describes a single event during the custodial history of a manuscript or other object. [10.9.1.2. Availability and Custodial History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: custodialHist
                                      May contain
                                      Example
                                      <custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date>
                                      </custEvent>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <custEvent>

                                      <custEvent> (custodial event) describes a single event during the custodial history of a manuscript or other object. [10.9.1.2. Availability and Custodial History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: custodialHist
                                      May contain
                                      Example
                                      <custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date>
                                      </custEvent>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element custEvent
                                       {
                                          tei_att.global.attributes,
                                          tei_att.datable.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-custodialHist.html b/gl/dev/ref-custodialHist.html index 5b1ca6b8d..e9e470938 100644 --- a/gl/dev/ref-custodialHist.html +++ b/gl/dev/ref-custodialHist.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <custodialHist>

                                      <custodialHist> (custodial history) contains a description of a manuscript or other object's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: adminInfo
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: custEvent
                                      Example
                                      <custodialHist>
                                       <custEvent type="conservation"
                                        notBefore="1961-03notAfter="1963-02">
                                      Conserved between March 1961 and February 1963 at
                                         Birgitte Dalls Konserveringsværksted.</custEvent>
                                       <custEvent type="photography"
                                        notBefore="1988-05-01notAfter="1988-05-30">
                                      Photographed in
                                         May 1988 by AMI/FA.</custEvent>
                                       <custEvent type="transfer-dispatch"
                                        notBefore="1989-11-13notAfter="1989-11-13">
                                      Dispatched to Iceland
                                         13 November 1989.</custEvent>
                                      </custodialHist>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="custEventminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <custodialHist>

                                      <custodialHist> (custodial history) contains a description of a manuscript or other object's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: adminInfo
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: custEvent
                                      Example
                                      <custodialHist>
                                       <custEvent type="conservation"
                                        notBefore="1961-03notAfter="1963-02">
                                      Conserved between March 1961 and February 1963 at
                                         Birgitte Dalls Konserveringsværksted.</custEvent>
                                       <custEvent type="photography"
                                        notBefore="1988-05-01notAfter="1988-05-30">
                                      Photographed in
                                         May 1988 by AMI/FA.</custEvent>
                                       <custEvent type="transfer-dispatch"
                                        notBefore="1989-11-13notAfter="1989-11-13">
                                      Dispatched to Iceland
                                         13 November 1989.</custEvent>
                                      </custodialHist>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="custEventminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element custodialHist
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | tei_custEvent+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-damage.html b/gl/dev/ref-damage.html index 0fdeb81f4..790ba60d6 100644 --- a/gl/dev/ref-damage.html +++ b/gl/dev/ref-damage.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <damage>

                                      <damage> (damage) contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.damaged (@agent, @degree, @group) (att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.written (@hand))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Since damage to text witnesses frequently makes them harder to read, the damage element will often contain an unclear element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related damage elements; alternatively the join element may be used to indicate which damage and unclear elements are part of the same physical phenomenon.

                                      The damage, gap, del, unclear and supplied elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      Example
                                      <l>The Moving Finger wri<damage agent="watergroup="1">es; and</damage> having writ,</l>
                                      <l>Moves <damage agent="watergroup="1">
                                        <supplied>on: nor all your</supplied>
                                       </damage> Piety nor Wit</l>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <damage>

                                      <damage> (damage) contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.damaged (@agent, @degree, @group) (att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.written (@hand))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Since damage to text witnesses frequently makes them harder to read, the damage element will often contain an unclear element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related damage elements; alternatively the join element may be used to indicate which damage and unclear elements are part of the same physical phenomenon.

                                      The damage, gap, del, unclear and supplied elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      Example
                                      <l>The Moving Finger wri<damage agent="watergroup="1">es; and</damage> having writ,</l>
                                      <l>Moves <damage agent="watergroup="1">
                                        <supplied>on: nor all your</supplied>
                                       </damage> Piety nor Wit</l>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element damage
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.damaged.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-date.html b/gl/dev/ref-date.html index e6082baa6..408115e62 100644 --- a/gl/dev/ref-date.html +++ b/gl/dev/ref-date.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <date>

                                      <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <date when="1980-02">early February 1980</date>
                                      Example
                                      Given on the <date when="1977-06-12">Twelfth Day
                                      of June 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.</date>
                                      Example
                                      <date when="1990-09">September 1990</date>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <date>

                                      <date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <date when="1980-02">early February 1980</date>
                                      Example
                                      Given on the <date when="1977-06-12">Twelfth Day
                                      of June 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.</date>
                                      Example
                                      <date when="1990-09">September 1990</date>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element date
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          tei_att.dimensions.attributes,
                                          tei_att.typed.attributes,
                                          ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-dateline.html b/gl/dev/ref-dateline.html index 35c6bfddc..0dd4a8605 100644 --- a/gl/dev/ref-dateline.html +++ b/gl/dev/ref-dateline.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <dateline>

                                      <dateline> (dateline) contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      textstructure: back body div front group
                                      May contain
                                      Example
                                      <dateline>Walden, this 29. of August 1592</dateline>
                                      Example
                                      <div type="chapter">
                                       <p>
                                      <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>
                                       <closer>
                                        <dateline>
                                         <name type="place">Trieste-Zürich-Paris,</name>
                                         <date>1914–1921</date>
                                        </dateline>
                                       </closer>
                                      </div>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                        <elementRef key="docDate"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <dateline>

                                      <dateline> (dateline) contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      textstructure: back body div front group
                                      May contain
                                      Example
                                      <dateline>Walden, this 29. of August 1592</dateline>
                                      Example
                                      <div type="chapter">
                                       <p>
                                      <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>
                                       <closer>
                                        <dateline>
                                         <name type="place">Trieste-Zürich-Paris,</name>
                                         <date>1914–1921</date>
                                        </dateline>
                                       </closer>
                                      </div>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                        <elementRef key="docDate"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element dateline
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                           | tei_model.global
                                           | tei_docDate
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-death.html b/gl/dev/ref-death.html index 7fcbd5f98..a07c31133 100644 --- a/gl/dev/ref-death.html +++ b/gl/dev/ref-death.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <death>

                                      <death> (death) contains information about a person's death, such as its date and place. [15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (type, @subtype)
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      proclaimed
                                      assumed
                                      verified
                                      clinical
                                      brain
                                      natural
                                      unnatural
                                      fragmentation
                                      dissolution
                                      Note

                                      This attribute is not intended to express the cause of death.

                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <death when="1902-10-01"/>
                                      Example
                                      <death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <death>

                                      <death> (death) contains information about a person's death, such as its date and place. [15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (type, @subtype)
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      proclaimed
                                      assumed
                                      verified
                                      clinical
                                      brain
                                      natural
                                      unnatural
                                      fragmentation
                                      dissolution
                                      Note

                                      This attribute is not intended to express the cause of death.

                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <death when="1902-10-01"/>
                                      Example
                                      <death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element death
                                       {
                                          tei_att.datable.attributes,
                                      @@ -32,4 +32,4 @@
                                          tei_att.typed.attribute.subtype,
                                          attribute type { teidata.enumerated }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-decoDesc.html b/gl/dev/ref-decoDesc.html index 83fbfec1d..d8e484426 100644 --- a/gl/dev/ref-decoDesc.html +++ b/gl/dev/ref-decoDesc.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <decoDesc>

                                      <decoDesc> (decoration description) contains a description of the decoration of a manuscript or other object, either as in paragraphs, or as one or more decoNote elements. [10.7.3. Bindings, Seals, and Additional Material]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: decoNote summary
                                      Example
                                      <decoDesc>
                                       <p>The start of each book of the Bible with a 10-line historiated
                                         illuminated initial; prefaces decorated with 6-line blue initials with red
                                         penwork flourishing; chapters marked by 3-line plain red initials; verses
                                         with 1-line initials, alternately blue or red.</p>
                                      </decoDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="decoNoteminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <decoDesc>

                                      <decoDesc> (decoration description) contains a description of the decoration of a manuscript or other object, either as in paragraphs, or as one or more decoNote elements. [10.7.3. Bindings, Seals, and Additional Material]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: decoNote summary
                                      Example
                                      <decoDesc>
                                       <p>The start of each book of the Bible with a 10-line historiated
                                         illuminated initial; prefaces decorated with 6-line blue initials with red
                                         penwork flourishing; chapters marked by 3-line plain red initials; verses
                                         with 1-line initials, alternately blue or red.</p>
                                      </decoDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="decoNoteminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element decoDesc
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | ( tei_summary?, tei_decoNote+ ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-decoNote.html b/gl/dev/ref-decoNote.html index 64eba787b..435843ebb 100644 --- a/gl/dev/ref-decoNote.html +++ b/gl/dev/ref-decoNote.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <decoNote>

                                      <decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <decoDesc>
                                       <decoNote type="initial">
                                        <p>The start of each book of the Bible with
                                           a 10-line historiated illuminated initial;
                                           prefaces decorated with 6-line blue initials
                                           with red penwork flourishing; chapters marked by
                                           3-line plain red initials; verses with 1-line initials,
                                           alternately blue or red.</p>
                                       </decoNote>
                                      </decoDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <decoNote>

                                      <decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <decoDesc>
                                       <decoNote type="initial">
                                        <p>The start of each book of the Bible with
                                           a 10-line historiated illuminated initial;
                                           prefaces decorated with 6-line blue initials
                                           with red penwork flourishing; chapters marked by
                                           3-line plain red initials; verses with 1-line initials,
                                           alternately blue or red.</p>
                                       </decoNote>
                                      </decoDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element decoNote
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-del.html b/gl/dev/ref-del.html index af0e66fb9..cafe27233 100644 --- a/gl/dev/ref-del.html +++ b/gl/dev/ref-del.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <del>

                                      <del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      This element should be used for deletion of shorter sequences of text, typically single words or phrases. The delSpan element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

                                      The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a supplied tag). Illegible or lost text within a deletion may be marked using the gap tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the gap element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the unclear element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.

                                      Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the certainty element (see 21. Certainty, Precision, and Responsibility).

                                      There is a clear distinction in the TEI between del and surplus on the one hand and gap or unclear on the other. del indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. surplus indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. gap or unclear, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

                                      Example
                                      <l>
                                       <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del>
                                      weht der Wind
                                      </l>
                                      Example
                                      <del rend="overstrike">
                                       <gap reason="illegiblequantity="5"
                                        unit="character"/>

                                      </del>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <del>

                                      <del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      This element should be used for deletion of shorter sequences of text, typically single words or phrases. The delSpan element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

                                      The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a supplied tag). Illegible or lost text within a deletion may be marked using the gap tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the gap element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the unclear element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.

                                      Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the certainty element (see 21. Certainty, Precision, and Responsibility).

                                      There is a clear distinction in the TEI between del and surplus on the one hand and gap or unclear on the other. del indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. surplus indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. gap or unclear, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

                                      Example
                                      <l>
                                       <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del>
                                      weht der Wind
                                      </l>
                                      Example
                                      <del rend="overstrike">
                                       <gap reason="illegiblequantity="5"
                                        unit="character"/>

                                      </del>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element del
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-delSpan.html b/gl/dev/ref-delSpan.html index 3b2996444..21d1ff341 100644 --- a/gl/dev/ref-delSpan.html +++ b/gl/dev/ref-delSpan.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <delSpan>

                                      <delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [11.3.1.4. Additions and Deletions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      Both the beginning and ending of the deleted sequence must be marked: the beginning by the delSpan element, the ending by the target of the spanTo attribute.

                                      The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the delSpan tag should not be used. Rather, the gap tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the unclear element should be used to signal the areas of text which cannot be read with confidence. See further sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the delSpan tag with the gap, damage, unclear and supplied elements, 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

                                      The delSpan tag should not be used for deletions made by editors or encoders. In these cases, either the corr tag or the gap tag should be used.

                                      Example
                                      <p>Paragraph partially deleted. This is the undeleted
                                      portion <delSpan spanTo="#a23"/>and this the deleted
                                      portion of the paragraph.</p>
                                      <p>Paragraph deleted together with adjacent material.</p>
                                      <p>Second fully deleted paragraph.</p>
                                      <p>Paragraph partially deleted; in the middle of this
                                      paragraph the deletion ends and the anchor point marks
                                      the resumption <anchor xml:id="a23"/> of the text. ...</p>
                                      Schematron

                                      <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert>
                                      Schematron

                                      <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <delSpan>

                                      <delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [11.3.1.4. Additions and Deletions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      Both the beginning and ending of the deleted sequence must be marked: the beginning by the delSpan element, the ending by the target of the spanTo attribute.

                                      The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the delSpan tag should not be used. Rather, the gap tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the unclear element should be used to signal the areas of text which cannot be read with confidence. See further sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and, for the close association of the delSpan tag with the gap, damage, unclear and supplied elements, 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination.

                                      The delSpan tag should not be used for deletions made by editors or encoders. In these cases, either the corr tag or the gap tag should be used.

                                      Example
                                      <p>Paragraph partially deleted. This is the undeleted
                                      portion <delSpan spanTo="#a23"/>and this the deleted
                                      portion of the paragraph.</p>
                                      <p>Paragraph deleted together with adjacent material.</p>
                                      <p>Second fully deleted paragraph.</p>
                                      <p>Paragraph partially deleted; in the middle of this
                                      paragraph the deletion ends and the anchor point marks
                                      the resumption <anchor xml:id="a23"/> of the text. ...</p>
                                      Schematron

                                      <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert>
                                      Schematron

                                      <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element delSpan
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.spanning.attributes,
                                          tei_att.dimensions.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-depth.html b/gl/dev/ref-depth.html index 4ec03817a..442b57781 100644 --- a/gl/dev/ref-depth.html +++ b/gl/dev/ref-depth.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <depth>

                                      <depth> (depth) contains a measurement from the front to the back of an object, perpendicular to the measurement given by the width element. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Example
                                      <depth unit="inquantity="4"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <depth>

                                      <depth> (depth) contains a measurement from the front to the back of an object, perpendicular to the measurement given by the width element. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Example
                                      <depth unit="inquantity="4"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element depth
                                       {
                                          tei_att.global.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-desc.html b/gl/dev/ref-desc.html index 48a33edf1..2097d2893 100644 --- a/gl/dev/ref-desc.html +++ b/gl/dev/ref-desc.html @@ -22,11 +22,11 @@ }); });

                                      <desc>

                                      <desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typecharacterizes the element in some sense, using any convenient classification scheme or typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      deprecationInfo
                                      (deprecation - information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
                                      <dataSpec module="tei"
                                       ident="teidata.pointvalidUntil="2050-02-25">

                                       <desc type="deprecationInfo"
                                        versionDate="2018-09-14xml:lang="en">
                                      Several standards bodies, including NIST in the USA,
                                         strongly recommend against ending the representation of a number
                                         with a decimal point. So instead of <q>3.</q> use either <q>3</q>
                                         or <q>3.0</q>.</desc>
                                      <!-- ... -->
                                      </dataSpec>
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

                                      Example

                                      Example of a desc element inside a documentation element.

                                      <dataSpec module="tei"
                                       ident="teidata.point">

                                       <desc versionDate="2010-10-17"
                                        xml:lang="en">
                                      defines the data type used to express a point in cartesian space.</desc>
                                       <content>
                                        <dataRef name="token"
                                         restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>

                                       </content>
                                      <!-- ... -->
                                      </dataSpec>
                                      Example

                                      Example of a desc element in a non-documentation element.

                                      <place xml:id="KERG2">
                                       <placeName>Kerguelen Islands</placeName>
                                      <!-- ... -->
                                       <terrain>
                                        <desc>antarctic tundra</desc>
                                       </terrain>
                                      <!-- ... -->
                                      </place>
                                      SchematronA desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element.

                                      <sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
                                      <sch:assert test="../@validUntil">Information about a
                                      deprecation should only be present in a specification element
                                      that is being deprecated: that is, only an element that has a
                                      @validUntil attribute should have a child <desc
                                      type="deprecationInfo">.</sch:assert>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                      +          information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
                                      <dataSpec module="tei"
                                       ident="teidata.pointvalidUntil="2050-02-25">

                                       <desc type="deprecationInfo"
                                        versionDate="2018-09-14xml:lang="en">
                                      Several standards bodies, including NIST in the USA,
                                         strongly recommend against ending the representation of a number
                                         with a decimal point. So instead of <q>3.</q> use either <q>3</q>
                                         or <q>3.0</q>.</desc>
                                      <!-- ... -->
                                      </dataSpec>
                                      Member ofContained byMay containNote

                                      When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

                                      Example

                                      Example of a desc element inside a documentation element.

                                      <dataSpec module="tei"
                                       ident="teidata.point">

                                       <desc versionDate="2010-10-17"
                                        xml:lang="en">
                                      defines the data type used to express a point in cartesian space.</desc>
                                       <content>
                                        <dataRef name="token"
                                         restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>

                                       </content>
                                      <!-- ... -->
                                      </dataSpec>
                                      Example

                                      Example of a desc element in a non-documentation element.

                                      <place xml:id="KERG2">
                                       <placeName>Kerguelen Islands</placeName>
                                      <!-- ... -->
                                       <terrain>
                                        <desc>antarctic tundra</desc>
                                       </terrain>
                                      <!-- ... -->
                                      </place>
                                      SchematronA desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element.

                                      <sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
                                      <sch:assert test="../@validUntil">Information about a
                                      deprecation should only be present in a specification element
                                      that is being deprecated: that is, only an element that has a
                                      @validUntil attribute should have a child <desc
                                      type="deprecationInfo">.</sch:assert>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                       element desc
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attribute.subtype,
                                          attribute type { "deprecationInfo" | teidata.enumerated }?,
                                          tei_macro.limitedContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-dim.html b/gl/dev/ref-dim.html index 25f41cd09..57bf70aef 100644 --- a/gl/dev/ref-dim.html +++ b/gl/dev/ref-dim.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <dim>

                                      <dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      The specific elements width, height, and depth should be used in preference to this generic element wherever appropriate.

                                      Example
                                      <dim type="circumferenceextent="4.67 in"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <dim>

                                      <dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      The specific elements width, height, and depth should be used in preference to this generic element wherever appropriate.

                                      Example
                                      <dim type="circumferenceextent="4.67 in"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element dim
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-dimensions.html b/gl/dev/ref-dimensions.html index b491a8018..76ffb3691 100644 --- a/gl/dev/ref-dimensions.html +++ b/gl/dev/ref-dimensions.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <dimensions>

                                      <dimensions> (dimensions) contains a dimensional specification. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (type, @subtype)
                                      typeindicates which aspect of the object is being measured.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      leaves
                                      dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part)
                                      ruled
                                      dimensions relate to the area of a leaf which has been ruled in preparation for writing.
                                      pricked
                                      dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (used where this differs significantly from the ruled area, or where the ruling is not measurable).
                                      written
                                      dimensions relate to the area of a leaf which has been written, with the height measured from the top of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing.
                                      miniatures
                                      dimensions relate to the miniatures within the manuscript
                                      binding
                                      dimensions relate to the binding in which the codex or manuscript is contained
                                      box
                                      dimensions relate to the box or other container in which the manuscript is stored.
                                      Member of
                                      Contained by
                                      May contain
                                      msdescription: depth dim height width
                                      Note

                                      Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

                                      Example
                                      <dimensions type="leaves">
                                       <height scope="range">157-160</height>
                                       <width>105</width>
                                      </dimensions>
                                      <dimensions type="ruled">
                                       <height scope="most">90</height>
                                       <width scope="most">48</width>
                                      </dimensions>
                                      <dimensions unit="in">
                                       <height>12</height>
                                       <width>10</width>
                                      </dimensions>
                                      Example

                                      This element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:

                                      <dimensions type="panels">
                                       <height scope="all">7004</height>
                                       <width scope="all">1803</width>
                                       <dim type="reliefunit="mm">345</dim>
                                      </dimensions>

                                      This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.

                                      Example

                                      When simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:

                                      <dimensions type="leaves">
                                       <height scope="range">157-160</height>
                                       <width quantity="105"/>
                                      </dimensions>
                                      <dimensions type="ruled">
                                       <height unit="cmscope="most"
                                        quantity="90"/>

                                       <width unit="cmscope="mostquantity="48"/>
                                      </dimensions>
                                      <dimensions unit="in">
                                       <height quantity="12"/>
                                       <width quantity="10"/>
                                      </dimensions>
                                      Schematron

                                      <s:report test="count(tei:width)> 1">The element <s:name/> may appear once only
                                      </s:report>
                                      <s:report test="count(tei:height)> 1">The element <s:name/> may appear once only
                                      </s:report>
                                      <s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only
                                      </s:report>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="dim"/>
                                        <classRef key="model.dimLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <dimensions>

                                      <dimensions> (dimensions) contains a dimensional specification. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (type, @subtype)
                                      typeindicates which aspect of the object is being measured.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      leaves
                                      dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part)
                                      ruled
                                      dimensions relate to the area of a leaf which has been ruled in preparation for writing.
                                      pricked
                                      dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (used where this differs significantly from the ruled area, or where the ruling is not measurable).
                                      written
                                      dimensions relate to the area of a leaf which has been written, with the height measured from the top of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing.
                                      miniatures
                                      dimensions relate to the miniatures within the manuscript
                                      binding
                                      dimensions relate to the binding in which the codex or manuscript is contained
                                      box
                                      dimensions relate to the box or other container in which the manuscript is stored.
                                      Member of
                                      Contained by
                                      May contain
                                      msdescription: depth dim height width
                                      Note

                                      Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

                                      Example
                                      <dimensions type="leaves">
                                       <height scope="range">157-160</height>
                                       <width>105</width>
                                      </dimensions>
                                      <dimensions type="ruled">
                                       <height scope="most">90</height>
                                       <width scope="most">48</width>
                                      </dimensions>
                                      <dimensions unit="in">
                                       <height>12</height>
                                       <width>10</width>
                                      </dimensions>
                                      Example

                                      This element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:

                                      <dimensions type="panels">
                                       <height scope="all">7004</height>
                                       <width scope="all">1803</width>
                                       <dim type="reliefunit="mm">345</dim>
                                      </dimensions>

                                      This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.

                                      Example

                                      When simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:

                                      <dimensions type="leaves">
                                       <height scope="range">157-160</height>
                                       <width quantity="105"/>
                                      </dimensions>
                                      <dimensions type="ruled">
                                       <height unit="cmscope="most"
                                        quantity="90"/>

                                       <width unit="cmscope="mostquantity="48"/>
                                      </dimensions>
                                      <dimensions unit="in">
                                       <height quantity="12"/>
                                       <width quantity="10"/>
                                      </dimensions>
                                      Schematron

                                      <s:report test="count(tei:width)> 1">The element <s:name/> may appear once only
                                      </s:report>
                                      <s:report test="count(tei:height)> 1">The element <s:name/> may appear once only
                                      </s:report>
                                      <s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only
                                      </s:report>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="dim"/>
                                        <classRef key="model.dimLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element dimensions
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attribute.subtype,
                                          attribute type { teidata.enumerated }?,
                                          ( tei_dim | tei_model.dimLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-distinct.html b/gl/dev/ref-distinct.html index 8724bfe84..a489ff2f1 100644 --- a/gl/dev/ref-distinct.html +++ b/gl/dev/ref-distinct.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <distinct>

                                      <distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typespecifies the sublanguage or register to which the word or phrase is being assigned
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      timespecifies how the phrase is distinct diachronically
                                      Status Optional
                                      Datatype teidata.text
                                      spacespecifies how the phrase is distinct diatopically
                                      Status Optional
                                      Datatype teidata.text
                                      socialspecifies how the phrase is distinct diastratically
                                      Status Optional
                                      Datatype teidata.text
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      Next morning a boy
                                      in that dormitory confided to his bosom friend, a <distinct type="ps_slang">fag</distinct> of
                                      Macrea's, that there was trouble in their midst which King <distinct type="archaic">would fain</distinct>
                                      keep secret.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <distinct>

                                      <distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typespecifies the sublanguage or register to which the word or phrase is being assigned
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      timespecifies how the phrase is distinct diachronically
                                      Status Optional
                                      Datatype teidata.text
                                      spacespecifies how the phrase is distinct diatopically
                                      Status Optional
                                      Datatype teidata.text
                                      socialspecifies how the phrase is distinct diastratically
                                      Status Optional
                                      Datatype teidata.text
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      Next morning a boy
                                      in that dormitory confided to his bosom friend, a <distinct type="ps_slang">fag</distinct> of
                                      Macrea's, that there was trouble in their midst which King <distinct type="archaic">would fain</distinct>
                                      keep secret.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element distinct
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          attribute space { teidata.text }?,
                                          attribute social { teidata.text }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-distributor.html b/gl/dev/ref-distributor.html index e2a2941c6..9e5335a7b 100644 --- a/gl/dev/ref-distributor.html +++ b/gl/dev/ref-distributor.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <distributor>

                                      <distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <distributor>Oxford Text Archive</distributor>
                                      <distributor>Redwood and Burn Ltd</distributor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <distributor>

                                      <distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <distributor>Oxford Text Archive</distributor>
                                      <distributor>Redwood and Burn Ltd</distributor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element distributor
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-district.html b/gl/dev/ref-district.html index 99c6c6b57..2efec668c 100644 --- a/gl/dev/ref-district.html +++ b/gl/dev/ref-district.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <district>

                                      <district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <district type="ward">Jericho</district>
                                       <settlement>Oxford</settlement>
                                      </placeName>
                                      Example
                                      <placeName>
                                       <district type="area">South Side</district>
                                       <settlement>Chicago</settlement>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <district>

                                      <district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <district type="ward">Jericho</district>
                                       <settlement>Oxford</settlement>
                                      </placeName>
                                      Example
                                      <placeName>
                                       <district type="area">South Side</district>
                                       <settlement>Chicago</settlement>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element district
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-div.html b/gl/dev/ref-div.html index 4bb644c87..5e28ff0b4 100644 --- a/gl/dev/ref-div.html +++ b/gl/dev/ref-div.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <div>

                                      <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.divLike (@org, @sample) (att.metrical (@met, @real, @rhyme)) (att.fragmentable (@part)) att.declaring (@decls) att.written (@hand) att.typed (type, @subtype)
                                      type
                                      Status Required
                                      Legal values are:
                                      apparatus
                                      to contain apparatus criticus or textual notes
                                      bibliography
                                      to contain iographical information, previous publications, etc.
                                      commentary
                                      to contain all editorial commentary, historical/prosopographical discussion, etc.
                                      edition
                                      to contain the text of the edition itself; may include multiple text-parts
                                      textpart
                                      used to divide a div[type=edition] into multiple parts (fragments, columns, faces, etc.)
                                      translation
                                      to contain a translation of the text into one or more modern languages
                                      Member of
                                      Contained by
                                      textcrit: lem rdg
                                      textstructure: back body div front
                                      May contain
                                      Example
                                      <body>
                                       <div type="part">
                                        <head>Fallacies of Authority</head>
                                        <p>The subject of which is Authority in various shapes, and the object, to repress all
                                           exercise of the reasoning faculty.</p>
                                        <div n="1type="chapter">
                                         <head>The Nature of Authority</head>
                                         <p>With reference to any proposed measures having for their object the greatest
                                             happiness of the greatest number [...]</p>
                                         <div n="1.1type="section">
                                          <head>Analysis of Authority</head>
                                          <p>What on any given occasion is the legitimate weight or influence to be attached to
                                               authority [...] </p>
                                         </div>
                                         <div n="1.2type="section">
                                          <head>Appeal to Authority, in What Cases Fallacious.</head>
                                          <p>Reference to authority is open to the charge of fallacy when [...] </p>
                                         </div>
                                        </div>
                                       </div>
                                      </body>
                                      Schematron

                                      <sch:rule context="tei:div">
                                      <sch:report test="@type != 'textpart' and parent::tei:div and @type!=parent::tei:div/@type"> Divs other than @type=textpart may not nest in divs of different @type
                                      </sch:report>
                                      </sch:rule>
                                      Schematron

                                      <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
                                      </sch:report>
                                      Schematron

                                      <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
                                      </sch:report>
                                      Content model
                                      <content>
                                       <sequence minOccurs="1maxOccurs="1">
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <sequence minOccurs="0maxOccurs="1">
                                         <alternate minOccurs="1maxOccurs="1">
                                          <sequence minOccurs="1"
                                           maxOccurs="unbounded">

                                           <alternate minOccurs="1maxOccurs="1">
                                            <classRef key="model.divLike"/>
                                            <classRef key="model.divGenLike"/>
                                           </alternate>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                          </sequence>
                                          <sequence minOccurs="1maxOccurs="1">
                                           <sequence minOccurs="1"
                                            maxOccurs="unbounded">

                                            <alternate minOccurs="1"
                                             maxOccurs="1">

                                             <elementRef key="schemaSpec"/>
                                             <classRef key="model.common"/>
                                            </alternate>
                                            <classRef key="model.global"
                                             minOccurs="0maxOccurs="unbounded"/>

                                           </sequence>
                                           <sequence minOccurs="0"
                                            maxOccurs="unbounded">

                                            <alternate minOccurs="1"
                                             maxOccurs="1">

                                             <classRef key="model.divLike"/>
                                             <classRef key="model.divGenLike"/>
                                            </alternate>
                                            <classRef key="model.global"
                                             minOccurs="0maxOccurs="unbounded"/>

                                           </sequence>
                                          </sequence>
                                         </alternate>
                                         <sequence minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.divBottom"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <div>

                                      <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.divLike (@org, @sample) (att.metrical (@met, @real, @rhyme)) (att.fragmentable (@part)) att.declaring (@decls) att.written (@hand) att.typed (type, @subtype)
                                      type
                                      Status Required
                                      Legal values are:
                                      apparatus
                                      to contain apparatus criticus or textual notes
                                      bibliography
                                      to contain iographical information, previous publications, etc.
                                      commentary
                                      to contain all editorial commentary, historical/prosopographical discussion, etc.
                                      edition
                                      to contain the text of the edition itself; may include multiple text-parts
                                      textpart
                                      used to divide a div[type=edition] into multiple parts (fragments, columns, faces, etc.)
                                      translation
                                      to contain a translation of the text into one or more modern languages
                                      Member of
                                      Contained by
                                      textcrit: lem rdg
                                      textstructure: back body div front
                                      May contain
                                      Example
                                      <body>
                                       <div type="part">
                                        <head>Fallacies of Authority</head>
                                        <p>The subject of which is Authority in various shapes, and the object, to repress all
                                           exercise of the reasoning faculty.</p>
                                        <div n="1type="chapter">
                                         <head>The Nature of Authority</head>
                                         <p>With reference to any proposed measures having for their object the greatest
                                             happiness of the greatest number [...]</p>
                                         <div n="1.1type="section">
                                          <head>Analysis of Authority</head>
                                          <p>What on any given occasion is the legitimate weight or influence to be attached to
                                               authority [...] </p>
                                         </div>
                                         <div n="1.2type="section">
                                          <head>Appeal to Authority, in What Cases Fallacious.</head>
                                          <p>Reference to authority is open to the charge of fallacy when [...] </p>
                                         </div>
                                        </div>
                                       </div>
                                      </body>
                                      Schematron

                                      <sch:rule context="tei:div">
                                      <sch:report test="@type != 'textpart' and parent::tei:div and @type!=parent::tei:div/@type"> Divs other than @type=textpart may not nest in divs of different @type
                                      </sch:report>
                                      </sch:rule>
                                      Schematron

                                      <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
                                      </sch:report>
                                      Schematron

                                      <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
                                      </sch:report>
                                      Content model
                                      <content>
                                       <sequence minOccurs="1maxOccurs="1">
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <sequence minOccurs="0maxOccurs="1">
                                         <alternate minOccurs="1maxOccurs="1">
                                          <sequence minOccurs="1"
                                           maxOccurs="unbounded">

                                           <alternate minOccurs="1maxOccurs="1">
                                            <classRef key="model.divLike"/>
                                            <classRef key="model.divGenLike"/>
                                           </alternate>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                          </sequence>
                                          <sequence minOccurs="1maxOccurs="1">
                                           <sequence minOccurs="1"
                                            maxOccurs="unbounded">

                                            <alternate minOccurs="1"
                                             maxOccurs="1">

                                             <elementRef key="schemaSpec"/>
                                             <classRef key="model.common"/>
                                            </alternate>
                                            <classRef key="model.global"
                                             minOccurs="0maxOccurs="unbounded"/>

                                           </sequence>
                                           <sequence minOccurs="0"
                                            maxOccurs="unbounded">

                                            <alternate minOccurs="1"
                                             maxOccurs="1">

                                             <classRef key="model.divLike"/>
                                             <classRef key="model.divGenLike"/>
                                            </alternate>
                                            <classRef key="model.global"
                                             minOccurs="0maxOccurs="unbounded"/>

                                           </sequence>
                                          </sequence>
                                         </alternate>
                                         <sequence minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.divBottom"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element div
                                       {
                                          tei_att.global.attributes,
                                      @@ -54,4 +54,4 @@
                                                ( tei_model.divBottom, tei_model.global* )*
                                             )?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-divGen.html b/gl/dev/ref-divGen.html index 7efeaaf31..c65099452 100644 --- a/gl/dev/ref-divGen.html +++ b/gl/dev/ref-divGen.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <divGen>

                                      <divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typespecifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      index
                                      an index is to be generated and inserted at this point.
                                      toc
                                      a table of contents
                                      figlist
                                      a list of figures
                                      tablist
                                      a list of tables
                                      Note

                                      Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

                                      Member of
                                      Contained by
                                      textstructure: back body div front
                                      May contain
                                      core: head
                                      Note

                                      This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

                                      Example

                                      One use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on index elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:

                                      <back>
                                       <div1 type="backmat">
                                        <head>Bibliography</head>
                                      <!-- ... -->
                                       </div1>
                                       <div1 type="backmat">
                                        <head>Indices</head>
                                        <divGen n="Index Nominumtype="NAMES"/>
                                        <divGen n="Index Rerumtype="THINGS"/>
                                       </div1>
                                      </back>
                                      Example

                                      Another use for divGen is to specify the location of an automatically produced table of contents:

                                      <front>
                                      <!--<titlePage>...</titlePage>-->
                                       <divGen type="toc"/>
                                       <div>
                                        <head>Preface</head>
                                        <p> ... </p>
                                       </div>
                                      </front>
                                      Content model
                                      <content>
                                       <classRef key="model.headLike"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <divGen>

                                      <divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
                                      typespecifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      index
                                      an index is to be generated and inserted at this point.
                                      toc
                                      a table of contents
                                      figlist
                                      a list of figures
                                      tablist
                                      a list of tables
                                      Note

                                      Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

                                      Member of
                                      Contained by
                                      textstructure: back body div front
                                      May contain
                                      core: head
                                      Note

                                      This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

                                      Example

                                      One use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on index elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:

                                      <back>
                                       <div1 type="backmat">
                                        <head>Bibliography</head>
                                      <!-- ... -->
                                       </div1>
                                       <div1 type="backmat">
                                        <head>Indices</head>
                                        <divGen n="Index Nominumtype="NAMES"/>
                                        <divGen n="Index Rerumtype="THINGS"/>
                                       </div1>
                                      </back>
                                      Example

                                      Another use for divGen is to specify the location of an automatically produced table of contents:

                                      <front>
                                      <!--<titlePage>...</titlePage>-->
                                       <divGen type="toc"/>
                                       <div>
                                        <head>Preface</head>
                                        <p> ... </p>
                                       </div>
                                      </front>
                                      Content model
                                      <content>
                                       <classRef key="model.headLike"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element divGen
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attribute.subtype,
                                          attribute type { teidata.enumerated }?,
                                          tei_model.headLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-docAuthor.html b/gl/dev/ref-docAuthor.html index 073c4bac8..3398aa847 100644 --- a/gl/dev/ref-docAuthor.html +++ b/gl/dev/ref-docAuthor.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <docAuthor>

                                      <docAuthor> (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back body div front group
                                      May contain
                                      Note

                                      The document author's name often occurs within a byline, but the docAuthor element may be used whether the <byline> element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with <byline> without docAuthor.)

                                      Example
                                      <titlePage>
                                       <docTitle>
                                        <titlePart>Travels into Several Remote Nations of the World, in Four
                                           Parts.</titlePart>
                                       </docTitle>
                                       <byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon,
                                         and then a Captain of several Ships</byline>
                                      </titlePage>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <docAuthor>

                                      <docAuthor> (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back body div front group
                                      May contain
                                      Note

                                      The document author's name often occurs within a byline, but the docAuthor element may be used whether the <byline> element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with <byline> without docAuthor.)

                                      Example
                                      <titlePage>
                                       <docTitle>
                                        <titlePart>Travels into Several Remote Nations of the World, in Four
                                           Parts.</titlePart>
                                       </docTitle>
                                       <byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon,
                                         and then a Captain of several Ships</byline>
                                      </titlePage>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element docAuthor
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-docDate.html b/gl/dev/ref-docDate.html index 783be0675..321a27bce 100644 --- a/gl/dev/ref-docDate.html +++ b/gl/dev/ref-docDate.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <docDate>

                                      <docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      when(when) gives the value of the date in standard form, i.e. YYYY-MM-DD.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      Note

                                      For simple dates, the when attribute should give the Gregorian or proleptic Gregorian date in one of the formats specified in XML Schema Part 2: Datatypes Second Edition.

                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      May contain
                                      Note

                                      Cf. the general date element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it.

                                      Example
                                      <docImprint>Oxford, Clarendon Press, <docDate>1987</docDate>
                                      </docImprint>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <docDate>

                                      <docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      when(when) gives the value of the date in standard form, i.e. YYYY-MM-DD.
                                      Status Optional
                                      Datatype teidata.temporal.w3c
                                      Note

                                      For simple dates, the when attribute should give the Gregorian or proleptic Gregorian date in one of the formats specified in XML Schema Part 2: Datatypes Second Edition.

                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      May contain
                                      Note

                                      Cf. the general date element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it.

                                      Example
                                      <docImprint>Oxford, Clarendon Press, <docDate>1987</docDate>
                                      </docImprint>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element docDate
                                       {
                                          tei_att.global.attributes,
                                          attribute when { teidata.temporal.w3c }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-docEdition.html b/gl/dev/ref-docEdition.html index 08e27f5a8..6580c111d 100644 --- a/gl/dev/ref-docEdition.html +++ b/gl/dev/ref-docEdition.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <docEdition>

                                      <docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back front
                                      May contain
                                      Note

                                      Cf. the edition element of bibliographic citation. As usual, the shorter name has been given to the more frequent element.

                                      Example
                                      <docEdition>The Third edition Corrected</docEdition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      -element docEdition { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <docEdition>

                                      <docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back front
                                      May contain
                                      Note

                                      Cf. the edition element of bibliographic citation. As usual, the shorter name has been given to the more frequent element.

                                      Example
                                      <docEdition>The Third edition Corrected</docEdition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +element docEdition { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-docImprint.html b/gl/dev/ref-docImprint.html index bd806e828..e9d1a22f7 100644 --- a/gl/dev/ref-docImprint.html +++ b/gl/dev/ref-docImprint.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <docImprint>

                                      <docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back front
                                      May contain
                                      Note

                                      Cf. the imprint element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often.

                                      Example
                                      <docImprint>Oxford, Clarendon Press, 1987</docImprint>
                                      Imprints may be somewhat more complex:
                                      <docImprint>
                                       <pubPlace>London</pubPlace>
                                      Printed for <name>E. Nutt</name>,
                                      at
                                      <pubPlace>Royal Exchange</pubPlace>;
                                      <name>J. Roberts</name> in
                                      <pubPlace>wick-Lane</pubPlace>;
                                      <name>A. Dodd</name> without
                                      <pubPlace>Temple-Bar</pubPlace>;
                                      and <name>J. Graves</name> in
                                      <pubPlace>St. James's-street.</pubPlace>
                                       <date>1722.</date>
                                      </docImprint>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <elementRef key="pubPlace"/>
                                        <elementRef key="docDate"/>
                                        <elementRef key="publisher"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <docImprint>

                                      <docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back front
                                      May contain
                                      Note

                                      Cf. the imprint element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often.

                                      Example
                                      <docImprint>Oxford, Clarendon Press, 1987</docImprint>
                                      Imprints may be somewhat more complex:
                                      <docImprint>
                                       <pubPlace>London</pubPlace>
                                      Printed for <name>E. Nutt</name>,
                                      at
                                      <pubPlace>Royal Exchange</pubPlace>;
                                      <name>J. Roberts</name> in
                                      <pubPlace>wick-Lane</pubPlace>;
                                      <name>A. Dodd</name> without
                                      <pubPlace>Temple-Bar</pubPlace>;
                                      and <name>J. Graves</name> in
                                      <pubPlace>St. James's-street.</pubPlace>
                                       <date>1722.</date>
                                      </docImprint>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <elementRef key="pubPlace"/>
                                        <elementRef key="docDate"/>
                                        <elementRef key="publisher"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element docImprint
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                           | tei_publisher
                                           | tei_model.global
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-docTitle.html b/gl/dev/ref-docTitle.html index b56daa70c..0db13e7ac 100644 --- a/gl/dev/ref-docTitle.html +++ b/gl/dev/ref-docTitle.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <docTitle>

                                      <docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back front
                                      May contain
                                      Example
                                      <docTitle>
                                       <titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart>
                                       <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart>
                                      </docTitle>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="titlePart"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <docTitle>

                                      <docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back front
                                      May contain
                                      Example
                                      <docTitle>
                                       <titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart>
                                       <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart>
                                      </docTitle>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="titlePart"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element docTitle
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          ( tei_model.global*, ( titlePart, tei_model.global* )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-edition.html b/gl/dev/ref-edition.html index c132d504e..42ee1419a 100644 --- a/gl/dev/ref-edition.html +++ b/gl/dev/ref-edition.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <edition>

                                      <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      header: editionStmt
                                      May contain
                                      Example
                                      <edition>First edition <date>Oct 1990</date>
                                      </edition>
                                      <edition n="S2">Students' edition</edition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element edition { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <edition>

                                      <edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      header: editionStmt
                                      May contain
                                      Example
                                      <edition>First edition <date>Oct 1990</date>
                                      </edition>
                                      <edition n="S2">Students' edition</edition>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element edition { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-editionStmt.html b/gl/dev/ref-editionStmt.html index 5bd7eb4db..a09c0fa28 100644 --- a/gl/dev/ref-editionStmt.html +++ b/gl/dev/ref-editionStmt.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <editionStmt>

                                      <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <editionStmt>
                                       <edition n="S2">Students' edition</edition>
                                       <respStmt>
                                        <resp>Adapted by </resp>
                                        <name>Elizabeth Kirk</name>
                                       </respStmt>
                                      </editionStmt>
                                      Example
                                      <editionStmt>
                                       <p>First edition, <date>Michaelmas Term, 1991.</date>
                                       </p>
                                      </editionStmt>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="edition"/>
                                         <classRef key="model.respLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <editionStmt>

                                      <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <editionStmt>
                                       <edition n="S2">Students' edition</edition>
                                       <respStmt>
                                        <resp>Adapted by </resp>
                                        <name>Elizabeth Kirk</name>
                                       </respStmt>
                                      </editionStmt>
                                      Example
                                      <editionStmt>
                                       <p>First edition, <date>Michaelmas Term, 1991.</date>
                                       </p>
                                      </editionStmt>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="edition"/>
                                         <classRef key="model.respLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element editionStmt
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-editor.html b/gl/dev/ref-editor.html index a0606c7c7..07ec39a0b 100644 --- a/gl/dev/ref-editor.html +++ b/gl/dev/ref-editor.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <editor>

                                      <editor> 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, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      A consistent format should be adopted.

                                      Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

                                      Example
                                      <editor role="Technical_Editor">Ron Van den Branden</editor>
                                      <editor role="Editor-in-Chief">John Walsh</editor>
                                      <editor role="Managing_Editor">Anne Baillot</editor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <editor>

                                      <editor> 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, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      A consistent format should be adopted.

                                      Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

                                      Example
                                      <editor role="Technical_Editor">Ron Van den Branden</editor>
                                      <editor role="Editor-in-Chief">John Walsh</editor>
                                      <editor role="Managing_Editor">Anne Baillot</editor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element editor
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-editorialDecl.html b/gl/dev/ref-editorialDecl.html index 84f369af7..050e64b9c 100644 --- a/gl/dev/ref-editorialDecl.html +++ b/gl/dev/ref-editorialDecl.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <editorialDecl>

                                      <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      Example
                                      <editorialDecl>
                                       <normalization>
                                        <p>All words converted to Modern American spelling using
                                           Websters 9th Collegiate dictionary
                                        </p>
                                       </normalization>
                                       <quotation marks="all">
                                        <p>All opening quotation marks converted to “ all closing
                                           quotation marks converted to &amp;cdq;.</p>
                                       </quotation>
                                      </editorialDecl>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <classRef key="model.editorialDeclPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <editorialDecl>

                                      <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      Example
                                      <editorialDecl>
                                       <normalization>
                                        <p>All words converted to Modern American spelling using
                                           Websters 9th Collegiate dictionary
                                        </p>
                                       </normalization>
                                       <quotation marks="all">
                                        <p>All opening quotation marks converted to “ all closing
                                           quotation marks converted to &amp;cdq;.</p>
                                       </quotation>
                                      </editorialDecl>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <classRef key="model.editorialDeclPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element editorialDecl
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          ( tei_model.pLike | tei_model.editorialDeclPart )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-ellipsis.html b/gl/dev/ref-ellipsis.html index 2b1991b97..f2343a3e7 100644 --- a/gl/dev/ref-ellipsis.html +++ b/gl/dev/ref-ellipsis.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <ellipsis>

                                      <ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) )
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      Unlike gap, which indicates content that the encoder cannot or chooses not to represent, ellipsis indicates a passage explicitly signalled in the source document as absent. The ellipsis element is not appropriate for every use of ellipsis points, such as when they indicate that a speaker is pausing.

                                      Example
                                      <lg>
                                       <l>What projects men make—what queer turns they take,</l>
                                       <l>Since <emph>steam</emph> has improved our condition;</l>
                                       <l>They never are still, but must cure or must kill</l>
                                       <l>With steam physic or steam ammunition.</l>
                                       <l>But a short time ago, to a quack you would go,</l>
                                       <l>To steam a fat man to a thinner;</l>
                                       <l>Now changed from all that, if you wish to get <emph>fat</emph>,</l>
                                       <l>Come to Barton’s and eat a <emph>steam dinner!</emph>
                                       </l>
                                       <l>Oh dear! think of a scheme, odd though it seem—</l>
                                       <l>I’m sure ’twill succeed if you make it by steam.</l>
                                      </lg>
                                      <lg>
                                       <l>You may sleep, you may dream, you may travel by steam,</l>
                                       <l>For the outcry is still to go faster;</l>
                                       <l>And what does it reck, should you e’en break your neck,</l>
                                       <l>If ’tis <emph>steam</emph> that brings on the disaster?</l>
                                       <ellipsis resp="#ChambersEdnbrghJrnl1880">
                                        <metamark function="multilineEllipsis"> * * * * </metamark>
                                        <desc resp="#teiProjectEditor2021">The printer omits four lines here,
                                           skipping the second half of the second octave, before the refrain.</desc>
                                       </ellipsis>
                                       <l>Oh dear! think of a scheme, odd though it seem—</l>
                                       <l>I’m sure ’twill succeed if you make it by steam.</l>
                                      </lg>
                                      Example
                                      <lg>
                                       <l>You think you’ve lost your love </l>
                                       <l>Well, I saw her yesterday </l>
                                       <l>It’s you she's thinking of </l>
                                       <l>And she told me what to say</l>
                                      </lg>
                                      <lg xml:id="chorus">
                                       <label>[Refrain]</label>
                                       <l>She says she loves you </l>
                                       <l>And you know that can’t be bad </l>
                                       <l>Yes, she loves you </l>
                                       <l>And you know you should be glad</l>
                                      </lg>
                                      <lg>
                                       <l>She said you hurt her so </l>
                                       <l>She almost lost her mind </l>
                                       <l>But now she said she knows </l>
                                       <l>You’re not the hurting kind</l>
                                      </lg>
                                      <ellipsis>
                                       <metamark>******</metamark>
                                       <supplied copyOf="#chorus"/>
                                      </ellipsis>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="metamark"/>
                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="1"/>

                                        <elementRef key="suppliedminOccurs="0"
                                         maxOccurs="1"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <ellipsis>

                                      <ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) )
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      Unlike gap, which indicates content that the encoder cannot or chooses not to represent, ellipsis indicates a passage explicitly signalled in the source document as absent. The ellipsis element is not appropriate for every use of ellipsis points, such as when they indicate that a speaker is pausing.

                                      Example
                                      <lg>
                                       <l>What projects men make—what queer turns they take,</l>
                                       <l>Since <emph>steam</emph> has improved our condition;</l>
                                       <l>They never are still, but must cure or must kill</l>
                                       <l>With steam physic or steam ammunition.</l>
                                       <l>But a short time ago, to a quack you would go,</l>
                                       <l>To steam a fat man to a thinner;</l>
                                       <l>Now changed from all that, if you wish to get <emph>fat</emph>,</l>
                                       <l>Come to Barton’s and eat a <emph>steam dinner!</emph>
                                       </l>
                                       <l>Oh dear! think of a scheme, odd though it seem—</l>
                                       <l>I’m sure ’twill succeed if you make it by steam.</l>
                                      </lg>
                                      <lg>
                                       <l>You may sleep, you may dream, you may travel by steam,</l>
                                       <l>For the outcry is still to go faster;</l>
                                       <l>And what does it reck, should you e’en break your neck,</l>
                                       <l>If ’tis <emph>steam</emph> that brings on the disaster?</l>
                                       <ellipsis resp="#ChambersEdnbrghJrnl1880">
                                        <metamark function="multilineEllipsis"> * * * * </metamark>
                                        <desc resp="#teiProjectEditor2021">The printer omits four lines here,
                                           skipping the second half of the second octave, before the refrain.</desc>
                                       </ellipsis>
                                       <l>Oh dear! think of a scheme, odd though it seem—</l>
                                       <l>I’m sure ’twill succeed if you make it by steam.</l>
                                      </lg>
                                      Example
                                      <lg>
                                       <l>You think you’ve lost your love </l>
                                       <l>Well, I saw her yesterday </l>
                                       <l>It’s you she's thinking of </l>
                                       <l>And she told me what to say</l>
                                      </lg>
                                      <lg xml:id="chorus">
                                       <label>[Refrain]</label>
                                       <l>She says she loves you </l>
                                       <l>And you know that can’t be bad </l>
                                       <l>Yes, she loves you </l>
                                       <l>And you know you should be glad</l>
                                      </lg>
                                      <lg>
                                       <l>She said you hurt her so </l>
                                       <l>She almost lost her mind </l>
                                       <l>But now she said she knows </l>
                                       <l>You’re not the hurting kind</l>
                                      </lg>
                                      <ellipsis>
                                       <metamark>******</metamark>
                                       <supplied copyOf="#chorus"/>
                                      </ellipsis>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="metamark"/>
                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="1"/>

                                        <elementRef key="suppliedminOccurs="0"
                                         maxOccurs="1"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element ellipsis
                                       {
                                          tei_att.global.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_att.timed.attributes,
                                          ( tei_metamark, tei_model.descLike?, tei_supplied? )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-email.html b/gl/dev/ref-email.html index e88ad077a..441c67307 100644 --- a/gl/dev/ref-email.html +++ b/gl/dev/ref-email.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <email>

                                      <email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The format of a modern Internet email address is defined in RFC 2822

                                      Example
                                      <email>membership@tei-c.org</email>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element email { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <email>

                                      <email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The format of a modern Internet email address is defined in RFC 2822

                                      Example
                                      <email>membership@tei-c.org</email>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element email { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-emph.html b/gl/dev/ref-emph.html index 4ebe21196..146a39e5b 100644 --- a/gl/dev/ref-emph.html +++ b/gl/dev/ref-emph.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <emph>

                                      <emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      You took the car and did <emph>what</emph>?!!
                                      Example
                                      <q>What it all comes to is this,</q> he said.
                                      <q>
                                       <emph>What
                                         does Christopher Robin do in the morning nowadays?</emph>
                                      </q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      -element emph { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <emph>

                                      <emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      You took the car and did <emph>what</emph>?!!
                                      Example
                                      <q>What it all comes to is this,</q> he said.
                                      <q>
                                       <emph>What
                                         does Christopher Robin do in the morning nowadays?</emph>
                                      </q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +element emph { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-encodingDesc.html b/gl/dev/ref-encodingDesc.html index a744d87e1..e72dcd07f 100644 --- a/gl/dev/ref-encodingDesc.html +++ b/gl/dev/ref-encodingDesc.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <encodingDesc>

                                      <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: teiHeader
                                      May contain
                                      Example
                                      <encodingDesc>
                                       <p>Basic encoding, capturing lexical information only. All
                                         hyphenation, punctuation, and variant spellings normalized. No
                                         formatting or layout information preserved.</p>
                                      </encodingDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.encodingDescPart"/>
                                        <classRef key="model.pLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <encodingDesc>

                                      <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: teiHeader
                                      May contain
                                      Example
                                      <encodingDesc>
                                       <p>Basic encoding, capturing lexical information only. All
                                         hyphenation, punctuation, and variant spellings normalized. No
                                         formatting or layout information preserved.</p>
                                      </encodingDesc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.encodingDescPart"/>
                                        <classRef key="model.pLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element encodingDesc
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.encodingDescPart | tei_model.pLike )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-epigraph.html b/gl/dev/ref-epigraph.html index c7d07f5b0..d9829d040 100644 --- a/gl/dev/ref-epigraph.html +++ b/gl/dev/ref-epigraph.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <epigraph>

                                      <epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back body div front group
                                      May contain
                                      Example
                                      <epigraph xml:lang="la">
                                       <cit>
                                        <bibl>Lucret.</bibl>
                                        <quote>
                                         <l part="F">petere inde coronam,</l>
                                         <l>Vnde prius nulli velarint tempora Musae.</l>
                                        </quote>
                                       </cit>
                                      </epigraph>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.common"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <epigraph>

                                      <epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: lg list
                                      figures: figure table
                                      msdescription: msItem
                                      textcrit: lem rdg
                                      textstructure: back body div front group
                                      May contain
                                      Example
                                      <epigraph xml:lang="la">
                                       <cit>
                                        <bibl>Lucret.</bibl>
                                        <quote>
                                         <l part="F">petere inde coronam,</l>
                                         <l>Vnde prius nulli velarint tempora Musae.</l>
                                        </quote>
                                       </cit>
                                      </epigraph>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.common"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element epigraph
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.common | tei_model.global )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-event.html b/gl/dev/ref-event.html index 47c27cc58..812fc368f 100644 --- a/gl/dev/ref-event.html +++ b/gl/dev/ref-event.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <event>

                                      <event> (event) contains data relating to any kind of significant event associated with a person, place, or organization. [13.3.1. Basic Principles]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.sortable (@sortKey) att.locatable (@where)
                                      Member of
                                      Contained by
                                      May contain
                                      header: biblFull idno
                                      linking: ab link linkGrp
                                      msdescription: msDesc
                                      namesdates: event
                                      Example
                                      <person>
                                       <event type="matwhen="1972-10-12">
                                        <label>matriculation</label>
                                       </event>
                                       <event type="gradwhen="1975-06-23">
                                        <label>graduation</label>
                                       </event>
                                      </person>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="idnominOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <classRef key="model.labelLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                         <elementRef key="idno"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                        <elementRef key="eventminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <event>

                                      <event> (event) contains data relating to any kind of significant event associated with a person, place, or organization. [13.3.1. Basic Principles]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.sortable (@sortKey) att.locatable (@where)
                                      Member of
                                      Contained by
                                      May contain
                                      header: biblFull idno
                                      linking: ab link linkGrp
                                      msdescription: msDesc
                                      namesdates: event
                                      Example
                                      <person>
                                       <event type="matwhen="1972-10-12">
                                        <label>matriculation</label>
                                       </event>
                                       <event type="gradwhen="1975-06-23">
                                        <label>graduation</label>
                                       </event>
                                      </person>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="idnominOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <classRef key="model.labelLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                         <elementRef key="idno"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                        <elementRef key="eventminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element event
                                       {
                                          tei_att.global.attributes,
                                      @@ -45,4 +45,4 @@
                                             )*,
                                             tei_event*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-ex.html b/gl/dev/ref-ex.html index 651902e52..cc30af764 100644 --- a/gl/dev/ref-ex.html +++ b/gl/dev/ref-ex.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <ex>

                                      <ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Example
                                      The address is Southmoor <choice>
                                       <expan>R<ex>oa</ex>d</expan>
                                       <abbr>Rd</abbr>
                                      </choice>
                                      Schematron

                                      <sch:rule context="tei:ex">
                                      <sch:report test="not(ancestor::tei:expan)">ex should only appear inside expan</sch:report>
                                      <sch:report test="parent::tei:abbr">ex should not be a child of abbr</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <ex>

                                      <ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Example
                                      The address is Southmoor <choice>
                                       <expan>R<ex>oa</ex>d</expan>
                                       <abbr>Rd</abbr>
                                      </choice>
                                      Schematron

                                      <sch:rule context="tei:ex">
                                      <sch:report test="not(ancestor::tei:expan)">ex should only appear inside expan</sch:report>
                                      <sch:report test="parent::tei:abbr">ex should not be a child of abbr</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element ex
                                       {
                                          tei_att.global.attributes,
                                          tei_att.editLike.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-expan.html b/gl/dev/ref-expan.html index 7c52610eb..afacac06d 100644 --- a/gl/dev/ref-expan.html +++ b/gl/dev/ref-expan.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <expan>

                                      <expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      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.

                                      Example
                                      The address is Southmoor
                                      <choice>
                                       <expan>Road</expan>
                                       <abbr>Rd</abbr>
                                      </choice>
                                      Example
                                      <choice xml:lang="la">
                                       <abbr>Imp</abbr>
                                       <expan>Imp<ex>erator</ex>
                                       </expan>
                                      </choice>
                                      Schematron

                                      <sch:rule context="tei:expan">
                                      <sch:report test="not(descendant::tei:ex)">expan should contain ex</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <expan>

                                      <expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      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.

                                      Example
                                      The address is Southmoor
                                      <choice>
                                       <expan>Road</expan>
                                       <abbr>Rd</abbr>
                                      </choice>
                                      Example
                                      <choice xml:lang="la">
                                       <abbr>Imp</abbr>
                                       <expan>Imp<ex>erator</ex>
                                       </expan>
                                      </choice>
                                      Schematron

                                      <sch:rule context="tei:expan">
                                      <sch:report test="not(descendant::tei:ex)">expan should contain ex</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element expan
                                       {
                                          tei_att.global.attributes,
                                          tei_att.editLike.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-explicit.html b/gl/dev/ref-explicit.html index 7a20f693b..b698098c4 100644 --- a/gl/dev/ref-explicit.html +++ b/gl/dev/ref-explicit.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <explicit>

                                      <explicit> (explicit) contains the explicit of a item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <explicit>sed libera nos a malo.</explicit>
                                      <rubric>Hic explicit oratio qui dicitur dominica.</rubric>
                                      <explicit type="defective">ex materia quasi et forma sibi
                                      proporti<gap/>
                                      </explicit>
                                      <explicit type="reverse">saued be shulle that doome of day the at
                                      </explicit>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <explicit>

                                      <explicit> (explicit) contains the explicit of a item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <explicit>sed libera nos a malo.</explicit>
                                      <rubric>Hic explicit oratio qui dicitur dominica.</rubric>
                                      <explicit type="defective">ex materia quasi et forma sibi
                                      proporti<gap/>
                                      </explicit>
                                      <explicit type="reverse">saued be shulle that doome of day the at
                                      </explicit>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element explicit
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.msExcerpt.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-extent.html b/gl/dev/ref-extent.html index 37f0793e7..c148c76d2 100644 --- a/gl/dev/ref-extent.html +++ b/gl/dev/ref-extent.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <extent>

                                      <extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <extent>3200 sentences</extent>
                                      <extent>between 10 and 20 Mb</extent>
                                      <extent>ten 3.5 inch high density diskettes</extent>
                                      Example

                                      The measure element may be used to supply normalized or machine tractable versions of the size or sizes concerned.

                                      <extent>
                                       <measure unit="MiBquantity="4.2">About four megabytes</measure>
                                       <measure unit="pagesquantity="245">245 pages of source
                                         material</measure>
                                      </extent>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element extent { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <extent>

                                      <extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <extent>3200 sentences</extent>
                                      <extent>between 10 and 20 Mb</extent>
                                      <extent>ten 3.5 inch high density diskettes</extent>
                                      Example

                                      The measure element may be used to supply normalized or machine tractable versions of the size or sizes concerned.

                                      <extent>
                                       <measure unit="MiBquantity="4.2">About four megabytes</measure>
                                       <measure unit="pagesquantity="245">245 pages of source
                                         material</measure>
                                      </extent>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element extent { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-facsimile.html b/gl/dev/ref-facsimile.html index da56a9d9d..2d40ed42e 100644 --- a/gl/dev/ref-facsimile.html +++ b/gl/dev/ref-facsimile.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <facsimile>

                                      <facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      textstructure: back front
                                      Example
                                      <facsimile>
                                       <graphic url="page1.png"/>
                                       <surface>
                                        <graphic url="page2-highRes.png"/>
                                        <graphic url="page2-lowRes.png"/>
                                       </surface>
                                       <graphic url="page3.png"/>
                                       <graphic url="page4.png"/>
                                      </facsimile>
                                      Example
                                      <facsimile>
                                       <surface ulx="0uly="0lrx="200lry="300">
                                        <graphic url="Bovelles-49r.png"/>
                                       </surface>
                                      </facsimile>
                                      Schematron

                                      <sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone">
                                      <sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus
                                      transcribed text should not be present within it.
                                      </sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="frontminOccurs="0"/>
                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.graphicLike"/>
                                         <elementRef key="surface"/>
                                         <elementRef key="surfaceGrp"/>
                                        </alternate>
                                        <elementRef key="backminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <facsimile>

                                      <facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      textstructure: back front
                                      Example
                                      <facsimile>
                                       <graphic url="page1.png"/>
                                       <surface>
                                        <graphic url="page2-highRes.png"/>
                                        <graphic url="page2-lowRes.png"/>
                                       </surface>
                                       <graphic url="page3.png"/>
                                       <graphic url="page4.png"/>
                                      </facsimile>
                                      Example
                                      <facsimile>
                                       <surface ulx="0uly="0lrx="200lry="300">
                                        <graphic url="Bovelles-49r.png"/>
                                       </surface>
                                      </facsimile>
                                      Schematron

                                      <sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone">
                                      <sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus
                                      transcribed text should not be present within it.
                                      </sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="frontminOccurs="0"/>
                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.graphicLike"/>
                                         <elementRef key="surface"/>
                                         <elementRef key="surfaceGrp"/>
                                        </alternate>
                                        <elementRef key="backminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element facsimile
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                             ( tei_model.graphicLike | tei_surface | tei_surfaceGrp )+,
                                             tei_back?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-figDesc.html b/gl/dev/ref-figDesc.html index 1b82fec92..983bddeef 100644 --- a/gl/dev/ref-figDesc.html +++ b/gl/dev/ref-figDesc.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <figDesc>

                                      <figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      figures: figure
                                      May contain
                                      Note

                                      This element is intended for use as an alternative to the content of its parent figure element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

                                      Example
                                      <figure>
                                       <graphic url="emblem1.png"/>
                                       <head>Emblemi d'Amore</head>
                                       <figDesc>A pair of naked winged cupids, each holding a
                                         flaming torch, in a rural setting.</figDesc>
                                      </figure>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                      -element figDesc { tei_att.global.attributes, tei_macro.limitedContent }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <figDesc>

                                      <figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      figures: figure
                                      May contain
                                      Note

                                      This element is intended for use as an alternative to the content of its parent figure element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

                                      Example
                                      <figure>
                                       <graphic url="emblem1.png"/>
                                       <head>Emblemi d'Amore</head>
                                       <figDesc>A pair of naked winged cupids, each holding a
                                         flaming torch, in a rural setting.</figDesc>
                                      </figure>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                      +element figDesc { tei_att.global.attributes, tei_macro.limitedContent }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-figure.html b/gl/dev/ref-figure.html index 28f456869..3060746e4 100644 --- a/gl/dev/ref-figure.html +++ b/gl/dev/ref-figure.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <figure>

                                      <figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <figure>
                                       <head>The View from the Bridge</head>
                                       <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
                                         series of buoys strung out between them.</figDesc>
                                       <graphic url="http://www.example.org/fig1.png"
                                        scale="0.5"/>

                                      </figure>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.headLike"/>
                                        <classRef key="model.common"/>
                                        <elementRef key="figDesc"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.divBottom"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <figure>

                                      <figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <figure>
                                       <head>The View from the Bridge</head>
                                       <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
                                         series of buoys strung out between them.</figDesc>
                                       <graphic url="http://www.example.org/fig1.png"
                                        scale="0.5"/>

                                      </figure>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.headLike"/>
                                        <classRef key="model.common"/>
                                        <elementRef key="figDesc"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.divBottom"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element figure
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                           | tei_model.global
                                           | tei_model.divBottom
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-fileDesc.html b/gl/dev/ref-fileDesc.html index 390815c83..ecf018d0b 100644 --- a/gl/dev/ref-fileDesc.html +++ b/gl/dev/ref-fileDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <fileDesc>

                                      <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

                                      Example
                                      <fileDesc>
                                       <titleStmt>
                                        <title>The shortest possible TEI document</title>
                                       </titleStmt>
                                       <publicationStmt>
                                        <p>Distributed as part of TEI P5</p>
                                       </publicationStmt>
                                       <sourceDesc>
                                        <p>No print source exists: this is an original digital text</p>
                                       </sourceDesc>
                                      </fileDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <sequence>
                                         <elementRef key="titleStmt"/>
                                         <elementRef key="editionStmt"
                                          minOccurs="0"/>

                                         <elementRef key="extentminOccurs="0"/>
                                         <elementRef key="publicationStmt"/>
                                         <elementRef key="seriesStmt"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="notesStmt"
                                          minOccurs="0"/>

                                        </sequence>
                                        <elementRef key="sourceDesc"
                                         minOccurs="1maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <fileDesc>

                                      <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

                                      Example
                                      <fileDesc>
                                       <titleStmt>
                                        <title>The shortest possible TEI document</title>
                                       </titleStmt>
                                       <publicationStmt>
                                        <p>Distributed as part of TEI P5</p>
                                       </publicationStmt>
                                       <sourceDesc>
                                        <p>No print source exists: this is an original digital text</p>
                                       </sourceDesc>
                                      </fileDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <sequence>
                                         <elementRef key="titleStmt"/>
                                         <elementRef key="editionStmt"
                                          minOccurs="0"/>

                                         <elementRef key="extentminOccurs="0"/>
                                         <elementRef key="publicationStmt"/>
                                         <elementRef key="seriesStmt"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="notesStmt"
                                          minOccurs="0"/>

                                        </sequence>
                                        <elementRef key="sourceDesc"
                                         minOccurs="1maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element fileDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                             ),
                                             tei_sourceDesc+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-filiation.html b/gl/dev/ref-filiation.html index 7bb1aed1d..bb36a81f1 100644 --- a/gl/dev/ref-filiation.html +++ b/gl/dev/ref-filiation.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <filiation>

                                      <filiation> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <msContents>
                                       <msItem>
                                        <title>Beljakovski sbornik</title>
                                        <filiation type="protograph">Bulgarian</filiation>
                                        <filiation type="antigraph">Middle Bulgarian</filiation>
                                        <filiation type="apograph">
                                         <ref target="#DN17">Dujchev N 17</ref>
                                        </filiation>
                                       </msItem>
                                      </msContents>
                                      <!-- ... -->
                                      <msDesc xml:id="DN17">
                                       <msIdentifier>
                                        <settlement>Faraway</settlement>
                                       </msIdentifier>
                                      <!-- ... -->
                                      </msDesc>

                                      In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17.

                                      Example
                                      <msItem>
                                       <title>Guan-ben</title>
                                       <filiation>
                                        <p>The "Guan-ben" was widely current among mathematicians in the
                                           Qing dynasty, and "Zhao Qimei version" was also read. It is
                                           therefore difficult to know the correct filiation path to follow.
                                           The study of this era is much indebted to Li Di. We explain the
                                           outline of his conclusion here. Kong Guangsen
                                           (1752-1786)(17) was from the same town as Dai Zhen, so he obtained
                                           "Guan-ben" from him and studied it(18). Li Huang (d. 1811)
                                           (19) took part in editing Si Ku Quan Shu, so he must have had
                                           "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,
                                           and studied "Da Yan Zong Shu Shu" (The General Dayan
                                           Computation). He wrote Jiu Yi Suan Shu (Mathematics
                                           Searching for One, 1803) based on this version of Shu Xue Jiu
                                           Zhang (20).</p>
                                        <p>One of the most important persons in restoring our knowledge
                                           concerning the filiation of these books was Li Rui (1768(21)
                                           -1817)(see his biography). ... only two volumes remain of this
                                           manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,
                                           question 2 of "Huan Tian San Ji" (square of three loops),
                                           which later has been lost.</p>
                                       </filiation>
                                      </msItem>
                                      <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <filiation>

                                      <filiation> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <msContents>
                                       <msItem>
                                        <title>Beljakovski sbornik</title>
                                        <filiation type="protograph">Bulgarian</filiation>
                                        <filiation type="antigraph">Middle Bulgarian</filiation>
                                        <filiation type="apograph">
                                         <ref target="#DN17">Dujchev N 17</ref>
                                        </filiation>
                                       </msItem>
                                      </msContents>
                                      <!-- ... -->
                                      <msDesc xml:id="DN17">
                                       <msIdentifier>
                                        <settlement>Faraway</settlement>
                                       </msIdentifier>
                                      <!-- ... -->
                                      </msDesc>

                                      In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17.

                                      Example
                                      <msItem>
                                       <title>Guan-ben</title>
                                       <filiation>
                                        <p>The "Guan-ben" was widely current among mathematicians in the
                                           Qing dynasty, and "Zhao Qimei version" was also read. It is
                                           therefore difficult to know the correct filiation path to follow.
                                           The study of this era is much indebted to Li Di. We explain the
                                           outline of his conclusion here. Kong Guangsen
                                           (1752-1786)(17) was from the same town as Dai Zhen, so he obtained
                                           "Guan-ben" from him and studied it(18). Li Huang (d. 1811)
                                           (19) took part in editing Si Ku Quan Shu, so he must have had
                                           "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,
                                           and studied "Da Yan Zong Shu Shu" (The General Dayan
                                           Computation). He wrote Jiu Yi Suan Shu (Mathematics
                                           Searching for One, 1803) based on this version of Shu Xue Jiu
                                           Zhang (20).</p>
                                        <p>One of the most important persons in restoring our knowledge
                                           concerning the filiation of these books was Li Rui (1768(21)
                                           -1817)(see his biography). ... only two volumes remain of this
                                           manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,
                                           question 2 of "Huan Tian San Ji" (square of three loops),
                                           which later has been lost.</p>
                                       </filiation>
                                      </msItem>
                                      <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element filiation
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-finalRubric.html b/gl/dev/ref-finalRubric.html index 7c63f8a19..1a72969e8 100644 --- a/gl/dev/ref-finalRubric.html +++ b/gl/dev/ref-finalRubric.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <finalRubric>

                                      <finalRubric> (final rubric) contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <finalRubric>Explicit le romans de la Rose ou l'art
                                      d'amours est toute enclose.</finalRubric>
                                      <finalRubric>ok lúkv ver þar Brennu-Nials savgv</finalRubric>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <finalRubric>

                                      <finalRubric> (final rubric) contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <finalRubric>Explicit le romans de la Rose ou l'art
                                      d'amours est toute enclose.</finalRubric>
                                      <finalRubric>ok lúkv ver þar Brennu-Nials savgv</finalRubric>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element finalRubric
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.msExcerpt.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-floatingText.html b/gl/dev/ref-floatingText.html index 1e2b80f6d..042d4cdbc 100644 --- a/gl/dev/ref-floatingText.html +++ b/gl/dev/ref-floatingText.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <floatingText>

                                      <floatingText> (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      A floating text has the same content as any other text and may thus be interrupted by another floating text, or contain a group of tesselated texts.

                                      Example
                                      <body>
                                       <div type="scene">
                                        <sp>
                                         <p>Hush, the players begin...</p>
                                        </sp>
                                        <floatingText type="pwp">
                                         <body>
                                          <div type="act">
                                           <sp>
                                            <l>In Athens our tale takes place [...]</l>
                                           </sp>
                                      <!-- ... rest of nested act here -->
                                          </div>
                                         </body>
                                        </floatingText>
                                        <sp>
                                         <p>Now that the play is finished ...</p>
                                        </sp>
                                       </div>
                                      </body>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="front"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate>
                                         <elementRef key="body"/>
                                         <elementRef key="group"/>
                                        </alternate>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="back"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <floatingText>

                                      <floatingText> (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      A floating text has the same content as any other text and may thus be interrupted by another floating text, or contain a group of tesselated texts.

                                      Example
                                      <body>
                                       <div type="scene">
                                        <sp>
                                         <p>Hush, the players begin...</p>
                                        </sp>
                                        <floatingText type="pwp">
                                         <body>
                                          <div type="act">
                                           <sp>
                                            <l>In Athens our tale takes place [...]</l>
                                           </sp>
                                      <!-- ... rest of nested act here -->
                                          </div>
                                         </body>
                                        </floatingText>
                                        <sp>
                                         <p>Now that the play is finished ...</p>
                                        </sp>
                                       </div>
                                      </body>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="front"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate>
                                         <elementRef key="body"/>
                                         <elementRef key="group"/>
                                        </alternate>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="back"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element floatingText
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                             tei_model.global*,
                                             ( tei_back, tei_model.global* )?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-floruit.html b/gl/dev/ref-floruit.html index 1df0e252a..98984f503 100644 --- a/gl/dev/ref-floruit.html +++ b/gl/dev/ref-floruit.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <floruit>

                                      <floruit> (floruit) contains information about a person's period of activity. [13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <floruit notBefore="1066notAfter="1100"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <floruit>

                                      <floruit> (floruit) contains information about a person's period of activity. [13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <floruit notBefore="1066notAfter="1100"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element floruit
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.dimensions.attributes,
                                          tei_att.editLike.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-foliation.html b/gl/dev/ref-foliation.html index 2f1ff2b7c..a32df2cd1 100644 --- a/gl/dev/ref-foliation.html +++ b/gl/dev/ref-foliation.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <foliation>

                                      <foliation> (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object. [10.7.1.4. Foliation]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <foliation>Contemporary foliation in red
                                      roman numerals in the centre
                                      of the outer margin.</foliation>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element foliation { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <foliation>

                                      <foliation> (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object. [10.7.1.4. Foliation]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <foliation>Contemporary foliation in red
                                      roman numerals in the centre
                                      of the outer margin.</foliation>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element foliation { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-foreign.html b/gl/dev/ref-foreign.html index 93ffe778e..d7319c8be 100644 --- a/gl/dev/ref-foreign.html +++ b/gl/dev/ref-foreign.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <foreign>

                                      <foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

                                      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.

                                      Example
                                      This is
                                      heathen Greek to you still? Your <foreign xml:lang="la">lapis
                                      philosophicus</foreign>?
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element foreign { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <foreign>

                                      <foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

                                      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.

                                      Example
                                      This is
                                      heathen Greek to you still? Your <foreign xml:lang="la">lapis
                                      philosophicus</foreign>?
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element foreign { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-forename.html b/gl/dev/ref-forename.html index b31a1a97a..d01ab5c95 100644 --- a/gl/dev/ref-forename.html +++ b/gl/dev/ref-forename.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <forename>

                                      <forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <roleName>Ex-President</roleName>
                                       <forename>George</forename>
                                       <surname>Bush</surname>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <forename>

                                      <forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <roleName>Ex-President</roleName>
                                       <forename>George</forename>
                                       <surname>Bush</surname>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element forename
                                       {
                                          tei_att.global.attributes,
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-form.html b/gl/dev/ref-form.html index 54a001029..2e5d4fd1b 100644 --- a/gl/dev/ref-form.html +++ b/gl/dev/ref-form.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <form>

                                      <form> (form information group) groups all the information on the written and spoken forms of one headword. [9.3.1. Information on Written and Spoken Forms]
                                      Moduledictionaries
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
                                      typeclassifies form as simple, compound, etc.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      simple
                                      single free lexical item
                                      lemma
                                      the headword itself
                                      variant
                                      a variant form
                                      compound
                                      word formed from simple lexical items
                                      derivative
                                      word derived from headword
                                      inflected
                                      word in other than usual dictionary form
                                      phrase
                                      multiple-word lexical item
                                      Member of
                                      Contained by
                                      core: cit
                                      dictionaries: form
                                      namesdates: nym
                                      May contain
                                      Example
                                      <form>
                                       <orth>zaptié</orth>
                                       <orth>zaptyé</orth>
                                      </form>

                                      (from TLFi)

                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.formPart"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <form>

                                      <form> (form information group) groups all the information on the written and spoken forms of one headword. [9.3.1. Information on Written and Spoken Forms]
                                      Moduledictionaries
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.lexicographic.normalized (@norm, @orig)) att.typed (type, @subtype)
                                      typeclassifies form as simple, compound, etc.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      simple
                                      single free lexical item
                                      lemma
                                      the headword itself
                                      variant
                                      a variant form
                                      compound
                                      word formed from simple lexical items
                                      derivative
                                      word derived from headword
                                      inflected
                                      word in other than usual dictionary form
                                      phrase
                                      multiple-word lexical item
                                      Member of
                                      Contained by
                                      core: cit
                                      dictionaries: form
                                      namesdates: nym
                                      May contain
                                      Example
                                      <form>
                                       <orth>zaptié</orth>
                                       <orth>zaptyé</orth>
                                      </form>

                                      (from TLFi)

                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.formPart"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element form
                                       {
                                          tei_att.global.attributes,
                                      @@ -46,4 +46,4 @@
                                           | tei_model.formPart
                                           | tei_model.global
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-front.html b/gl/dev/ref-front.html index bfafda224..158cbfc4c 100644 --- a/gl/dev/ref-front.html +++ b/gl/dev/ref-front.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <front>

                                      <front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Contained by
                                      textstructure: floatingText text
                                      transcr: facsimile
                                      May contain
                                      Note

                                      Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the front and back elements are identical.

                                      Example
                                      <front>
                                       <epigraph>
                                        <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla
                                           pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί
                                             θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>
                                        </quote>
                                       </epigraph>
                                       <div type="dedication">
                                        <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
                                        </p>
                                       </div>
                                      </front>
                                      Example
                                      <front>
                                       <div type="dedication">
                                        <p>To our three selves</p>
                                       </div>
                                       <div type="preface">
                                        <head>Author's Note</head>
                                        <p>All the characters in this book are purely imaginary, and if the
                                           author has used names that may suggest a reference to living persons
                                           she has done so inadvertently. ...</p>
                                       </div>
                                      </front>
                                      Example
                                      <front>
                                       <div type="abstract">
                                        <div>
                                         <head> BACKGROUND:</head>
                                         <p>Food insecurity can put children at greater risk of obesity because
                                             of altered food choices and nonuniform consumption patterns.</p>
                                        </div>
                                        <div>
                                         <head> OBJECTIVE:</head>
                                         <p>We examined the association between obesity and both child-level
                                             food insecurity and personal food insecurity in US children.</p>
                                        </div>
                                        <div>
                                         <head> DESIGN:</head>
                                         <p>Data from 9,701 participants in the National Health and Nutrition
                                             Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.
                                             Child-level food insecurity was assessed with the US Department of
                                             Agriculture's Food Security Survey Module based on eight
                                             child-specific questions. Personal food insecurity was assessed with
                                             five additional questions. Obesity was defined, using physical
                                             measurements, as body mass index (calculated as kg/m2) greater than
                                             or equal to the age- and sex-specific 95th percentile of the Centers
                                             for Disease Control and Prevention growth charts. Logistic
                                             regressions adjusted for sex, race/ethnic group, poverty level, and
                                             survey year were conducted to describe associations between obesity
                                             and food insecurity.</p>
                                        </div>
                                        <div>
                                         <head> RESULTS:</head>
                                         <p>Obesity was significantly associated with personal food insecurity
                                             for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to
                                             2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%
                                             CI 0.51 to 1.51). Child-level food insecurity was not associated
                                             with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>
                                        </div>
                                        <div>
                                         <head> CONCLUSIONS:</head>
                                         <p>Personal food insecurity is associated with an increased risk of
                                             obesity only in children aged 6 to 11 years. Personal
                                             food-insecurity measures may give different results than aggregate
                                             food-insecurity measures in children.</p>
                                        </div>
                                       </div>
                                      </front>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.frontPart"/>
                                         <classRef key="model.pLike"/>
                                         <classRef key="model.pLike.front"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <sequence minOccurs="0">
                                         <alternate>
                                          <sequence>
                                           <classRef key="model.div1Like"/>
                                           <alternate minOccurs="0"
                                            maxOccurs="unbounded">

                                            <classRef key="model.div1Like"/>
                                            <classRef key="model.frontPart"/>
                                            <classRef key="model.global"/>
                                           </alternate>
                                          </sequence>
                                          <sequence>
                                           <classRef key="model.divLike"/>
                                           <alternate minOccurs="0"
                                            maxOccurs="unbounded">

                                            <classRef key="model.divLike"/>
                                            <classRef key="model.frontPart"/>
                                            <classRef key="model.global"/>
                                           </alternate>
                                          </sequence>
                                         </alternate>
                                         <sequence minOccurs="0">
                                          <classRef key="model.divBottom"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.divBottom"/>
                                           <classRef key="model.global"/>
                                          </alternate>
                                         </sequence>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <front>

                                      <front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Contained by
                                      textstructure: floatingText text
                                      transcr: facsimile
                                      May contain
                                      Note

                                      Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the front and back elements are identical.

                                      Example
                                      <front>
                                       <epigraph>
                                        <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla
                                           pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί
                                             θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>
                                        </quote>
                                       </epigraph>
                                       <div type="dedication">
                                        <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
                                        </p>
                                       </div>
                                      </front>
                                      Example
                                      <front>
                                       <div type="dedication">
                                        <p>To our three selves</p>
                                       </div>
                                       <div type="preface">
                                        <head>Author's Note</head>
                                        <p>All the characters in this book are purely imaginary, and if the
                                           author has used names that may suggest a reference to living persons
                                           she has done so inadvertently. ...</p>
                                       </div>
                                      </front>
                                      Example
                                      <front>
                                       <div type="abstract">
                                        <div>
                                         <head> BACKGROUND:</head>
                                         <p>Food insecurity can put children at greater risk of obesity because
                                             of altered food choices and nonuniform consumption patterns.</p>
                                        </div>
                                        <div>
                                         <head> OBJECTIVE:</head>
                                         <p>We examined the association between obesity and both child-level
                                             food insecurity and personal food insecurity in US children.</p>
                                        </div>
                                        <div>
                                         <head> DESIGN:</head>
                                         <p>Data from 9,701 participants in the National Health and Nutrition
                                             Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.
                                             Child-level food insecurity was assessed with the US Department of
                                             Agriculture's Food Security Survey Module based on eight
                                             child-specific questions. Personal food insecurity was assessed with
                                             five additional questions. Obesity was defined, using physical
                                             measurements, as body mass index (calculated as kg/m2) greater than
                                             or equal to the age- and sex-specific 95th percentile of the Centers
                                             for Disease Control and Prevention growth charts. Logistic
                                             regressions adjusted for sex, race/ethnic group, poverty level, and
                                             survey year were conducted to describe associations between obesity
                                             and food insecurity.</p>
                                        </div>
                                        <div>
                                         <head> RESULTS:</head>
                                         <p>Obesity was significantly associated with personal food insecurity
                                             for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to
                                             2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%
                                             CI 0.51 to 1.51). Child-level food insecurity was not associated
                                             with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>
                                        </div>
                                        <div>
                                         <head> CONCLUSIONS:</head>
                                         <p>Personal food insecurity is associated with an increased risk of
                                             obesity only in children aged 6 to 11 years. Personal
                                             food-insecurity measures may give different results than aggregate
                                             food-insecurity measures in children.</p>
                                        </div>
                                       </div>
                                      </front>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.frontPart"/>
                                         <classRef key="model.pLike"/>
                                         <classRef key="model.pLike.front"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <sequence minOccurs="0">
                                         <alternate>
                                          <sequence>
                                           <classRef key="model.div1Like"/>
                                           <alternate minOccurs="0"
                                            maxOccurs="unbounded">

                                            <classRef key="model.div1Like"/>
                                            <classRef key="model.frontPart"/>
                                            <classRef key="model.global"/>
                                           </alternate>
                                          </sequence>
                                          <sequence>
                                           <classRef key="model.divLike"/>
                                           <alternate minOccurs="0"
                                            maxOccurs="unbounded">

                                            <classRef key="model.divLike"/>
                                            <classRef key="model.frontPart"/>
                                            <classRef key="model.global"/>
                                           </alternate>
                                          </sequence>
                                         </alternate>
                                         <sequence minOccurs="0">
                                          <classRef key="model.divBottom"/>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.divBottom"/>
                                           <classRef key="model.global"/>
                                          </alternate>
                                         </sequence>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element front
                                       {
                                          tei_att.global.attributes,
                                      @@ -47,4 +47,4 @@
                                                ( tei_model.divBottom, ( tei_model.divBottom | tei_model.global )* )?
                                             )?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-funder.html b/gl/dev/ref-funder.html index cce1f5be6..4e27556ee 100644 --- a/gl/dev/ref-funder.html +++ b/gl/dev/ref-funder.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <funder>

                                      <funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      msdescription: msItem
                                      May contain
                                      Note

                                      Funders provide financial support for a project; they are distinct from sponsors (see element sponsor), who provide intellectual support and authority.

                                      Example
                                      <funder>The National Endowment for the Humanities, an independent federal agency</funder>
                                      <funder>Directorate General XIII of the Commission of the European Communities</funder>
                                      <funder>The Andrew W. Mellon Foundation</funder>
                                      <funder>The Social Sciences and Humanities Research Council of Canada</funder>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <funder>

                                      <funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      msdescription: msItem
                                      May contain
                                      Note

                                      Funders provide financial support for a project; they are distinct from sponsors (see element sponsor), who provide intellectual support and authority.

                                      Example
                                      <funder>The National Endowment for the Humanities, an independent federal agency</funder>
                                      <funder>Directorate General XIII of the Commission of the European Communities</funder>
                                      <funder>The Andrew W. Mellon Foundation</funder>
                                      <funder>The Social Sciences and Humanities Research Council of Canada</funder>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element funder
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-fw.html b/gl/dev/ref-fw.html index a705f2771..945661247 100644 --- a/gl/dev/ref-fw.html +++ b/gl/dev/ref-fw.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <fw>

                                      <fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.written (@hand) att.typed (type, @subtype)
                                      typeclassifies the material encoded according to some useful typology.
                                      Derived fromatt.typed
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      header
                                      a running title at the top of the page
                                      footer
                                      a running title at the bottom of the page
                                      pageNum
                                      (page number) a page number or foliation symbol
                                      lineNum
                                      (line number) a line number, either of prose or poetry
                                      sig
                                      (signature) a signature or gathering symbol
                                      catch
                                      (catchword) a catch-word
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The fw element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

                                      Example
                                      <fw type="sigplace="bottom">C3</fw>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <fw>

                                      <fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.written (@hand) att.typed (type, @subtype)
                                      typeclassifies the material encoded according to some useful typology.
                                      Derived fromatt.typed
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      header
                                      a running title at the top of the page
                                      footer
                                      a running title at the bottom of the page
                                      pageNum
                                      (page number) a page number or foliation symbol
                                      lineNum
                                      (line number) a line number, either of prose or poetry
                                      sig
                                      (signature) a signature or gathering symbol
                                      catch
                                      (catchword) a catch-word
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The fw element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

                                      Example
                                      <fw type="sigplace="bottom">C3</fw>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element fw
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.written.attributes,
                                          attribute type { teidata.enumerated }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-g.html b/gl/dev/ref-g.html index f40845af8..12e37c9fc 100644 --- a/gl/dev/ref-g.html +++ b/gl/dev/ref-g.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <g>

                                      <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      refpoints to a description of the character or glyph intended.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Member of
                                      Contained by
                                      May containCharacter data only
                                      Note

                                      The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

                                      Example
                                      <g ref="#ctlig">ct</g>
                                      This example points to a glyph element with the identifier ctlig like the following:
                                      <glyph xml:id="ctlig">
                                      <!-- here we describe the particular ct-ligature intended -->
                                      </glyph>
                                      Example
                                      <g ref="#per-glyph">per</g>
                                      The medieval brevigraph per could similarly be considered as an individual glyph, defined in a glyph element with the identifier per-glyph as follows:
                                      <glyph xml:id="per-glyph">
                                      <!-- ... -->
                                      </glyph>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <g>

                                      <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      refpoints to a description of the character or glyph intended.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Member of
                                      Contained by
                                      May containCharacter data only
                                      Note

                                      The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

                                      Example
                                      <g ref="#ctlig">ct</g>
                                      This example points to a glyph element with the identifier ctlig like the following:
                                      <glyph xml:id="ctlig">
                                      <!-- here we describe the particular ct-ligature intended -->
                                      </glyph>
                                      Example
                                      <g ref="#per-glyph">per</g>
                                      The medieval brevigraph per could similarly be considered as an individual glyph, defined in a glyph element with the identifier per-glyph as follows:
                                      <glyph xml:id="per-glyph">
                                      <!-- ... -->
                                      </glyph>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                       element g
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          attribute ref { teidata.pointer }?,
                                          text
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-gap.html b/gl/dev/ref-gap.html index c67968f0a..9714a881a 100644 --- a/gl/dev/ref-gap.html +++ b/gl/dev/ref-gap.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <gap>

                                      <gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.timed (@start, @end) att.duration.iso (@dur-iso)
                                      reason
                                      Status Required
                                      Legal values are:
                                      lost
                                      Text completely lost from the surface and unrecoverable
                                      illegible
                                      Traces of text remains on the surface but cannot be interpreted
                                      omitted
                                      Text erroneously omitted from the surface by the scribe/cutter
                                      ellipsis
                                      Text omitted from the edition by the editor, for whatever reason (brevity, context, language, etc.)
                                      undefined
                                      Text omitted from the edition by the editor without specification of current state of this text (NB this should not be possible with valid Leiden Conventions)
                                      agent(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      rubbing
                                      (rubbing) damage results from rubbing of the leaf edges
                                      mildew
                                      (mildew) damage results from mildew on the leaf surface
                                      smoke
                                      (smoke) damage results from smoke
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Note

                                      The gap, unclear, and del core tag elements may be closely allied in use with the damage and supplied elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      The gap tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as del in the case of deliberate deletion.

                                      Example
                                      <gap quantity="4unit="chars"
                                       reason="illegible"/>
                                      Example
                                      <gap quantity="1unit="essay"
                                       reason="sampling"/>
                                      Example
                                      <del>
                                       <gap atLeast="4atMost="8unit="chars"
                                        reason="illegible"/>

                                      </del>
                                      Example
                                      <gap extent="several linesreason="lost"/>
                                      Schematron

                                      <sch:rule context="tei:gap">
                                      <sch:report test="@quantity and @extent">gap may have @quantity (a figure) or @extent (a descriptive text value) but not both</sch:report>
                                      <sch:report test="@quantity and not(@unit)">If gap has @quantity then @unit is required</sch:report>
                                      <sch:report test="not(@reason='ellipsis') and ancestor::tei:supplied[not(@reason='undefined')]">gap may not appear within supplied text</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <gap>

                                      <gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.timed (@start, @end) att.duration.iso (@dur-iso)
                                      reason
                                      Status Required
                                      Legal values are:
                                      lost
                                      Text completely lost from the surface and unrecoverable
                                      illegible
                                      Traces of text remains on the surface but cannot be interpreted
                                      omitted
                                      Text erroneously omitted from the surface by the scribe/cutter
                                      ellipsis
                                      Text omitted from the edition by the editor, for whatever reason (brevity, context, language, etc.)
                                      undefined
                                      Text omitted from the edition by the editor without specification of current state of this text (NB this should not be possible with valid Leiden Conventions)
                                      agent(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      rubbing
                                      (rubbing) damage results from rubbing of the leaf edges
                                      mildew
                                      (mildew) damage results from mildew on the leaf surface
                                      smoke
                                      (smoke) damage results from smoke
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Note

                                      The gap, unclear, and del core tag elements may be closely allied in use with the damage and supplied elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      The gap tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as del in the case of deliberate deletion.

                                      Example
                                      <gap quantity="4unit="chars"
                                       reason="illegible"/>
                                      Example
                                      <gap quantity="1unit="essay"
                                       reason="sampling"/>
                                      Example
                                      <del>
                                       <gap atLeast="4atMost="8unit="chars"
                                        reason="illegible"/>

                                      </del>
                                      Example
                                      <gap extent="several linesreason="lost"/>
                                      Schematron

                                      <sch:rule context="tei:gap">
                                      <sch:report test="@quantity and @extent">gap may have @quantity (a figure) or @extent (a descriptive text value) but not both</sch:report>
                                      <sch:report test="@quantity and not(@unit)">If gap has @quantity then @unit is required</sch:report>
                                      <sch:report test="not(@reason='ellipsis') and ancestor::tei:supplied[not(@reason='undefined')]">gap may not appear within supplied text</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element gap
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                          },
                                          attribute agent { teidata.enumerated }?,
                                          ( tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-gb.html b/gl/dev/ref-gb.html index d1e9f8012..d80a4cf1a 100644 --- a/gl/dev/ref-gb.html +++ b/gl/dev/ref-gb.html @@ -22,7 +22,7 @@ }); });

                                      <gb>

                                      <gb> (gathering beginning) marks the beginning of a new gathering or quire in a transcribed codex. [3.11.3. Milestone -Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.spanning (@spanTo) att.breaking (@break) att.edition (@ed, @edRef)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      By convention, gb elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation.

                                      The type attribute may be used to further characterize the gathering in any respect.

                                      Example
                                      <gb n="iii"/>
                                      <pb n="2r"/>
                                      <!-- material from page 2 recto of gathering iii here -->
                                      <pb n="2v"/>
                                      <!-- material from page 2 verso of gathering iii here -->
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.spanning (@spanTo) att.breaking (@break) att.edition (@ed, @edRef)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      By convention, gb elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation.

                                      The type attribute may be used to further characterize the gathering in any respect.

                                      Example
                                      <gb n="iii"/>
                                      <pb n="2r"/>
                                      <!-- material from page 2 recto of gathering iii here -->
                                      <pb n="2v"/>
                                      <!-- material from page 2 verso of gathering iii here -->
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element gb
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.breaking.attributes,
                                          tei_att.edition.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-gen.html b/gl/dev/ref-gen.html index e607caf3a..b1810789b 100644 --- a/gl/dev/ref-gen.html +++ b/gl/dev/ref-gen.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <gen>

                                      <gen> (gender) identifies the morphological gender of a lexical item, as given in the dictionary. [9.3.1. Information on Written and Spoken Forms]
                                      Moduledictionaries
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.lexicographic.normalized (@norm, @orig))
                                      Member of
                                      Contained by
                                      dictionaries: form
                                      May contain
                                      Note

                                      May contain character data and phrase-level elements. Typical content will be masculine, feminine, neuter etc.

                                      This element is synonymous with <gram type="gender">.

                                      Example
                                      <entry>
                                       <form>
                                        <orth>pamplemousse</orth>
                                       </form>
                                       <gramGrp>
                                        <pos>noun</pos>
                                        <gen>masculine</gen>
                                       </gramGrp>
                                      </entry>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <gen>

                                      <gen> (gender) identifies the morphological gender of a lexical item, as given in the dictionary. [9.3.1. Information on Written and Spoken Forms]
                                      Moduledictionaries
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.lexicographic.normalized (@norm, @orig))
                                      Member of
                                      Contained by
                                      dictionaries: form
                                      May contain
                                      Note

                                      May contain character data and phrase-level elements. Typical content will be masculine, feminine, neuter etc.

                                      This element is synonymous with <gram type="gender">.

                                      Example
                                      <entry>
                                       <form>
                                        <orth>pamplemousse</orth>
                                       </form>
                                       <gramGrp>
                                        <pos>noun</pos>
                                        <gen>masculine</gen>
                                       </gramGrp>
                                      </entry>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element gen
                                       {
                                          tei_att.global.attributes,
                                          tei_att.lexicographic.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-genName.html b/gl/dev/ref-genName.html index 8ca569ccd..4481bf7b1 100644 --- a/gl/dev/ref-genName.html +++ b/gl/dev/ref-genName.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <genName>

                                      <genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <forename>Charles</forename>
                                       <genName>II</genName>
                                      </persName>
                                      Example
                                      <persName>
                                       <surname>Pitt</surname>
                                       <genName>the Younger</genName>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <genName>

                                      <genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <forename>Charles</forename>
                                       <genName>II</genName>
                                      </persName>
                                      Example
                                      <persName>
                                       <surname>Pitt</surname>
                                       <genName>the Younger</genName>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element genName
                                       {
                                          tei_att.global.attributes,
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-gender.html b/gl/dev/ref-gender.html index 7019ec752..e07dcbe3a 100644 --- a/gl/dev/ref-gender.html +++ b/gl/dev/ref-gender.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <gender>

                                      <gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      valuesupplies a coded value for gender identity
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, or they may refer to an external standard.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

                                      Example
                                      <gender value="W">woman</gender>
                                      Example
                                      <gender value="NB">non-binary</gender>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <gender>

                                      <gender> (gender) specifies the gender identity of a person, persona, or character. [13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      valuesupplies a coded value for gender identity
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, or they may refer to an external standard.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

                                      Example
                                      <gender value="W">woman</gender>
                                      Example
                                      <gender value="NB">non-binary</gender>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element gender
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.typed.attributes,
                                          attribute value { list { teidata.gender+ } }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-geo.html b/gl/dev/ref-geo.html index 8af89f6ef..49ce0dddd 100644 --- a/gl/dev/ref-geo.html +++ b/gl/dev/ref-geo.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <geo>

                                      <geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      May containCharacter data only
                                      Note

                                      Uses of geo can be associated with a coordinate system, defined by a geoDecl element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each geo element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

                                      Example
                                      <geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl>
                                      <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl>
                                      <!-- ... -->
                                      <location>
                                       <desc>A tombstone plus six lines of
                                         Anglo-Saxon text, built into the west tower (on the south side
                                         of the archway, at 8 ft. above the ground) of the
                                         Church of St. Mary-le-Wigford in Lincoln.</desc>
                                       <geo decls="#WGS">53.226658 -0.541254</geo>
                                       <geo decls="#OS">SK 97481 70947</geo>
                                      </location>
                                      Example
                                      <geo>41.687142 -74.870109</geo>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      -element geo { tei_att.global.attributes, tei_att.declaring.attributes, text }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <geo>

                                      <geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      May containCharacter data only
                                      Note

                                      Uses of geo can be associated with a coordinate system, defined by a geoDecl element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each geo element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

                                      Example
                                      <geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl>
                                      <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl>
                                      <!-- ... -->
                                      <location>
                                       <desc>A tombstone plus six lines of
                                         Anglo-Saxon text, built into the west tower (on the south side
                                         of the archway, at 8 ft. above the ground) of the
                                         Church of St. Mary-le-Wigford in Lincoln.</desc>
                                       <geo decls="#WGS">53.226658 -0.541254</geo>
                                       <geo decls="#OS">SK 97481 70947</geo>
                                      </location>
                                      Example
                                      <geo>41.687142 -74.870109</geo>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      +element geo { tei_att.global.attributes, tei_att.declaring.attributes, text }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-geoDecl.html b/gl/dev/ref-geoDecl.html index d37628e28..d59b12d19 100644 --- a/gl/dev/ref-geoDecl.html +++ b/gl/dev/ref-geoDecl.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <geoDecl>

                                      <geoDecl> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the geo element elsewhere within the document. [2.3.8. The Geographic Coordinates Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      datumsupplies a commonly used code name for the datum employed.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      WGS84
                                      (World Geodetic System) a pair of numbers to be interpreted as latitude followed by longitude according to the World Geodetic System. [Default]
                                      MGRS
                                      (Military Grid Reference System) the values supplied are geospatial entity object codes, based on
                                      OSGB36
                                      (ordnance survey great britain) the value supplied is to be interpreted as a British National Grid Reference.
                                      ED50
                                      (European Datum coordinate system) the value supplied is to be interpreted as latitude followed by longitude according to the European Datum coordinate system.
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      Example
                                      <geoDecl datum="OSGB36"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <geoDecl>

                                      <geoDecl> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the geo element elsewhere within the document. [2.3.8. The Geographic Coordinates Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      datumsupplies a commonly used code name for the datum employed.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      WGS84
                                      (World Geodetic System) a pair of numbers to be interpreted as latitude followed by longitude according to the World Geodetic System. [Default]
                                      MGRS
                                      (Military Grid Reference System) the values supplied are geospatial entity object codes, based on
                                      OSGB36
                                      (ordnance survey great britain) the value supplied is to be interpreted as a British National Grid Reference.
                                      ED50
                                      (European Datum coordinate system) the value supplied is to be interpreted as latitude followed by longitude according to the European Datum coordinate system.
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      Example
                                      <geoDecl datum="OSGB36"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element geoDecl
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                             "WGS84" | "MGRS" | "OSGB36" | "ED50" | teidata.enumerated
                                          }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-geogFeat.html b/gl/dev/ref-geogFeat.html index 23f03925d..9ea3bd72b 100644 --- a/gl/dev/ref-geogFeat.html +++ b/gl/dev/ref-geogFeat.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <geogFeat>

                                      <geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <geogName> The <geogFeat>vale</geogFeat> of White Horse</geogName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <geogFeat>

                                      <geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <geogName> The <geogFeat>vale</geogFeat> of White Horse</geogName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element geogFeat
                                       {
                                          tei_att.datable.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-geogName.html b/gl/dev/ref-geogName.html index 402ad8ea3..ce50026c5 100644 --- a/gl/dev/ref-geogName.html +++ b/gl/dev/ref-geogName.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <geogName>

                                      <geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <geogName>
                                       <geogFeat>Mount</geogFeat>
                                       <name>Sinai</name>
                                      </geogName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <geogName>

                                      <geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <geogName>
                                       <geogFeat>Mount</geogFeat>
                                       <name>Sinai</name>
                                      </geogName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element geogName
                                       {
                                          tei_att.datable.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.naming.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-gloss.html b/gl/dev/ref-gloss.html index 9b80e53db..69aca26be 100644 --- a/gl/dev/ref-gloss.html +++ b/gl/dev/ref-gloss.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <gloss>

                                      <gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 22.4.1. Description of Components]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype) att.pointing (@targetLang, @target, @evaluate) att.cReferencing (@cRef)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The target and cRef attributes are mutually exclusive.

                                      Example
                                      We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as
                                      <gloss target="#tdpv">the relationship, expressed
                                      through discourse structure, between the implied author or some other addresser, and the
                                      fiction.</gloss>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <gloss>

                                      <gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 22.4.1. Description of Components]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype) att.pointing (@targetLang, @target, @evaluate) att.cReferencing (@cRef)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The target and cRef attributes are mutually exclusive.

                                      Example
                                      We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as
                                      <gloss target="#tdpv">the relationship, expressed
                                      through discourse structure, between the implied author or some other addresser, and the
                                      fiction.</gloss>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element gloss
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.pointing.attributes,
                                          tei_att.cReferencing.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-glyph.html b/gl/dev/ref-glyph.html index 225e6a620..9f53eebb5 100644 --- a/gl/dev/ref-glyph.html +++ b/gl/dev/ref-glyph.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <glyph>

                                      <glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      gaiji: charDecl
                                      May contain
                                      Example
                                      <glyph xml:id="rstroke">
                                       <localProp name="Name"
                                        value="LATIN SMALL LETTER R WITH A FUNNY STROKE"/>

                                       <localProp name="entityvalue="rstroke"/>
                                       <figure>
                                        <graphic url="glyph-rstroke.png"/>
                                       </figure>
                                      </glyph>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="unicodeProp"/>
                                        <elementRef key="unihanProp"/>
                                        <elementRef key="localProp"/>
                                        <elementRef key="mapping"/>
                                        <elementRef key="figure"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.noteLike"/>
                                        <classRef key="model.descLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <glyph>

                                      <glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      gaiji: charDecl
                                      May contain
                                      Example
                                      <glyph xml:id="rstroke">
                                       <localProp name="Name"
                                        value="LATIN SMALL LETTER R WITH A FUNNY STROKE"/>

                                       <localProp name="entityvalue="rstroke"/>
                                       <figure>
                                        <graphic url="glyph-rstroke.png"/>
                                       </figure>
                                      </glyph>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="unicodeProp"/>
                                        <elementRef key="unihanProp"/>
                                        <elementRef key="localProp"/>
                                        <elementRef key="mapping"/>
                                        <elementRef key="figure"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.noteLike"/>
                                        <classRef key="model.descLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element glyph
                                       {
                                          tei_att.global.attributes,
                                      @@ -35,4 +35,4 @@
                                           | tei_model.noteLike
                                           | tei_model.descLike
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-graphic.html b/gl/dev/ref-graphic.html index 2005b99ec..dcd85ffb0 100644 --- a/gl/dev/ref-graphic.html +++ b/gl/dev/ref-graphic.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <graphic>

                                      <graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url) att.declaring (@decls) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      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 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.

                                      Example
                                      <figure>
                                       <graphic url="fig1.png"/>
                                       <head>Figure One: The View from the Bridge</head>
                                       <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
                                         series of buoys strung out between them.</figDesc>
                                      </figure>
                                      Example
                                      <facsimile>
                                       <surfaceGrp n="leaf1">
                                        <surface>
                                         <graphic url="page1.png"/>
                                        </surface>
                                        <surface>
                                         <graphic url="page2-highRes.png"/>
                                         <graphic url="page2-lowRes.png"/>
                                        </surface>
                                       </surfaceGrp>
                                      </facsimile>
                                      Example
                                      <facsimile>
                                       <surfaceGrp n="leaf1xml:id="spi001">
                                        <surface xml:id="spi001r">
                                         <graphic type="normal"
                                          subtype="thumbnailurl="spi/thumb/001r.jpg"/>

                                         <graphic type="normalsubtype="low-res"
                                          url="spi/normal/lowRes/001r.jpg"/>

                                         <graphic type="normal"
                                          subtype="high-resurl="spi/normal/highRes/001r.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="low-resurl="spi/contrast/lowRes/001r.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="high-resurl="spi/contrast/highRes/001r.jpg"/>

                                        </surface>
                                        <surface xml:id="spi001v">
                                         <graphic type="normal"
                                          subtype="thumbnailurl="spi/thumb/001v.jpg"/>

                                         <graphic type="normalsubtype="low-res"
                                          url="spi/normal/lowRes/001v.jpg"/>

                                         <graphic type="normal"
                                          subtype="high-resurl="spi/normal/highRes/001v.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="low-resurl="spi/contrast/lowRes/001v.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="high-resurl="spi/contrast/highRes/001v.jpg"/>

                                         <zone xml:id="spi001v_detail01">
                                          <graphic type="normal"
                                           subtype="thumbnailurl="spi/thumb/001v-detail01.jpg"/>

                                          <graphic type="normal"
                                           subtype="low-res"
                                           url="spi/normal/lowRes/001v-detail01.jpg"/>

                                          <graphic type="normal"
                                           subtype="high-res"
                                           url="spi/normal/highRes/001v-detail01.jpg"/>

                                          <graphic type="high-contrast"
                                           subtype="low-res"
                                           url="spi/contrast/lowRes/001v-detail01.jpg"/>

                                          <graphic type="high-contrast"
                                           subtype="high-res"
                                           url="spi/contrast/highRes/001v-detail01.jpg"/>

                                         </zone>
                                        </surface>
                                       </surfaceGrp>
                                      </facsimile>
                                      Content model
                                      <content>
                                       <classRef key="model.descLike"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <graphic>

                                      <graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url) att.declaring (@decls) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      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 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.

                                      Example
                                      <figure>
                                       <graphic url="fig1.png"/>
                                       <head>Figure One: The View from the Bridge</head>
                                       <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
                                         series of buoys strung out between them.</figDesc>
                                      </figure>
                                      Example
                                      <facsimile>
                                       <surfaceGrp n="leaf1">
                                        <surface>
                                         <graphic url="page1.png"/>
                                        </surface>
                                        <surface>
                                         <graphic url="page2-highRes.png"/>
                                         <graphic url="page2-lowRes.png"/>
                                        </surface>
                                       </surfaceGrp>
                                      </facsimile>
                                      Example
                                      <facsimile>
                                       <surfaceGrp n="leaf1xml:id="spi001">
                                        <surface xml:id="spi001r">
                                         <graphic type="normal"
                                          subtype="thumbnailurl="spi/thumb/001r.jpg"/>

                                         <graphic type="normalsubtype="low-res"
                                          url="spi/normal/lowRes/001r.jpg"/>

                                         <graphic type="normal"
                                          subtype="high-resurl="spi/normal/highRes/001r.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="low-resurl="spi/contrast/lowRes/001r.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="high-resurl="spi/contrast/highRes/001r.jpg"/>

                                        </surface>
                                        <surface xml:id="spi001v">
                                         <graphic type="normal"
                                          subtype="thumbnailurl="spi/thumb/001v.jpg"/>

                                         <graphic type="normalsubtype="low-res"
                                          url="spi/normal/lowRes/001v.jpg"/>

                                         <graphic type="normal"
                                          subtype="high-resurl="spi/normal/highRes/001v.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="low-resurl="spi/contrast/lowRes/001v.jpg"/>

                                         <graphic type="high-contrast"
                                          subtype="high-resurl="spi/contrast/highRes/001v.jpg"/>

                                         <zone xml:id="spi001v_detail01">
                                          <graphic type="normal"
                                           subtype="thumbnailurl="spi/thumb/001v-detail01.jpg"/>

                                          <graphic type="normal"
                                           subtype="low-res"
                                           url="spi/normal/lowRes/001v-detail01.jpg"/>

                                          <graphic type="normal"
                                           subtype="high-res"
                                           url="spi/normal/highRes/001v-detail01.jpg"/>

                                          <graphic type="high-contrast"
                                           subtype="low-res"
                                           url="spi/contrast/lowRes/001v-detail01.jpg"/>

                                          <graphic type="high-contrast"
                                           subtype="high-res"
                                           url="spi/contrast/highRes/001v-detail01.jpg"/>

                                         </zone>
                                        </surface>
                                       </surfaceGrp>
                                      </facsimile>
                                      Content model
                                      <content>
                                       <classRef key="model.descLike"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element graphic
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.declaring.attributes,
                                          tei_att.typed.attributes,
                                          tei_model.descLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-group.html b/gl/dev/ref-group.html index 96760c5bb..b4cde8175 100644 --- a/gl/dev/ref-group.html +++ b/gl/dev/ref-group.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <group>

                                      <group> (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 15.1. Varieties of Composite Text]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
                                      Contained by
                                      textstructure: floatingText group text
                                      May contain
                                      Example
                                      <text>
                                      <!-- Section on Alexander Pope starts -->
                                       <front>
                                      <!-- biographical notice by editor -->
                                       </front>
                                       <group>
                                        <text>
                                      <!-- first poem -->
                                        </text>
                                        <text>
                                      <!-- second poem -->
                                        </text>
                                       </group>
                                      </text>
                                      <!-- end of Pope section-->
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <sequence>
                                         <alternate>
                                          <elementRef key="text"/>
                                          <elementRef key="group"/>
                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="text"/>
                                          <elementRef key="group"/>
                                          <classRef key="model.global"/>
                                         </alternate>
                                        </sequence>
                                        <classRef key="model.divBottom"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <group>

                                      <group> (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 15.1. Varieties of Composite Text]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
                                      Contained by
                                      textstructure: floatingText group text
                                      May contain
                                      Example
                                      <text>
                                      <!-- Section on Alexander Pope starts -->
                                       <front>
                                      <!-- biographical notice by editor -->
                                       </front>
                                       <group>
                                        <text>
                                      <!-- first poem -->
                                        </text>
                                        <text>
                                      <!-- second poem -->
                                        </text>
                                       </group>
                                      </text>
                                      <!-- end of Pope section-->
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <sequence>
                                         <alternate>
                                          <elementRef key="text"/>
                                          <elementRef key="group"/>
                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="text"/>
                                          <elementRef key="group"/>
                                          <classRef key="model.global"/>
                                         </alternate>
                                        </sequence>
                                        <classRef key="model.divBottom"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element group
                                       {
                                          tei_att.global.attributes,
                                      @@ -35,4 +35,4 @@
                                             ),
                                             tei_model.divBottom*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-handDesc.html b/gl/dev/ref-handDesc.html index 6e809f2fa..d8c8d4343 100644 --- a/gl/dev/ref-handDesc.html +++ b/gl/dev/ref-handDesc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <handDesc>

                                      <handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      hands(hands) specifies the number of distinct hands identified within the manuscript
                                      Status Optional
                                      Datatype teidata.count
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      header: handNote
                                      linking: ab
                                      msdescription: summary
                                      Example
                                      <handDesc>
                                       <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote>
                                      </handDesc>
                                      Example
                                      <handDesc hands="2">
                                       <p>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.</p>
                                      </handDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="handNoteminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <handDesc>

                                      <handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      hands(hands) specifies the number of distinct hands identified within the manuscript
                                      Status Optional
                                      Datatype teidata.count
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      header: handNote
                                      linking: ab
                                      msdescription: summary
                                      Example
                                      <handDesc>
                                       <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote>
                                      </handDesc>
                                      Example
                                      <handDesc hands="2">
                                       <p>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.</p>
                                      </handDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="handNoteminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element handDesc
                                       {
                                          tei_att.global.attributes,
                                          attribute hands { teidata.count }?,
                                          ( tei_model.pLike+ | ( tei_summary?, tei_handNote+ ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-handNote.html b/gl/dev/ref-handNote.html index c98760906..ac1b88426 100644 --- a/gl/dev/ref-handNote.html +++ b/gl/dev/ref-handNote.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <handNote>

                                      <handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      Contained by
                                      msdescription: handDesc
                                      transcr: handNotes
                                      May contain
                                      Example
                                      <handNote scope="sole">
                                       <p>Written in insular
                                         phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed
                                         minuscule.</p>
                                      </handNote>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <handNote>

                                      <handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      Contained by
                                      msdescription: handDesc
                                      transcr: handNotes
                                      May contain
                                      Example
                                      <handNote scope="sole">
                                       <p>Written in insular
                                         phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed
                                         minuscule.</p>
                                      </handNote>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element handNote
                                       {
                                          tei_att.global.attributes,
                                          tei_att.handFeatures.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-handNotes.html b/gl/dev/ref-handNotes.html index 2b1681b33..7c340d4de 100644 --- a/gl/dev/ref-handNotes.html +++ b/gl/dev/ref-handNotes.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <handNotes>

                                      <handNotes> contains one or more handNote elements documenting the different hands identified within the source texts. [11.3.2.1. Document Hands]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      header: handNote
                                      Example
                                      <handNotes>
                                       <handNote xml:id="H1script="copperplate"
                                        medium="brown-ink">
                                      Carefully written with regular descenders</handNote>
                                       <handNote xml:id="H2script="print"
                                        medium="pencil">
                                      Unschooled scrawl</handNote>
                                      </handNotes>
                                      Content model
                                      <content>
                                       <elementRef key="handNoteminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      -element handNotes { tei_att.global.attributes, tei_handNote+ }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <handNotes>

                                      <handNotes> contains one or more handNote elements documenting the different hands identified within the source texts. [11.3.2.1. Document Hands]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      header: handNote
                                      Example
                                      <handNotes>
                                       <handNote xml:id="H1script="copperplate"
                                        medium="brown-ink">
                                      Carefully written with regular descenders</handNote>
                                       <handNote xml:id="H2script="print"
                                        medium="pencil">
                                      Unschooled scrawl</handNote>
                                      </handNotes>
                                      Content model
                                      <content>
                                       <elementRef key="handNoteminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +element handNotes { tei_att.global.attributes, tei_handNote+ }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-handShift.html b/gl/dev/ref-handShift.html index 4f41c642b..48011dd7c 100644 --- a/gl/dev/ref-handShift.html +++ b/gl/dev/ref-handShift.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <handShift>

                                      <handShift> (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. Document Hands]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      newindicates a handNote element describing the hand concerned.
                                      Status Recommended
                                      Datatype teidata.pointer
                                      Note

                                      This attribute serves the same function as the hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.

                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      The handShift element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

                                      Example
                                      <l>When wolde the cat dwelle in his ynne</l>
                                      <handShift medium="greenish-ink"/>
                                      <l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <handShift>

                                      <handShift> (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. Document Hands]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      newindicates a handNote element describing the hand concerned.
                                      Status Recommended
                                      Datatype teidata.pointer
                                      Note

                                      This attribute serves the same function as the hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.

                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      The handShift element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

                                      Example
                                      <l>When wolde the cat dwelle in his ynne</l>
                                      <handShift medium="greenish-ink"/>
                                      <l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element handShift
                                       {
                                          tei_att.global.attributes,
                                          tei_att.handFeatures.attributes,
                                          attribute new { teidata.pointer }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-head.html b/gl/dev/ref-head.html index eb7f1522f..001838b46 100644 --- a/gl/dev/ref-head.html +++ b/gl/dev/ref-head.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -
                                      <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The head element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a head element based on its structural position. A head occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

                                      Example

                                      The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:

                                      <div1 n="Itype="book">
                                       <head>In the name of Christ here begins the first book of the ecclesiastical history of
                                         Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
                                       <div2 type="section">
                                        <head>In the name of Christ here begins Book I of the history.</head>
                                        <p>Proposing as I do ...</p>
                                        <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
                                           years passed.</p>
                                        <trailer>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.</trailer>
                                       </div2>
                                      </div1>
                                      Example

                                      When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.

                                      <div type="subsection">
                                       <head place="margin">Secunda conclusio</head>
                                       <p>
                                        <lb n="1251"/>
                                        <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
                                        </hi>
                                        <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
                                         [...]
                                       </p>
                                      </div>
                                      Example

                                      The head element is also used to mark headings of other units, such as lists:

                                      With a few exceptions, connectives are equally
                                      useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
                                       <head>Connectives</head>
                                       <item>above</item>
                                       <item>accordingly</item>
                                       <item>across from</item>
                                       <item>adjacent to</item>
                                       <item>again</item>
                                       <item>
                                      <!-- ... -->
                                       </item>
                                      </list>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <elementRef key="lg"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.lLike"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    
                                      <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The head element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a head element based on its structural position. A head occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

                                      Example

                                      The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:

                                      <div1 n="Itype="book">
                                       <head>In the name of Christ here begins the first book of the ecclesiastical history of
                                         Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
                                       <div2 type="section">
                                        <head>In the name of Christ here begins Book I of the history.</head>
                                        <p>Proposing as I do ...</p>
                                        <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
                                           years passed.</p>
                                        <trailer>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.</trailer>
                                       </div2>
                                      </div1>
                                      Example

                                      When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.

                                      <div type="subsection">
                                       <head place="margin">Secunda conclusio</head>
                                       <p>
                                        <lb n="1251"/>
                                        <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
                                        </hi>
                                        <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
                                         [...]
                                       </p>
                                      </div>
                                      Example

                                      The head element is also used to mark headings of other units, such as lists:

                                      With a few exceptions, connectives are equally
                                      useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
                                       <head>Connectives</head>
                                       <item>above</item>
                                       <item>accordingly</item>
                                       <item>across from</item>
                                       <item>adjacent to</item>
                                       <item>again</item>
                                       <item>
                                      <!-- ... -->
                                       </item>
                                      </list>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <elementRef key="lg"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.lLike"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element head
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                           | tei_model.lLike
                                           | tei_model.global
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-headItem.html b/gl/dev/ref-headItem.html index cdd6e58e7..b17f0f69e 100644 --- a/gl/dev/ref-headItem.html +++ b/gl/dev/ref-headItem.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <headItem>

                                      <headItem> (heading for list items) contains the heading for the item or gloss column in a glossary list or similar structured list. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: list
                                      May contain
                                      Note

                                      The headItem element may appear only if each item in the list is preceded by a label.

                                      Example
                                      The simple, straightforward statement of an
                                      idea is preferable to the use of a worn-out expression. <list type="gloss">
                                       <headLabel rend="smallcaps">TRITE</headLabel>
                                       <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>
                                       <label>bury the hatchet</label>
                                       <item>stop fighting, make peace</item>
                                       <label>at loose ends</label>
                                       <item>disorganized</item>
                                       <label>on speaking terms</label>
                                       <item>friendly</item>
                                       <label>fair and square</label>
                                       <item>completely honest</item>
                                       <label>at death's door</label>
                                       <item>near death</item>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element headItem { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <headItem>

                                      <headItem> (heading for list items) contains the heading for the item or gloss column in a glossary list or similar structured list. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: list
                                      May contain
                                      Note

                                      The headItem element may appear only if each item in the list is preceded by a label.

                                      Example
                                      The simple, straightforward statement of an
                                      idea is preferable to the use of a worn-out expression. <list type="gloss">
                                       <headLabel rend="smallcaps">TRITE</headLabel>
                                       <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>
                                       <label>bury the hatchet</label>
                                       <item>stop fighting, make peace</item>
                                       <label>at loose ends</label>
                                       <item>disorganized</item>
                                       <label>on speaking terms</label>
                                       <item>friendly</item>
                                       <label>fair and square</label>
                                       <item>completely honest</item>
                                       <label>at death's door</label>
                                       <item>near death</item>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element headItem { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-headLabel.html b/gl/dev/ref-headLabel.html index 719fd8743..508ed79e9 100644 --- a/gl/dev/ref-headLabel.html +++ b/gl/dev/ref-headLabel.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <headLabel>

                                      <headLabel> (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: list
                                      May contain
                                      Note

                                      The headLabel element may appear only if each item in the list is preceded by a label.

                                      Example
                                      The simple, straightforward statement of an
                                      idea is preferable to the use of a worn-out expression. <list type="gloss">
                                       <headLabel rend="smallcaps">TRITE</headLabel>
                                       <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>
                                       <label>bury the hatchet</label>
                                       <item>stop fighting, make peace</item>
                                       <label>at loose ends</label>
                                       <item>disorganized</item>
                                       <label>on speaking terms</label>
                                       <item>friendly</item>
                                       <label>fair and square</label>
                                       <item>completely honest</item>
                                       <label>at death's door</label>
                                       <item>near death</item>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element headLabel { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <headLabel>

                                      <headLabel> (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: list
                                      May contain
                                      Note

                                      The headLabel element may appear only if each item in the list is preceded by a label.

                                      Example
                                      The simple, straightforward statement of an
                                      idea is preferable to the use of a worn-out expression. <list type="gloss">
                                       <headLabel rend="smallcaps">TRITE</headLabel>
                                       <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>
                                       <label>bury the hatchet</label>
                                       <item>stop fighting, make peace</item>
                                       <label>at loose ends</label>
                                       <item>disorganized</item>
                                       <label>on speaking terms</label>
                                       <item>friendly</item>
                                       <label>fair and square</label>
                                       <item>completely honest</item>
                                       <label>at death's door</label>
                                       <item>near death</item>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element headLabel { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-height.html b/gl/dev/ref-height.html index 6beecdcdc..1db541360 100644 --- a/gl/dev/ref-height.html +++ b/gl/dev/ref-height.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <height>

                                      <height> (height) contains a measurement measured along the axis at a right angle to the bottom of the object. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Example
                                      <height unit="inquantity="7"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <height>

                                      <height> (height) contains a measurement measured along the axis at a right angle to the bottom of the object. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Example
                                      <height unit="inquantity="7"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element height
                                       {
                                          tei_att.global.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-heraldry.html b/gl/dev/ref-heraldry.html index 8a8332e26..73e00bd2c 100644 --- a/gl/dev/ref-heraldry.html +++ b/gl/dev/ref-heraldry.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <heraldry>

                                      <heraldry> (heraldry) contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. [10.3.8. Heraldry]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <p>Ownership stamp (xvii cent.) on i recto with the arms
                                      <heraldry>A bull passant within a bordure bezanty,
                                         in chief a crescent for difference</heraldry> [Cole],
                                      crest, and the legend <q>Cole Deum</q>.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element heraldry { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <heraldry>

                                      <heraldry> (heraldry) contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. [10.3.8. Heraldry]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <p>Ownership stamp (xvii cent.) on i recto with the arms
                                      <heraldry>A bull passant within a bordure bezanty,
                                         in chief a crescent for difference</heraldry> [Cole],
                                      crest, and the legend <q>Cole Deum</q>.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element heraldry { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-hi.html b/gl/dev/ref-hi.html index c9ab83488..d64c16b69 100644 --- a/gl/dev/ref-hi.html +++ b/gl/dev/ref-hi.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <hi>

                                      <hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
                                      Modulecore
                                      Attributesatt.written (@hand) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
                                      rend
                                      Status Required
                                      Datatype 1–5 occurrences of teidata.word separated by whitespace
                                      Suggested values include:
                                      acute
                                      ancient acute (oxia, tonos) diacritic
                                      apex
                                      apex or long vowel mark
                                      asper
                                      ancient asper (rough breathing) diacritic
                                      circumflex
                                      ancient circumflex (perispomeni) diacritic
                                      diaeresis
                                      ancient diaeresis
                                      grave
                                      ancient grave (varia) diacritic
                                      intraline
                                      characters scored or struck through at the mid-line level
                                      inverted
                                      character(s) inverted or rotated with respect to the rest of the text
                                      italic
                                      characters italicised or slanted
                                      lenis
                                      ancient lenis (smooth breathing) diacritic
                                      ligature
                                      two (or more) letters ligatured, monogrammed, or therwise joined
                                      normal
                                      characters written in normal form (e.g. in otherwise highlighted or unusual span of text
                                      reversed
                                      characters reversed (backward-facing) with respect to the rest of the line of text
                                      sling-above
                                      characters written with or joined by "sling" above text
                                      sling-below
                                      characters written with or joined by "sling" below text
                                      small
                                      characters smaller than those around them
                                      stacked
                                      a character written directly above another character (as opposed to superscript)
                                      subscript
                                      characters written lower than the surrounding text
                                      superscript
                                      characters written higher than the surrounding text
                                      supraline
                                      characters written with a supralinear line above (e.g. for abbreviation or numerals)
                                      tall
                                      characters taller than those around, e.g. I-longa
                                      underline
                                      text written with solid line beneath
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <hi rend="gothic">And this Indenture further witnesseth</hi>
                                      that the said <hi rend="italic">Walter Shandy</hi>, merchant,
                                      in consideration of the said intended marriage ...
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <hi>

                                      <hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
                                      Modulecore
                                      Attributesatt.written (@hand) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
                                      rend
                                      Status Required
                                      Datatype 1–5 occurrences of teidata.word separated by whitespace
                                      Suggested values include:
                                      acute
                                      ancient acute (oxia, tonos) diacritic
                                      apex
                                      apex or long vowel mark
                                      asper
                                      ancient asper (rough breathing) diacritic
                                      circumflex
                                      ancient circumflex (perispomeni) diacritic
                                      diaeresis
                                      ancient diaeresis
                                      grave
                                      ancient grave (varia) diacritic
                                      intraline
                                      characters scored or struck through at the mid-line level
                                      inverted
                                      character(s) inverted or rotated with respect to the rest of the text
                                      italic
                                      characters italicised or slanted
                                      lenis
                                      ancient lenis (smooth breathing) diacritic
                                      ligature
                                      two (or more) letters ligatured, monogrammed, or therwise joined
                                      normal
                                      characters written in normal form (e.g. in otherwise highlighted or unusual span of text
                                      reversed
                                      characters reversed (backward-facing) with respect to the rest of the line of text
                                      sling-above
                                      characters written with or joined by "sling" above text
                                      sling-below
                                      characters written with or joined by "sling" below text
                                      small
                                      characters smaller than those around them
                                      stacked
                                      a character written directly above another character (as opposed to superscript)
                                      subscript
                                      characters written lower than the surrounding text
                                      superscript
                                      characters written higher than the surrounding text
                                      supraline
                                      characters written with a supralinear line above (e.g. for abbreviation or numerals)
                                      tall
                                      characters taller than those around, e.g. I-longa
                                      underline
                                      text written with solid line beneath
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <hi rend="gothic">And this Indenture further witnesseth</hi>
                                      that the said <hi rend="italic">Walter Shandy</hi>, merchant,
                                      in consideration of the said intended marriage ...
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element hi
                                       {
                                          tei_att.global.attribute.xmlid,
                                      @@ -178,4 +178,4 @@
                                             }
                                          },
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-history.html b/gl/dev/ref-history.html index 0245548fa..034b3713d 100644 --- a/gl/dev/ref-history.html +++ b/gl/dev/ref-history.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <history>

                                      <history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <history>
                                       <origin>
                                        <p>Written in Durham during the mid twelfth
                                           century.</p>
                                       </origin>
                                       <provenance>
                                        <p>Recorded in two medieval
                                           catalogues of the books belonging to Durham Priory, made in 1391 and
                                           1405.</p>
                                       </provenance>
                                       <provenance>
                                        <p>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.</p>
                                       </provenance>
                                       <acquisition>
                                        <p>Presented to Trinity College in 1738 by
                                           Thomas Gale and his son Roger.</p>
                                       </acquisition>
                                      </history>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="originminOccurs="0"/>
                                         <elementRef key="provenance"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="acquisition"
                                          minOccurs="0"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <history>

                                      <history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <history>
                                       <origin>
                                        <p>Written in Durham during the mid twelfth
                                           century.</p>
                                       </origin>
                                       <provenance>
                                        <p>Recorded in two medieval
                                           catalogues of the books belonging to Durham Priory, made in 1391 and
                                           1405.</p>
                                       </provenance>
                                       <provenance>
                                        <p>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.</p>
                                       </provenance>
                                       <acquisition>
                                        <p>Presented to Trinity College in 1738 by
                                           Thomas Gale and his son Roger.</p>
                                       </acquisition>
                                      </history>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="originminOccurs="0"/>
                                         <elementRef key="provenance"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="acquisition"
                                          minOccurs="0"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element history
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                             tei_model.pLike+
                                           | ( tei_summary?, tei_origin?, tei_provenance*, tei_acquisition? )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-hyphenation.html b/gl/dev/ref-hyphenation.html index 6235e189c..fbcb16195 100644 --- a/gl/dev/ref-hyphenation.html +++ b/gl/dev/ref-hyphenation.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <hyphenation>

                                      <hyphenation> (hyphenation) summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      all
                                      all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
                                      some
                                      end-of-line hyphenation has been retained in some cases. [Default]
                                      hard
                                      all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
                                      none
                                      all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <hyphenation eol="some">
                                       <p>End-of-line hyphenation silently removed where appropriate</p>
                                      </hyphenation>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <hyphenation>

                                      <hyphenation> (hyphenation) summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      all
                                      all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
                                      some
                                      end-of-line hyphenation has been retained in some cases. [Default]
                                      hard
                                      all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
                                      none
                                      all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <hyphenation eol="some">
                                       <p>End-of-line hyphenation silently removed where appropriate</p>
                                      </hyphenation>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element hyphenation
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          attribute eol { "all" | "some" | "hard" | "none" }?,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-idno.html b/gl/dev/ref-idno.html index ea54c3552..fdcdcbdd1 100644 --- a/gl/dev/ref-idno.html +++ b/gl/dev/ref-idno.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <idno>

                                      <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (type, @subtype)
                                      typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      ISBN
                                      International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
                                      ISSN
                                      International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
                                      DOI
                                      Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
                                      URI
                                      Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.
                                      VIAF
                                      A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
                                      ESTC
                                      English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
                                      OCLC
                                      OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      header: idno
                                      character data
                                      Note

                                      idno should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on idno are ISBN, ISSN, DOI, and URI.

                                      Example
                                      <idno type="ISBN">978-1-906964-22-1</idno>
                                      <idno type="ISSN">0143-3385</idno>
                                      <idno type="DOI">10.1000/123</idno>
                                      <idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
                                      <idno type="URI">http://authority.nzetc.org/463/</idno>
                                      <idno type="LT">Thomason Tract E.537(17)</idno>
                                      <idno type="Wing">C695</idno>
                                      <idno type="oldCat">
                                       <g ref="#sym"/>345
                                      </idno>

                                      In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a glyph or <char> element referenced here as #sym.

                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="idno"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <idno>

                                      <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (type, @subtype)
                                      typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      ISBN
                                      International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
                                      ISSN
                                      International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
                                      DOI
                                      Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
                                      URI
                                      Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.
                                      VIAF
                                      A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
                                      ESTC
                                      English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
                                      OCLC
                                      OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      header: idno
                                      character data
                                      Note

                                      idno should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on idno are ISBN, ISSN, DOI, and URI.

                                      Example
                                      <idno type="ISBN">978-1-906964-22-1</idno>
                                      <idno type="ISSN">0143-3385</idno>
                                      <idno type="DOI">10.1000/123</idno>
                                      <idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
                                      <idno type="URI">http://authority.nzetc.org/463/</idno>
                                      <idno type="LT">Thomason Tract E.537(17)</idno>
                                      <idno type="Wing">C695</idno>
                                      <idno type="oldCat">
                                       <g ref="#sym"/>345
                                      </idno>

                                      In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a glyph or <char> element referenced here as #sym.

                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="idno"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element idno
                                       {
                                          tei_att.global.attributes,
                                      @@ -40,4 +40,4 @@
                                           | teidata.enumerated
                                          }?,
                                          ( text | tei_model.gLike | tei_idno )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-imprint.html b/gl/dev/ref-imprint.html index add99fed8..05bf789ef 100644 --- a/gl/dev/ref-imprint.html +++ b/gl/dev/ref-imprint.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <imprint>

                                      <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: monogr
                                      May contain
                                      Example
                                      <imprint>
                                       <pubPlace>Oxford</pubPlace>
                                       <publisher>Clarendon Press</publisher>
                                       <date>1987</date>
                                      </imprint>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="classCode"/>
                                         <elementRef key="catRef"/>
                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate>
                                          <classRef key="model.imprintPart"/>
                                          <classRef key="model.dateLike"/>
                                         </alternate>
                                         <elementRef key="respStmtminOccurs="0"
                                          maxOccurs="unbounded"/>

                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <imprint>

                                      <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: monogr
                                      May contain
                                      Example
                                      <imprint>
                                       <pubPlace>Oxford</pubPlace>
                                       <publisher>Clarendon Press</publisher>
                                       <date>1987</date>
                                      </imprint>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="classCode"/>
                                         <elementRef key="catRef"/>
                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate>
                                          <classRef key="model.imprintPart"/>
                                          <classRef key="model.dateLike"/>
                                         </alternate>
                                         <elementRef key="respStmtminOccurs="0"
                                          maxOccurs="unbounded"/>

                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element imprint
                                       {
                                          tei_att.global.attributes,
                                      @@ -33,4 +33,4 @@
                                                tei_model.global*
                                             )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-incipit.html b/gl/dev/ref-incipit.html index 31cb4f655..675a0cb60 100644 --- a/gl/dev/ref-incipit.html +++ b/gl/dev/ref-incipit.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <incipit>

                                      <incipit> 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. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <incipit>Pater noster qui es in celis</incipit>
                                      <incipit defective="true">tatem dedit hominibus alleluia.</incipit>
                                      <incipit type="biblical">Ghif ons huden onse dagelix broet</incipit>
                                      <incipit>O ongehoerde gewerdighe christi</incipit>
                                      <incipit type="lemma">Firmiter</incipit>
                                      <incipit>Ideo dicit firmiter quia ordo fidei nostre probari non potest</incipit>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <incipit>

                                      <incipit> 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. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <incipit>Pater noster qui es in celis</incipit>
                                      <incipit defective="true">tatem dedit hominibus alleluia.</incipit>
                                      <incipit type="biblical">Ghif ons huden onse dagelix broet</incipit>
                                      <incipit>O ongehoerde gewerdighe christi</incipit>
                                      <incipit type="lemma">Firmiter</incipit>
                                      <incipit>Ideo dicit firmiter quia ordo fidei nostre probari non potest</incipit>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element incipit
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.msExcerpt.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-index.html b/gl/dev/ref-index.html index f4c0374ec..d63764b01 100644 --- a/gl/dev/ref-index.html +++ b/gl/dev/ref-index.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <index>

                                      <index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.spanning (@spanTo)
                                      indexNamea single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name), supplying a name to specify which index (of several) the index entry belongs to.
                                      Status Optional
                                      Datatype teidata.name
                                      Note

                                      This attribute makes it possible to create multiple indexes for a text.

                                      Member of
                                      Contained by
                                      May contain
                                      core: index term
                                      Example
                                      David's other principal backer, Josiah ha-Kohen
                                      <index indexName="NAMES">
                                       <term>Josiah ha-Kohen b. Azarya</term>
                                      </index> b. Azarya, son of one of the last gaons of Sura <index indexName="PLACES">
                                       <term>Sura</term>
                                      </index> was David's own first cousin.
                                      Content model
                                      <content>
                                       <sequence minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="term"/>
                                        <elementRef key="indexminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <index>

                                      <index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.spanning (@spanTo)
                                      indexNamea single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name), supplying a name to specify which index (of several) the index entry belongs to.
                                      Status Optional
                                      Datatype teidata.name
                                      Note

                                      This attribute makes it possible to create multiple indexes for a text.

                                      Member of
                                      Contained by
                                      May contain
                                      core: index term
                                      Example
                                      David's other principal backer, Josiah ha-Kohen
                                      <index indexName="NAMES">
                                       <term>Josiah ha-Kohen b. Azarya</term>
                                      </index> b. Azarya, son of one of the last gaons of Sura <index indexName="PLACES">
                                       <term>Sura</term>
                                      </index> was David's own first cousin.
                                      Content model
                                      <content>
                                       <sequence minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="term"/>
                                        <elementRef key="indexminOccurs="0"/>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element index
                                       {
                                          tei_att.global.attributes,
                                          tei_att.spanning.attributes,
                                          attribute indexName { teidata.name }?,
                                          ( tei_term, tei_index? )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-institution.html b/gl/dev/ref-institution.html index 38a964c64..70a77ccae 100644 --- a/gl/dev/ref-institution.html +++ b/gl/dev/ref-institution.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <institution>

                                      <institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      Contained by
                                      namesdates: objectIdentifier
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <settlement>Oxford</settlement>
                                       <institution>University of Oxford</institution>
                                       <repository>Bodleian Library</repository>
                                       <idno>MS. Bodley 406</idno>
                                      </msIdentifier>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <institution>

                                      <institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      Contained by
                                      namesdates: objectIdentifier
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <settlement>Oxford</settlement>
                                       <institution>University of Oxford</institution>
                                       <repository>Bodleian Library</repository>
                                       <idno>MS. Bodley 406</idno>
                                      </msIdentifier>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element institution
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-interp.html b/gl/dev/ref-interp.html index aa3f7d8a1..e45fa3fc3 100644 --- a/gl/dev/ref-interp.html +++ b/gl/dev/ref-interp.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <interp>

                                      <interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. Spans and Interpretations]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.interpLike (@type, @subtype, @inst)
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      gaiji: g
                                      character data
                                      Note

                                      Generally, each interp element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an interp with any textual element through its ana attribute.

                                      Alternatively (or, in addition) an interp may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the interp applies.

                                      Example
                                      <interp type="structuralunit"
                                       xml:id="ana_am">
                                      aftermath</interp>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <interp>

                                      <interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. Spans and Interpretations]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.interpLike (@type, @subtype, @inst)
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      gaiji: g
                                      character data
                                      Note

                                      Generally, each interp element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an interp with any textual element through its ana attribute.

                                      Alternatively (or, in addition) an interp may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the interp applies.

                                      Example
                                      <interp type="structuralunit"
                                       xml:id="ana_am">
                                      aftermath</interp>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element interp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.interpLike.attributes,
                                          ( text | tei_model.gLike | tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-interpGrp.html b/gl/dev/ref-interpGrp.html index fe93d0224..594ba89f5 100644 --- a/gl/dev/ref-interpGrp.html +++ b/gl/dev/ref-interpGrp.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <interpGrp>

                                      <interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. Spans and Interpretations]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.interpLike (@type, @subtype, @inst)
                                      Member of
                                      Contained by
                                      May contain
                                      analysis: interp
                                      core: desc
                                      Note

                                      Any number of interp elements.

                                      Example
                                      <interpGrp resp="#TMA"
                                       type="structuralunit">

                                       <desc>basic structural organization</desc>
                                       <interp xml:id="I1">introduction</interp>
                                       <interp xml:id="I2">conflict</interp>
                                       <interp xml:id="I3">climax</interp>
                                       <interp xml:id="I4">revenge</interp>
                                       <interp xml:id="I5">reconciliation</interp>
                                       <interp xml:id="I6">aftermath</interp>
                                      </interpGrp>
                                      <bibl xml:id="TMA">
                                      <!-- bibliographic citation for source of this +

                                      <interpGrp>

                                      <interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. Spans and Interpretations]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.interpLike (@type, @subtype, @inst)
                                      Member of
                                      Contained by
                                      May contain
                                      analysis: interp
                                      core: desc
                                      Note

                                      Any number of interp elements.

                                      Example
                                      <interpGrp resp="#TMA"
                                       type="structuralunit">

                                       <desc>basic structural organization</desc>
                                       <interp xml:id="I1">introduction</interp>
                                       <interp xml:id="I2">conflict</interp>
                                       <interp xml:id="I3">climax</interp>
                                       <interp xml:id="I4">revenge</interp>
                                       <interp xml:id="I5">reconciliation</interp>
                                       <interp xml:id="I6">aftermath</interp>
                                      </interpGrp>
                                      <bibl xml:id="TMA">
                                      <!-- bibliographic citation for source of this interpretive framework -->
                                      </bibl>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="interpminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element interpGrp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.interpLike.attributes,
                                          ( tei_model.descLike*, tei_interp+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-interpretation.html b/gl/dev/ref-interpretation.html index 88e3a1605..02a640f6f 100644 --- a/gl/dev/ref-interpretation.html +++ b/gl/dev/ref-interpretation.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <interpretation>

                                      <interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <interpretation>
                                       <p>The part of speech analysis applied throughout section 4 was added by hand and has not
                                         been checked</p>
                                      </interpretation>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <interpretation>

                                      <interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <interpretation>
                                       <p>The part of speech analysis applied throughout section 4 was added by hand and has not
                                         been checked</p>
                                      </interpretation>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element interpretation
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-item.html b/gl/dev/ref-item.html index 4cb53a73d..37a699b95 100644 --- a/gl/dev/ref-item.html +++ b/gl/dev/ref-item.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <item>

                                      <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
                                      Contained by
                                      core: list
                                      May contain
                                      Note

                                      May contain simple prose or a sequence of chunks.

                                      Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n.

                                      Example
                                      <list rend="numbered">
                                       <head>Here begin the chapter headings of Book IV</head>
                                       <item n="4.1">The death of Queen Clotild.</item>
                                       <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
                                       <item n="4.3">The wives and children of Lothar.</item>
                                       <item n="4.4">The Counts of the Bretons.</item>
                                       <item n="4.5">Saint Gall the Bishop.</item>
                                       <item n="4.6">The priest Cato.</item>
                                       <item> ...</item>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <item>

                                      <item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
                                      Contained by
                                      core: list
                                      May contain
                                      Note

                                      May contain simple prose or a sequence of chunks.

                                      Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n.

                                      Example
                                      <list rend="numbered">
                                       <head>Here begin the chapter headings of Book IV</head>
                                       <item n="4.1">The death of Queen Clotild.</item>
                                       <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
                                       <item n="4.3">The wives and children of Lothar.</item>
                                       <item n="4.4">The Counts of the Bretons.</item>
                                       <item n="4.5">Saint Gall the Bishop.</item>
                                       <item n="4.6">The priest Cato.</item>
                                       <item> ...</item>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element item
                                       {
                                          tei_att.global.attributes,
                                          tei_att.sortable.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-join.html b/gl/dev/ref-join.html index 7a6911624..9140005f8 100644 --- a/gl/dev/ref-join.html +++ b/gl/dev/ref-join.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <join>

                                      <join> (join) identifies a possibly fragmented segment of text, by pointing at the possibly discontiguous elements which compose it. [16.7. Aggregation]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      resultspecifies the name of an element which this aggregation may be understood to represent.
                                      Status Optional
                                      Datatype teidata.name
                                      scopeindicates 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).
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      root
                                      the rooted subtrees indicated by the target attribute are joined, each subtree become a child of the virtual element created by the join [Default]
                                      branches
                                      the children of the subtrees indicated by the target attribute become the children of the virtual element (i.e. the roots of the subtrees are discarded)
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example

                                      The following example is discussed in section [ID SAAG in TEI Guidelines]:

                                      <sp>
                                       <speaker>Hughie</speaker>
                                       <p>How does it go? <q>
                                         <l xml:id="frog_x1">da-da-da</l>
                                         <l xml:id="frog_l2">gets a new frog</l>
                                         <l>...</l>
                                        </q>
                                       </p>
                                      </sp>
                                      <sp>
                                       <speaker>Louie</speaker>
                                       <p>
                                        <q>
                                         <l xml:id="frog_l1">When the old pond</l>
                                         <l>...</l>
                                        </q>
                                       </p>
                                      </sp>
                                      <sp>
                                       <speaker>Dewey</speaker>
                                       <p>
                                        <q>... <l xml:id="frog_l3">It's a new pond.</l>
                                        </q>
                                       </p>
                                       <join target="#frog_l1 #frog_l2 #frog_l3"
                                        result="lgscope="root"/>

                                      </sp>

                                      The join element here identifies a linegroup (lg) comprising the three lines indicated by the target attribute. The value root for the scope attribute indicates that the resulting virtual element contains the three l elements linked to at #frog_l1 #frog_l2 #frog_l3, rather than their character data content.

                                      Example

                                      In this example, the attribute scope is specified with the value of branches to indicate that the virtual list being constructed is to be made by taking the lists indicated by the target attribute of the join element, discarding the list tags which enclose them, and combining the items contained within the lists into a single virtual list:

                                      <p>Southern dialect (my own variety, at least) has only <list xml:id="LP1">
                                        <item>
                                         <s>I done gone</s>
                                        </item>
                                        <item>
                                         <s>I done went</s>
                                        </item>
                                       </list> whereas Negro Non-Standard basilect has both these and <list xml:id="LP2">
                                        <item>
                                         <s>I done go</s>
                                        </item>
                                       </list>.</p>
                                      <p>White Southern dialect also has <list xml:id="LP3">
                                        <item>
                                         <s>I've done gone</s>
                                        </item>
                                        <item>
                                         <s>I've done went</s>
                                        </item>
                                       </list> which, when they occur in Negro dialect, should probably be considered as borrowings from other varieties of English.</p>
                                      <join result="listxml:id="LST1"
                                       target="#LP1 #LP2 #LP3scope="branches">

                                       <desc>Sample sentences in Southern speech</desc>
                                      </join>
                                      Schematron

                                      <s:assert test="contains(@target,' ')">You must supply at least two values for @target on <s:name/>
                                      </s:assert>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <join>

                                      <join> (join) identifies a possibly fragmented segment of text, by pointing at the possibly discontiguous elements which compose it. [16.7. Aggregation]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      resultspecifies the name of an element which this aggregation may be understood to represent.
                                      Status Optional
                                      Datatype teidata.name
                                      scopeindicates 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).
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      root
                                      the rooted subtrees indicated by the target attribute are joined, each subtree become a child of the virtual element created by the join [Default]
                                      branches
                                      the children of the subtrees indicated by the target attribute become the children of the virtual element (i.e. the roots of the subtrees are discarded)
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example

                                      The following example is discussed in section [ID SAAG in TEI Guidelines]:

                                      <sp>
                                       <speaker>Hughie</speaker>
                                       <p>How does it go? <q>
                                         <l xml:id="frog_x1">da-da-da</l>
                                         <l xml:id="frog_l2">gets a new frog</l>
                                         <l>...</l>
                                        </q>
                                       </p>
                                      </sp>
                                      <sp>
                                       <speaker>Louie</speaker>
                                       <p>
                                        <q>
                                         <l xml:id="frog_l1">When the old pond</l>
                                         <l>...</l>
                                        </q>
                                       </p>
                                      </sp>
                                      <sp>
                                       <speaker>Dewey</speaker>
                                       <p>
                                        <q>... <l xml:id="frog_l3">It's a new pond.</l>
                                        </q>
                                       </p>
                                       <join target="#frog_l1 #frog_l2 #frog_l3"
                                        result="lgscope="root"/>

                                      </sp>

                                      The join element here identifies a linegroup (lg) comprising the three lines indicated by the target attribute. The value root for the scope attribute indicates that the resulting virtual element contains the three l elements linked to at #frog_l1 #frog_l2 #frog_l3, rather than their character data content.

                                      Example

                                      In this example, the attribute scope is specified with the value of branches to indicate that the virtual list being constructed is to be made by taking the lists indicated by the target attribute of the join element, discarding the list tags which enclose them, and combining the items contained within the lists into a single virtual list:

                                      <p>Southern dialect (my own variety, at least) has only <list xml:id="LP1">
                                        <item>
                                         <s>I done gone</s>
                                        </item>
                                        <item>
                                         <s>I done went</s>
                                        </item>
                                       </list> whereas Negro Non-Standard basilect has both these and <list xml:id="LP2">
                                        <item>
                                         <s>I done go</s>
                                        </item>
                                       </list>.</p>
                                      <p>White Southern dialect also has <list xml:id="LP3">
                                        <item>
                                         <s>I've done gone</s>
                                        </item>
                                        <item>
                                         <s>I've done went</s>
                                        </item>
                                       </list> which, when they occur in Negro dialect, should probably be considered as borrowings from other varieties of English.</p>
                                      <join result="listxml:id="LST1"
                                       target="#LP1 #LP2 #LP3scope="branches">

                                       <desc>Sample sentences in Southern speech</desc>
                                      </join>
                                      Schematron

                                      <s:assert test="contains(@target,' ')">You must supply at least two values for @target on <s:name/>
                                      </s:assert>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element join
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute result { teidata.name }?,
                                          attribute scope { "root" | "branches" }?,
                                          ( tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-keywords.html b/gl/dev/ref-keywords.html index 534952a48..0911167e7 100644 --- a/gl/dev/ref-keywords.html +++ b/gl/dev/ref-keywords.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <keywords>

                                      <keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a taxonomy element, or by some other resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Contained by
                                      header: textClass
                                      May contain
                                      core: list term
                                      Note

                                      Each individual keyword (including compound subject headings) should be supplied as a term element directly within the keywords element. An alternative usage, in which each term appears within an item inside a list is permitted for backwards compatibility, but is deprecated.

                                      If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.

                                      Example
                                      <keywords scheme="http://classificationweb.net">
                                       <term>Babbage, Charles</term>
                                       <term>Mathematicians - Great Britain - Biography</term>
                                      </keywords>
                                      Example
                                      <keywords>
                                       <term>Fermented beverages</term>
                                       <term>Central Andes</term>
                                       <term>Schinus molle</term>
                                       <term>Molle beer</term>
                                       <term>Indigenous peoples</term>
                                       <term>Ethnography</term>
                                       <term>Archaeology</term>
                                      </keywords>
                                      Content model
                                      <content>
                                       <alternate>
                                        <elementRef key="termminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="list"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <keywords>

                                      <keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a taxonomy element, or by some other resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Contained by
                                      header: textClass
                                      May contain
                                      core: list term
                                      Note

                                      Each individual keyword (including compound subject headings) should be supplied as a term element directly within the keywords element. An alternative usage, in which each term appears within an item inside a list is permitted for backwards compatibility, but is deprecated.

                                      If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.

                                      Example
                                      <keywords scheme="http://classificationweb.net">
                                       <term>Babbage, Charles</term>
                                       <term>Mathematicians - Great Britain - Biography</term>
                                      </keywords>
                                      Example
                                      <keywords>
                                       <term>Fermented beverages</term>
                                       <term>Central Andes</term>
                                       <term>Schinus molle</term>
                                       <term>Molle beer</term>
                                       <term>Indigenous peoples</term>
                                       <term>Ethnography</term>
                                       <term>Archaeology</term>
                                      </keywords>
                                      Content model
                                      <content>
                                       <alternate>
                                        <elementRef key="termminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="list"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element keywords
                                       {
                                          tei_att.global.attributes,
                                          attribute scheme { teidata.pointer }?,
                                          ( tei_term+ | tei_list )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-l.html b/gl/dev/ref-l.html index 796e232b3..264a79f31 100644 --- a/gl/dev/ref-l.html +++ b/gl/dev/ref-l.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <l>

                                      <l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.metrical (@met, @real, @rhyme) att.enjamb (@enjamb) att.fragmentable (@part)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
                                      Schematron

                                      <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements.
                                      </sch:report>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <l>

                                      <l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.metrical (@met, @real, @rhyme) att.enjamb (@enjamb) att.fragmentable (@part)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
                                      Schematron

                                      <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements.
                                      </sch:report>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element l
                                       {
                                          tei_att.global.attributes,
                                      @@ -35,4 +35,4 @@
                                           | tei_model.inter
                                           | tei_model.global
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-label.html b/gl/dev/ref-label.html index 5d0bb479b..3e100a29d 100644 --- a/gl/dev/ref-label.html +++ b/gl/dev/ref-label.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <label>

                                      <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

                                      <list type="glossxml:lang="enm">
                                       <head xml:lang="en">Vocabulary</head>
                                       <headLabel xml:lang="en">Middle English</headLabel>
                                       <headItem xml:lang="en">New English</headItem>
                                       <label>nu</label>
                                       <item xml:lang="en">now</item>
                                       <label>lhude</label>
                                       <item xml:lang="en">loudly</item>
                                       <label>bloweth</label>
                                       <item xml:lang="en">blooms</item>
                                       <label>med</label>
                                       <item xml:lang="en">meadow</item>
                                       <label>wude</label>
                                       <item xml:lang="en">wood</item>
                                       <label>awe</label>
                                       <item xml:lang="en">ewe</item>
                                       <label>lhouth</label>
                                       <item xml:lang="en">lows</item>
                                       <label>sterteth</label>
                                       <item xml:lang="en">bounds, frisks (cf. <cit>
                                         <ref>Chaucer, K.T.644</ref>
                                         <quote>a courser, <term>sterting</term>as the fyr</quote>
                                        </cit>
                                       </item>
                                       <label>verteth</label>
                                       <item xml:lang="la">pedit</item>
                                       <label>murie</label>
                                       <item xml:lang="en">merrily</item>
                                       <label>swik</label>
                                       <item xml:lang="en">cease</item>
                                       <label>naver</label>
                                       <item xml:lang="en">never</item>
                                      </list>
                                      Example

                                      Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

                                      I will add two facts, which have seldom occurred
                                      in the composition of six, or at least of five quartos. <list rend="runontype="ordered">
                                       <label>(1)</label>
                                       <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
                                       <label>(2) </label>
                                       <item>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.</item>
                                      </list>
                                      Example

                                      Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

                                      <list type="gloss">
                                       <label>March 1757.</label>
                                       <item>I wrote some critical observations upon Plautus.</item>
                                       <label>March 8th.</label>
                                       <item>I wrote a long dissertation upon some lines of Virgil.</item>
                                       <label>June.</label>
                                       <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
                                           amori.</quote>
                                       </item>
                                       <label>August.</label>
                                       <item>I went to Crassy, and staid two days.</item>
                                      </list>

                                      Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.

                                      Example

                                      Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it.

                                      <p>[...]
                                      <lb/>&amp; n’entrer en mauuais &amp; mal-heu-
                                      <lb/>ré meſnage. Or des que le conſente-
                                      <lb/>ment des parties y eſt le mariage eſt
                                      <lb/> arreſté, quoy que de faict il ne ſoit
                                      <label place="margin">Puiſſance maritale
                                         entre les Romains.</label>
                                       <lb/> conſommé. Depuis la conſomma-
                                      <lb/>tion du mariage la femme eſt ſoubs
                                      <lb/> la puiſſance du mary, s’il n’eſt eſcla-
                                      <lb/>ue ou enfant de famille : car en ce
                                      <lb/> cas, la femme, qui a eſpouſé vn en-
                                      <lb/>fant de famille, eſt ſous la puiſſance
                                      [...]</p>

                                      In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it.

                                      If so desired the type attribute may be used to distinguish different categories of label.

                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <label>

                                      <label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

                                      <list type="glossxml:lang="enm">
                                       <head xml:lang="en">Vocabulary</head>
                                       <headLabel xml:lang="en">Middle English</headLabel>
                                       <headItem xml:lang="en">New English</headItem>
                                       <label>nu</label>
                                       <item xml:lang="en">now</item>
                                       <label>lhude</label>
                                       <item xml:lang="en">loudly</item>
                                       <label>bloweth</label>
                                       <item xml:lang="en">blooms</item>
                                       <label>med</label>
                                       <item xml:lang="en">meadow</item>
                                       <label>wude</label>
                                       <item xml:lang="en">wood</item>
                                       <label>awe</label>
                                       <item xml:lang="en">ewe</item>
                                       <label>lhouth</label>
                                       <item xml:lang="en">lows</item>
                                       <label>sterteth</label>
                                       <item xml:lang="en">bounds, frisks (cf. <cit>
                                         <ref>Chaucer, K.T.644</ref>
                                         <quote>a courser, <term>sterting</term>as the fyr</quote>
                                        </cit>
                                       </item>
                                       <label>verteth</label>
                                       <item xml:lang="la">pedit</item>
                                       <label>murie</label>
                                       <item xml:lang="en">merrily</item>
                                       <label>swik</label>
                                       <item xml:lang="en">cease</item>
                                       <label>naver</label>
                                       <item xml:lang="en">never</item>
                                      </list>
                                      Example

                                      Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

                                      I will add two facts, which have seldom occurred
                                      in the composition of six, or at least of five quartos. <list rend="runontype="ordered">
                                       <label>(1)</label>
                                       <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
                                       <label>(2) </label>
                                       <item>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.</item>
                                      </list>
                                      Example

                                      Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

                                      <list type="gloss">
                                       <label>March 1757.</label>
                                       <item>I wrote some critical observations upon Plautus.</item>
                                       <label>March 8th.</label>
                                       <item>I wrote a long dissertation upon some lines of Virgil.</item>
                                       <label>June.</label>
                                       <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
                                           amori.</quote>
                                       </item>
                                       <label>August.</label>
                                       <item>I went to Crassy, and staid two days.</item>
                                      </list>

                                      Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.

                                      Example

                                      Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it.

                                      <p>[...]
                                      <lb/>&amp; n’entrer en mauuais &amp; mal-heu-
                                      <lb/>ré meſnage. Or des que le conſente-
                                      <lb/>ment des parties y eſt le mariage eſt
                                      <lb/> arreſté, quoy que de faict il ne ſoit
                                      <label place="margin">Puiſſance maritale
                                         entre les Romains.</label>
                                       <lb/> conſommé. Depuis la conſomma-
                                      <lb/>tion du mariage la femme eſt ſoubs
                                      <lb/> la puiſſance du mary, s’il n’eſt eſcla-
                                      <lb/>ue ou enfant de famille : car en ce
                                      <lb/> cas, la femme, qui a eſpouſé vn en-
                                      <lb/>fant de famille, eſt ſous la puiſſance
                                      [...]</p>

                                      In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it.

                                      If so desired the type attribute may be used to distinguish different categories of label.

                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element label
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.placement.attributes,
                                          tei_att.written.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-lang.html b/gl/dev/ref-lang.html index d39e94658..67867e1db 100644 --- a/gl/dev/ref-lang.html +++ b/gl/dev/ref-lang.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <lang>

                                      <lang> (language name) contains the name of a language mentioned in etymological or other linguistic discussion. [9.3.4. Etymological Information]
                                      Moduledictionaries
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.lexicographic.normalized (@norm, @orig))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      May contain character data mixed with phrase-level elements.

                                      Example
                                      <entry>
                                       <form>
                                        <orth>publish</orth> ... </form>
                                       <etym>
                                        <lang>ME.</lang>
                                        <mentioned>publisshen</mentioned>,
                                       <lang>F.</lang>
                                        <mentioned>publier</mentioned>, <lang>L.</lang>
                                        <mentioned>publicare,
                                           publicatum</mentioned>. <xr>See <ref>public</ref>; cf. <ref>2d -ish</ref>.</xr>
                                       </etym>
                                      </entry>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <lang>

                                      <lang> (language name) contains the name of a language mentioned in etymological or other linguistic discussion. [9.3.4. Etymological Information]
                                      Moduledictionaries
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.lexicographic (@expand, @split, @value, @location, @mergedIn, @opt) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.lexicographic.normalized (@norm, @orig))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      May contain character data mixed with phrase-level elements.

                                      Example
                                      <entry>
                                       <form>
                                        <orth>publish</orth> ... </form>
                                       <etym>
                                        <lang>ME.</lang>
                                        <mentioned>publisshen</mentioned>,
                                       <lang>F.</lang>
                                        <mentioned>publier</mentioned>, <lang>L.</lang>
                                        <mentioned>publicare,
                                           publicatum</mentioned>. <xr>See <ref>public</ref>; cf. <ref>2d -ish</ref>.</xr>
                                       </etym>
                                      </entry>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element lang
                                       {
                                          tei_att.global.attributes,
                                          tei_att.lexicographic.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-langUsage.html b/gl/dev/ref-langUsage.html index 4eb7e5b18..2d05aaf59 100644 --- a/gl/dev/ref-langUsage.html +++ b/gl/dev/ref-langUsage.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <langUsage>

                                      <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      core: p
                                      header: language
                                      linking: ab
                                      Example
                                      <langUsage>
                                       <language ident="fr-CAusage="60">Québecois</language>
                                       <language ident="en-CAusage="20">Canadian business English</language>
                                       <language ident="en-GBusage="20">British English</language>
                                      </langUsage>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="languageminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <langUsage>

                                      <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      core: p
                                      header: language
                                      linking: ab
                                      Example
                                      <langUsage>
                                       <language ident="fr-CAusage="60">Québecois</language>
                                       <language ident="en-CAusage="20">Canadian business English</language>
                                       <language ident="en-GBusage="20">British English</language>
                                      </langUsage>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="languageminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element langUsage
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          ( tei_model.pLike+ | tei_language+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-language.html b/gl/dev/ref-language.html index a9cad6da2..a9cf90e7b 100644 --- a/gl/dev/ref-language.html +++ b/gl/dev/ref-language.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <language>

                                      <language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
                                      Status Required
                                      Datatype teidata.language
                                      usagespecifies the approximate percentage (by volume) of the text which uses this language.
                                      Status Optional
                                      Datatype nonNegativeInteger
                                      Contained by
                                      header: langUsage
                                      May contain
                                      Note

                                      Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

                                      Example
                                      <langUsage>
                                       <language ident="en-USusage="75">modern American English</language>
                                       <language ident="i-az-Arabusage="20">Azerbaijani in Arabic script</language>
                                       <language ident="x-lapusage="05">Pig Latin</language>
                                      </langUsage>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <language>

                                      <language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
                                      Status Required
                                      Datatype teidata.language
                                      usagespecifies the approximate percentage (by volume) of the text which uses this language.
                                      Status Optional
                                      Datatype nonNegativeInteger
                                      Contained by
                                      header: langUsage
                                      May contain
                                      Note

                                      Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

                                      Example
                                      <langUsage>
                                       <language ident="en-USusage="75">modern American English</language>
                                       <language ident="i-az-Arabusage="20">Azerbaijani in Arabic script</language>
                                       <language ident="x-lapusage="05">Pig Latin</language>
                                      </langUsage>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element language
                                       {
                                          tei_att.global.attributes,
                                          attribute ident { teidata.language },
                                          attribute usage { xsd:nonNegativeInteger }?,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-layout.html b/gl/dev/ref-layout.html index 17ff185b9..b09b14735 100644 --- a/gl/dev/ref-layout.html +++ b/gl/dev/ref-layout.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <layout>

                                      <layout> (layout) describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      columns(columns) specifies the number of columns per page
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      streams(textual streams) indicates the number of streams per page, each of which contains an independent textual stream
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      ruledLines(ruled lines) specifies the number of ruled lines per column
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      writtenLines(written lines) specifies the number of written lines per column
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      Contained by
                                      msdescription: layoutDesc
                                      May contain
                                      Example
                                      <layout columns="1ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
                                      Example
                                      <layout columns="2ruledLines="42">
                                       <p>2 columns of 42 lines ruled in ink, with central rule
                                         between the columns.</p>
                                      </layout>
                                      Example
                                      <layout columns="1 2writtenLines="40 50">
                                       <p>Some pages have 2 columns, with central rule
                                         between the columns; each column with between 40 and 50 lines of writing.</p>
                                      </layout>
                                      Example
                                      <layout streams="3columns="3"/>
                                      <!-- Further down in document body -->
                                      <div type="page">
                                       <ab>
                                        <pb/>
                                         一二三<cb type="top-stream"/>
                                         一二三<cb type="mid-stream"/>
                                         一二三<cb type="bottom-stream"/>
                                      <!-- cb here for demo purposes -->
                                       </ab>
                                      </div>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <layout>

                                      <layout> (layout) describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      columns(columns) specifies the number of columns per page
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      streams(textual streams) indicates the number of streams per page, each of which contains an independent textual stream
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      ruledLines(ruled lines) specifies the number of ruled lines per column
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      writtenLines(written lines) specifies the number of written lines per column
                                      Status Optional
                                      Datatype 1–2 occurrences of teidata.count separated by whitespace
                                      Note

                                      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.

                                      Contained by
                                      msdescription: layoutDesc
                                      May contain
                                      Example
                                      <layout columns="1ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
                                      Example
                                      <layout columns="2ruledLines="42">
                                       <p>2 columns of 42 lines ruled in ink, with central rule
                                         between the columns.</p>
                                      </layout>
                                      Example
                                      <layout columns="1 2writtenLines="40 50">
                                       <p>Some pages have 2 columns, with central rule
                                         between the columns; each column with between 40 and 50 lines of writing.</p>
                                      </layout>
                                      Example
                                      <layout streams="3columns="3"/>
                                      <!-- Further down in document body -->
                                      <div type="page">
                                       <ab>
                                        <pb/>
                                         一二三<cb type="top-stream"/>
                                         一二三<cb type="mid-stream"/>
                                         一二三<cb type="bottom-stream"/>
                                      <!-- cb here for demo purposes -->
                                       </ab>
                                      </div>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element layout
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute ruledLines { list { teidata.count, teidata.count? } }?,
                                          attribute writtenLines { list { teidata.count, teidata.count? } }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-layoutDesc.html b/gl/dev/ref-layoutDesc.html index deee76021..87f9398eb 100644 --- a/gl/dev/ref-layoutDesc.html +++ b/gl/dev/ref-layoutDesc.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <layoutDesc>

                                      <layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: objectDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: layout summary
                                      Example
                                      <layoutDesc>
                                       <p>Most pages have between 25 and 32 long lines ruled in lead.</p>
                                      </layoutDesc>
                                      Example
                                      <layoutDesc>
                                       <layout columns="2ruledLines="42">
                                        <p>
                                         <locus from="f12rto="f15v"/>
                                           2 columns of 42 lines pricked and ruled in ink, with
                                           central rule between the columns.</p>
                                       </layout>
                                       <layout columns="3">
                                        <p>
                                         <locus from="f16"/>Prickings for three columns are visible.</p>
                                       </layout>
                                      </layoutDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="layoutminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <layoutDesc>

                                      <layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: objectDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: layout summary
                                      Example
                                      <layoutDesc>
                                       <p>Most pages have between 25 and 32 long lines ruled in lead.</p>
                                      </layoutDesc>
                                      Example
                                      <layoutDesc>
                                       <layout columns="2ruledLines="42">
                                        <p>
                                         <locus from="f12rto="f15v"/>
                                           2 columns of 42 lines pricked and ruled in ink, with
                                           central rule between the columns.</p>
                                       </layout>
                                       <layout columns="3">
                                        <p>
                                         <locus from="f16"/>Prickings for three columns are visible.</p>
                                       </layout>
                                      </layoutDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="layoutminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element layoutDesc
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | ( tei_summary?, tei_layout+ ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-lb.html b/gl/dev/ref-lb.html index 71c18708c..923ac1b5a 100644 --- a/gl/dev/ref-lb.html +++ b/gl/dev/ref-lb.html @@ -22,7 +22,7 @@ }); });

                                      <lb>

                                      <lb> (line-beginning) marks the start of each line of the transcribed text, including the first [3.11.3. Milestone -Elements 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo)
                                      break
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      no
                                      this line-beginning should not be taken as a word-break, i.e. word would be hyphenated in a printed text
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked.

                                      The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.

                                      Example

                                      This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:

                                      <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
                                      <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
                                      <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
                                      Example

                                      This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.

                                      <titlePart>
                                       <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
                                      </titlePart>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +Elements 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo)
                                      break
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      no
                                      this line-beginning should not be taken as a word-break, i.e. word would be hyphenated in a printed text
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked.

                                      The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.

                                      Example

                                      This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:

                                      <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
                                      <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
                                      <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
                                      Example

                                      This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.

                                      <titlePart>
                                       <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
                                      </titlePart>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element lb
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.spanning.attributes,
                                          attribute break { "no" | teidata.enumerated }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-lem.html b/gl/dev/ref-lem.html index 56eca3925..608440f95 100644 --- a/gl/dev/ref-lem.html +++ b/gl/dev/ref-lem.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <lem>

                                      <lem> (lemma) contains the lemma, or base text, of a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.textCritical (@type, @cause, @varSeq, @require) (att.written (@hand)) att.witnessed (@wit)
                                      Contained by
                                      textcrit: app rdgGrp
                                      May contain
                                      Note

                                      The term lemma is used in text criticism to describe the reading given in the main text, which may be used as a heading in the apparatus itself. This usage connects it to mathematics (where a lemma is a proven proposition used as a step in a proof, a "given") and natural-language processing (where a lemma is the dictionary headword associated with an inflected form in the running text).

                                      Example
                                      <app>
                                       <lem wit="#El #Hg">Experience</lem>
                                       <rdg wit="#Latype="substantive">Experiment</rdg>
                                       <rdg wit="#Ra2type="substantive">Eryment</rdg>
                                      </app>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.divLike"/>
                                        <classRef key="model.divPart"/>
                                        <elementRef key="titlePage"/>
                                        <elementRef key="argument"/>
                                        <elementRef key="byline"/>
                                        <elementRef key="docAuthor"/>
                                        <elementRef key="docDate"/>
                                        <elementRef key="docEdition"/>
                                        <elementRef key="docImprint"/>
                                        <elementRef key="docTitle"/>
                                        <elementRef key="epigraph"/>
                                        <elementRef key="imprimatur"/>
                                        <elementRef key="titlePart"/>
                                        <elementRef key="epilogue"/>
                                        <elementRef key="performance"/>
                                        <elementRef key="prologue"/>
                                        <elementRef key="set"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.rdgPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <lem>

                                      <lem> (lemma) contains the lemma, or base text, of a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.textCritical (@type, @cause, @varSeq, @require) (att.written (@hand)) att.witnessed (@wit)
                                      Contained by
                                      textcrit: app rdgGrp
                                      May contain
                                      Note

                                      The term lemma is used in text criticism to describe the reading given in the main text, which may be used as a heading in the apparatus itself. This usage connects it to mathematics (where a lemma is a proven proposition used as a step in a proof, a "given") and natural-language processing (where a lemma is the dictionary headword associated with an inflected form in the running text).

                                      Example
                                      <app>
                                       <lem wit="#El #Hg">Experience</lem>
                                       <rdg wit="#Latype="substantive">Experiment</rdg>
                                       <rdg wit="#Ra2type="substantive">Eryment</rdg>
                                      </app>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.divLike"/>
                                        <classRef key="model.divPart"/>
                                        <elementRef key="titlePage"/>
                                        <elementRef key="argument"/>
                                        <elementRef key="byline"/>
                                        <elementRef key="docAuthor"/>
                                        <elementRef key="docDate"/>
                                        <elementRef key="docEdition"/>
                                        <elementRef key="docImprint"/>
                                        <elementRef key="docTitle"/>
                                        <elementRef key="epigraph"/>
                                        <elementRef key="imprimatur"/>
                                        <elementRef key="titlePart"/>
                                        <elementRef key="epilogue"/>
                                        <elementRef key="performance"/>
                                        <elementRef key="prologue"/>
                                        <elementRef key="set"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.rdgPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element lem
                                       {
                                          tei_att.global.attributes,
                                      @@ -52,4 +52,4 @@
                                           | tei_model.global
                                           | tei_model.rdgPart
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-lg.html b/gl/dev/ref-lg.html index 0b404e2dc..49979bc10 100644 --- a/gl/dev/ref-lg.html +++ b/gl/dev/ref-lg.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <lg>

                                      <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.divLike (@org, @sample) (att.metrical (@met, @real, @rhyme)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      contains verse lines or nested line groups only, possibly prefixed by a heading.

                                      Example
                                      <lg type="free">
                                       <l>Let me be my own fool</l>
                                       <l>of my own making, the sum of it</l>
                                      </lg>
                                      <lg type="free">
                                       <l>is equivocal.</l>
                                       <l>One says of the drunken farmer:</l>
                                      </lg>
                                      <lg type="free">
                                       <l>leave him lay off it. And this is</l>
                                       <l>the explanation.</l>
                                      </lg>
                                      Schematron

                                      <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > +

                                      <lg>

                                      <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.divLike (@org, @sample) (att.metrical (@met, @real, @rhyme)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      contains verse lines or nested line groups only, possibly prefixed by a heading.

                                      Example
                                      <lg type="free">
                                       <l>Let me be my own fool</l>
                                       <l>of my own making, the sum of it</l>
                                      </lg>
                                      <lg type="free">
                                       <l>is equivocal.</l>
                                       <l>One says of the drunken farmer:</l>
                                      </lg>
                                      <lg type="free">
                                       <l>leave him lay off it. And this is</l>
                                       <l>the explanation.</l>
                                      </lg>
                                      Schematron

                                      <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element
                                      must contain at least one child l, lg, or gap element.</sch:assert>
                                      Schematron

                                      <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups.
                                      </sch:report>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <alternate>
                                         <classRef key="model.lLike"/>
                                         <classRef key="model.stageLike"/>
                                         <classRef key="model.labelLike"/>
                                         <classRef key="model.pPart.transcriptional"/>
                                         <elementRef key="lg"/>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.lLike"/>
                                         <classRef key="model.stageLike"/>
                                         <classRef key="model.labelLike"/>
                                         <classRef key="model.pPart.transcriptional"/>
                                         <classRef key="model.global"/>
                                         <elementRef key="lg"/>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element lg
                                       {
                                      @@ -48,4 +48,4 @@
                                             )*,
                                             ( tei_model.divBottom, tei_model.global* )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-licence.html b/gl/dev/ref-licence.html index d44727a8a..78a18c76e 100644 --- a/gl/dev/ref-licence.html +++ b/gl/dev/ref-licence.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <licence>

                                      <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      header: availability
                                      linking: annotation
                                      May contain
                                      Note

                                      A licence element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

                                      Example
                                      <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
                                      </licence>
                                      Example
                                      <availability>
                                       <licence target="http://creativecommons.org/licenses/by/3.0/"
                                        notBefore="2013-01-01">

                                        <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
                                           applies to this document.</p>
                                        <p>The licence was added on January 1, 2013.</p>
                                       </licence>
                                      </availability>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <licence>

                                      <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      header: availability
                                      linking: annotation
                                      May contain
                                      Note

                                      A licence element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

                                      Example
                                      <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
                                      </licence>
                                      Example
                                      <availability>
                                       <licence target="http://creativecommons.org/licenses/by/3.0/"
                                        notBefore="2013-01-01">

                                        <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
                                           applies to this document.</p>
                                        <p>The licence was added on January 1, 2013.</p>
                                       </licence>
                                      </availability>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element licence
                                       {
                                          tei_att.global.attributes,
                                          tei_att.pointing.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-line.html b/gl/dev/ref-line.html index db1ab8060..306f4ae9d 100644 --- a/gl/dev/ref-line.html +++ b/gl/dev/ref-line.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <line>

                                      <line> contains the transcription of a topographic line in the source document [11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.written (@hand)
                                      Member of
                                      Contained by
                                      transcr: line surface zone
                                      May contain
                                      Note

                                      This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use l) nor to mark linebreaks within text which has been encoded using structural elements such as p (for which use lb).

                                      Example
                                      <surface>
                                       <zone>
                                        <line>Poem</line>
                                        <line>As in Visions of — at</line>
                                        <line>night —</line>
                                        <line>All sorts of fancies running through</line>
                                        <line>the head</line>
                                       </zone>
                                      </surface>
                                      Example
                                      <surface>
                                       <zone>
                                        <line>Hope you enjoyed</line>
                                        <line>Wales, as they
                                           said</line>
                                        <line>to Mrs FitzHerbert</line>
                                        <line>Mama</line>
                                       </zone>
                                       <zone>
                                        <line>Printed in England</line>
                                       </zone>
                                      </surface>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.linePart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <line>

                                      <line> contains the transcription of a topographic line in the source document [11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.written (@hand)
                                      Member of
                                      Contained by
                                      transcr: line surface zone
                                      May contain
                                      Note

                                      This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use l) nor to mark linebreaks within text which has been encoded using structural elements such as p (for which use lb).

                                      Example
                                      <surface>
                                       <zone>
                                        <line>Poem</line>
                                        <line>As in Visions of — at</line>
                                        <line>night —</line>
                                        <line>All sorts of fancies running through</line>
                                        <line>the head</line>
                                       </zone>
                                      </surface>
                                      Example
                                      <surface>
                                       <zone>
                                        <line>Hope you enjoyed</line>
                                        <line>Wales, as they
                                           said</line>
                                        <line>to Mrs FitzHerbert</line>
                                        <line>Mama</line>
                                       </zone>
                                       <zone>
                                        <line>Printed in England</line>
                                       </zone>
                                      </surface>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.linePart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element line
                                       {
                                          tei_att.typed.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.coordinated.attributes,
                                          tei_att.written.attributes,
                                          ( text | tei_model.global | tei_model.gLike | tei_model.linePart )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-link.html b/gl/dev/ref-link.html index 75ace05b4..576350d01 100644 --- a/gl/dev/ref-link.html +++ b/gl/dev/ref-link.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -
                                      <link> (link) defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements. [16.1. Links]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      This element should only be used to encode associations not otherwise provided for by more specific elements.

                                      The location of this element within a document has no significance, unless it is included within a linkGrp, in which case it may inherit the value of the type attribute from the value given on the linkGrp.

                                      Example
                                      <s n="1">The state Supreme Court has refused to release <rs xml:id="R1">
                                        <rs xml:id="R2">Rahway State Prison</rs> inmate</rs>
                                       <rs xml:id="R3">James Scott</rs> on bail.</s>
                                      <s n="2">
                                       <rs xml:id="R4">The fighter</rs> is serving 30-40 years
                                      for a 1975 armed robbery conviction in <rs xml:id="R5">the penitentiary</rs>.
                                      </s>
                                      <!-- ... -->
                                      <linkGrp type="periphrasis">
                                       <link target="#R1 #R3 #R4"/>
                                       <link target="#R2 #R5"/>
                                      </linkGrp>
                                      Schematron

                                      <sch:assert test="contains(normalize-space(@target),' ')">You must supply at least two values for @target or on <sch:name/>
                                      </sch:assert>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    
                                      <link> (link) defines an association or hypertextual link among elements or passages, of some type not more precisely specifiable by other elements. [16.1. Links]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      This element should only be used to encode associations not otherwise provided for by more specific elements.

                                      The location of this element within a document has no significance, unless it is included within a linkGrp, in which case it may inherit the value of the type attribute from the value given on the linkGrp.

                                      Example
                                      <s n="1">The state Supreme Court has refused to release <rs xml:id="R1">
                                        <rs xml:id="R2">Rahway State Prison</rs> inmate</rs>
                                       <rs xml:id="R3">James Scott</rs> on bail.</s>
                                      <s n="2">
                                       <rs xml:id="R4">The fighter</rs> is serving 30-40 years
                                      for a 1975 armed robbery conviction in <rs xml:id="R5">the penitentiary</rs>.
                                      </s>
                                      <!-- ... -->
                                      <linkGrp type="periphrasis">
                                       <link target="#R1 #R3 #R4"/>
                                       <link target="#R2 #R5"/>
                                      </linkGrp>
                                      Schematron

                                      <sch:assert test="contains(normalize-space(@target),' ')">You must supply at least two values for @target or on <sch:name/>
                                      </sch:assert>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element link
                                       {
                                          tei_att.global.attributes,
                                          tei_att.pointing.attributes,
                                          tei_att.typed.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-linkGrp.html b/gl/dev/ref-linkGrp.html index 096167cf9..7ddf88316 100644 --- a/gl/dev/ref-linkGrp.html +++ b/gl/dev/ref-linkGrp.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <linkGrp>

                                      <linkGrp> (link group) defines a collection of associations or hypertextual links. [16.1. Links]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing.group (@domains, @targFunc) (att.pointing (@targetLang, @target, @evaluate)) (att.typed (@type, @subtype))
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc ptr
                                      linking: link
                                      Note

                                      May contain one or more link or ptr elements.

                                      A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

                                      Example
                                      <linkGrp type="translation">
                                       <link target="#CCS1 #SW1"/>
                                       <link target="#CCS2 #SW2"/>
                                       <link target="#CCS #SW"/>
                                      </linkGrp>
                                      <div type="volumexml:id="CCS"
                                       xml:lang="fr">

                                       <p>
                                        <s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>
                                        <s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas le temps de me dire : "Je m'endors."</s>
                                       </p>
                                      <!-- ... -->
                                      </div>
                                      <div type="volumexml:id="SWxml:lang="en">
                                       <p>
                                        <s xml:id="SW1">For a long time I used to go to bed early.</s>
                                        <s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had not even time to say "I'm going to sleep."</s>
                                       </p>
                                      <!-- ... -->
                                      </div>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="link"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <linkGrp>

                                      <linkGrp> (link group) defines a collection of associations or hypertextual links. [16.1. Links]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing.group (@domains, @targFunc) (att.pointing (@targetLang, @target, @evaluate)) (att.typed (@type, @subtype))
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc ptr
                                      linking: link
                                      Note

                                      May contain one or more link or ptr elements.

                                      A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

                                      Example
                                      <linkGrp type="translation">
                                       <link target="#CCS1 #SW1"/>
                                       <link target="#CCS2 #SW2"/>
                                       <link target="#CCS #SW"/>
                                      </linkGrp>
                                      <div type="volumexml:id="CCS"
                                       xml:lang="fr">

                                       <p>
                                        <s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>
                                        <s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas le temps de me dire : "Je m'endors."</s>
                                       </p>
                                      <!-- ... -->
                                      </div>
                                      <div type="volumexml:id="SWxml:lang="en">
                                       <p>
                                        <s xml:id="SW1">For a long time I used to go to bed early.</s>
                                        <s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had not even time to say "I'm going to sleep."</s>
                                       </p>
                                      <!-- ... -->
                                      </div>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.descLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="link"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element linkGrp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.pointing.group.attributes,
                                          ( tei_model.descLike*, ( tei_link | tei_ptr )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-list.html b/gl/dev/ref-list.html index 2bd7b3c1b..7bb5f3ac0 100644 --- a/gl/dev/ref-list.html +++ b/gl/dev/ref-list.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <list>

                                      <list> (list) contains any sequence of items organized as a list. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
                                      type(type) describes the nature of the items in the list.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      gloss
                                      (gloss) each list item glosses some term or concept, which is given by a label element preceding the list item.
                                      index
                                      (index) each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
                                      instructions
                                      (instructions) each list item is a step in a sequence of instructions, as in a recipe.
                                      litany
                                      (litany) each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
                                      syllogism
                                      (syllogism) each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
                                      Note

                                      Previous versions of these Guidelines recommended the use of type on list to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.

                                      The formal syntax of the element declarations allows label tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

                                      Example
                                      <list rend="numbered">
                                       <item>a butcher</item>
                                       <item>a baker</item>
                                       <item>a candlestick maker, with
                                       <list rend="bulleted">
                                         <item>rings on his fingers</item>
                                         <item>bells on his toes</item>
                                        </list>
                                       </item>
                                      </list>
                                      Example
                                      <list type="syllogismrend="bulleted">
                                       <item>All Cretans are liars.</item>
                                       <item>Epimenides is a Cretan.</item>
                                       <item>ERGO Epimenides is a liar.</item>
                                      </list>
                                      Example
                                      <list type="litanyrend="simple">
                                       <item>God save us from drought.</item>
                                       <item>God save us from pestilence.</item>
                                       <item>God save us from wickedness in high places.</item>
                                       <item>Praise be to God.</item>
                                      </list>
                                      Example

                                      The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):

                                      <div1 type="section">
                                       <head>Athelstan's Ordinance</head>
                                       <list rend="numbered">
                                        <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
                                           the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
                                           eightpence.
                                        <list rend="numbered">
                                          <item n="1.1">And if anyone does spare one, he is to pay for the thief with his
                                               wergild — and the thief is to be no nearer a settlement on that account — or to
                                               clear himself by an oath of that amount.</item>
                                          <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
                                               not to be spared [whether younger or older than twelve].</item>
                                          <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
                                               then be redeemed with 120 shillings; and the kindred are to stand surety for him
                                               that he will desist for ever.</item>
                                          <item n="1.4">And if he steals after that, they are to pay for him with his wergild,
                                               or to bring him back there.</item>
                                          <item n="1.5">And if he steals after that, they are to pay for him with his wergild,
                                               whether to the king or to him to whom it rightly belongs; and everyone of those who
                                               supported him is to pay 120 shillings to the king as a fine.</item>
                                         </list>
                                        </item>
                                        <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
                                           no justice can be obtained, that one should order their kindred to fetch back such a
                                           person to justice and to find him a lord in public meeting.
                                        <list rend="numbered">
                                          <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
                                               he is then to be a fugitive afterwards, and he who encounters him is to strike him
                                               down as a thief.</item>
                                          <item n="2.2">And he who harbours him after that, is to pay for him with his wergild
                                               or to clear himself by an oath of that amount.</item>
                                         </list>
                                        </item>
                                        <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
                                           his guilty man, so that the king is appealed to, is to repay the value of the goods and
                                           120 shillings to the king; and he who appeals to the king before he demands justice as
                                           often as he ought, is to pay the same fine as the other would have done, if he had
                                           refused him justice.
                                        <list rend="numbered">
                                          <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
                                               known about him, is to forfeit the slave and be liable to his wergild on the first
                                               occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
                                          <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
                                               an accessory of thieves who have committed theft, is to liable to the same.</item>
                                         </list>
                                        </item>
                                        <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
                                           a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
                                           afterwards convicted at the three-fold ordeal.</item>
                                       </list>
                                      </div1>

                                      Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

                                      Example
                                      <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
                                      confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
                                      inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
                                      Cross.
                                      <list rend="simple">
                                        <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
                                           subscribed to the pious and catholic validity of this document with the sign of the Holy
                                           Cross.</item>
                                        <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
                                           the sign of the Holy Cross.</item>
                                        <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
                                           sign of the Holy Cross.</item>
                                        <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
                                           sign of the Holy Cross.</item>
                                        <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
                                           the Holy Cross.</item>
                                        <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
                                        <item>I, Æthelwine, bishop, have subscribed through delegates.</item>
                                        <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
                                           Cross.</item>
                                       </list>
                                      </p>
                                      Schematron

                                      <sch:rule context="tei:list[@type='gloss']">
                                      <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                         <elementRef key="descminOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </alternate>
                                        <alternate>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="item"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                         <sequence>
                                          <elementRef key="headLabel"
                                           minOccurs="0"/>

                                          <elementRef key="headItem"
                                           minOccurs="0"/>

                                          <sequence minOccurs="1"
                                           maxOccurs="unbounded">

                                           <elementRef key="label"/>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                           <elementRef key="item"/>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                          </sequence>
                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <list>

                                      <list> (list) contains any sequence of items organized as a list. [3.8. Lists]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
                                      type(type) describes the nature of the items in the list.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      gloss
                                      (gloss) each list item glosses some term or concept, which is given by a label element preceding the list item.
                                      index
                                      (index) each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
                                      instructions
                                      (instructions) each list item is a step in a sequence of instructions, as in a recipe.
                                      litany
                                      (litany) each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
                                      syllogism
                                      (syllogism) each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
                                      Note

                                      Previous versions of these Guidelines recommended the use of type on list to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.

                                      The formal syntax of the element declarations allows label tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

                                      Example
                                      <list rend="numbered">
                                       <item>a butcher</item>
                                       <item>a baker</item>
                                       <item>a candlestick maker, with
                                       <list rend="bulleted">
                                         <item>rings on his fingers</item>
                                         <item>bells on his toes</item>
                                        </list>
                                       </item>
                                      </list>
                                      Example
                                      <list type="syllogismrend="bulleted">
                                       <item>All Cretans are liars.</item>
                                       <item>Epimenides is a Cretan.</item>
                                       <item>ERGO Epimenides is a liar.</item>
                                      </list>
                                      Example
                                      <list type="litanyrend="simple">
                                       <item>God save us from drought.</item>
                                       <item>God save us from pestilence.</item>
                                       <item>God save us from wickedness in high places.</item>
                                       <item>Praise be to God.</item>
                                      </list>
                                      Example

                                      The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):

                                      <div1 type="section">
                                       <head>Athelstan's Ordinance</head>
                                       <list rend="numbered">
                                        <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
                                           the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
                                           eightpence.
                                        <list rend="numbered">
                                          <item n="1.1">And if anyone does spare one, he is to pay for the thief with his
                                               wergild — and the thief is to be no nearer a settlement on that account — or to
                                               clear himself by an oath of that amount.</item>
                                          <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
                                               not to be spared [whether younger or older than twelve].</item>
                                          <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
                                               then be redeemed with 120 shillings; and the kindred are to stand surety for him
                                               that he will desist for ever.</item>
                                          <item n="1.4">And if he steals after that, they are to pay for him with his wergild,
                                               or to bring him back there.</item>
                                          <item n="1.5">And if he steals after that, they are to pay for him with his wergild,
                                               whether to the king or to him to whom it rightly belongs; and everyone of those who
                                               supported him is to pay 120 shillings to the king as a fine.</item>
                                         </list>
                                        </item>
                                        <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
                                           no justice can be obtained, that one should order their kindred to fetch back such a
                                           person to justice and to find him a lord in public meeting.
                                        <list rend="numbered">
                                          <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
                                               he is then to be a fugitive afterwards, and he who encounters him is to strike him
                                               down as a thief.</item>
                                          <item n="2.2">And he who harbours him after that, is to pay for him with his wergild
                                               or to clear himself by an oath of that amount.</item>
                                         </list>
                                        </item>
                                        <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
                                           his guilty man, so that the king is appealed to, is to repay the value of the goods and
                                           120 shillings to the king; and he who appeals to the king before he demands justice as
                                           often as he ought, is to pay the same fine as the other would have done, if he had
                                           refused him justice.
                                        <list rend="numbered">
                                          <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
                                               known about him, is to forfeit the slave and be liable to his wergild on the first
                                               occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
                                          <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
                                               an accessory of thieves who have committed theft, is to liable to the same.</item>
                                         </list>
                                        </item>
                                        <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
                                           a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
                                           afterwards convicted at the three-fold ordeal.</item>
                                       </list>
                                      </div1>

                                      Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

                                      Example
                                      <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
                                      confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
                                      inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
                                      Cross.
                                      <list rend="simple">
                                        <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
                                           subscribed to the pious and catholic validity of this document with the sign of the Holy
                                           Cross.</item>
                                        <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
                                           the sign of the Holy Cross.</item>
                                        <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
                                           sign of the Holy Cross.</item>
                                        <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
                                           sign of the Holy Cross.</item>
                                        <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
                                           the Holy Cross.</item>
                                        <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
                                        <item>I, Æthelwine, bishop, have subscribed through delegates.</item>
                                        <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
                                           Cross.</item>
                                       </list>
                                      </p>
                                      Schematron

                                      <sch:rule context="tei:list[@type='gloss']">
                                      <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divTop"/>
                                         <classRef key="model.global"/>
                                         <elementRef key="descminOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </alternate>
                                        <alternate>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="item"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                         <sequence>
                                          <elementRef key="headLabel"
                                           minOccurs="0"/>

                                          <elementRef key="headItem"
                                           minOccurs="0"/>

                                          <sequence minOccurs="1"
                                           maxOccurs="unbounded">

                                           <elementRef key="label"/>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                           <elementRef key="item"/>
                                           <classRef key="model.global"
                                            minOccurs="0maxOccurs="unbounded"/>

                                          </sequence>
                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element list
                                       {
                                          tei_att.global.attributes,
                                      @@ -48,4 +48,4 @@
                                             ),
                                             ( tei_model.divBottom, tei_model.global* )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listAnnotation.html b/gl/dev/ref-listAnnotation.html index 6d5c3a3a6..0557ca6a4 100644 --- a/gl/dev/ref-listAnnotation.html +++ b/gl/dev/ref-listAnnotation.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listAnnotation>

                                      <listAnnotation> contains a list of annotations, typically encoded as annotation, annotationBlock, or note, possibly organized with nested listAnnotation elements. [16.10. The standOff Container]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.notated (@notation) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The enclosed annotations may use the general-purpose note element; or, for annotations pertaining to transcriptions of speech, the special-purpose annotationBlock element; or the annotation element, which is intended to map cleanly onto the Web Annotation Data Model.

                                      Example
                                      <standOff>
                                       <listAnnotation>
                                        <note target="#RotAM.4.15place="margin"
                                         resp="#STCtype="gloss">
                                      The spell begins to
                                           break </note>
                                        <note target="#RotAM.4.15place="bottom"
                                         resp="#JLL">
                                      The turning point of the poem...
                                        </note>
                                       </listAnnotation>
                                      </standOff>
                                      <!-- ... -->
                                      <lg xml:id="RotAM.4.15rhyme="ABCB">
                                       <l>The self-same moment I could pray;</l>
                                       <l>And from my neck so free</l>
                                       <l>The albatross fell off, and sank</l>
                                       <l>Like lead into the sea.</l>
                                      </lg>
                                      Example
                                      <listAnnotation>
                                       <annotationBlock corresp="#u1">
                                        <spanGrp type="pos">
                                         <span from="#e14.w1to="#e14.w1">CONJ</span>
                                         <span from="#e14.w2to="#e14.w2">RELPRO</span>
                                         <span from="#e14.w3to="#e14.w3">V</span>
                                        </spanGrp>
                                        <spanGrp type="prosody">
                                         <span from="#T0to="#T1">faster</span>
                                        </spanGrp>
                                       </annotationBlock>
                                      <!-- ... annotationBlocks for #u2 through #u27 here -->
                                      </listAnnotation>
                                      Example
                                      <listAnnotation>
                                       <annotation xml:id="bgann1"
                                        motivation="commenting"
                                        target="#match(bg-c1p1s1,'Gallia.*omnis')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Francis Kelsey</persName>
                                        </respStmt>
                                        <note>‘Gaul as a whole,’ contrasted with Gaul in the narrower sense, or Celtic Gaul; Celtic Gaul also is often called Gallia.</note>
                                       </annotation>
                                       <annotation xml:id="bgann2"
                                        motivation="commenting"
                                        target="#match(bg-c1p1s1,'Gallia.*divisa')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Rice Holmes</persName>
                                        </respStmt>
                                        <note>Gallia...divisa: Notice the order of the words. ‘Gaul, taken as a whole, is divided’.</note>
                                       </annotation>
                                       <annotation xml:id="bgann3"
                                        motivation="commentingtarget="#match(bg-c1p1s1,'Belgae')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Arthur Tappan Walker</persName>
                                        </respStmt>
                                        <note>Belgae -arum m., the Belgae or Belgians</note>
                                       </annotation>
                                       <annotation xml:id="bgann4"
                                        motivation="commentingtarget="#match(bg-c1p1s1,'Aquitani')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Arthur Tappan Walker</persName>
                                        </respStmt>
                                        <note>Aquitani, -orum m.: the Aquitani, inhabiting southwestern Gaul</note>
                                       </annotation>
                                       <annotation xml:id="bgann5"
                                        motivation="commentingtarget="#match(bg-c1p1s1,'Celtae')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Arthur Tappan Walker</persName>
                                        </respStmt>
                                        <note>Celtae, -arum m: the Celtae or Celts</note>
                                       </annotation>
                                       <annotation xml:id="bgann6"
                                        motivation="commenting"
                                        target="#match(bg-c1p1s2,'Gallos(.|\n)*dividit')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>William Francis Allen</persName>
                                         <persName>Joseph Henry Allen</persName>
                                         <persName>Harry Pratt Judson</persName>
                                        </respStmt>
                                        <note>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.’</note>
                                       </annotation>
                                      </listAnnotation>
                                      <!-- Elsewhere in the document -->
                                      <text>
                                       <body>
                                        <div type="edition">
                                         <div type="textpartsubtype="chapter"
                                          n="1xml:id="bg-c1">

                                          <p n="1xml:id="bg-c1p1">
                                           <seg n="1xml:id="bg-c1p1s1">Gallia est omnis divisa in partes tres, quarum unam incolunt Belgae, aliam
                                                 Aquitani, tertiam qui ipsorum lingua Celtae, nostra Galli appellantur.</seg>
                                           <seg n="2xml:id="bg-c1p1s2">Hi omnes lingua, institutis, legibus inter se differunt. Gallos ab Aquitanis
                                                 Garumna flumen, a Belgis Matrona et Sequana dividit.</seg>
                                      <!-- ... -->
                                          </p>
                                         </div>
                                        </div>
                                       </body>
                                      </text>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.labelLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.annotationLike"/>
                                         <elementRef key="listAnnotation"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listAnnotation>

                                      <listAnnotation> contains a list of annotations, typically encoded as annotation, annotationBlock, or note, possibly organized with nested listAnnotation elements. [16.10. The standOff Container]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.notated (@notation) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The enclosed annotations may use the general-purpose note element; or, for annotations pertaining to transcriptions of speech, the special-purpose annotationBlock element; or the annotation element, which is intended to map cleanly onto the Web Annotation Data Model.

                                      Example
                                      <standOff>
                                       <listAnnotation>
                                        <note target="#RotAM.4.15place="margin"
                                         resp="#STCtype="gloss">
                                      The spell begins to
                                           break </note>
                                        <note target="#RotAM.4.15place="bottom"
                                         resp="#JLL">
                                      The turning point of the poem...
                                        </note>
                                       </listAnnotation>
                                      </standOff>
                                      <!-- ... -->
                                      <lg xml:id="RotAM.4.15rhyme="ABCB">
                                       <l>The self-same moment I could pray;</l>
                                       <l>And from my neck so free</l>
                                       <l>The albatross fell off, and sank</l>
                                       <l>Like lead into the sea.</l>
                                      </lg>
                                      Example
                                      <listAnnotation>
                                       <annotationBlock corresp="#u1">
                                        <spanGrp type="pos">
                                         <span from="#e14.w1to="#e14.w1">CONJ</span>
                                         <span from="#e14.w2to="#e14.w2">RELPRO</span>
                                         <span from="#e14.w3to="#e14.w3">V</span>
                                        </spanGrp>
                                        <spanGrp type="prosody">
                                         <span from="#T0to="#T1">faster</span>
                                        </spanGrp>
                                       </annotationBlock>
                                      <!-- ... annotationBlocks for #u2 through #u27 here -->
                                      </listAnnotation>
                                      Example
                                      <listAnnotation>
                                       <annotation xml:id="bgann1"
                                        motivation="commenting"
                                        target="#match(bg-c1p1s1,'Gallia.*omnis')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Francis Kelsey</persName>
                                        </respStmt>
                                        <note>‘Gaul as a whole,’ contrasted with Gaul in the narrower sense, or Celtic Gaul; Celtic Gaul also is often called Gallia.</note>
                                       </annotation>
                                       <annotation xml:id="bgann2"
                                        motivation="commenting"
                                        target="#match(bg-c1p1s1,'Gallia.*divisa')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Rice Holmes</persName>
                                        </respStmt>
                                        <note>Gallia...divisa: Notice the order of the words. ‘Gaul, taken as a whole, is divided’.</note>
                                       </annotation>
                                       <annotation xml:id="bgann3"
                                        motivation="commentingtarget="#match(bg-c1p1s1,'Belgae')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Arthur Tappan Walker</persName>
                                        </respStmt>
                                        <note>Belgae -arum m., the Belgae or Belgians</note>
                                       </annotation>
                                       <annotation xml:id="bgann4"
                                        motivation="commentingtarget="#match(bg-c1p1s1,'Aquitani')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Arthur Tappan Walker</persName>
                                        </respStmt>
                                        <note>Aquitani, -orum m.: the Aquitani, inhabiting southwestern Gaul</note>
                                       </annotation>
                                       <annotation xml:id="bgann5"
                                        motivation="commentingtarget="#match(bg-c1p1s1,'Celtae')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>Arthur Tappan Walker</persName>
                                        </respStmt>
                                        <note>Celtae, -arum m: the Celtae or Celts</note>
                                       </annotation>
                                       <annotation xml:id="bgann6"
                                        motivation="commenting"
                                        target="#match(bg-c1p1s2,'Gallos(.|\n)*dividit')">

                                        <respStmt>
                                         <resp>creator</resp>
                                         <persName>William Francis Allen</persName>
                                         <persName>Joseph Henry Allen</persName>
                                         <persName>Harry Pratt Judson</persName>
                                        </respStmt>
                                        <note>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.’</note>
                                       </annotation>
                                      </listAnnotation>
                                      <!-- Elsewhere in the document -->
                                      <text>
                                       <body>
                                        <div type="edition">
                                         <div type="textpartsubtype="chapter"
                                          n="1xml:id="bg-c1">

                                          <p n="1xml:id="bg-c1p1">
                                           <seg n="1xml:id="bg-c1p1s1">Gallia est omnis divisa in partes tres, quarum unam incolunt Belgae, aliam
                                                 Aquitani, tertiam qui ipsorum lingua Celtae, nostra Galli appellantur.</seg>
                                           <seg n="2xml:id="bg-c1p1s2">Hi omnes lingua, institutis, legibus inter se differunt. Gallos ab Aquitanis
                                                 Garumna flumen, a Belgis Matrona et Sequana dividit.</seg>
                                      <!-- ... -->
                                          </p>
                                         </div>
                                        </div>
                                       </body>
                                      </text>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.labelLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.annotationLike"/>
                                         <elementRef key="listAnnotation"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listAnnotation
                                       {
                                          tei_att.global.attributes,
                                      @@ -33,4 +33,4 @@
                                             tei_model.labelLike*,
                                             ( tei_model.annotationLike | tei_listAnnotation )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listApp.html b/gl/dev/ref-listApp.html index d65cac423..f401a6a2a 100644 --- a/gl/dev/ref-listApp.html +++ b/gl/dev/ref-listApp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listApp>

                                      <listApp> (list of apparatus entries) contains a list of apparatus entries. [12.2. Linking the Apparatus to the Text]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc head
                                      textcrit: app listApp
                                      Note

                                      listApp elements would normally be located in the back part of a document, but they may appear elsewhere.

                                      Example

                                      In the following example from the exegetical Yasna, the base text is encoded in the body of the document, and two separate listApp elements are used in the back, containing variant readings written in different scripts.

                                      <body>
                                       <div>
                                        <lg type="stanzaxml:id="Y-36.01"
                                         xml:lang="pal-Avstrend="italic">

                                         <l xml:id="Y-36.01_L-1">
                                          <w xml:id="Y-36.01_L1_W-01">ahiiā</w>
                                          <w xml:id="Y-36.01_L1_W-02">ϑβā</w>
                                          <w xml:id="Y-36.01_L1_W-03">āϑrō</w>
                                          <w xml:id="Y-36.01_L1_W-04">vərəzə̄nā</w>
                                          <w xml:id="Y-36.01_L1_W-05">paouruiiē</w>
                                          <w xml:id="Y-36.01_L1_W-06">pairijasāmaiδē</w>
                                          <w xml:id="Y-36.01_L1_W-07">mazdā</w>
                                          <w xml:id="Y-36.01_L1_W-08">ahurā</w>
                                         </l>
                                      <!-- ... -->
                                        </lg>
                                       </div>
                                      </body>
                                      <!-- ... -->
                                      <back>
                                       <div>
                                        <listApp xml:id="CA_Y-36"
                                         xml:lang="pal-Avst">

                                         <head>Variants from witnesses in Avestan script</head>
                                         <app from="#Y-36.01_L1_W-01">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ahiiā</rdg>
                                         </app>
                                         <app from="#Y-36.01_L1_W-02">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ϑβā</rdg>
                                         </app>
                                         <app from="#Y-36.01_L1_W-03">
                                          <rdg wit="#Pt4 #J2 #M1">āϑrō</rdg>
                                          <rdg wit="#F2">āϑrōi</rdg>
                                         </app>
                                      <!-- ... -->
                                        </listApp>
                                        <listApp xml:id="CA_PY-36"
                                         xml:lang="pal-Phlv">

                                         <head>Variants from witnesses written in Pahlavi script</head>
                                         <app from="#PY-36.01_L1_W-01">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ʾytwnˈ</rdg>
                                         </app>
                                         <app from="#PY-36.01_L1_W-02">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ʾwˈ</rdg>
                                         </app>
                                         <app from="#PY-36.01_L1_W-03">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ḤNʾ</rdg>
                                         </app>
                                      <!-- ... -->
                                        </listApp>
                                       </div>
                                      </back>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="app"/>
                                         <elementRef key="listApp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listApp>

                                      <listApp> (list of apparatus entries) contains a list of apparatus entries. [12.2. Linking the Apparatus to the Text]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc head
                                      textcrit: app listApp
                                      Note

                                      listApp elements would normally be located in the back part of a document, but they may appear elsewhere.

                                      Example

                                      In the following example from the exegetical Yasna, the base text is encoded in the body of the document, and two separate listApp elements are used in the back, containing variant readings written in different scripts.

                                      <body>
                                       <div>
                                        <lg type="stanzaxml:id="Y-36.01"
                                         xml:lang="pal-Avstrend="italic">

                                         <l xml:id="Y-36.01_L-1">
                                          <w xml:id="Y-36.01_L1_W-01">ahiiā</w>
                                          <w xml:id="Y-36.01_L1_W-02">ϑβā</w>
                                          <w xml:id="Y-36.01_L1_W-03">āϑrō</w>
                                          <w xml:id="Y-36.01_L1_W-04">vərəzə̄nā</w>
                                          <w xml:id="Y-36.01_L1_W-05">paouruiiē</w>
                                          <w xml:id="Y-36.01_L1_W-06">pairijasāmaiδē</w>
                                          <w xml:id="Y-36.01_L1_W-07">mazdā</w>
                                          <w xml:id="Y-36.01_L1_W-08">ahurā</w>
                                         </l>
                                      <!-- ... -->
                                        </lg>
                                       </div>
                                      </body>
                                      <!-- ... -->
                                      <back>
                                       <div>
                                        <listApp xml:id="CA_Y-36"
                                         xml:lang="pal-Avst">

                                         <head>Variants from witnesses in Avestan script</head>
                                         <app from="#Y-36.01_L1_W-01">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ahiiā</rdg>
                                         </app>
                                         <app from="#Y-36.01_L1_W-02">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ϑβā</rdg>
                                         </app>
                                         <app from="#Y-36.01_L1_W-03">
                                          <rdg wit="#Pt4 #J2 #M1">āϑrō</rdg>
                                          <rdg wit="#F2">āϑrōi</rdg>
                                         </app>
                                      <!-- ... -->
                                        </listApp>
                                        <listApp xml:id="CA_PY-36"
                                         xml:lang="pal-Phlv">

                                         <head>Variants from witnesses written in Pahlavi script</head>
                                         <app from="#PY-36.01_L1_W-01">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ʾytwnˈ</rdg>
                                         </app>
                                         <app from="#PY-36.01_L1_W-02">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ʾwˈ</rdg>
                                         </app>
                                         <app from="#PY-36.01_L1_W-03">
                                          <rdg wit="#Pt4 #F2 #J2 #M1">ḤNʾ</rdg>
                                         </app>
                                      <!-- ... -->
                                        </listApp>
                                       </div>
                                      </back>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="app"/>
                                         <elementRef key="listApp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listApp
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.declarable.attributes,
                                          tei_att.typed.attributes,
                                          ( tei_model.headLike*, tei_desc*, ( tei_app | tei_listApp )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listBibl.html b/gl/dev/ref-listBibl.html index 71da6472e..e5370acbc 100644 --- a/gl/dev/ref-listBibl.html +++ b/gl/dev/ref-listBibl.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listBibl>

                                      <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      header: biblFull
                                      linking: anchor
                                      msdescription: msDesc
                                      transcr: fw
                                      Example
                                      <listBibl>
                                       <head>Works consulted</head>
                                       <bibl>Blain, Clements and Grundy: Feminist Companion to
                                         Literature in English (Yale, 1990)
                                       </bibl>
                                       <biblStruct>
                                        <analytic>
                                         <title>The Interesting story of the Children in the Wood</title>
                                        </analytic>
                                        <monogr>
                                         <title>The Penny Histories</title>
                                         <author>Victor E Neuberg</author>
                                         <imprint>
                                          <publisher>OUP</publisher>
                                          <date>1968</date>
                                         </imprint>
                                        </monogr>
                                       </biblStruct>
                                      </listBibl>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.milestoneLike"
                                          minOccurs="1maxOccurs="1"/>

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.biblLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.milestoneLike"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listBibl>

                                      <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      header: biblFull
                                      linking: anchor
                                      msdescription: msDesc
                                      transcr: fw
                                      Example
                                      <listBibl>
                                       <head>Works consulted</head>
                                       <bibl>Blain, Clements and Grundy: Feminist Companion to
                                         Literature in English (Yale, 1990)
                                       </bibl>
                                       <biblStruct>
                                        <analytic>
                                         <title>The Interesting story of the Children in the Wood</title>
                                        </analytic>
                                        <monogr>
                                         <title>The Penny Histories</title>
                                         <author>Victor E Neuberg</author>
                                         <imprint>
                                          <publisher>OUP</publisher>
                                          <date>1968</date>
                                         </imprint>
                                        </monogr>
                                       </biblStruct>
                                      </listBibl>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.milestoneLike"
                                          minOccurs="1maxOccurs="1"/>

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.biblLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.milestoneLike"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listBibl
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                                ( tei_model.milestoneLike | tei_relation | tei_listRelation )*
                                             )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listChange.html b/gl/dev/ref-listChange.html index 0b21b4cc8..4067b0d0c 100644 --- a/gl/dev/ref-listChange.html +++ b/gl/dev/ref-listChange.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listChange>

                                      <listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 11.7. Identifying Changes and Revisions]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype)
                                      orderedindicates whether the ordering of its child change elements is to be considered significant or not
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Default true
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      When this element appears within the creation element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the revisionDesc element, it documents only changes made during the evolution of the encoded representation of that text.

                                      Example
                                      <revisionDesc>
                                       <listChange>
                                        <change when="1991-11-11who="#LB"> deleted chapter 10 </change>
                                        <change when="1991-11-02who="#MSM"> completed first draft </change>
                                       </listChange>
                                      </revisionDesc>
                                      Example
                                      <profileDesc>
                                       <creation>
                                        <listChange ordered="true">
                                         <change xml:id="CHG-1">First stage, written in ink by a writer</change>
                                         <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>
                                         <change xml:id="CHG-3">Fixation of the revised passages and further revisions by
                                             Goethe using ink</change>
                                         <change xml:id="CHG-4">Addition of another stanza in a different hand,
                                             probably at a later stage</change>
                                        </listChange>
                                       </creation>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="listChange"/>
                                         <elementRef key="change"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listChange>

                                      <listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 11.7. Identifying Changes and Revisions]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype)
                                      orderedindicates whether the ordering of its child change elements is to be considered significant or not
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Default true
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      When this element appears within the creation element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the revisionDesc element, it documents only changes made during the evolution of the encoded representation of that text.

                                      Example
                                      <revisionDesc>
                                       <listChange>
                                        <change when="1991-11-11who="#LB"> deleted chapter 10 </change>
                                        <change when="1991-11-02who="#MSM"> completed first draft </change>
                                       </listChange>
                                      </revisionDesc>
                                      Example
                                      <profileDesc>
                                       <creation>
                                        <listChange ordered="true">
                                         <change xml:id="CHG-1">First stage, written in ink by a writer</change>
                                         <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>
                                         <change xml:id="CHG-3">Fixation of the revised passages and further revisions by
                                             Goethe using ink</change>
                                         <change xml:id="CHG-4">Addition of another stanza in a different hand,
                                             probably at a later stage</change>
                                        </listChange>
                                       </creation>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="listChange"/>
                                         <elementRef key="change"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listChange
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          attribute ordered { teidata.truthValue }?,
                                          ( tei_desc*, ( tei_listChange | tei_change )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listEvent.html b/gl/dev/ref-listEvent.html index 71626705e..ecf3998b7 100644 --- a/gl/dev/ref-listEvent.html +++ b/gl/dev/ref-listEvent.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listEvent>

                                      <listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [13.3.1. Basic Principles]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <listEvent>
                                       <head>Battles of the American Civil War: Kentucky</head>
                                       <event xml:id="event01when="1861-09-19">
                                        <label>Barbourville</label>
                                        <desc>The Battle of Barbourville was one of the early engagements of
                                           the American Civil War. It occurred September 19, 1861, in Knox
                                           County, Kentucky during the campaign known as the Kentucky Confederate
                                           Offensive. The battle is considered the first Confederate victory in
                                           the commonwealth, and threw a scare into Federal commanders, who
                                           rushed troops to central Kentucky in an effort to repel the invasion,
                                           which was finally thwarted at the <ref target="#event02">Battle of
                                             Camp Wildcat</ref> in October.</desc>
                                       </event>
                                       <event xml:id="event02when="1861-10-21">
                                        <label>Camp Wild Cat</label>
                                        <desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp
                                           Wild Cat) was one of the early engagements of the American Civil
                                           War. It occurred October 21, 1861, in northern Laurel County, Kentucky
                                           during the campaign known as the Kentucky Confederate Offensive. The
                                           battle is considered one of the very first Union victories, and marked
                                           the first engagement of troops in the commonwealth of Kentucky.</desc>
                                       </event>
                                       <event xml:id="event03from="1864-06-11"
                                        to="1864-06-12">

                                        <label>Cynthiana</label>
                                        <desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement
                                           during the American Civil War that was fought on June 11 and 12, 1864,
                                           in Harrison County, Kentucky, near the town of Cynthiana. A part of
                                           Confederate Brigadier General John Hunt Morgan's 1864 Raid into
                                           Kentucky, the battle resulted in a victory by Union forces over the
                                           raiders and saved the town from capture.</desc>
                                       </event>
                                      </listEvent>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.eventLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listEvent>

                                      <listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [13.3.1. Basic Principles]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <listEvent>
                                       <head>Battles of the American Civil War: Kentucky</head>
                                       <event xml:id="event01when="1861-09-19">
                                        <label>Barbourville</label>
                                        <desc>The Battle of Barbourville was one of the early engagements of
                                           the American Civil War. It occurred September 19, 1861, in Knox
                                           County, Kentucky during the campaign known as the Kentucky Confederate
                                           Offensive. The battle is considered the first Confederate victory in
                                           the commonwealth, and threw a scare into Federal commanders, who
                                           rushed troops to central Kentucky in an effort to repel the invasion,
                                           which was finally thwarted at the <ref target="#event02">Battle of
                                             Camp Wildcat</ref> in October.</desc>
                                       </event>
                                       <event xml:id="event02when="1861-10-21">
                                        <label>Camp Wild Cat</label>
                                        <desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp
                                           Wild Cat) was one of the early engagements of the American Civil
                                           War. It occurred October 21, 1861, in northern Laurel County, Kentucky
                                           during the campaign known as the Kentucky Confederate Offensive. The
                                           battle is considered one of the very first Union victories, and marked
                                           the first engagement of troops in the commonwealth of Kentucky.</desc>
                                       </event>
                                       <event xml:id="event03from="1864-06-11"
                                        to="1864-06-12">

                                        <label>Cynthiana</label>
                                        <desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement
                                           during the American Civil War that was fought on June 11 and 12, 1864,
                                           in Harrison County, Kentucky, near the town of Cynthiana. A part of
                                           Confederate Brigadier General John Hunt Morgan's 1864 Raid into
                                           Kentucky, the battle resulted in a victory by Union forces over the
                                           raiders and saved the town from capture.</desc>
                                       </event>
                                      </listEvent>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.eventLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listEvent
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                             ( tei_relation | tei_listRelation )*,
                                             ( tei_model.eventLike+, ( tei_relation | tei_listRelation )* )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listNym.html b/gl/dev/ref-listNym.html index 02ca8b6ca..8716b9779 100644 --- a/gl/dev/ref-listNym.html +++ b/gl/dev/ref-listNym.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listNym>

                                      <listNym> (list of canonical names) contains a list of nyms, that is, standardized names for any thing. [13.3.6. Names and Nyms]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish lists of names of a particular type if convenient.

                                      Example
                                      <listNym type="floral">
                                       <nym xml:id="ROSE">
                                        <form>Rose</form>
                                       </nym>
                                       <nym xml:id="DAISY">
                                        <form>Daisy</form>
                                        <etym>Contraction of <mentioned>day's eye</mentioned>
                                        </etym>
                                       </nym>
                                       <nym xml:id="HTHR">
                                        <form>Heather</form>
                                       </nym>
                                      </listNym>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="nymminOccurs="1"
                                           maxOccurs="1"/>

                                          <elementRef key="listNymminOccurs="1"
                                           maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listNym>

                                      <listNym> (list of canonical names) contains a list of nyms, that is, standardized names for any thing. [13.3.6. Names and Nyms]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish lists of names of a particular type if convenient.

                                      Example
                                      <listNym type="floral">
                                       <nym xml:id="ROSE">
                                        <form>Rose</form>
                                       </nym>
                                       <nym xml:id="DAISY">
                                        <form>Daisy</form>
                                        <etym>Contraction of <mentioned>day's eye</mentioned>
                                        </etym>
                                       </nym>
                                       <nym xml:id="HTHR">
                                        <form>Heather</form>
                                       </nym>
                                      </listNym>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="nymminOccurs="1"
                                           maxOccurs="1"/>

                                          <elementRef key="listNymminOccurs="1"
                                           maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listNym
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                             ( tei_relation | tei_listRelation )*,
                                             ( ( tei_nym | tei_listNym )+, ( tei_relation | tei_listRelation )* )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listObject.html b/gl/dev/ref-listObject.html index 79cbb8980..12db26f7b 100644 --- a/gl/dev/ref-listObject.html +++ b/gl/dev/ref-listObject.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listObject>

                                      <listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [13.3.5. Objects]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish different types of objects.

                                      Example
                                      <listObject>
                                       <object xml:id="AlfredJewel">
                                        <objectIdentifier>
                                         <country>United Kingdom</country>
                                         <region>Oxfordshire</region>
                                         <settlement>Oxford</settlement>
                                         <institution>University of Oxford</institution>
                                         <repository>Ashmolean Museum</repository>
                                         <collection>English Treasures</collection>
                                         <idno type="ashmolean">AN1836p.135.371</idno>
                                         <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>
                                         <objectName>Alfred Jewel</objectName>
                                        </objectIdentifier>
                                        <physDesc>
                                         <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>
                                             surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. 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'. </p>
                                        </physDesc>
                                        <history>
                                         <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and was
                                             most likely made in <origPlace>England</origPlace>. </origin>
                                         <provenance when="1693">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. </provenance>
                                         <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical
                                             Transactions of the Royal Society.</provenance>
                                         <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in the
                                             Ashmolean Museum in Oxford. </acquisition>
                                        </history>
                                       </object>
                                      </listObject>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.objectLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listObject>

                                      <listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [13.3.5. Objects]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish different types of objects.

                                      Example
                                      <listObject>
                                       <object xml:id="AlfredJewel">
                                        <objectIdentifier>
                                         <country>United Kingdom</country>
                                         <region>Oxfordshire</region>
                                         <settlement>Oxford</settlement>
                                         <institution>University of Oxford</institution>
                                         <repository>Ashmolean Museum</repository>
                                         <collection>English Treasures</collection>
                                         <idno type="ashmolean">AN1836p.135.371</idno>
                                         <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>
                                         <objectName>Alfred Jewel</objectName>
                                        </objectIdentifier>
                                        <physDesc>
                                         <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>
                                             surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. 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'. </p>
                                        </physDesc>
                                        <history>
                                         <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and was
                                             most likely made in <origPlace>England</origPlace>. </origin>
                                         <provenance when="1693">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. </provenance>
                                         <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical
                                             Transactions of the Royal Society.</provenance>
                                         <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in the
                                             Ashmolean Museum in Oxford. </acquisition>
                                        </history>
                                       </object>
                                      </listObject>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.objectLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listObject
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                             ( tei_relation | tei_listRelation )*,
                                             ( tei_model.objectLike+, ( tei_relation | tei_listRelation )* )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listOrg.html b/gl/dev/ref-listOrg.html index fa61864ae..6e71a124e 100644 --- a/gl/dev/ref-listOrg.html +++ b/gl/dev/ref-listOrg.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listOrg>

                                      <listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [13.2.2. Organizational Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish lists of organizations of a particular type if convenient.

                                      Example
                                      <listOrg>
                                       <head>Libyans</head>
                                       <org>
                                        <orgName>Adyrmachidae</orgName>
                                        <desc>These people have, in most points, the same customs as the Egyptians, but
                                           use the costume of the Libyans. Their women wear on each leg a ring made of
                                           bronze [...]</desc>
                                       </org>
                                       <org>
                                        <orgName>Nasamonians</orgName>
                                        <desc>In summer they leave their flocks and herds upon the sea-shore, and go up
                                           the country to a place called Augila, where they gather the dates from the
                                           palms [...]</desc>
                                       </org>
                                       <org>
                                        <orgName>Garamantians</orgName>
                                        <desc>[...] avoid all society or intercourse with their fellow-men, have no
                                           weapon of war, and do not know how to defend themselves. [...]</desc>
                                      <!-- ... -->
                                       </org>
                                      </listOrg>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="orgminOccurs="1"
                                           maxOccurs="1"/>

                                          <elementRef key="listOrgminOccurs="1"
                                           maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listOrg>

                                      <listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [13.2.2. Organizational Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish lists of organizations of a particular type if convenient.

                                      Example
                                      <listOrg>
                                       <head>Libyans</head>
                                       <org>
                                        <orgName>Adyrmachidae</orgName>
                                        <desc>These people have, in most points, the same customs as the Egyptians, but
                                           use the costume of the Libyans. Their women wear on each leg a ring made of
                                           bronze [...]</desc>
                                       </org>
                                       <org>
                                        <orgName>Nasamonians</orgName>
                                        <desc>In summer they leave their flocks and herds upon the sea-shore, and go up
                                           the country to a place called Augila, where they gather the dates from the
                                           palms [...]</desc>
                                       </org>
                                       <org>
                                        <orgName>Garamantians</orgName>
                                        <desc>[...] avoid all society or intercourse with their fellow-men, have no
                                           weapon of war, and do not know how to defend themselves. [...]</desc>
                                      <!-- ... -->
                                       </org>
                                      </listOrg>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="orgminOccurs="1"
                                           maxOccurs="1"/>

                                          <elementRef key="listOrgminOccurs="1"
                                           maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listOrg
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                             ( tei_relation | tei_listRelation )*,
                                             ( ( tei_org | tei_listOrg )+, ( tei_relation | tei_listRelation )* )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listPerson.html b/gl/dev/ref-listPerson.html index 72c650913..92999efaf 100644 --- a/gl/dev/ref-listPerson.html +++ b/gl/dev/ref-listPerson.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listPerson>

                                      <listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish lists of people of a particular type if convenient.

                                      Example
                                      <listPerson type="respondents">
                                       <personGrp xml:id="PXXX"/>
                                       <person xml:id="P1234sex="2age="mid"/>
                                       <person xml:id="P4332sex="1age="mid"/>
                                       <listRelation>
                                        <relation type="personalname="spouse"
                                         mutual="#P1234 #P4332"/>

                                       </listRelation>
                                      </listPerson>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.personLike"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listPerson"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listPerson>

                                      <listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish lists of people of a particular type if convenient.

                                      Example
                                      <listPerson type="respondents">
                                       <personGrp xml:id="PXXX"/>
                                       <person xml:id="P1234sex="2age="mid"/>
                                       <person xml:id="P4332sex="1age="mid"/>
                                       <listRelation>
                                        <relation type="personalname="spouse"
                                         mutual="#P1234 #P4332"/>

                                       </listRelation>
                                      </listPerson>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.personLike"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listPerson"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listPerson
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                                ( tei_relation | tei_listRelation )*
                                             )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listPlace.html b/gl/dev/ref-listPlace.html index fcfe5775b..7ad2f0303 100644 --- a/gl/dev/ref-listPlace.html +++ b/gl/dev/ref-listPlace.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listPlace>

                                      <listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 13.3.4. Places]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <listPlace type="offshoreIslands">
                                       <place>
                                        <placeName>La roche qui pleure</placeName>
                                       </place>
                                       <place>
                                        <placeName>Ile aux cerfs</placeName>
                                       </place>
                                      </listPlace>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.placeLike"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listPlace"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listPlace>

                                      <listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 13.3.4. Places]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declarable (@default) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <listPlace type="offshoreIslands">
                                       <place>
                                        <placeName>La roche qui pleure</placeName>
                                       </place>
                                       <place>
                                        <placeName>Ile aux cerfs</placeName>
                                       </place>
                                      </listPlace>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="relationminOccurs="1"
                                          maxOccurs="1"/>

                                         <elementRef key="listRelation"
                                          minOccurs="1maxOccurs="1"/>

                                        </alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.placeLike"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listPlace"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listPlace
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                                ( tei_relation | tei_listRelation )*
                                             )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listPrefixDef.html b/gl/dev/ref-listPrefixDef.html index 09e8a57ca..2824fd8d9 100644 --- a/gl/dev/ref-listPrefixDef.html +++ b/gl/dev/ref-listPrefixDef.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listPrefixDef>

                                      <listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      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 p element.

                                      <listPrefixDef>
                                       <prefixDef ident="psn"
                                        matchPattern="([A-Z]+)"
                                        replacementPattern="personography.xml#$1">

                                        <p> Private URIs using the <code>psn</code>
                                           prefix are pointers to <gi>person</gi>
                                           elements in the personography.xml file.
                                           For example, <code>psn:MDH</code>
                                           dereferences to <code>personography.xml#MDH</code>.
                                        </p>
                                       </prefixDef>
                                       <prefixDef ident="bibl"
                                        matchPattern="([a-z]+[a-z0-9]*)"
                                        replacementPattern="http://www.example.com/getBibl.xql?id=$1">

                                        <p> Private URIs using the <code>bibl</code> prefix can be
                                           expanded to form URIs which retrieve the relevant
                                           bibliographical reference from www.example.com.
                                        </p>
                                       </prefixDef>
                                      </listPrefixDef>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="prefixDef"/>
                                         <elementRef key="listPrefixDef"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listPrefixDef>

                                      <listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      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 p element.

                                      <listPrefixDef>
                                       <prefixDef ident="psn"
                                        matchPattern="([A-Z]+)"
                                        replacementPattern="personography.xml#$1">

                                        <p> Private URIs using the <code>psn</code>
                                           prefix are pointers to <gi>person</gi>
                                           elements in the personography.xml file.
                                           For example, <code>psn:MDH</code>
                                           dereferences to <code>personography.xml#MDH</code>.
                                        </p>
                                       </prefixDef>
                                       <prefixDef ident="bibl"
                                        matchPattern="([a-z]+[a-z0-9]*)"
                                        replacementPattern="http://www.example.com/getBibl.xql?id=$1">

                                        <p> Private URIs using the <code>bibl</code> prefix can be
                                           expanded to form URIs which retrieve the relevant
                                           bibliographical reference from www.example.com.
                                        </p>
                                       </prefixDef>
                                      </listPrefixDef>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="prefixDef"/>
                                         <elementRef key="listPrefixDef"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listPrefixDef
                                       {
                                          tei_att.global.attributes,
                                          ( tei_desc*, ( tei_prefixDef | tei_listPrefixDef )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listRelation.html b/gl/dev/ref-listRelation.html index f9fb0237e..735bda85b 100644 --- a/gl/dev/ref-listRelation.html +++ b/gl/dev/ref-listRelation.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listRelation>

                                      <listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc head p
                                      linking: ab
                                      Note

                                      May contain a prose description organized as paragraphs, or a sequence of relation elements.

                                      Example
                                      <listPerson>
                                       <person xml:id="pp1">
                                      <!-- data about person pp1 -->
                                       </person>
                                       <person xml:id="pp2">
                                      <!-- data about person pp1 -->
                                       </person>
                                      <!-- more person (pp3, pp4) elements here -->
                                       <listRelation type="personal">
                                        <relation name="parent"
                                         active="#pp1 #pp2passive="#pp3 #pp4"/>

                                        <relation name="spouse"
                                         mutual="#pp1 #pp2"/>

                                       </listRelation>
                                       <listRelation type="social">
                                        <relation name="employeractive="#pp1"
                                         passive="#pp3 #pp5 #pp6 #pp7"/>

                                       </listRelation>
                                      </listPerson>

                                      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.

                                      Example
                                      <listPerson>
                                       <person xml:id="en_pp1">
                                      <!-- data about person en_pp1 -->
                                       </person>
                                       <person xml:id="en_pp2">
                                      <!-- data about person en_pp2 -->
                                       </person>
                                      <!-- more person (en_pp3, en_pp4) elements here -->
                                      </listPerson>
                                      <listPlace>
                                       <place xml:id="en_pl1">
                                      <!-- data about place en_pl1 -->
                                       </place>
                                      <!-- more place (en_pl2, en_pl3) elements here -->
                                      </listPlace>
                                      <listRelation>
                                       <relation name="residence"
                                        active="#en_pp1 #en_pp2passive="#en_pl1"/>

                                      </listRelation>

                                      The persons with identifiers en_pp1 and en_pp2 live in en_pl1.

                                      Example
                                      <listRelation>
                                       <p>All speakers are members of the Ceruli family, born in Naples.</p>
                                      </listRelation>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1maxOccurs="1">
                                         <classRef key="model.pLike"/>
                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listRelation>

                                      <listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc head p
                                      linking: ab
                                      Note

                                      May contain a prose description organized as paragraphs, or a sequence of relation elements.

                                      Example
                                      <listPerson>
                                       <person xml:id="pp1">
                                      <!-- data about person pp1 -->
                                       </person>
                                       <person xml:id="pp2">
                                      <!-- data about person pp1 -->
                                       </person>
                                      <!-- more person (pp3, pp4) elements here -->
                                       <listRelation type="personal">
                                        <relation name="parent"
                                         active="#pp1 #pp2passive="#pp3 #pp4"/>

                                        <relation name="spouse"
                                         mutual="#pp1 #pp2"/>

                                       </listRelation>
                                       <listRelation type="social">
                                        <relation name="employeractive="#pp1"
                                         passive="#pp3 #pp5 #pp6 #pp7"/>

                                       </listRelation>
                                      </listPerson>

                                      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.

                                      Example
                                      <listPerson>
                                       <person xml:id="en_pp1">
                                      <!-- data about person en_pp1 -->
                                       </person>
                                       <person xml:id="en_pp2">
                                      <!-- data about person en_pp2 -->
                                       </person>
                                      <!-- more person (en_pp3, en_pp4) elements here -->
                                      </listPerson>
                                      <listPlace>
                                       <place xml:id="en_pl1">
                                      <!-- data about place en_pl1 -->
                                       </place>
                                      <!-- more place (en_pl2, en_pl3) elements here -->
                                      </listPlace>
                                      <listRelation>
                                       <relation name="residence"
                                        active="#en_pp1 #en_pp2passive="#en_pl1"/>

                                      </listRelation>

                                      The persons with identifiers en_pp1 and en_pp2 live in en_pl1.

                                      Example
                                      <listRelation>
                                       <p>All speakers are members of the Ceruli family, born in Naples.</p>
                                      </listRelation>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1maxOccurs="1">
                                         <classRef key="model.pLike"/>
                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="relation"
                                           minOccurs="1maxOccurs="1"/>

                                          <elementRef key="listRelation"
                                           minOccurs="1maxOccurs="1"/>

                                         </alternate>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listRelation
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                             tei_desc*,
                                             ( tei_model.pLike | ( tei_relation | tei_listRelation )+ )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-listTranspose.html b/gl/dev/ref-listTranspose.html index ec570f5fa..8c32b1294 100644 --- a/gl/dev/ref-listTranspose.html +++ b/gl/dev/ref-listTranspose.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <listTranspose>

                                      <listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [11.3.4.5. Transpositions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      transcr: transpose
                                      Example
                                      <listTranspose>
                                       <transpose>
                                        <ptr target="#ib02"/>
                                        <ptr target="#ib01"/>
                                       </transpose>
                                      </listTranspose>

                                      This example might be used for a source document which indicates in some way that the elements identified by ib02 and code ib01 should be read in that order (ib02 followed by ib01), rather than in the reading order in which they are presented in the source.

                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="transposeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <listTranspose>

                                      <listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [11.3.4.5. Transpositions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      transcr: transpose
                                      Example
                                      <listTranspose>
                                       <transpose>
                                        <ptr target="#ib02"/>
                                        <ptr target="#ib01"/>
                                       </transpose>
                                      </listTranspose>

                                      This example might be used for a source document which indicates in some way that the elements identified by ib02 and code ib01 should be read in that order (ib02 followed by ib01), rather than in the reading order in which they are presented in the source.

                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="transposeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element listTranspose
                                       {
                                          tei_att.global.attributes,
                                          ( tei_desc*, tei_transpose+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-localProp.html b/gl/dev/ref-localProp.html index 6e32a1477..15d020c65 100644 --- a/gl/dev/ref-localProp.html +++ b/gl/dev/ref-localProp.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <localProp>

                                      <localProp> (locally defined property) provides a locally defined character (or glyph) property. [5.2.1. Character Properties]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (@name, @value, @version)
                                      Contained by
                                      gaiji: glyph
                                      May containEmpty element
                                      Note

                                      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.

                                      Example
                                      <char xml:id="daikanwaU4EBA">
                                       <localProp name="name"
                                        value="CIRCLED IDEOGRAPH 4EBA"/>

                                       <localProp name="entityvalue="daikanwa"/>
                                       <unicodeProp name="Decomposition_Mapping"
                                        value="circle"/>

                                       <mapping type="standard"></mapping>
                                      </char>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <localProp>

                                      <localProp> (locally defined property) provides a locally defined character (or glyph) property. [5.2.1. Character Properties]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (@name, @value, @version)
                                      Contained by
                                      gaiji: glyph
                                      May containEmpty element
                                      Note

                                      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.

                                      Example
                                      <char xml:id="daikanwaU4EBA">
                                       <localProp name="name"
                                        value="CIRCLED IDEOGRAPH 4EBA"/>

                                       <localProp name="entityvalue="daikanwa"/>
                                       <unicodeProp name="Decomposition_Mapping"
                                        value="circle"/>

                                       <mapping type="standard"></mapping>
                                      </char>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element localProp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.gaijiProp.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-location.html b/gl/dev/ref-location.html index 1c595aba0..d397cf832 100644 --- a/gl/dev/ref-location.html +++ b/gl/dev/ref-location.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <location>

                                      <location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [13.3.4. Places]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <place>
                                       <placeName>Abbey Dore</placeName>
                                       <location>
                                        <geo>51.969604 -2.893146</geo>
                                       </location>
                                      </place>
                                      Example
                                      <place xml:id="BGbuildingtype="building">
                                       <placeName>Brasserie Georges</placeName>
                                       <location>
                                        <country key="FR"/>
                                        <settlement type="city">Lyon</settlement>
                                        <district type="arrondissement">IIème</district>
                                        <district type="quartier">Perrache</district>
                                        <placeName type="street">
                                         <num>30</num>, Cours de Verdun</placeName>
                                       </location>
                                      </place>
                                      Example
                                      <place type="imaginary">
                                       <placeName>Atlantis</placeName>
                                       <location>
                                        <offset>beyond</offset>
                                        <placeName>The Pillars of <persName>Hercules</persName>
                                        </placeName>
                                       </location>
                                      </place>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="precision"/>
                                        <classRef key="model.labelLike"/>
                                        <classRef key="model.placeNamePart"/>
                                        <classRef key="model.offsetLike"/>
                                        <classRef key="model.measureLike"/>
                                        <classRef key="model.addressLike"/>
                                        <classRef key="model.noteLike"/>
                                        <classRef key="model.biblLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <location>

                                      <location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [13.3.4. Places]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <place>
                                       <placeName>Abbey Dore</placeName>
                                       <location>
                                        <geo>51.969604 -2.893146</geo>
                                       </location>
                                      </place>
                                      Example
                                      <place xml:id="BGbuildingtype="building">
                                       <placeName>Brasserie Georges</placeName>
                                       <location>
                                        <country key="FR"/>
                                        <settlement type="city">Lyon</settlement>
                                        <district type="arrondissement">IIème</district>
                                        <district type="quartier">Perrache</district>
                                        <placeName type="street">
                                         <num>30</num>, Cours de Verdun</placeName>
                                       </location>
                                      </place>
                                      Example
                                      <place type="imaginary">
                                       <placeName>Atlantis</placeName>
                                       <location>
                                        <offset>beyond</offset>
                                        <placeName>The Pillars of <persName>Hercules</persName>
                                        </placeName>
                                       </location>
                                      </place>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="precision"/>
                                        <classRef key="model.labelLike"/>
                                        <classRef key="model.placeNamePart"/>
                                        <classRef key="model.offsetLike"/>
                                        <classRef key="model.measureLike"/>
                                        <classRef key="model.addressLike"/>
                                        <classRef key="model.noteLike"/>
                                        <classRef key="model.biblLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element location
                                       {
                                          tei_att.global.attributes,
                                      @@ -38,4 +38,4 @@
                                           | tei_model.noteLike
                                           | tei_model.biblLike
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-locus.html b/gl/dev/ref-locus.html index 481ff1377..3dad035b0 100644 --- a/gl/dev/ref-locus.html +++ b/gl/dev/ref-locus.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <locus>

                                      <locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      scheme(scheme) identifies the foliation scheme in terms of which the location is being specified by pointing to some foliation element defining it, or to some other equivalent resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      from(from) specifies the starting point of the location in a normalized form, typically a page number.
                                      Status Optional
                                      Datatype teidata.word
                                      to(to) specifies the end-point of the location in a normalized form, typically as a page number.
                                      Status Optional
                                      Datatype teidata.word
                                      Member of
                                      Contained by
                                      May contain
                                      core: hi
                                      gaiji: g
                                      msdescription: locus
                                      character data
                                      Note

                                      The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example.

                                      To associate a locus element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the surface, zone, graphic, or binaryObject elements.

                                      When a single page is being cited, use the from and to attributes with 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 <locus from="3">p. 3ff</locus>.

                                      Example

                                      <!-- within ms description --><msItem n="1">
                                       <locus target="#F1r #F1v #F2rfrom="1r"
                                        to="2r">
                                      ff. 1r-2r</locus>
                                       <author>Ben Jonson</author>
                                       <title>Ode to himself</title>
                                       <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
                                       <incipit>Com leaue the loathed stage</incipit>
                                       <explicit>And see his chariot triumph ore his wayne.</explicit>
                                       <bibl>
                                        <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
                                      </msItem>
                                      <!-- within transcription ... -->
                                      <pb xml:id="F1r"/>
                                      <!-- ... -->
                                      <pb xml:id="F1v"/>
                                      <!-- ... -->
                                      <pb xml:id="F2r"/>
                                      <!-- ... -->
                                      Example

                                      The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:

                                      <msItem>
                                       <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
                                       <title>Birds Praise of Love</title>
                                       <bibl>
                                        <title>IMEV</title>
                                        <biblScope>1506</biblScope>
                                       </bibl>
                                      </msItem>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="hi"/>
                                        <elementRef key="locus"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <locus>

                                      <locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      scheme(scheme) identifies the foliation scheme in terms of which the location is being specified by pointing to some foliation element defining it, or to some other equivalent resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      from(from) specifies the starting point of the location in a normalized form, typically a page number.
                                      Status Optional
                                      Datatype teidata.word
                                      to(to) specifies the end-point of the location in a normalized form, typically as a page number.
                                      Status Optional
                                      Datatype teidata.word
                                      Member of
                                      Contained by
                                      May contain
                                      core: hi
                                      gaiji: g
                                      msdescription: locus
                                      character data
                                      Note

                                      The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example.

                                      To associate a locus element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the surface, zone, graphic, or binaryObject elements.

                                      When a single page is being cited, use the from and to attributes with 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 <locus from="3">p. 3ff</locus>.

                                      Example

                                      <!-- within ms description --><msItem n="1">
                                       <locus target="#F1r #F1v #F2rfrom="1r"
                                        to="2r">
                                      ff. 1r-2r</locus>
                                       <author>Ben Jonson</author>
                                       <title>Ode to himself</title>
                                       <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
                                       <incipit>Com leaue the loathed stage</incipit>
                                       <explicit>And see his chariot triumph ore his wayne.</explicit>
                                       <bibl>
                                        <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
                                      </msItem>
                                      <!-- within transcription ... -->
                                      <pb xml:id="F1r"/>
                                      <!-- ... -->
                                      <pb xml:id="F1v"/>
                                      <!-- ... -->
                                      <pb xml:id="F2r"/>
                                      <!-- ... -->
                                      Example

                                      The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:

                                      <msItem>
                                       <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
                                       <title>Birds Praise of Love</title>
                                       <bibl>
                                        <title>IMEV</title>
                                        <biblScope>1506</biblScope>
                                       </bibl>
                                      </msItem>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="hi"/>
                                        <elementRef key="locus"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element locus
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          attribute from { teidata.word }?,
                                          attribute to { teidata.word }?,
                                          ( text | tei_model.gLike | tei_hi | tei_locus )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-locusGrp.html b/gl/dev/ref-locusGrp.html index ee9fe1062..9ba580a78 100644 --- a/gl/dev/ref-locusGrp.html +++ b/gl/dev/ref-locusGrp.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <locusGrp>

                                      <locusGrp> (locus group) groups a number of locations which together form a distinct but discontinuous item within a manuscript, manuscript part, or other object. [10.3.5. References to Locations within a Manuscript]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      scheme(scheme) identifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some foliation element defining it, or to some other equivalent resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Member of
                                      Contained by
                                      May contain
                                      msdescription: locus
                                      Example
                                      <msItem>
                                       <locusGrp>
                                        <locus from="13to="26">Bl. 13--26</locus>
                                        <locus from="37to="58">37--58</locus>
                                        <locus from="82to="96">82--96</locus>
                                       </locusGrp>
                                       <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note>
                                      </msItem>
                                      Content model
                                      <content>
                                       <elementRef key="locusminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <locusGrp>

                                      <locusGrp> (locus group) groups a number of locations which together form a distinct but discontinuous item within a manuscript, manuscript part, or other object. [10.3.5. References to Locations within a Manuscript]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      scheme(scheme) identifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some foliation element defining it, or to some other equivalent resource.
                                      Status Optional
                                      Datatype teidata.pointer
                                      Member of
                                      Contained by
                                      May contain
                                      msdescription: locus
                                      Example
                                      <msItem>
                                       <locusGrp>
                                        <locus from="13to="26">Bl. 13--26</locus>
                                        <locus from="37to="58">37--58</locus>
                                        <locus from="82to="96">82--96</locus>
                                       </locusGrp>
                                       <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note>
                                      </msItem>
                                      Content model
                                      <content>
                                       <elementRef key="locusminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element locusGrp
                                       {
                                          tei_att.global.attributes,
                                          attribute scheme { teidata.pointer }?,
                                          tei_locus+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-m.html b/gl/dev/ref-m.html index 7d119c047..b6314a4fe 100644 --- a/gl/dev/ref-m.html +++ b/gl/dev/ref-m.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <m>

                                      <m> (morpheme) represents a grammatical morpheme. [17.1. Linguistic Segment Categories]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      baseFormsupplies the morpheme's base form.
                                      Status Optional
                                      Datatype teidata.word
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to indicate the type of morpheme, taking values such as clitic, prefix, stem, etc. as appropriate.

                                      Example
                                      <w type="adjective">
                                       <w type="noun">
                                        <m type="prefixbaseForm="con">com</m>
                                        <m type="root">fort</m>
                                       </w>
                                       <m type="suffix">able</m>
                                      </w>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.hiLike"/>
                                        <elementRef key="seg"/>
                                        <elementRef key="m"/>
                                        <elementRef key="c"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <m>

                                      <m> (morpheme) represents a grammatical morpheme. [17.1. Linguistic Segment Categories]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      baseFormsupplies the morpheme's base form.
                                      Status Optional
                                      Datatype teidata.word
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to indicate the type of morpheme, taking values such as clitic, prefix, stem, etc. as appropriate.

                                      Example
                                      <w type="adjective">
                                       <w type="noun">
                                        <m type="prefixbaseForm="con">com</m>
                                        <m type="root">fort</m>
                                       </w>
                                       <m type="suffix">able</m>
                                      </w>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.hiLike"/>
                                        <elementRef key="seg"/>
                                        <elementRef key="m"/>
                                        <elementRef key="c"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element m
                                       {
                                          tei_att.global.attributes,
                                      @@ -38,4 +38,4 @@
                                           | tei_c
                                           | tei_model.global
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.abContent.html b/gl/dev/ref-macro.abContent.html index 6a4cea5b5..6f8787c3c 100644 --- a/gl/dev/ref-macro.abContent.html +++ b/gl/dev/ref-macro.abContent.html @@ -22,4 +22,4 @@ }); });

                                      macro.abContent

                                      macro.abContent (anonymous block content) defines the content of anonymous block elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.paraPart"/>
                                        <elementRef key="ab"/>
                                       </alternate>
                                      </content>
                                      Declaration
                                      -tei_macro.abContent = ( text | tei_model.paraPart | tei_ab )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +tei_macro.abContent = ( text | tei_model.paraPart | tei_ab )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.limitedContent.html b/gl/dev/ref-macro.limitedContent.html index fc53c4ff3..4f2e35f20 100644 --- a/gl/dev/ref-macro.limitedContent.html +++ b/gl/dev/ref-macro.limitedContent.html @@ -23,4 +23,4 @@ });

                                      macro.limitedContent

                                      macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.limitedPhrase"/>
                                        <classRef key="model.inter"/>
                                       </alternate>
                                      </content>
                                      Declaration
                                       tei_macro.limitedContent =
                                      -   ( text | tei_model.limitedPhrase | tei_model.inter )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file + ( text | tei_model.limitedPhrase | tei_model.inter )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.paraContent.html b/gl/dev/ref-macro.paraContent.html index 8a7a7ff77..30f7faf4e 100644 --- a/gl/dev/ref-macro.paraContent.html +++ b/gl/dev/ref-macro.paraContent.html @@ -22,4 +22,4 @@ }); });

                                      macro.paraContent

                                      macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.paraPart"/>
                                       </alternate>
                                      </content>
                                      Declaration
                                      -tei_macro.paraContent = ( text | tei_model.paraPart )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +tei_macro.paraContent = ( text | tei_model.paraPart )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.phraseSeq.html b/gl/dev/ref-macro.phraseSeq.html index 9cb2a9112..88c148874 100644 --- a/gl/dev/ref-macro.phraseSeq.html +++ b/gl/dev/ref-macro.phraseSeq.html @@ -29,4 +29,4 @@ | tei_model.attributable | tei_model.phrase | tei_model.global - )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file + )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.phraseSeq.limited.html b/gl/dev/ref-macro.phraseSeq.limited.html index 5a0e382a3..f87cd57ae 100644 --- a/gl/dev/ref-macro.phraseSeq.limited.html +++ b/gl/dev/ref-macro.phraseSeq.limited.html @@ -23,4 +23,4 @@ });

                                      macro.phraseSeq.limited

                                      macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
                                      Moduletei
                                      Used by
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.limitedPhrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Declaration
                                       tei_macro.phraseSeq.limited =
                                      -   ( text | tei_model.limitedPhrase | tei_model.global )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file + ( text | tei_model.limitedPhrase | tei_model.global )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.specialPara.html b/gl/dev/ref-macro.specialPara.html index 384541886..09946ba0a 100644 --- a/gl/dev/ref-macro.specialPara.html +++ b/gl/dev/ref-macro.specialPara.html @@ -30,4 +30,4 @@ | tei_model.inter | tei_model.divPart | tei_model.global - )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file + )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-macro.xtext.html b/gl/dev/ref-macro.xtext.html index 1af0588c8..483fbafcc 100644 --- a/gl/dev/ref-macro.xtext.html +++ b/gl/dev/ref-macro.xtext.html @@ -22,4 +22,4 @@ }); });

                                      macro.xtext

                                      macro.xtext (extended text) defines a sequence of character data and gaiji elements.
                                      Moduletei
                                      Used by
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                       </alternate>
                                      </content>
                                      Declaration
                                      -tei_macro.xtext = ( text | tei_model.gLike )*

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +tei_macro.xtext = ( text | tei_model.gLike )*

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-mapping.html b/gl/dev/ref-mapping.html index 82838e80b..63a81f7b7 100644 --- a/gl/dev/ref-mapping.html +++ b/gl/dev/ref-mapping.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <mapping>

                                      <mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      gaiji: glyph
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The g elements contained by this element can point to either another <char> or glyphelement or contain a character that is intended to be the target of this mapping.

                                      Example
                                      <mapping type="modern">r</mapping>
                                      <mapping type="standard"></mapping>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <mapping>

                                      <mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      gaiji: glyph
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The g elements contained by this element can point to either another <char> or glyphelement or contain a character that is intended to be the target of this mapping.

                                      Example
                                      <mapping type="modern">r</mapping>
                                      <mapping type="standard"></mapping>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element mapping
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-material.html b/gl/dev/ref-material.html index ba44c6167..daf00fb0e 100644 --- a/gl/dev/ref-material.html +++ b/gl/dev/ref-material.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <material>

                                      <material> (material) contains a word or phrase describing the material of which the object being described is composed. [10.3.2. Material and Object Type]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.typed (@type, @subtype)
                                      functiondescribes the function or use of the material in relation to the object as a whole.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      binding
                                      covering material of a codex
                                      endband
                                      sewing at the head or tail of the codex spine to strengthen the binding, often decorative
                                      slipcase
                                      removable protective cover for a set of one or more codices
                                      support
                                      the surface for writing
                                      tie
                                      a ribbon or string used to bind or close a codex or rolled scroll
                                      Note

                                      The sample values here are for descriptive bibliography. Other sets of sample values might include armrests, legs, tabletop, pan, and back for furniture; or wall, floor, window, column, ceiling, roof, stairs, chimney for architecture.

                                      targetidentifies one or more elements to which the metamark applies.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally.

                                      Example
                                      <physDesc>
                                       <p>
                                        <material>Parchment</material> leaves with a
                                       <material>sharkskin</material> binding.</p>
                                      </physDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <material>

                                      <material> (material) contains a word or phrase describing the material of which the object being described is composed. [10.3.2. Material and Object Type]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.typed (@type, @subtype)
                                      functiondescribes the function or use of the material in relation to the object as a whole.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      binding
                                      covering material of a codex
                                      endband
                                      sewing at the head or tail of the codex spine to strengthen the binding, often decorative
                                      slipcase
                                      removable protective cover for a set of one or more codices
                                      support
                                      the surface for writing
                                      tie
                                      a ribbon or string used to bind or close a codex or rolled scroll
                                      Note

                                      The sample values here are for descriptive bibliography. Other sets of sample values might include armrests, legs, tabletop, pan, and back for furniture; or wall, floor, window, column, ceiling, roof, stairs, chimney for architecture.

                                      targetidentifies one or more elements to which the metamark applies.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally.

                                      Example
                                      <physDesc>
                                       <p>
                                        <material>Parchment</material> leaves with a
                                       <material>sharkskin</material> binding.</p>
                                      </physDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element material
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute function { teidata.enumerated }?,
                                          attribute target { list { teidata.pointer+ } }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-measure.html b/gl/dev/ref-measure.html index 25e7fe764..eb156e1c1 100644 --- a/gl/dev/ref-measure.html +++ b/gl/dev/ref-measure.html @@ -22,7 +22,7 @@ }); });

                                      <measure>

                                      <measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and -Measures]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.measurement (@unit, @unitRef, @quantity, @commodity) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.typed (type, @subtype)
                                      typespecifies the type of measurement in any convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      This example references a definition of a measurement unit declared in the TEI header:

                                      <measure type="weight">
                                       <num>2</num> pounds of flesh
                                      </measure>
                                      <measure type="currency">£10-11-6d</measure>
                                      <measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure>
                                      <!-- In the TEI Header: -->
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="merktype="area">
                                         <label>merk</label>
                                         <placeName ref="#Scotland"/>
                                         <desc>A merk was an area of land determined variably by its agricultural
                                             productivity.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <measure quantity="40unit="hogshead"
                                       commodity="rum">
                                      2 score hh rum</measure>
                                      <measure quantity="12unit="count"
                                       commodity="roses">
                                      1 doz. roses</measure>
                                      <measure quantity="1unit="count"
                                       commodity="tulips">
                                      a yellow tulip</measure>
                                      Example
                                      <head>Long papers.</head>
                                      <p>Speakers will be given 30 minutes each: 20 minutes for
                                      presentation, 10 minutes for discussion. Proposals should not
                                      exceed <measure max="500unit="count"
                                        commodity="words">
                                      500
                                         words</measure>. This presentation type is suitable for
                                      substantial research, theoretical or critical discussions.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +Measures]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.measurement (@unit, @unitRef, @quantity, @commodity) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.typed (type, @subtype)
                                      typespecifies the type of measurement in any convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      This example references a definition of a measurement unit declared in the TEI header:

                                      <measure type="weight">
                                       <num>2</num> pounds of flesh
                                      </measure>
                                      <measure type="currency">£10-11-6d</measure>
                                      <measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure>
                                      <!-- In the TEI Header: -->
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="merktype="area">
                                         <label>merk</label>
                                         <placeName ref="#Scotland"/>
                                         <desc>A merk was an area of land determined variably by its agricultural
                                             productivity.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <measure quantity="40unit="hogshead"
                                       commodity="rum">
                                      2 score hh rum</measure>
                                      <measure quantity="12unit="count"
                                       commodity="roses">
                                      1 doz. roses</measure>
                                      <measure quantity="1unit="count"
                                       commodity="tulips">
                                      a yellow tulip</measure>
                                      Example
                                      <head>Long papers.</head>
                                      <p>Speakers will be given 30 minutes each: 20 minutes for
                                      presentation, 10 minutes for discussion. Proposals should not
                                      exceed <measure max="500unit="count"
                                        commodity="words">
                                      500
                                         words</measure>. This presentation type is suitable for
                                      substantial research, theoretical or critical discussions.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element measure
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.ranging.attributes,
                                          attribute type { teidata.enumerated }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-measureGrp.html b/gl/dev/ref-measureGrp.html index 484ac1ffb..546c39dc4 100644 --- a/gl/dev/ref-measureGrp.html +++ b/gl/dev/ref-measureGrp.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <measureGrp>

                                      <measureGrp> (measure group) contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page. [10.3.4. Dimensions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.measurement (@unit, @unitRef, @quantity, @commodity) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      msdescription: depth dim height width
                                      namesdates: geo
                                      character data
                                      Example
                                      <measureGrp type="leavesunit="mm">
                                       <height scope="range">157-160</height>
                                       <width quantity="105"/>
                                      </measureGrp>
                                      <measureGrp type="ruledAreaunit="mm">
                                       <height scope="mostquantity="90"/>
                                       <width scope="mostquantity="48"/>
                                      </measureGrp>
                                      <measureGrp type="boxunit="in">
                                       <height quantity="12"/>
                                       <width quantity="10"/>
                                       <depth quantity="6"/>
                                      </measureGrp>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.measureLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <measureGrp>

                                      <measureGrp> (measure group) contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page. [10.3.4. Dimensions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.measurement (@unit, @unitRef, @quantity, @commodity) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      msdescription: depth dim height width
                                      namesdates: geo
                                      character data
                                      Example
                                      <measureGrp type="leavesunit="mm">
                                       <height scope="range">157-160</height>
                                       <width quantity="105"/>
                                      </measureGrp>
                                      <measureGrp type="ruledAreaunit="mm">
                                       <height scope="mostquantity="90"/>
                                       <width scope="mostquantity="48"/>
                                      </measureGrp>
                                      <measureGrp type="boxunit="in">
                                       <height quantity="12"/>
                                       <width quantity="10"/>
                                       <depth quantity="6"/>
                                      </measureGrp>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.measureLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element measureGrp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.measurement.attributes,
                                          tei_att.typed.attributes,
                                          ( text | tei_model.gLike | tei_model.measureLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-media.html b/gl/dev/ref-media.html index 537a9f70f..aa4140a67 100644 --- a/gl/dev/ref-media.html +++ b/gl/dev/ref-media.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <media>

                                      <media> indicates the location of any form of external media such as an audio or video clip etc. [3.10. Graphics and Other Non-textual Components]
                                      Modulecore
                                      Attributesatt.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.resourced (@url) att.declaring (@decls) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.media (@width, @height, @scale)
                                      mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
                                      Derived fromatt.internetMedia
                                      Status Required
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      The attributes available for this element are not appropriate in all cases. For example, it makes no sense to specify the temporal duration of a graphic. Such errors are not currently detected.

                                      The mimeType attribute must be used to specify the MIME media type of the resource specified by the url attribute.

                                      Example
                                      <figure>
                                       <media mimeType="image/pngurl="fig1.png"/>
                                       <head>Figure One: The View from the Bridge</head>
                                       <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
                                         series of buoys strung out between them.</figDesc>
                                      </figure>
                                      Example
                                      <media mimeType="audio/wav"
                                       url="dingDong.wavdur="PT10S">

                                       <desc>Ten seconds of bellringing sound</desc>
                                      </media>
                                      Example
                                      <media mimeType="video/mp4"
                                       url="clip45.mp4dur="PT45Mwidth="500px">

                                       <desc>A 45 minute video clip to be displayed in a window 500
                                         px wide</desc>
                                      </media>
                                      Content model
                                      <content>
                                       <classRef key="model.descLike"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <media>

                                      <media> indicates the location of any form of external media such as an audio or video clip etc. [3.10. Graphics and Other Non-textual Components]
                                      Modulecore
                                      Attributesatt.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.resourced (@url) att.declaring (@decls) att.timed (@start, @end) (att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) ) att.media (@width, @height, @scale)
                                      mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
                                      Derived fromatt.internetMedia
                                      Status Required
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      The attributes available for this element are not appropriate in all cases. For example, it makes no sense to specify the temporal duration of a graphic. Such errors are not currently detected.

                                      The mimeType attribute must be used to specify the MIME media type of the resource specified by the url attribute.

                                      Example
                                      <figure>
                                       <media mimeType="image/pngurl="fig1.png"/>
                                       <head>Figure One: The View from the Bridge</head>
                                       <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
                                         series of buoys strung out between them.</figDesc>
                                      </figure>
                                      Example
                                      <media mimeType="audio/wav"
                                       url="dingDong.wavdur="PT10S">

                                       <desc>Ten seconds of bellringing sound</desc>
                                      </media>
                                      Example
                                      <media mimeType="video/mp4"
                                       url="clip45.mp4dur="PT45Mwidth="500px">

                                       <desc>A 45 minute video clip to be displayed in a window 500
                                         px wide</desc>
                                      </media>
                                      Content model
                                      <content>
                                       <classRef key="model.descLike"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element media
                                       {
                                          tei_att.typed.attributes,
                                      @@ -34,4 +34,4 @@
                                          tei_att.timed.attributes,
                                          attribute mimeType { list { teidata.word+ } },
                                          tei_model.descLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-meeting.html b/gl/dev/ref-meeting.html index 8914b02e3..c5d7e9265 100644 --- a/gl/dev/ref-meeting.html +++ b/gl/dev/ref-meeting.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <meeting>

                                      <meeting> 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. [3.12.2.2. Titles, Authors, and Editors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      figures: figure table
                                      msdescription: msItem
                                      textstructure: body div front group
                                      May contain
                                      Example
                                      <div>
                                       <meeting>Ninth International Conference on Middle High German Textual Criticism, Aachen,
                                         June 1998.</meeting>
                                       <list type="attendance">
                                        <head>List of Participants</head>
                                        <item>
                                         <persName>...</persName>
                                        </item>
                                        <item>
                                         <persName>...</persName>
                                        </item>
                                      <!--...-->
                                       </list>
                                       <p>...</p>
                                      </div>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <meeting>

                                      <meeting> 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. [3.12.2.2. Titles, Authors, and Editors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      figures: figure table
                                      msdescription: msItem
                                      textstructure: body div front group
                                      May contain
                                      Example
                                      <div>
                                       <meeting>Ninth International Conference on Middle High German Textual Criticism, Aachen,
                                         June 1998.</meeting>
                                       <list type="attendance">
                                        <head>List of Participants</head>
                                        <item>
                                         <persName>...</persName>
                                        </item>
                                        <item>
                                         <persName>...</persName>
                                        </item>
                                      <!--...-->
                                       </list>
                                       <p>...</p>
                                      </div>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                       element meeting
                                       {
                                          tei_att.global.attributes,
                                          tei_att.datable.attributes,
                                          tei_att.canonical.attributes,
                                          tei_macro.limitedContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-mentioned.html b/gl/dev/ref-mentioned.html index d015547ed..b3d961566 100644 --- a/gl/dev/ref-mentioned.html +++ b/gl/dev/ref-mentioned.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <mentioned>

                                      <mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      There is thus a
                                      striking accentual difference between a verbal form like <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned>
                                      <gloss target="#X234">we were released,</gloss> accented on the second syllable of the
                                      word, and its participial derivative
                                      <mentioned xml:id="X235xml:lang="el">lutheis</mentioned>
                                      <gloss target="#X235">released,</gloss> accented on the last.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element mentioned { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <mentioned>

                                      <mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      There is thus a
                                      striking accentual difference between a verbal form like <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned>
                                      <gloss target="#X234">we were released,</gloss> accented on the second syllable of the
                                      word, and its participial derivative
                                      <mentioned xml:id="X235xml:lang="el">lutheis</mentioned>
                                      <gloss target="#X235">released,</gloss> accented on the last.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element mentioned { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-metamark.html b/gl/dev/ref-metamark.html index 7a14bf32e..f0d343a6a 100644 --- a/gl/dev/ref-metamark.html +++ b/gl/dev/ref-metamark.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <metamark>

                                      <metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [11.3.4.2. Metamarks]
                                      Moduletranscr
                                      Attributesatt.spanning (@spanTo) att.placement (@place) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      functiondescribes the function (for example status, insertion, deletion, transposition) of the metamark.
                                      Status Optional
                                      Datatype teidata.word
                                      targetidentifies one or more elements to which the metamark applies.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <surface>
                                       <metamark function="usedrend="line"
                                        target="#X2"/>

                                       <zone xml:id="zone-X2">
                                        <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line>
                                        <line>The tears of foolish passion yet undried</line>
                                        <line>upon my cheeks.</line>
                                      <!-- ... -->
                                        <line>I pass through <add>the</add> travels and <del>fortunes</del> of
                                        <retrace>thirty</retrace>
                                        </line>
                                        <line>years and become old,</line>
                                        <line>Each in its due order comes and goes,</line>
                                        <line>And thus a message for me comes.</line>
                                        <line>The</line>
                                       </zone>
                                       <metamark function="used"
                                        target="#zone-X2">
                                      Entered - Yes</metamark>
                                      </surface>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <metamark>

                                      <metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [11.3.4.2. Metamarks]
                                      Moduletranscr
                                      Attributesatt.spanning (@spanTo) att.placement (@place) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      functiondescribes the function (for example status, insertion, deletion, transposition) of the metamark.
                                      Status Optional
                                      Datatype teidata.word
                                      targetidentifies one or more elements to which the metamark applies.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <surface>
                                       <metamark function="usedrend="line"
                                        target="#X2"/>

                                       <zone xml:id="zone-X2">
                                        <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line>
                                        <line>The tears of foolish passion yet undried</line>
                                        <line>upon my cheeks.</line>
                                      <!-- ... -->
                                        <line>I pass through <add>the</add> travels and <del>fortunes</del> of
                                        <retrace>thirty</retrace>
                                        </line>
                                        <line>years and become old,</line>
                                        <line>Each in its due order comes and goes,</line>
                                        <line>And thus a message for me comes.</line>
                                        <line>The</line>
                                       </zone>
                                       <metamark function="used"
                                        target="#zone-X2">
                                      Entered - Yes</metamark>
                                      </surface>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element metamark
                                       {
                                          tei_att.spanning.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute function { teidata.word }?,
                                          attribute target { list { teidata.pointer+ } }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-milestone.html b/gl/dev/ref-milestone.html index c94783903..6c9fd62af 100644 --- a/gl/dev/ref-milestone.html +++ b/gl/dev/ref-milestone.html @@ -22,7 +22,7 @@ }); });

                                      <milestone>

                                      <milestone> (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone -Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.milestoneUnit (@unit) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

                                      The order in which milestone elements are given at a given point is not normally significant.

                                      Example
                                      <milestone n="23ed="Launit="Dreissiger"/>
                                      ... <milestone n="24ed="AVunit="verse"/> ...
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.milestoneUnit (@unit) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

                                      The order in which milestone elements are given at a given point is not normally significant.

                                      Example
                                      <milestone n="23ed="Launit="Dreissiger"/>
                                      ... <milestone n="24ed="AVunit="verse"/> ...
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element milestone
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          tei_att.spanning.attributes,
                                          tei_att.breaking.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-mod.html b/gl/dev/ref-mod.html index d8036bc94..22feea8b3 100644 --- a/gl/dev/ref-mod.html +++ b/gl/dev/ref-mod.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <mod>

                                      <mod> represents any kind of modification identified within a single document. [11.3.4.1. Generic Modification]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <mod type="subst">
                                       <add>pleasing</add>
                                       <del>agreable</del>
                                      </mod>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <mod>

                                      <mod> represents any kind of modification identified within a single document. [11.3.4.1. Generic Modification]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.spanning (@spanTo) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <mod type="subst">
                                       <add>pleasing</add>
                                       <del>agreable</del>
                                      </mod>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element mod
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.spanning.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.addrPart.html b/gl/dev/ref-model.addrPart.html index 5ab4cfd96..37ee680bb 100644 --- a/gl/dev/ref-model.addrPart.html +++ b/gl/dev/ref-model.addrPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.addrPart

                                      model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
                                      Moduletei
                                      Used by
                                      Membersmodel.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] addrLine postBox postCode street

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.addrPart

                                      model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
                                      Moduletei
                                      Used by
                                      Membersmodel.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] addrLine postBox postCode street

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.addressLike.html b/gl/dev/ref-model.addressLike.html index 856ae4e65..e932b5cc9 100644 --- a/gl/dev/ref-model.addressLike.html +++ b/gl/dev/ref-model.addressLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.addressLike

                                      model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
                                      Moduletei
                                      Used by
                                      Membersaddress email

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.addressLike

                                      model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
                                      Moduletei
                                      Used by
                                      Membersaddress email

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.annotationLike.html b/gl/dev/ref-model.annotationLike.html index e0d69f2e4..7792e2314 100644 --- a/gl/dev/ref-model.annotationLike.html +++ b/gl/dev/ref-model.annotationLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.annotationLike

                                      model.annotationLike groups elements used to represent annotations. [16.10. The standOff Container]
                                      Moduletei
                                      Used by
                                      Membersannotation annotationBlock note

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.annotationLike

                                      model.annotationLike groups elements used to represent annotations. [16.10. The standOff Container]
                                      Moduletei
                                      Used by
                                      Membersannotation annotationBlock note

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.annotationPart.body.html b/gl/dev/ref-model.annotationPart.body.html index a1fdf7be1..f7febc3b9 100644 --- a/gl/dev/ref-model.annotationPart.body.html +++ b/gl/dev/ref-model.annotationPart.body.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.annotationPart.body

                                      model.annotationPart.body groups elements which may be used as an annotation body.
                                      Moduletei
                                      Used by
                                      Membersnote ptr ref

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.annotationPart.body

                                      model.annotationPart.body groups elements which may be used as an annotation body.
                                      Moduletei
                                      Used by
                                      Membersnote ptr ref

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.attributable.html b/gl/dev/ref-model.attributable.html index db7be6370..0c1ed3537 100644 --- a/gl/dev/ref-model.attributable.html +++ b/gl/dev/ref-model.attributable.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.attributable

                                      model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
                                      Moduletei
                                      Used by
                                      Membersmodel.quoteLike [cit quote] floatingText said

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.attributable

                                      model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
                                      Moduletei
                                      Used by
                                      Membersmodel.quoteLike [cit quote] floatingText said

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.availabilityPart.html b/gl/dev/ref-model.availabilityPart.html index 6507ec7d6..6191e9ff6 100644 --- a/gl/dev/ref-model.availabilityPart.html +++ b/gl/dev/ref-model.availabilityPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.availabilityPart

                                      model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduletei
                                      Used by
                                      Memberslicence

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.availabilityPart

                                      model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduletei
                                      Used by
                                      Memberslicence

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.biblLike.html b/gl/dev/ref-model.biblLike.html index e8653d0a6..692c1e8fd 100644 --- a/gl/dev/ref-model.biblLike.html +++ b/gl/dev/ref-model.biblLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.biblLike

                                      model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
                                      Moduletei
                                      Used by
                                      Membersbibl biblFull biblStruct listBibl msDesc

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.biblLike

                                      model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
                                      Moduletei
                                      Used by
                                      Membersbibl biblFull biblStruct listBibl msDesc

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.biblPart.html b/gl/dev/ref-model.biblPart.html index deabadbbc..6119968fb 100644 --- a/gl/dev/ref-model.biblPart.html +++ b/gl/dev/ref-model.biblPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.biblPart

                                      model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
                                      Moduletei
                                      Used by
                                      Membersmodel.imprintPart [biblScope distributor pubPlace publisher] model.respLike [author editor funder meeting principal respStmt sponsor] availability bibl citedRange decoNote edition explicit extent incipit listRelation msIdentifier objectIdentifier relatedItem series textLang

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.biblPart

                                      model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
                                      Moduletei
                                      Used by
                                      Membersmodel.imprintPart [biblScope distributor pubPlace publisher] model.respLike [author editor funder meeting principal respStmt sponsor] availability bibl citedRange decoNote edition explicit extent incipit listRelation msIdentifier objectIdentifier relatedItem series textLang

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.certLike.html b/gl/dev/ref-model.certLike.html index abcb2f3af..84df54a5f 100644 --- a/gl/dev/ref-model.certLike.html +++ b/gl/dev/ref-model.certLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.certLike

                                      model.certLike groups elements which are used to indicate uncertainty or precision of other elements.
                                      Moduletei
                                      Used by
                                      Memberscertainty precision

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.certLike

                                      model.certLike groups elements which are used to indicate uncertainty or precision of other elements.
                                      Moduletei
                                      Used by
                                      Memberscertainty precision

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.choicePart.html b/gl/dev/ref-model.choicePart.html index 20742bf2f..282ebe9b2 100644 --- a/gl/dev/ref-model.choicePart.html +++ b/gl/dev/ref-model.choicePart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.choicePart

                                      model.choicePart groups elements (other than choice itself) which can be used within a choice alternation. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersabbr am corr ex expan orig reg seg sic supplied unclear

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.choicePart

                                      model.choicePart groups elements (other than choice itself) which can be used within a choice alternation. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersabbr am corr ex expan orig reg seg sic supplied unclear

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.common.html b/gl/dev/ref-model.common.html index 931c8486a..85cb68069 100644 --- a/gl/dev/ref-model.common.html +++ b/gl/dev/ref-model.common.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.common

                                      model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.divPart [model.divPart.spoken [annotationBlock] model.lLike [l] model.pLike [ab p] lg sp] model.entryLike model.inter [model.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike [stage] ] q
                                      Note

                                      This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.common

                                      model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.divPart [model.divPart.spoken [annotationBlock] model.lLike [l] model.pLike [ab p] lg sp] model.entryLike model.inter [model.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike [stage] ] q
                                      Note

                                      This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.correspActionPart.html b/gl/dev/ref-model.correspActionPart.html index 4d76622bc..99d41ed99 100644 --- a/gl/dev/ref-model.correspActionPart.html +++ b/gl/dev/ref-model.correspActionPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.correspActionPart

                                      model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
                                      Moduletei
                                      Used by
                                      Membersmodel.addressLike [address email] model.dateLike [date time] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] note noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.correspActionPart

                                      model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
                                      Moduletei
                                      Used by
                                      Membersmodel.addressLike [address email] model.dateLike [date time] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] note noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.correspContextPart.html b/gl/dev/ref-model.correspContextPart.html index 9bdd1f741..0d14ae324 100644 --- a/gl/dev/ref-model.correspContextPart.html +++ b/gl/dev/ref-model.correspContextPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.correspContextPart

                                      model.correspContextPart groups elements which may appear as part of the correspContext element
                                      Moduletei
                                      Used by
                                      Membersmodel.pLike [ab p] model.ptrLike [ptr ref] note noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.correspContextPart

                                      model.correspContextPart groups elements which may appear as part of the correspContext element
                                      Moduletei
                                      Used by
                                      Membersmodel.pLike [ab p] model.ptrLike [ptr ref] note noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.correspDescPart.html b/gl/dev/ref-model.correspDescPart.html index 9ea5b65eb..c5cb85fe3 100644 --- a/gl/dev/ref-model.correspDescPart.html +++ b/gl/dev/ref-model.correspDescPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.correspDescPart

                                      model.correspDescPart groups together metadata elements for describing correspondence
                                      Moduletei
                                      Used by
                                      MemberscorrespAction correspContext note noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.correspDescPart

                                      model.correspDescPart groups together metadata elements for describing correspondence
                                      Moduletei
                                      Used by
                                      MemberscorrespAction correspContext note noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.dateLike.html b/gl/dev/ref-model.dateLike.html index eac875e99..ecfd55caf 100644 --- a/gl/dev/ref-model.dateLike.html +++ b/gl/dev/ref-model.dateLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.dateLike

                                      model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Used by
                                      Membersdate time

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.dateLike

                                      model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
                                      Moduletei
                                      Used by
                                      Membersdate time

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.descLike.html b/gl/dev/ref-model.descLike.html index 0d998f0c7..a815efef4 100644 --- a/gl/dev/ref-model.descLike.html +++ b/gl/dev/ref-model.descLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.descLike

                                      model.descLike groups elements which contain a description of their function.
                                      Moduletei
                                      Used by
                                      Membersdesc

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.descLike

                                      model.descLike groups elements which contain a description of their function.
                                      Moduletei
                                      Used by
                                      Membersdesc

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.describedResource.html b/gl/dev/ref-model.describedResource.html index ddac68b04..7829ea645 100644 --- a/gl/dev/ref-model.describedResource.html +++ b/gl/dev/ref-model.describedResource.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.describedResource

                                      model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      MembersTEI teiCorpus

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.describedResource

                                      model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      MembersTEI teiCorpus

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.dimLike.html b/gl/dev/ref-model.dimLike.html index 76561d716..b9b7c2492 100644 --- a/gl/dev/ref-model.dimLike.html +++ b/gl/dev/ref-model.dimLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.dimLike

                                      model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
                                      Moduletei
                                      Used by
                                      Membersdepth height width

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.dimLike

                                      model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
                                      Moduletei
                                      Used by
                                      Membersdepth height width

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divBottom.html b/gl/dev/ref-model.divBottom.html index b12928027..9cccd99ab 100644 --- a/gl/dev/ref-model.divBottom.html +++ b/gl/dev/ref-model.divBottom.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divBottom

                                      model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
                                      Moduletei
                                      Used by
                                      Membersmodel.divBottomPart model.divWrapper [dateline docAuthor docDate epigraph meeting]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divBottom

                                      model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
                                      Moduletei
                                      Used by
                                      Membersmodel.divBottomPart model.divWrapper [dateline docAuthor docDate epigraph meeting]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divGenLike.html b/gl/dev/ref-model.divGenLike.html index cffd9efe8..ad60ebf1a 100644 --- a/gl/dev/ref-model.divGenLike.html +++ b/gl/dev/ref-model.divGenLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divGenLike

                                      model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source.
                                      Moduletei
                                      Used by
                                      MembersdivGen

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divGenLike

                                      model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source.
                                      Moduletei
                                      Used by
                                      MembersdivGen

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divLike.html b/gl/dev/ref-model.divLike.html index acaf0c49a..3f05fca65 100644 --- a/gl/dev/ref-model.divLike.html +++ b/gl/dev/ref-model.divLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divLike

                                      model.divLike groups elements used to represent un-numbered generic structural divisions.
                                      Moduletei
                                      Used by
                                      Membersdiv

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divLike

                                      model.divLike groups elements used to represent un-numbered generic structural divisions.
                                      Moduletei
                                      Used by
                                      Membersdiv

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divPart.html b/gl/dev/ref-model.divPart.html index 6ce6ecfe4..f08b2d7dd 100644 --- a/gl/dev/ref-model.divPart.html +++ b/gl/dev/ref-model.divPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divPart

                                      model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.divPart.spoken [annotationBlock] model.lLike [l] model.pLike [ab p] lg sp
                                      Note

                                      Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divPart

                                      model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.divPart.spoken [annotationBlock] model.lLike [l] model.pLike [ab p] lg sp
                                      Note

                                      Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divPart.spoken.html b/gl/dev/ref-model.divPart.spoken.html index 9032d2876..9e953bba8 100644 --- a/gl/dev/ref-model.divPart.spoken.html +++ b/gl/dev/ref-model.divPart.spoken.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divPart.spoken

                                      model.divPart.spoken groups elements structurally analogous to paragraphs within spoken texts. [8.1. General Considerations and Overview]
                                      Modulespoken
                                      Used by
                                      MembersannotationBlock
                                      Note

                                      Spoken texts may be structured in many ways; elements in this class are typically larger units such as turns or utterances.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divPart.spoken

                                      model.divPart.spoken groups elements structurally analogous to paragraphs within spoken texts. [8.1. General Considerations and Overview]
                                      Modulespoken
                                      Used by
                                      MembersannotationBlock
                                      Note

                                      Spoken texts may be structured in many ways; elements in this class are typically larger units such as turns or utterances.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divTop.html b/gl/dev/ref-model.divTop.html index 496b80782..9a7a2ed9e 100644 --- a/gl/dev/ref-model.divTop.html +++ b/gl/dev/ref-model.divTop.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divTop

                                      model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
                                      Moduletei
                                      Used by
                                      Membersmodel.divTopPart [model.headLike [head] ] model.divWrapper [dateline docAuthor docDate epigraph meeting]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divTop

                                      model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
                                      Moduletei
                                      Used by
                                      Membersmodel.divTopPart [model.headLike [head] ] model.divWrapper [dateline docAuthor docDate epigraph meeting]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divTopPart.html b/gl/dev/ref-model.divTopPart.html index f7ff2c4a5..ddf8618fa 100644 --- a/gl/dev/ref-model.divTopPart.html +++ b/gl/dev/ref-model.divTopPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divTopPart

                                      model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
                                      Moduletei
                                      Used by
                                      Membersmodel.headLike [head]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divTopPart

                                      model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
                                      Moduletei
                                      Used by
                                      Membersmodel.headLike [head]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.divWrapper.html b/gl/dev/ref-model.divWrapper.html index 02c2b199f..7825fb2ea 100644 --- a/gl/dev/ref-model.divWrapper.html +++ b/gl/dev/ref-model.divWrapper.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.divWrapper

                                      model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
                                      Moduletei
                                      Used by
                                      Membersdateline docAuthor docDate epigraph meeting

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.divWrapper

                                      model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
                                      Moduletei
                                      Used by
                                      Membersdateline docAuthor docDate epigraph meeting

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.editorialDeclPart.html b/gl/dev/ref-model.editorialDeclPart.html index 6dd72f2a1..3bf034a28 100644 --- a/gl/dev/ref-model.editorialDeclPart.html +++ b/gl/dev/ref-model.editorialDeclPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.editorialDeclPart

                                      model.editorialDeclPart groups elements which may be used inside editorialDecl and appear multiple times.
                                      Moduletei
                                      Used by
                                      Memberscorrection hyphenation interpretation normalization punctuation quotation segmentation stdVals

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.editorialDeclPart

                                      model.editorialDeclPart groups elements which may be used inside editorialDecl and appear multiple times.
                                      Moduletei
                                      Used by
                                      Memberscorrection hyphenation interpretation normalization punctuation quotation segmentation stdVals

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.emphLike.html b/gl/dev/ref-model.emphLike.html index da8e2f866..945f761da 100644 --- a/gl/dev/ref-model.emphLike.html +++ b/gl/dev/ref-model.emphLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.emphLike

                                      model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
                                      Moduletei
                                      Used by
                                      Membersdistinct emph foreign gloss mentioned soCalled term title

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.emphLike

                                      model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
                                      Moduletei
                                      Used by
                                      Membersdistinct emph foreign gloss mentioned soCalled term title

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.encodingDescPart.html b/gl/dev/ref-model.encodingDescPart.html index 12fccab87..e7b940540 100644 --- a/gl/dev/ref-model.encodingDescPart.html +++ b/gl/dev/ref-model.encodingDescPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.encodingDescPart

                                      model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times.
                                      Moduletei
                                      Used by
                                      MemberscharDecl classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl schemaRef styleDefDecl tagsDecl transcriptionDesc unitDecl variantEncoding

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.encodingDescPart

                                      model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times.
                                      Moduletei
                                      Used by
                                      MemberscharDecl classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl schemaRef styleDefDecl tagsDecl transcriptionDesc unitDecl variantEncoding

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.entryPart.html b/gl/dev/ref-model.entryPart.html index 0372f4217..6d030e623 100644 --- a/gl/dev/ref-model.entryPart.html +++ b/gl/dev/ref-model.entryPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.entryPart

                                      model.entryPart groups non-morphological elements appearing within a dictionary entry. [9.1. Dictionary Body and Overall Structure]
                                      Moduletei
                                      Used by
                                      Membersform

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.entryPart

                                      model.entryPart groups non-morphological elements appearing within a dictionary entry. [9.1. Dictionary Body and Overall Structure]
                                      Moduletei
                                      Used by
                                      Membersform

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.eventLike.html b/gl/dev/ref-model.eventLike.html index f4316581d..1277f2e7f 100644 --- a/gl/dev/ref-model.eventLike.html +++ b/gl/dev/ref-model.eventLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.eventLike

                                      model.eventLike groups elements which describe events.
                                      Moduletei
                                      Used by
                                      Membersevent listEvent

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.eventLike

                                      model.eventLike groups elements which describe events.
                                      Moduletei
                                      Used by
                                      Membersevent listEvent

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.formPart.html b/gl/dev/ref-model.formPart.html index 05616d9ca..5a5edd642 100644 --- a/gl/dev/ref-model.formPart.html +++ b/gl/dev/ref-model.formPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.formPart

                                      model.formPart groups elements allowed within a form element in a dictionary. [9.3.1. Information on Written and Spoken Forms]
                                      Moduledictionaries
                                      Used by
                                      Membersmodel.gramPart [model.lexicalRefinement model.morphLike [gen] ] form

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.formPart

                                      model.formPart groups elements allowed within a form element in a dictionary. [9.3.1. Information on Written and Spoken Forms]
                                      Moduledictionaries
                                      Used by
                                      Membersmodel.gramPart [model.lexicalRefinement model.morphLike [gen] ] form

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.frontPart.html b/gl/dev/ref-model.frontPart.html index c9ec1ffa6..0f9b6a629 100644 --- a/gl/dev/ref-model.frontPart.html +++ b/gl/dev/ref-model.frontPart.html @@ -22,4 +22,4 @@ }); });

                                      model.frontPart

                                      model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter - ]
                                      Moduletei
                                      Used by
                                      Membersmodel.frontPart.drama divGen listBibl

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file + ]ModuleteiUsed by
                                      back front
                                      Membersmodel.frontPart.drama divGen listBibl

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.gLike.html b/gl/dev/ref-model.gLike.html index 7b23b7aff..a5b9994cc 100644 --- a/gl/dev/ref-model.gLike.html +++ b/gl/dev/ref-model.gLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.gLike

                                      model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
                                      Moduletei
                                      Used by
                                      Membersg

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.gLike

                                      model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
                                      Moduletei
                                      Used by
                                      Membersg

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.global.edit.html b/gl/dev/ref-model.global.edit.html index 72c4ad5e1..a4daa85c3 100644 --- a/gl/dev/ref-model.global.edit.html +++ b/gl/dev/ref-model.global.edit.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.global.edit

                                      model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      MembersaddSpan app delSpan ellipsis gap space

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.global.edit

                                      model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      MembersaddSpan app delSpan ellipsis gap space

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.global.html b/gl/dev/ref-model.global.html index 1830d9e3b..b9fb1e039 100644 --- a/gl/dev/ref-model.global.html +++ b/gl/dev/ref-model.global.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.global

                                      model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.global.edit [addSpan app delSpan ellipsis gap space] model.global.meta [certainty index interp interpGrp join link linkGrp listTranspose precision substJoin] model.global.spoken model.milestoneLike [anchor cb fw gb lb milestone pb] model.noteLike [note noteGrp] figure metamark notatedMusic

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.global

                                      model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.global.edit [addSpan app delSpan ellipsis gap space] model.global.meta [certainty index interp interpGrp join link linkGrp listTranspose precision substJoin] model.global.spoken model.milestoneLike [anchor cb fw gb lb milestone pb] model.noteLike [note noteGrp] figure metamark notatedMusic

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.global.meta.html b/gl/dev/ref-model.global.meta.html index 43651f25a..9d055099a 100644 --- a/gl/dev/ref-model.global.meta.html +++ b/gl/dev/ref-model.global.meta.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.global.meta

                                      model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Memberscertainty index interp interpGrp join link linkGrp listTranspose precision substJoin
                                      Note

                                      Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.global.meta

                                      model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Memberscertainty index interp interpGrp join link linkGrp listTranspose precision substJoin
                                      Note

                                      Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.gramPart.html b/gl/dev/ref-model.gramPart.html index 552090ee9..4e21e9fc3 100644 --- a/gl/dev/ref-model.gramPart.html +++ b/gl/dev/ref-model.gramPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.gramPart

                                      model.gramPart groups elements allowed within a <gramGrp> element in a dictionary. [9.3.2. Grammatical Information]
                                      Moduledictionaries
                                      Used by
                                      Membersmodel.lexicalRefinement model.morphLike [gen]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.gramPart

                                      model.gramPart groups elements allowed within a <gramGrp> element in a dictionary. [9.3.2. Grammatical Information]
                                      Moduledictionaries
                                      Used by
                                      Membersmodel.lexicalRefinement model.morphLike [gen]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.graphicLike.html b/gl/dev/ref-model.graphicLike.html index 3c2099fad..6f708955b 100644 --- a/gl/dev/ref-model.graphicLike.html +++ b/gl/dev/ref-model.graphicLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.graphicLike

                                      model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
                                      Moduletei
                                      Used by
                                      MembersbinaryObject graphic media

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.graphicLike

                                      model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
                                      Moduletei
                                      Used by
                                      MembersbinaryObject graphic media

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.headLike.html b/gl/dev/ref-model.headLike.html index 837717787..38e6a5c6c 100644 --- a/gl/dev/ref-model.headLike.html +++ b/gl/dev/ref-model.headLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.headLike

                                      model.headLike groups elements used to provide a title or heading at the start of a text division.
                                      Moduletei
                                      Used by
                                      Membershead

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.headLike

                                      model.headLike groups elements used to provide a title or heading at the start of a text division.
                                      Moduletei
                                      Used by
                                      Membershead

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.hiLike.html b/gl/dev/ref-model.hiLike.html index f412362bc..206f8ffc2 100644 --- a/gl/dev/ref-model.hiLike.html +++ b/gl/dev/ref-model.hiLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.hiLike

                                      model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
                                      Moduletei
                                      Used by
                                      Membershi q

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.hiLike

                                      model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
                                      Moduletei
                                      Used by
                                      Membershi q

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.highlighted.html b/gl/dev/ref-model.highlighted.html index 985c4696a..3d18f69aa 100644 --- a/gl/dev/ref-model.highlighted.html +++ b/gl/dev/ref-model.highlighted.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.highlighted

                                      model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
                                      Moduletei
                                      Used by
                                      Membersmodel.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.highlighted

                                      model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
                                      Moduletei
                                      Used by
                                      Membersmodel.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.imprintPart.html b/gl/dev/ref-model.imprintPart.html index 0d9f094df..687542549 100644 --- a/gl/dev/ref-model.imprintPart.html +++ b/gl/dev/ref-model.imprintPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.imprintPart

                                      model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
                                      Moduletei
                                      Used by
                                      MembersbiblScope distributor pubPlace publisher

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.imprintPart

                                      model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
                                      Moduletei
                                      Used by
                                      MembersbiblScope distributor pubPlace publisher

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.inter.html b/gl/dev/ref-model.inter.html index ef265039d..d97eae53a 100644 --- a/gl/dev/ref-model.inter.html +++ b/gl/dev/ref-model.inter.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.inter

                                      model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike [stage]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.inter

                                      model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike [stage]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.lLike.html b/gl/dev/ref-model.lLike.html index 317996fb8..b1509058b 100644 --- a/gl/dev/ref-model.lLike.html +++ b/gl/dev/ref-model.lLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.lLike

                                      model.lLike groups elements representing metrical components such as verse lines.
                                      Moduletei
                                      Used by
                                      Membersl

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.lLike

                                      model.lLike groups elements representing metrical components such as verse lines.
                                      Moduletei
                                      Used by
                                      Membersl

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.labelLike.html b/gl/dev/ref-model.labelLike.html index d0870e94c..4c1b22b5c 100644 --- a/gl/dev/ref-model.labelLike.html +++ b/gl/dev/ref-model.labelLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.labelLike

                                      model.labelLike groups elements used to gloss or explain other parts of a document.
                                      Moduletei
                                      Used by
                                      Membersdesc label

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.labelLike

                                      model.labelLike groups elements used to gloss or explain other parts of a document.
                                      Moduletei
                                      Used by
                                      Membersdesc label

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.limitedPhrase.html b/gl/dev/ref-model.limitedPhrase.html index c479ee00f..726bedb3c 100644 --- a/gl/dev/ref-model.limitedPhrase.html +++ b/gl/dev/ref-model.limitedPhrase.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.limitedPhrase

                                      model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q] model.pPart.data [model.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] ] model.pPart.editorial [abbr am choice ex expan subst] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ptr ref]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.limitedPhrase

                                      model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q] model.pPart.data [model.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] ] model.pPart.editorial [abbr am choice ex expan subst] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ptr ref]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.linePart.html b/gl/dev/ref-model.linePart.html index 8c9546cb8..61649f992 100644 --- a/gl/dev/ref-model.linePart.html +++ b/gl/dev/ref-model.linePart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.linePart

                                      model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a sourceDoc element.
                                      Moduletei
                                      Used by
                                      Membersmodel.hiLike [hi q] add c choice damage del handShift line mod path pc redo retrace seg unclear undo w zone

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.linePart

                                      model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a sourceDoc element.
                                      Moduletei
                                      Used by
                                      Membersmodel.hiLike [hi q] add c choice damage del handShift line mod path pc redo retrace seg unclear undo w zone

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.listLike.html b/gl/dev/ref-model.listLike.html index 9a239a382..43df86c8b 100644 --- a/gl/dev/ref-model.listLike.html +++ b/gl/dev/ref-model.listLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.listLike

                                      model.listLike groups list-like elements. [3.8. Lists]
                                      Moduletei
                                      Used by
                                      Memberslist listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.listLike

                                      model.listLike groups list-like elements. [3.8. Lists]
                                      Moduletei
                                      Used by
                                      Memberslist listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.measureLike.html b/gl/dev/ref-model.measureLike.html index 61fd2660f..bbf6fcd94 100644 --- a/gl/dev/ref-model.measureLike.html +++ b/gl/dev/ref-model.measureLike.html @@ -22,4 +22,4 @@ }); });

                                      model.measureLike

                                      model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and -Measures]
                                      Moduletei
                                      Used by
                                      Membersdepth dim geo height measure measureGrp num unit width

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Measures]ModuleteiUsed by
                                      location measureGrp model.pPart.data
                                      Membersdepth dim geo height measure measureGrp num unit width

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.milestoneLike.html b/gl/dev/ref-model.milestoneLike.html index 1820d893d..7d3aad96e 100644 --- a/gl/dev/ref-model.milestoneLike.html +++ b/gl/dev/ref-model.milestoneLike.html @@ -22,4 +22,4 @@ }); });

                                      model.milestoneLike

                                      model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone -Elements]
                                      Moduletei
                                      Used by
                                      Membersanchor cb fw gb lb milestone pb

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Elements]ModuleteiUsed by
                                      listBibl model.global org subst
                                      Membersanchor cb fw gb lb milestone pb

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.morphLike.html b/gl/dev/ref-model.morphLike.html index 79d525421..560f65343 100644 --- a/gl/dev/ref-model.morphLike.html +++ b/gl/dev/ref-model.morphLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.morphLike

                                      model.morphLike groups elements which provide morphological information within a dictionary entry. [9.3. Top-level Constituents of Entries]
                                      Moduledictionaries
                                      Used by
                                      Membersgen

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.morphLike

                                      model.morphLike groups elements which provide morphological information within a dictionary entry. [9.3. Top-level Constituents of Entries]
                                      Moduledictionaries
                                      Used by
                                      Membersgen

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.msItemPart.html b/gl/dev/ref-model.msItemPart.html index 5cc1959f3..f7cb458ab 100644 --- a/gl/dev/ref-model.msItemPart.html +++ b/gl/dev/ref-model.msItemPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.msItemPart

                                      model.msItemPart groups elements which can appear within a manuscript item description.
                                      Moduletei
                                      Used by
                                      Membersmodel.biblLike [bibl biblFull biblStruct listBibl msDesc] model.msQuoteLike [colophon explicit finalRubric incipit rubric title] model.quoteLike [cit quote] model.respLike [author editor funder meeting principal respStmt sponsor] decoNote filiation idno msItem msItemStruct textLang

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.msItemPart

                                      model.msItemPart groups elements which can appear within a manuscript item description.
                                      Moduletei
                                      Used by
                                      Membersmodel.biblLike [bibl biblFull biblStruct listBibl msDesc] model.msQuoteLike [colophon explicit finalRubric incipit rubric title] model.quoteLike [cit quote] model.respLike [author editor funder meeting principal respStmt sponsor] decoNote filiation idno msItem msItemStruct textLang

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.msQuoteLike.html b/gl/dev/ref-model.msQuoteLike.html index 5d4d1c58b..2ebc8a6f6 100644 --- a/gl/dev/ref-model.msQuoteLike.html +++ b/gl/dev/ref-model.msQuoteLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.msQuoteLike

                                      model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
                                      Moduletei
                                      Used by
                                      Memberscolophon explicit finalRubric incipit rubric title

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.msQuoteLike

                                      model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
                                      Moduletei
                                      Used by
                                      Memberscolophon explicit finalRubric incipit rubric title

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.nameLike.agent.html b/gl/dev/ref-model.nameLike.agent.html index 86525b226..7013a1f36 100644 --- a/gl/dev/ref-model.nameLike.agent.html +++ b/gl/dev/ref-model.nameLike.agent.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.nameLike.agent

                                      model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
                                      Moduletei
                                      Used by
                                      Membersname orgName persName
                                      Note

                                      This class is used in the content model of elements which reference names of people or organizations.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.nameLike.agent

                                      model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
                                      Moduletei
                                      Used by
                                      Membersname orgName persName
                                      Note

                                      This class is used in the content model of elements which reference names of people or organizations.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.nameLike.html b/gl/dev/ref-model.nameLike.html index e84e3d7c9..9a772ca7c 100644 --- a/gl/dev/ref-model.nameLike.html +++ b/gl/dev/ref-model.nameLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.nameLike

                                      model.nameLike groups elements which name or refer to a person, place, or organization.
                                      Moduletei
                                      Used by
                                      Membersmodel.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs
                                      Note

                                      A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.nameLike

                                      model.nameLike groups elements which name or refer to a person, place, or organization.
                                      Moduletei
                                      Used by
                                      Membersmodel.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs
                                      Note

                                      A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.noteLike.html b/gl/dev/ref-model.noteLike.html index 31787f774..67e9138b4 100644 --- a/gl/dev/ref-model.noteLike.html +++ b/gl/dev/ref-model.noteLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.noteLike

                                      model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
                                      Moduletei
                                      Used by
                                      Membersnote noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.noteLike

                                      model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
                                      Moduletei
                                      Used by
                                      Membersnote noteGrp

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.objectLike.html b/gl/dev/ref-model.objectLike.html index 142929950..03ac63604 100644 --- a/gl/dev/ref-model.objectLike.html +++ b/gl/dev/ref-model.objectLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.objectLike

                                      model.objectLike groups elements which describe objects.
                                      Moduletei
                                      Used by
                                      MemberslistObject object

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.objectLike

                                      model.objectLike groups elements which describe objects.
                                      Moduletei
                                      Used by
                                      MemberslistObject object

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.offsetLike.html b/gl/dev/ref-model.offsetLike.html index 7b6b25881..220809782 100644 --- a/gl/dev/ref-model.offsetLike.html +++ b/gl/dev/ref-model.offsetLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.offsetLike

                                      model.offsetLike groups elements which can appear only as part of a place name. [13.2.3. Place Names]
                                      Moduletei
                                      Used by
                                      MembersgeogFeat offset

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.offsetLike

                                      model.offsetLike groups elements which can appear only as part of a place name. [13.2.3. Place Names]
                                      Moduletei
                                      Used by
                                      MembersgeogFeat offset

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.orgPart.html b/gl/dev/ref-model.orgPart.html index 447df39d4..7f82e8d58 100644 --- a/gl/dev/ref-model.orgPart.html +++ b/gl/dev/ref-model.orgPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.orgPart

                                      model.orgPart groups elements which form part of the description of an organization.
                                      Moduletei
                                      Used by
                                      Membersmodel.eventLike [event listEvent] listOrg listPerson listPlace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.orgPart

                                      model.orgPart groups elements which form part of the description of an organization.
                                      Moduletei
                                      Used by
                                      Membersmodel.eventLike [event listEvent] listOrg listPerson listPlace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pLike.front.html b/gl/dev/ref-model.pLike.front.html index 36fff5310..cb94e20ba 100644 --- a/gl/dev/ref-model.pLike.front.html +++ b/gl/dev/ref-model.pLike.front.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pLike.front

                                      model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
                                      Moduletei
                                      Used by
                                      Membersdateline docAuthor docDate docEdition docImprint docTitle epigraph head

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pLike.front

                                      model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
                                      Moduletei
                                      Used by
                                      Membersdateline docAuthor docDate docEdition docImprint docTitle epigraph head

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pLike.html b/gl/dev/ref-model.pLike.html index 88e3117c0..41e689a14 100644 --- a/gl/dev/ref-model.pLike.html +++ b/gl/dev/ref-model.pLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pLike

                                      model.pLike groups paragraph-like elements.
                                      Moduletei
                                      Used by
                                      Membersab p

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pLike

                                      model.pLike groups paragraph-like elements.
                                      Moduletei
                                      Used by
                                      Membersab p

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pPart.data.html b/gl/dev/ref-model.pPart.data.html index b6965393b..2ba882d81 100644 --- a/gl/dev/ref-model.pPart.data.html +++ b/gl/dev/ref-model.pPart.data.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pPart.data

                                      model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
                                      Moduletei
                                      Used by
                                      Membersmodel.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pPart.data

                                      model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
                                      Moduletei
                                      Used by
                                      Membersmodel.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pPart.edit.html b/gl/dev/ref-model.pPart.edit.html index 0558ed637..e55a664a1 100644 --- a/gl/dev/ref-model.pPart.edit.html +++ b/gl/dev/ref-model.pPart.edit.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pPart.edit

                                      model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersmodel.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo]

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pPart.edit

                                      model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersmodel.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo]

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pPart.editorial.html b/gl/dev/ref-model.pPart.editorial.html index faf50fb3c..1cd094294 100644 --- a/gl/dev/ref-model.pPart.editorial.html +++ b/gl/dev/ref-model.pPart.editorial.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pPart.editorial

                                      model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersabbr am choice ex expan subst

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pPart.editorial

                                      model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersabbr am choice ex expan subst

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pPart.msdesc.html b/gl/dev/ref-model.pPart.msdesc.html index 5f83a1ee8..7cb951c84 100644 --- a/gl/dev/ref-model.pPart.msdesc.html +++ b/gl/dev/ref-model.pPart.msdesc.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pPart.msdesc

                                      model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
                                      Moduletei
                                      Used by
                                      Memberscatchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pPart.msdesc

                                      model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
                                      Moduletei
                                      Used by
                                      Memberscatchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.pPart.transcriptional.html b/gl/dev/ref-model.pPart.transcriptional.html index c2e9f2746..64133bfd1 100644 --- a/gl/dev/ref-model.pPart.transcriptional.html +++ b/gl/dev/ref-model.pPart.transcriptional.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.pPart.transcriptional

                                      model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersadd corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.pPart.transcriptional

                                      model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
                                      Moduletei
                                      Used by
                                      Membersadd corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.paraPart.html b/gl/dev/ref-model.paraPart.html index 236e83461..d9bff902a 100644 --- a/gl/dev/ref-model.paraPart.html +++ b/gl/dev/ref-model.paraPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.paraPart

                                      model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
                                      Moduletei
                                      Used by
                                      Membersmodel.gLike [g] model.global [model.global.edit [addSpan app delSpan ellipsis gap space] model.global.meta [certainty index interp interpGrp join link linkGrp listTranspose precision substJoin] model.global.spoken model.milestoneLike [anchor cb fw gb lb milestone pb] model.noteLike [note noteGrp] figure metamark notatedMusic] model.inter [model.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike [stage] ] model.lLike [l] model.phrase [model.graphicLike [binaryObject graphic media] model.highlighted [model.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ptr ref] model.ptrLike.form model.segLike [c m pc phr s seg w] model.specDescLike ruby] lg

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.paraPart

                                      model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
                                      Moduletei
                                      Used by
                                      Membersmodel.gLike [g] model.global [model.global.edit [addSpan app delSpan ellipsis gap space] model.global.meta [certainty index interp interpGrp join link linkGrp listTranspose precision substJoin] model.global.spoken model.milestoneLike [anchor cb fw gb lb milestone pb] model.noteLike [note noteGrp] figure metamark notatedMusic] model.inter [model.attributable [model.quoteLike [cit quote] floatingText said] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] model.oddDecl model.stageLike [stage] ] model.lLike [l] model.phrase [model.graphicLike [binaryObject graphic media] model.highlighted [model.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ptr ref] model.ptrLike.form model.segLike [c m pc phr s seg w] model.specDescLike ruby] lg

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.persNamePart.html b/gl/dev/ref-model.persNamePart.html index 9a90bd5c4..c35603525 100644 --- a/gl/dev/ref-model.persNamePart.html +++ b/gl/dev/ref-model.persNamePart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.persNamePart

                                      model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Used by
                                      MembersaddName forename genName persPronouns roleName surname

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.persNamePart

                                      model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Used by
                                      MembersaddName forename genName persPronouns roleName surname

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.persStateLike.html b/gl/dev/ref-model.persStateLike.html index cd3e07ebb..a722e209a 100644 --- a/gl/dev/ref-model.persStateLike.html +++ b/gl/dev/ref-model.persStateLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.persStateLike

                                      model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
                                      Moduletei
                                      Used by
                                      Membersfloruit gender persName persPronouns persona state
                                      Note

                                      These characteristics of an individual are typically a consequence of their own action or that of others.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.persStateLike

                                      model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
                                      Moduletei
                                      Used by
                                      Membersfloruit gender persName persPronouns persona state
                                      Note

                                      These characteristics of an individual are typically a consequence of their own action or that of others.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.personLike.html b/gl/dev/ref-model.personLike.html index 7045880ee..f53ee8945 100644 --- a/gl/dev/ref-model.personLike.html +++ b/gl/dev/ref-model.personLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.personLike

                                      model.personLike groups elements which provide information about people and their relationships.
                                      Moduletei
                                      Used by
                                      Membersorg person personGrp

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.personLike

                                      model.personLike groups elements which provide information about people and their relationships.
                                      Moduletei
                                      Used by
                                      Membersorg person personGrp

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.personPart.html b/gl/dev/ref-model.personPart.html index 9d370455f..7911f40ca 100644 --- a/gl/dev/ref-model.personPart.html +++ b/gl/dev/ref-model.personPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.personPart

                                      model.personPart groups elements which form part of the description of a person. [15.2.2. The Participant Description]
                                      Moduletei
                                      Used by
                                      Membersmodel.biblLike [bibl biblFull biblStruct listBibl msDesc] model.eventLike [event listEvent] model.persStateLike [floruit gender persName persPronouns persona state] birth death idno name

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.personPart

                                      model.personPart groups elements which form part of the description of a person. [15.2.2. The Participant Description]
                                      Moduletei
                                      Used by
                                      Membersmodel.biblLike [bibl biblFull biblStruct listBibl msDesc] model.eventLike [event listEvent] model.persStateLike [floruit gender persName persPronouns persona state] birth death idno name

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.phrase.html b/gl/dev/ref-model.phrase.html index aa336240f..39947a649 100644 --- a/gl/dev/ref-model.phrase.html +++ b/gl/dev/ref-model.phrase.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.phrase

                                      model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.graphicLike [binaryObject graphic media] model.highlighted [model.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ptr ref] model.ptrLike.form model.segLike [c m pc phr s seg w] model.specDescLike ruby
                                      Note

                                      This class of elements can occur within paragraphs, list items, lines of verse, etc.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.phrase

                                      model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersmodel.graphicLike [binaryObject graphic media] model.highlighted [model.emphLike [distinct emph foreign gloss mentioned soCalled term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address email] model.dateLike [date time] model.measureLike [depth dim geo height measure measureGrp num unit width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName persPronouns roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] location state] idno lang objectName rs] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del handShift mod orig redo reg retrace secl sic supplied surplus unclear undo] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ptr ref] model.ptrLike.form model.segLike [c m pc phr s seg w] model.specDescLike ruby
                                      Note

                                      This class of elements can occur within paragraphs, list items, lines of verse, etc.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.physDescPart.html b/gl/dev/ref-model.physDescPart.html index 15b8313d8..67d7e7024 100644 --- a/gl/dev/ref-model.physDescPart.html +++ b/gl/dev/ref-model.physDescPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.physDescPart

                                      model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
                                      Modulemsdescription
                                      Used by
                                      MembersaccMat additions bindingDesc decoDesc handDesc musicNotation objectDesc scriptDesc sealDesc typeDesc

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.physDescPart

                                      model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
                                      Modulemsdescription
                                      Used by
                                      MembersaccMat additions bindingDesc decoDesc handDesc musicNotation objectDesc scriptDesc sealDesc typeDesc

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.placeLike.html b/gl/dev/ref-model.placeLike.html index fac429aba..417b2ef02 100644 --- a/gl/dev/ref-model.placeLike.html +++ b/gl/dev/ref-model.placeLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.placeLike

                                      model.placeLike groups elements used to provide information about places and their relationships.
                                      Moduletei
                                      Used by
                                      Membersplace

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.placeLike

                                      model.placeLike groups elements used to provide information about places and their relationships.
                                      Moduletei
                                      Used by
                                      Membersplace

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.placeNamePart.html b/gl/dev/ref-model.placeNamePart.html index 30932ec2b..18da1da3c 100644 --- a/gl/dev/ref-model.placeNamePart.html +++ b/gl/dev/ref-model.placeNamePart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.placeNamePart

                                      model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
                                      Moduletei
                                      Used by
                                      Membersbloc country district geogName placeName region settlement

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.placeNamePart

                                      model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
                                      Moduletei
                                      Used by
                                      Membersbloc country district geogName placeName region settlement

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.placeStateLike.html b/gl/dev/ref-model.placeStateLike.html index 0bdcfbed3..18f9034b8 100644 --- a/gl/dev/ref-model.placeStateLike.html +++ b/gl/dev/ref-model.placeStateLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.placeStateLike

                                      model.placeStateLike groups elements which describe changing states of a place.
                                      Moduletei
                                      Used by
                                      Membersmodel.placeNamePart [bloc country district geogName placeName region settlement] location state

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.placeStateLike

                                      model.placeStateLike groups elements which describe changing states of a place.
                                      Moduletei
                                      Used by
                                      Membersmodel.placeNamePart [bloc country district geogName placeName region settlement] location state

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.profileDescPart.html b/gl/dev/ref-model.profileDescPart.html index a7f306c01..4216bad97 100644 --- a/gl/dev/ref-model.profileDescPart.html +++ b/gl/dev/ref-model.profileDescPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.profileDescPart

                                      model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times.
                                      Moduletei
                                      Used by
                                      Membersabstract calendarDesc correspDesc creation handNotes langUsage listTranspose particDesc settingDesc textClass

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.profileDescPart

                                      model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times.
                                      Moduletei
                                      Used by
                                      Membersabstract calendarDesc correspDesc creation handNotes langUsage listTranspose particDesc settingDesc textClass

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.ptrLike.html b/gl/dev/ref-model.ptrLike.html index acf89ec59..6312a824d 100644 --- a/gl/dev/ref-model.ptrLike.html +++ b/gl/dev/ref-model.ptrLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.ptrLike

                                      model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
                                      Moduletei
                                      Used by
                                      Membersptr ref

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.ptrLike

                                      model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
                                      Moduletei
                                      Used by
                                      Membersptr ref

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.publicationStmtPart.agency.html b/gl/dev/ref-model.publicationStmtPart.agency.html index c209df4f3..58d5d0826 100644 --- a/gl/dev/ref-model.publicationStmtPart.agency.html +++ b/gl/dev/ref-model.publicationStmtPart.agency.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.publicationStmtPart.agency

                                      model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduletei
                                      Used by
                                      Membersauthority distributor publisher
                                      Note

                                      The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

                                      See also model.publicationStmtPart.detail.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.publicationStmtPart.agency

                                      model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduletei
                                      Used by
                                      Membersauthority distributor publisher
                                      Note

                                      The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

                                      See also model.publicationStmtPart.detail.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.publicationStmtPart.detail.html b/gl/dev/ref-model.publicationStmtPart.detail.html index b0f136e81..3e78dbf2a 100644 --- a/gl/dev/ref-model.publicationStmtPart.detail.html +++ b/gl/dev/ref-model.publicationStmtPart.detail.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.publicationStmtPart.detail

                                      model.publicationStmtPart.detail groups the agency-specific child elements of the publicationStmt element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduletei
                                      Used by
                                      Membersmodel.ptrLike [ptr ref] address availability date idno pubPlace
                                      Note

                                      A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

                                      See also model.publicationStmtPart.agency.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.publicationStmtPart.detail

                                      model.publicationStmtPart.detail groups the agency-specific child elements of the publicationStmt element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
                                      Moduletei
                                      Used by
                                      Membersmodel.ptrLike [ptr ref] address availability date idno pubPlace
                                      Note

                                      A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

                                      See also model.publicationStmtPart.agency.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.quoteLike.html b/gl/dev/ref-model.quoteLike.html index da6b6b8ff..89877e2ea 100644 --- a/gl/dev/ref-model.quoteLike.html +++ b/gl/dev/ref-model.quoteLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.quoteLike

                                      model.quoteLike groups elements used to directly contain quotations.
                                      Moduletei
                                      Used by
                                      Memberscit quote

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.quoteLike

                                      model.quoteLike groups elements used to directly contain quotations.
                                      Moduletei
                                      Used by
                                      Memberscit quote

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.rdgLike.html b/gl/dev/ref-model.rdgLike.html index 53697ac76..876021ca6 100644 --- a/gl/dev/ref-model.rdgLike.html +++ b/gl/dev/ref-model.rdgLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.rdgLike

                                      model.rdgLike groups elements which contain a single reading, other than the lemma, within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Used by
                                      Membersrdg
                                      Note

                                      This class allows for variants of the rdg element to be easily created via TEI customizations.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.rdgLike

                                      model.rdgLike groups elements which contain a single reading, other than the lemma, within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Used by
                                      Membersrdg
                                      Note

                                      This class allows for variants of the rdg element to be easily created via TEI customizations.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.rdgPart.html b/gl/dev/ref-model.rdgPart.html index c02b637a2..68413e5df 100644 --- a/gl/dev/ref-model.rdgPart.html +++ b/gl/dev/ref-model.rdgPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.rdgPart

                                      model.rdgPart groups elements which mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. Fragmentary Witnesses]
                                      Moduletextcrit
                                      Used by
                                      Memberswit
                                      Note

                                      These elements may appear anywhere within the elements lem and rdg, and also within any of their constituent elements.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.rdgPart

                                      model.rdgPart groups elements which mark the beginning or ending of a fragmentary manuscript or other witness. [12.1.5. Fragmentary Witnesses]
                                      Moduletextcrit
                                      Used by
                                      Memberswit
                                      Note

                                      These elements may appear anywhere within the elements lem and rdg, and also within any of their constituent elements.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.resource.html b/gl/dev/ref-model.resource.html index 9c1ada872..65cdf2e8a 100644 --- a/gl/dev/ref-model.resource.html +++ b/gl/dev/ref-model.resource.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.resource

                                      model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersfacsimile sourceDoc standOff text

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.resource

                                      model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
                                      Moduletei
                                      Used by
                                      Membersfacsimile sourceDoc standOff text

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.respLike.html b/gl/dev/ref-model.respLike.html index 0dc12c9a8..35e74c394 100644 --- a/gl/dev/ref-model.respLike.html +++ b/gl/dev/ref-model.respLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.respLike

                                      model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
                                      Moduletei
                                      Used by
                                      Membersauthor editor funder meeting principal respStmt sponsor

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.respLike

                                      model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
                                      Moduletei
                                      Used by
                                      Membersauthor editor funder meeting principal respStmt sponsor

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.segLike.html b/gl/dev/ref-model.segLike.html index 27f17142a..965ed3024 100644 --- a/gl/dev/ref-model.segLike.html +++ b/gl/dev/ref-model.segLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.segLike

                                      model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
                                      Moduletei
                                      Used by
                                      Membersc m pc phr s seg w
                                      Note

                                      The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the segmentation element of the encodingDesc within the associated TEI header.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.segLike

                                      model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
                                      Moduletei
                                      Used by
                                      Membersc m pc phr s seg w
                                      Note

                                      The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the segmentation element of the encodingDesc within the associated TEI header.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.stageLike.html b/gl/dev/ref-model.stageLike.html index 6ca86483e..6aa811a7b 100644 --- a/gl/dev/ref-model.stageLike.html +++ b/gl/dev/ref-model.stageLike.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.stageLike

                                      model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]
                                      Moduletei
                                      Used by
                                      Membersstage
                                      Note

                                      Stage directions are members of class inter: that is, they can appear between or within component-level elements.

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.stageLike

                                      model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]
                                      Moduletei
                                      Used by
                                      Membersstage
                                      Note

                                      Stage directions are members of class inter: that is, they can appear between or within component-level elements.

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.standOffPart.html b/gl/dev/ref-model.standOffPart.html index 7124137af..7d2ba6c68 100644 --- a/gl/dev/ref-model.standOffPart.html +++ b/gl/dev/ref-model.standOffPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.standOffPart

                                      model.standOffPart groups elements which may be used as children of standOff.
                                      Moduletei
                                      Used by
                                      Membersmodel.annotationLike [annotation annotationBlock note] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.entryLike model.global.meta [certainty index interp interpGrp join link linkGrp listTranspose precision substJoin] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] listAnnotation listChange seg zone

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.standOffPart

                                      model.standOffPart groups elements which may be used as children of standOff.
                                      Moduletei
                                      Used by
                                      Membersmodel.annotationLike [annotation annotationBlock note] model.biblLike [bibl biblFull biblStruct listBibl msDesc] model.entryLike model.global.meta [certainty index interp interpGrp join link linkGrp listTranspose precision substJoin] model.listLike [list listApp listEvent listNym listObject listOrg listPerson listPlace listRelation table] listAnnotation listChange seg zone

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.teiHeaderPart.html b/gl/dev/ref-model.teiHeaderPart.html index 0d7b44644..d700db203 100644 --- a/gl/dev/ref-model.teiHeaderPart.html +++ b/gl/dev/ref-model.teiHeaderPart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.teiHeaderPart

                                      model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
                                      Moduletei
                                      Used by
                                      MembersencodingDesc profileDesc xenoData

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.teiHeaderPart

                                      model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
                                      Moduletei
                                      Used by
                                      MembersencodingDesc profileDesc xenoData

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-model.titlepagePart.html b/gl/dev/ref-model.titlepagePart.html index af012623a..b92dce20a 100644 --- a/gl/dev/ref-model.titlepagePart.html +++ b/gl/dev/ref-model.titlepagePart.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      model.titlepagePart

                                      model.titlepagePart groups elements which can occur as direct constituents of a title page, such as docTitle, docAuthor, docImprint, or epigraph. [4.6. Title Pages]
                                      Moduletei
                                      Used by
                                      MembersbinaryObject docAuthor docDate docEdition docImprint docTitle epigraph graphic

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      model.titlepagePart

                                      model.titlepagePart groups elements which can occur as direct constituents of a title page, such as docTitle, docAuthor, docImprint, or epigraph. [4.6. Title Pages]
                                      Moduletei
                                      Used by
                                      MembersbinaryObject docAuthor docDate docEdition docImprint docTitle epigraph graphic

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-monogr.html b/gl/dev/ref-monogr.html index 6c06f3d85..1e7bf5c38 100644 --- a/gl/dev/ref-monogr.html +++ b/gl/dev/ref-monogr.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <monogr>

                                      <monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      May contain specialized bibliographic elements, in a prescribed order.

                                      The monogr element may only occur only within a biblStruct, where its use is mandatory for the description of a monographic-level bibliographic item.

                                      Example
                                      <biblStruct>
                                       <analytic>
                                        <author>Chesnutt, David</author>
                                        <title>Historical Editions in the States</title>
                                       </analytic>
                                       <monogr>
                                        <title level="j">Computers and the Humanities</title>
                                        <imprint>
                                         <date when="1991-12">(December, 1991):</date>
                                        </imprint>
                                        <biblScope>25.6</biblScope>
                                        <biblScope unit="pagefrom="377to="380">377–380</biblScope>
                                       </monogr>
                                      </biblStruct>
                                      Example
                                      <biblStruct type="book">
                                       <monogr>
                                        <author>
                                         <persName>
                                          <forename>Leo Joachim</forename>
                                          <surname>Frachtenberg</surname>
                                         </persName>
                                        </author>
                                        <title type="mainlevel="m">Lower Umpqua Texts</title>
                                        <imprint>
                                         <pubPlace>New York</pubPlace>
                                         <publisher>Columbia University Press</publisher>
                                         <date>1914</date>
                                        </imprint>
                                       </monogr>
                                       <series>
                                        <title type="mainlevel="s">Columbia University Contributions to
                                           Anthropology</title>
                                        <biblScope unit="volume">4</biblScope>
                                       </series>
                                      </biblStruct>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0">
                                         <sequence>
                                          <alternate>
                                           <elementRef key="author"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="meeting"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="author"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="meeting"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                          <elementRef key="titleminOccurs="1"
                                           maxOccurs="unbounded"/>

                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.ptrLike"/>
                                           <elementRef key="idno"/>
                                           <elementRef key="textLang"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <alternate minOccurs="1"
                                           maxOccurs="unbounded">

                                           <elementRef key="title"/>
                                           <classRef key="model.ptrLike"/>
                                           <elementRef key="idno"/>
                                          </alternate>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="textLang"/>
                                           <elementRef key="author"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="meeting"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <elementRef key="authority"/>
                                          <elementRef key="idno"/>
                                         </sequence>
                                        </alternate>
                                        <elementRef key="availability"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.noteLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="edition"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="idno"/>
                                          <classRef key="model.ptrLike"/>
                                          <elementRef key="editor"/>
                                          <elementRef key="sponsor"/>
                                          <elementRef key="funder"/>
                                          <elementRef key="respStmt"/>
                                         </alternate>
                                        </sequence>
                                        <elementRef key="imprint"/>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="imprint"/>
                                         <elementRef key="extent"/>
                                         <elementRef key="biblScope"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <monogr>

                                      <monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      May contain specialized bibliographic elements, in a prescribed order.

                                      The monogr element may only occur only within a biblStruct, where its use is mandatory for the description of a monographic-level bibliographic item.

                                      Example
                                      <biblStruct>
                                       <analytic>
                                        <author>Chesnutt, David</author>
                                        <title>Historical Editions in the States</title>
                                       </analytic>
                                       <monogr>
                                        <title level="j">Computers and the Humanities</title>
                                        <imprint>
                                         <date when="1991-12">(December, 1991):</date>
                                        </imprint>
                                        <biblScope>25.6</biblScope>
                                        <biblScope unit="pagefrom="377to="380">377–380</biblScope>
                                       </monogr>
                                      </biblStruct>
                                      Example
                                      <biblStruct type="book">
                                       <monogr>
                                        <author>
                                         <persName>
                                          <forename>Leo Joachim</forename>
                                          <surname>Frachtenberg</surname>
                                         </persName>
                                        </author>
                                        <title type="mainlevel="m">Lower Umpqua Texts</title>
                                        <imprint>
                                         <pubPlace>New York</pubPlace>
                                         <publisher>Columbia University Press</publisher>
                                         <date>1914</date>
                                        </imprint>
                                       </monogr>
                                       <series>
                                        <title type="mainlevel="s">Columbia University Contributions to
                                           Anthropology</title>
                                        <biblScope unit="volume">4</biblScope>
                                       </series>
                                      </biblStruct>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0">
                                         <sequence>
                                          <alternate>
                                           <elementRef key="author"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="meeting"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="author"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="meeting"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                          <elementRef key="titleminOccurs="1"
                                           maxOccurs="unbounded"/>

                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.ptrLike"/>
                                           <elementRef key="idno"/>
                                           <elementRef key="textLang"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <alternate minOccurs="1"
                                           maxOccurs="unbounded">

                                           <elementRef key="title"/>
                                           <classRef key="model.ptrLike"/>
                                           <elementRef key="idno"/>
                                          </alternate>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="textLang"/>
                                           <elementRef key="author"/>
                                           <elementRef key="editor"/>
                                           <elementRef key="meeting"/>
                                           <elementRef key="respStmt"/>
                                          </alternate>
                                         </sequence>
                                         <sequence>
                                          <elementRef key="authority"/>
                                          <elementRef key="idno"/>
                                         </sequence>
                                        </alternate>
                                        <elementRef key="availability"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.noteLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="edition"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="idno"/>
                                          <classRef key="model.ptrLike"/>
                                          <elementRef key="editor"/>
                                          <elementRef key="sponsor"/>
                                          <elementRef key="funder"/>
                                          <elementRef key="respStmt"/>
                                         </alternate>
                                        </sequence>
                                        <elementRef key="imprint"/>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="imprint"/>
                                         <elementRef key="extent"/>
                                         <elementRef key="biblScope"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element monogr
                                       {
                                          tei_att.global.attributes,
                                      @@ -67,4 +67,4 @@
                                             tei_imprint,
                                             ( tei_imprint | tei_extent | tei_biblScope )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msContents.html b/gl/dev/ref-msContents.html index 6ab7293c9..63f3c1f56 100644 --- a/gl/dev/ref-msContents.html +++ b/gl/dev/ref-msContents.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msContents>

                                      <msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      core: p textLang
                                      linking: ab
                                      msdescription: msItem msItemStruct summary
                                      Note

                                      Unless it contains a simple prose description, this element should contain at least one of the elements summary, msItem, or msItemStruct. This constraint is not currently enforced by the schema.

                                      Example
                                      <msContents class="#sermons">
                                       <p>A collection of Lollard sermons</p>
                                      </msContents>
                                      Example
                                      <msContents>
                                       <msItem n="1">
                                        <locus>fols. 5r-7v</locus>
                                        <title>An ABC</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>239</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="2">
                                        <locus>fols. 7v-8v</locus>
                                        <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>3747</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="3">
                                        <locus>fol. 8v</locus>
                                        <title>Truth</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>809</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="4">
                                        <locus>fols. 8v-10v</locus>
                                        <title>Birds Praise of Love</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>1506</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="5">
                                        <locus>fols. 10v-11v</locus>
                                        <title xml:lang="la">De amico ad amicam</title>
                                        <title xml:lang="la">Responcio</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>16 &amp; 19</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="6">
                                        <locus>fols. 14r-126v</locus>
                                        <title>Troilus and Criseyde</title>
                                        <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>
                                       </msItem>
                                      </msContents>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="textLangminOccurs="0"/>
                                         <elementRef key="titlePage"
                                          minOccurs="0"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="msItem"/>
                                          <elementRef key="msItemStruct"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msContents>

                                      <msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      core: p textLang
                                      linking: ab
                                      msdescription: msItem msItemStruct summary
                                      Note

                                      Unless it contains a simple prose description, this element should contain at least one of the elements summary, msItem, or msItemStruct. This constraint is not currently enforced by the schema.

                                      Example
                                      <msContents class="#sermons">
                                       <p>A collection of Lollard sermons</p>
                                      </msContents>
                                      Example
                                      <msContents>
                                       <msItem n="1">
                                        <locus>fols. 5r-7v</locus>
                                        <title>An ABC</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>239</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="2">
                                        <locus>fols. 7v-8v</locus>
                                        <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>3747</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="3">
                                        <locus>fol. 8v</locus>
                                        <title>Truth</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>809</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="4">
                                        <locus>fols. 8v-10v</locus>
                                        <title>Birds Praise of Love</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>1506</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="5">
                                        <locus>fols. 10v-11v</locus>
                                        <title xml:lang="la">De amico ad amicam</title>
                                        <title xml:lang="la">Responcio</title>
                                        <bibl>
                                         <title>IMEV</title>
                                         <biblScope>16 &amp; 19</biblScope>
                                        </bibl>
                                       </msItem>
                                       <msItem n="6">
                                        <locus>fols. 14r-126v</locus>
                                        <title>Troilus and Criseyde</title>
                                        <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>
                                       </msItem>
                                      </msContents>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="textLangminOccurs="0"/>
                                         <elementRef key="titlePage"
                                          minOccurs="0"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="msItem"/>
                                          <elementRef key="msItemStruct"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element msContents
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                                ( tei_msItem | tei_msItemStruct )*
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msDesc.html b/gl/dev/ref-msDesc.html index b4c6258c1..11f2a70fa 100644 --- a/gl/dev/ref-msDesc.html +++ b/gl/dev/ref-msDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msDesc>

                                      <msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype) att.declaring (@decls) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Although the msDesc has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general object may be more suitable.

                                      Example
                                      <msDesc>
                                       <msIdentifier>
                                        <settlement>Oxford</settlement>
                                        <repository>Bodleian Library</repository>
                                        <idno type="Bod">MS Poet. Rawl. D. 169.</idno>
                                       </msIdentifier>
                                       <msContents>
                                        <msItem>
                                         <author>Geoffrey Chaucer</author>
                                         <title>The Canterbury Tales</title>
                                        </msItem>
                                       </msContents>
                                       <physDesc>
                                        <objectDesc>
                                         <p>A parchment codex of 136 folios, measuring approx
                                             28 by 19 inches, and containing 24 quires.</p>
                                         <p>The pages are margined and ruled throughout.</p>
                                         <p>Four hands have been identified in the manuscript: the first 44
                                             folios being written in two cursive anglicana scripts, while the
                                             remainder is for the most part in a mixed secretary hand.</p>
                                        </objectDesc>
                                       </physDesc>
                                      </msDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="msIdentifier"/>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                          <alternate>
                                           <elementRef key="msPartminOccurs="0"
                                            maxOccurs="unbounded"/>

                                           <elementRef key="msFragminOccurs="0"
                                            maxOccurs="unbounded"/>

                                          </alternate>
                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msDesc>

                                      <msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype) att.declaring (@decls) att.docStatus (@status)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Although the msDesc has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general object may be more suitable.

                                      Example
                                      <msDesc>
                                       <msIdentifier>
                                        <settlement>Oxford</settlement>
                                        <repository>Bodleian Library</repository>
                                        <idno type="Bod">MS Poet. Rawl. D. 169.</idno>
                                       </msIdentifier>
                                       <msContents>
                                        <msItem>
                                         <author>Geoffrey Chaucer</author>
                                         <title>The Canterbury Tales</title>
                                        </msItem>
                                       </msContents>
                                       <physDesc>
                                        <objectDesc>
                                         <p>A parchment codex of 136 folios, measuring approx
                                             28 by 19 inches, and containing 24 quires.</p>
                                         <p>The pages are margined and ruled throughout.</p>
                                         <p>Four hands have been identified in the manuscript: the first 44
                                             folios being written in two cursive anglicana scripts, while the
                                             remainder is for the most part in a mixed secretary hand.</p>
                                        </objectDesc>
                                       </physDesc>
                                      </msDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="msIdentifier"/>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                          <alternate>
                                           <elementRef key="msPartminOccurs="0"
                                            maxOccurs="unbounded"/>

                                           <elementRef key="msFragminOccurs="0"
                                            maxOccurs="unbounded"/>

                                          </alternate>
                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element msDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -43,4 +43,4 @@
                                                )
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msFrag.html b/gl/dev/ref-msFrag.html index 093ce10b8..db81f575d 100644 --- a/gl/dev/ref-msFrag.html +++ b/gl/dev/ref-msFrag.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msFrag>

                                      <msFrag> (manuscript fragment) 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 [10.11. Manuscript Fragments]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: msDesc
                                      May contain
                                      Example
                                      <msDesc>
                                       <msIdentifier>
                                        <msName xml:lang="la">Codex Suprasliensis</msName>
                                       </msIdentifier>
                                       <msFrag>
                                        <msIdentifier>
                                         <settlement>Ljubljana</settlement>
                                         <repository>Narodna in univerzitetna knjiznica</repository>
                                         <idno>MS Kopitar 2</idno>
                                        </msIdentifier>
                                        <msContents>
                                         <summary>Contains ff. 10 to 42 only</summary>
                                        </msContents>
                                       </msFrag>
                                       <msFrag>
                                        <msIdentifier>
                                         <settlement>Warszawa</settlement>
                                         <repository>Biblioteka Narodowa</repository>
                                         <idno>BO 3.201</idno>
                                        </msIdentifier>
                                       </msFrag>
                                       <msFrag>
                                        <msIdentifier>
                                         <settlement>Sankt-Peterburg</settlement>
                                         <repository>Rossiiskaia natsional'naia biblioteka</repository>
                                         <idno>Q.p.I.72</idno>
                                        </msIdentifier>
                                       </msFrag>
                                      </msDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate>
                                         <elementRef key="altIdentifier"/>
                                         <elementRef key="msIdentifier"/>
                                        </alternate>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msFrag>

                                      <msFrag> (manuscript fragment) 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 [10.11. Manuscript Fragments]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: msDesc
                                      May contain
                                      Example
                                      <msDesc>
                                       <msIdentifier>
                                        <msName xml:lang="la">Codex Suprasliensis</msName>
                                       </msIdentifier>
                                       <msFrag>
                                        <msIdentifier>
                                         <settlement>Ljubljana</settlement>
                                         <repository>Narodna in univerzitetna knjiznica</repository>
                                         <idno>MS Kopitar 2</idno>
                                        </msIdentifier>
                                        <msContents>
                                         <summary>Contains ff. 10 to 42 only</summary>
                                        </msContents>
                                       </msFrag>
                                       <msFrag>
                                        <msIdentifier>
                                         <settlement>Warszawa</settlement>
                                         <repository>Biblioteka Narodowa</repository>
                                         <idno>BO 3.201</idno>
                                        </msIdentifier>
                                       </msFrag>
                                       <msFrag>
                                        <msIdentifier>
                                         <settlement>Sankt-Peterburg</settlement>
                                         <repository>Rossiiskaia natsional'naia biblioteka</repository>
                                         <idno>Q.p.I.72</idno>
                                        </msIdentifier>
                                       </msFrag>
                                      </msDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate>
                                         <elementRef key="altIdentifier"/>
                                         <elementRef key="msIdentifier"/>
                                        </alternate>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element msFrag
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                              | ( tei_msContents?, tei_physDesc?, tei_history?, tei_additional? )
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msIdentifier.html b/gl/dev/ref-msIdentifier.html index cac2a5f69..e1b1cf625 100644 --- a/gl/dev/ref-msIdentifier.html +++ b/gl/dev/ref-msIdentifier.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msIdentifier>

                                      <msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msDesc msFrag msPart
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <settlement>San Marino</settlement>
                                       <repository>Huntington Library</repository>
                                       <idno>MS.El.26.C.9</idno>
                                      </msIdentifier>
                                      Schematron

                                      <s:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' +

                                      <msIdentifier>

                                      <msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msDesc msFrag msPart
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <settlement>San Marino</settlement>
                                       <repository>Huntington Library</repository>
                                       <idno>MS.El.26.C.9</idno>
                                      </msIdentifier>
                                      Schematron

                                      <s:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</s:report>
                                      Content model
                                      <content>
                                       <sequence>
                                        <sequence>
                                         <classRef key="model.placeNamePart"
                                          expand="sequenceOptional"/>

                                         <elementRef key="institution"
                                          minOccurs="0"/>

                                         <elementRef key="repository"
                                          minOccurs="0"/>

                                         <elementRef key="collection"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="idnominOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="msName"/>
                                         <elementRef key="objectName"/>
                                         <elementRef key="altIdentifier"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element msIdentifier
                                       {
                                      @@ -42,4 +42,4 @@
                                             ),
                                             ( tei_msName | tei_objectName | tei_altIdentifier )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msItem.html b/gl/dev/ref-msItem.html index bcc240466..8cdef0447 100644 --- a/gl/dev/ref-msItem.html +++ b/gl/dev/ref-msItem.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msItem>

                                      <msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
                                      Member of
                                      Contained by
                                      msdescription: msContents msItem
                                      May contain
                                      Example
                                      <msItem class="#saga">
                                       <locus>ff. 1r-24v</locus>
                                       <title>Agrip af Noregs konunga sögum</title>
                                       <incipit>regi oc h<ex>ann</ex> setiho
                                       <gap reason="illegibleextent="7"/>sc
                                         heim se<ex>m</ex> þio</incipit>
                                       <explicit>h<ex>on</ex> hev<ex>er</ex>
                                        <ex>oc</ex>þa buit hesta .ij. aNan viþ
                                         fé enh<ex>on</ex>o<ex>m</ex> aNan til
                                         reiþ<ex>ar</ex>
                                       </explicit>
                                       <textLang mainLang="non">Old Norse/Icelandic</textLang>
                                      </msItem>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="locus"/>
                                         <elementRef key="locusGrp"/>
                                        </alternate>
                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.titlepagePart"/>
                                          <classRef key="model.msItemPart"/>
                                          <classRef key="model.global"/>
                                         </alternate>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msItem>

                                      <msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
                                      Member of
                                      Contained by
                                      msdescription: msContents msItem
                                      May contain
                                      Example
                                      <msItem class="#saga">
                                       <locus>ff. 1r-24v</locus>
                                       <title>Agrip af Noregs konunga sögum</title>
                                       <incipit>regi oc h<ex>ann</ex> setiho
                                       <gap reason="illegibleextent="7"/>sc
                                         heim se<ex>m</ex> þio</incipit>
                                       <explicit>h<ex>on</ex> hev<ex>er</ex>
                                        <ex>oc</ex>þa buit hesta .ij. aNan viþ
                                         fé enh<ex>on</ex>o<ex>m</ex> aNan til
                                         reiþ<ex>ar</ex>
                                       </explicit>
                                       <textLang mainLang="non">Old Norse/Icelandic</textLang>
                                      </msItem>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <elementRef key="locus"/>
                                         <elementRef key="locusGrp"/>
                                        </alternate>
                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.titlepagePart"/>
                                          <classRef key="model.msItemPart"/>
                                          <classRef key="model.global"/>
                                         </alternate>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element msItem
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                              | ( tei_model.titlepagePart | tei_model.msItemPart | tei_model.global )+
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msItemStruct.html b/gl/dev/ref-msItemStruct.html index 2fdfde25d..401c4f4a0 100644 --- a/gl/dev/ref-msItemStruct.html +++ b/gl/dev/ref-msItemStruct.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msItemStruct>

                                      <msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <msItemStruct n="2defective="false"
                                       class="#biblComm">

                                       <locus from="24vto="97v">24v-97v</locus>
                                       <author>Apringius de Beja</author>
                                       <title type="uniformxml:lang="la">Tractatus in Apocalypsin</title>
                                       <rubric>Incipit Trac<supplied reason="omitted">ta</supplied>tus
                                         in apoka<lb/>lipsin eruditissimi uiri <lb/> Apringi ep<ex>iscop</ex>i
                                         Pacensis eccl<ex>esi</ex>e</rubric>
                                       <finalRubric>EXPLIC<ex>IT</ex> EXPO<lb/>SITIO APOCALIPSIS
                                         QVA<ex>M</ex> EXPOSVIT DOM<lb/>NVS APRINGIUS EP<ex>ISCOPU</ex>S.
                                         DEO GR<ex>ACI</ex>AS AGO. FI<lb/>NITO LABORE ISTO.</finalRubric>
                                       <bibl>
                                        <ref target="http://amiBibl.xml#Apringius1900">Apringius</ref>, ed. Férotin</bibl>
                                       <textLang mainLang="la">Latin</textLang>
                                      </msItemStruct>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0">
                                         <elementRef key="locus"/>
                                         <elementRef key="locusGrp"/>
                                        </alternate>
                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="authorminOccurs="0"
                                           maxOccurs="unbounded"/>

                                          <elementRef key="respStmt"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="titleminOccurs="0"
                                           maxOccurs="unbounded"/>

                                          <elementRef key="rubricminOccurs="0"/>
                                          <elementRef key="incipitminOccurs="0"/>
                                          <elementRef key="msItemStruct"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="explicit"
                                           minOccurs="0"/>

                                          <elementRef key="finalRubric"
                                           minOccurs="0"/>

                                          <elementRef key="colophon"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="decoNote"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="listBibl"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="bibl"/>
                                           <elementRef key="biblStruct"/>
                                          </alternate>
                                          <elementRef key="filiation"
                                           minOccurs="0"/>

                                          <classRef key="model.noteLike"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="textLang"
                                           minOccurs="0"/>

                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msItemStruct>

                                      <msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <msItemStruct n="2defective="false"
                                       class="#biblComm">

                                       <locus from="24vto="97v">24v-97v</locus>
                                       <author>Apringius de Beja</author>
                                       <title type="uniformxml:lang="la">Tractatus in Apocalypsin</title>
                                       <rubric>Incipit Trac<supplied reason="omitted">ta</supplied>tus
                                         in apoka<lb/>lipsin eruditissimi uiri <lb/> Apringi ep<ex>iscop</ex>i
                                         Pacensis eccl<ex>esi</ex>e</rubric>
                                       <finalRubric>EXPLIC<ex>IT</ex> EXPO<lb/>SITIO APOCALIPSIS
                                         QVA<ex>M</ex> EXPOSVIT DOM<lb/>NVS APRINGIUS EP<ex>ISCOPU</ex>S.
                                         DEO GR<ex>ACI</ex>AS AGO. FI<lb/>NITO LABORE ISTO.</finalRubric>
                                       <bibl>
                                        <ref target="http://amiBibl.xml#Apringius1900">Apringius</ref>, ed. Férotin</bibl>
                                       <textLang mainLang="la">Latin</textLang>
                                      </msItemStruct>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0">
                                         <elementRef key="locus"/>
                                         <elementRef key="locusGrp"/>
                                        </alternate>
                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="authorminOccurs="0"
                                           maxOccurs="unbounded"/>

                                          <elementRef key="respStmt"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="titleminOccurs="0"
                                           maxOccurs="unbounded"/>

                                          <elementRef key="rubricminOccurs="0"/>
                                          <elementRef key="incipitminOccurs="0"/>
                                          <elementRef key="msItemStruct"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="explicit"
                                           minOccurs="0"/>

                                          <elementRef key="finalRubric"
                                           minOccurs="0"/>

                                          <elementRef key="colophon"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="decoNote"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="listBibl"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="bibl"/>
                                           <elementRef key="biblStruct"/>
                                          </alternate>
                                          <elementRef key="filiation"
                                           minOccurs="0"/>

                                          <classRef key="model.noteLike"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="textLang"
                                           minOccurs="0"/>

                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element msItemStruct
                                       {
                                          tei_att.global.attributes,
                                      @@ -50,4 +50,4 @@
                                                )
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msName.html b/gl/dev/ref-msName.html index d3f8092fd..b23115832 100644 --- a/gl/dev/ref-msName.html +++ b/gl/dev/ref-msName.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msName>

                                      <msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: msIdentifier
                                      namesdates: objectIdentifier
                                      May contain
                                      core: name rs
                                      gaiji: g
                                      character data
                                      Example
                                      <msName>The Vercelli Book</msName>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="rs"/>
                                        <elementRef key="name"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msName>

                                      <msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: msIdentifier
                                      namesdates: objectIdentifier
                                      May contain
                                      core: name rs
                                      gaiji: g
                                      character data
                                      Example
                                      <msName>The Vercelli Book</msName>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="rs"/>
                                        <elementRef key="name"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element msName
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          ( text | tei_model.gLike | tei_rs | tei_name )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-msPart.html b/gl/dev/ref-msPart.html index c7c907301..b11314ace 100644 --- a/gl/dev/ref-msPart.html +++ b/gl/dev/ref-msPart.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <msPart>

                                      <msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [10.10. Manuscript Parts]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: msDesc msPart
                                      May contain
                                      Note

                                      As this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple altIdentifier rather than using the more structured msIdentifier element. This usage is however deprecated.

                                      Example
                                      <msPart>
                                       <msIdentifier>
                                        <idno>A</idno>
                                        <altIdentifier type="catalog">
                                         <collection>Becker</collection>
                                         <idno>48, Nr. 145</idno>
                                        </altIdentifier>
                                        <altIdentifier type="catalog">
                                         <collection>Wiener Liste</collection>
                                         <idno>4°5</idno>
                                        </altIdentifier>
                                       </msIdentifier>
                                       <head>
                                        <title xml:lang="la">Gregorius: Homiliae in Ezechielem</title>
                                        <origPlace key="tgn_7008085">Weissenburg (?)</origPlace>
                                        <origDate notBefore="0801"
                                         notAfter="0815">
                                      IX. Jh., Anfang</origDate>
                                       </head>
                                      </msPart>
                                      Example
                                      <msDesc>
                                       <msIdentifier>
                                        <settlement>Amiens</settlement>
                                        <repository>Bibliothèque Municipale</repository>
                                        <idno>MS 3</idno>
                                        <msName>Maurdramnus Bible</msName>
                                       </msIdentifier>
                                       <msContents>
                                        <summary>
                                         <list>
                                          <item xml:lang="en">Miscellany of various texts;</item>
                                          <item xml:lang="la">Prudentius, Psychomachia;</item>
                                          <item xml:lang="la">Physiologus de natura animantium</item>
                                         </list>
                                        </summary>
                                        <textLang mainLang="la">Latin</textLang>
                                       </msContents>
                                       <physDesc>
                                        <objectDesc form="composite_manuscript"/>
                                       </physDesc>
                                       <msPart>
                                        <msIdentifier>
                                         <idno>ms. 10066-77 ff. 140r-156v</idno>
                                        </msIdentifier>
                                        <msContents>
                                         <summary xml:lang="la">Physiologus</summary>
                                         <textLang mainLang="la">Latin</textLang>
                                        </msContents>
                                       </msPart>
                                       <msPart>
                                        <msIdentifier>
                                         <altIdentifier>
                                          <idno>MS 6</idno>
                                         </altIdentifier>
                                        </msIdentifier>
                                      <!-- other information specific to this part here -->
                                       </msPart>
                                      <!-- more parts here -->
                                      </msDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="msIdentifier"/>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                          <elementRef key="msPartminOccurs="0"
                                           maxOccurs="unbounded"/>

                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <msPart>

                                      <msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [10.10. Manuscript Parts]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: msDesc msPart
                                      May contain
                                      Note

                                      As this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple altIdentifier rather than using the more structured msIdentifier element. This usage is however deprecated.

                                      Example
                                      <msPart>
                                       <msIdentifier>
                                        <idno>A</idno>
                                        <altIdentifier type="catalog">
                                         <collection>Becker</collection>
                                         <idno>48, Nr. 145</idno>
                                        </altIdentifier>
                                        <altIdentifier type="catalog">
                                         <collection>Wiener Liste</collection>
                                         <idno>4°5</idno>
                                        </altIdentifier>
                                       </msIdentifier>
                                       <head>
                                        <title xml:lang="la">Gregorius: Homiliae in Ezechielem</title>
                                        <origPlace key="tgn_7008085">Weissenburg (?)</origPlace>
                                        <origDate notBefore="0801"
                                         notAfter="0815">
                                      IX. Jh., Anfang</origDate>
                                       </head>
                                      </msPart>
                                      Example
                                      <msDesc>
                                       <msIdentifier>
                                        <settlement>Amiens</settlement>
                                        <repository>Bibliothèque Municipale</repository>
                                        <idno>MS 3</idno>
                                        <msName>Maurdramnus Bible</msName>
                                       </msIdentifier>
                                       <msContents>
                                        <summary>
                                         <list>
                                          <item xml:lang="en">Miscellany of various texts;</item>
                                          <item xml:lang="la">Prudentius, Psychomachia;</item>
                                          <item xml:lang="la">Physiologus de natura animantium</item>
                                         </list>
                                        </summary>
                                        <textLang mainLang="la">Latin</textLang>
                                       </msContents>
                                       <physDesc>
                                        <objectDesc form="composite_manuscript"/>
                                       </physDesc>
                                       <msPart>
                                        <msIdentifier>
                                         <idno>ms. 10066-77 ff. 140r-156v</idno>
                                        </msIdentifier>
                                        <msContents>
                                         <summary xml:lang="la">Physiologus</summary>
                                         <textLang mainLang="la">Latin</textLang>
                                        </msContents>
                                       </msPart>
                                       <msPart>
                                        <msIdentifier>
                                         <altIdentifier>
                                          <idno>MS 6</idno>
                                         </altIdentifier>
                                        </msIdentifier>
                                      <!-- other information specific to this part here -->
                                       </msPart>
                                      <!-- more parts here -->
                                      </msDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="msIdentifier"/>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="1maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                          <elementRef key="msPartminOccurs="0"
                                           maxOccurs="unbounded"/>

                                         </sequence>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element msPart
                                       {
                                          tei_att.global.attributes,
                                      @@ -40,4 +40,4 @@
                                                )
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-musicNotation.html b/gl/dev/ref-musicNotation.html index abe1b10f5..f7943ef29 100644 --- a/gl/dev/ref-musicNotation.html +++ b/gl/dev/ref-musicNotation.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <musicNotation>

                                      <musicNotation> (music notation) contains description of type of musical notation. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      Example
                                      <musicNotation>
                                       <p>Square notation of 4-line red staves.</p>
                                      </musicNotation>
                                      Example
                                      <musicNotation>Neumes in <term>campo aperto</term> of the St. Gall type.
                                      </musicNotation>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element musicNotation { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <musicNotation>

                                      <musicNotation> (music notation) contains description of type of musical notation. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      Example
                                      <musicNotation>
                                       <p>Square notation of 4-line red staves.</p>
                                      </musicNotation>
                                      Example
                                      <musicNotation>Neumes in <term>campo aperto</term> of the St. Gall type.
                                      </musicNotation>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element musicNotation { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-name.html b/gl/dev/ref-name.html index bc31a4cab..d29a0c29d 100644 --- a/gl/dev/ref-name.html +++ b/gl/dev/ref-name.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <name>

                                      <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Proper nouns referring to people, places, and organizations may be tagged instead with persName, placeName, or orgName, when the TEI module for names and dates is included.

                                      Example
                                      <name type="person">Thomas Hoccleve</name>
                                      <name type="place">Villingaholt</name>
                                      <name type="org">Vetus Latina Institut</name>
                                      <name type="personref="#HOC001">Occleve</name>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <name>

                                      <name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Proper nouns referring to people, places, and organizations may be tagged instead with persName, placeName, or orgName, when the TEI module for names and dates is included.

                                      Example
                                      <name type="person">Thomas Hoccleve</name>
                                      <name type="place">Villingaholt</name>
                                      <name type="org">Vetus Latina Institut</name>
                                      <name type="personref="#HOC001">Occleve</name>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element name
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.editLike.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-namespace.html b/gl/dev/ref-namespace.html index 7c8934101..593dd517b 100644 --- a/gl/dev/ref-namespace.html +++ b/gl/dev/ref-namespace.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <namespace>

                                      <namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      namespecifies the full formal name of the namespace concerned.
                                      Status Required
                                      Datatype teidata.namespace
                                      Contained by
                                      header: tagsDecl
                                      May contain
                                      header: tagUsage
                                      Example
                                      <namespace name="http://www.tei-c.org/ns/1.0">
                                       <tagUsage gi="hioccurs="28withId="2"> Used only to mark English words
                                         italicized in the copy text </tagUsage>
                                      </namespace>
                                      Content model
                                      <content>
                                       <elementRef key="tagUsageminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <namespace>

                                      <namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      namespecifies the full formal name of the namespace concerned.
                                      Status Required
                                      Datatype teidata.namespace
                                      Contained by
                                      header: tagsDecl
                                      May contain
                                      header: tagUsage
                                      Example
                                      <namespace name="http://www.tei-c.org/ns/1.0">
                                       <tagUsage gi="hioccurs="28withId="2"> Used only to mark English words
                                         italicized in the copy text </tagUsage>
                                      </namespace>
                                      Content model
                                      <content>
                                       <elementRef key="tagUsageminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element namespace
                                       {
                                          tei_att.global.attributes,
                                          attribute name { teidata.namespace },
                                          tei_tagUsage+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-normalization.html b/gl/dev/ref-normalization.html index ee1fe4ac2..d4a3d0725 100644 --- a/gl/dev/ref-normalization.html +++ b/gl/dev/ref-normalization.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <normalization>

                                      <normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      methodindicates the method adopted to indicate normalizations within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      silent
                                      normalization made silently [Default]
                                      markup
                                      normalization represented using markup
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <editorialDecl>
                                       <normalization method="markup">
                                        <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern
                                           20th century typographical practice, the <gi>choice</gi> element has been used to
                                           enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values
                                           respectively. ... </p>
                                       </normalization>
                                       <normalization method="silent">
                                        <p>Spacing between words and following punctuation has been regularized to zero spaces;
                                           spacing between words has been regularized to one space.</p>
                                       </normalization>
                                       <normalization source="http://www.dict.sztaki.hu/webster">
                                        <p>Spelling converted throughout to Modern American usage, based on Websters 9th
                                           Collegiate dictionary.</p>
                                       </normalization>
                                      </editorialDecl>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <normalization>

                                      <normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      methodindicates the method adopted to indicate normalizations within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      silent
                                      normalization made silently [Default]
                                      markup
                                      normalization represented using markup
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <editorialDecl>
                                       <normalization method="markup">
                                        <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern
                                           20th century typographical practice, the <gi>choice</gi> element has been used to
                                           enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values
                                           respectively. ... </p>
                                       </normalization>
                                       <normalization method="silent">
                                        <p>Spacing between words and following punctuation has been regularized to zero spaces;
                                           spacing between words has been regularized to one space.</p>
                                       </normalization>
                                       <normalization source="http://www.dict.sztaki.hu/webster">
                                        <p>Spelling converted throughout to Modern American usage, based on Websters 9th
                                           Collegiate dictionary.</p>
                                       </normalization>
                                      </editorialDecl>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element normalization
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          attribute method { "silent" | "markup" }?,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-notatedMusic.html b/gl/dev/ref-notatedMusic.html index c037e8c8c..657815710 100644 --- a/gl/dev/ref-notatedMusic.html +++ b/gl/dev/ref-notatedMusic.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <notatedMusic>

                                      <notatedMusic> encodes the presence of music notation in a text [14.3. Notated Music in Written Text]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      It is possible to describe the content of the notation using elements from the model.labelLike class and it is possible to point to an external representation using elements from model.ptrLike. 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 encoder's interpretation of the correspondence between the notated music and these digital objects is not encoded explicitly. We recommend the use of graphic and binaryObject mainly as a fallback mechanism when the notated music format is not displayable by the 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 encoder to other formats and specifications such as MPEG-SMR.

                                      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.

                                      Example
                                      <notatedMusic>
                                       <ptr target="bar1.xml"/>
                                       <graphic url="bar1.jpg"/>
                                       <desc>First bar of Chopin's Scherzo No.3 Op.39</desc>
                                      </notatedMusic>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.labelLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <elementRef key="graphic"/>
                                        <elementRef key="binaryObject"/>
                                        <elementRef key="seg"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <notatedMusic>

                                      <notatedMusic> encodes the presence of music notation in a text [14.3. Notated Music in Written Text]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      It is possible to describe the content of the notation using elements from the model.labelLike class and it is possible to point to an external representation using elements from model.ptrLike. 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 encoder's interpretation of the correspondence between the notated music and these digital objects is not encoded explicitly. We recommend the use of graphic and binaryObject mainly as a fallback mechanism when the notated music format is not displayable by the 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 encoder to other formats and specifications such as MPEG-SMR.

                                      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.

                                      Example
                                      <notatedMusic>
                                       <ptr target="bar1.xml"/>
                                       <graphic url="bar1.jpg"/>
                                       <desc>First bar of Chopin's Scherzo No.3 Op.39</desc>
                                      </notatedMusic>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.labelLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <elementRef key="graphic"/>
                                        <elementRef key="binaryObject"/>
                                        <elementRef key="seg"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element notatedMusic
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                           | tei_binaryObject
                                           | tei_seg
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-note.html b/gl/dev/ref-note.html index 23700fcbd..ddb281e44 100644 --- a/gl/dev/ref-note.html +++ b/gl/dev/ref-note.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <note>

                                      <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd)
                                      Member of
                                      Contained by
                                      analysis: m phr s w
                                      dictionaries: form gen lang
                                      figures: cell figure table
                                      gaiji: glyph
                                      textcrit: app lem rdg rdgGrp wit
                                      May contain
                                      Example

                                      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
                                      in the great line of Italian renaissance art, but even in the
                                      painterly <note place="bottomtype="gloss"
                                       resp="#MDMH">

                                       <term xml:lang="de">Malerisch</term>. This word has, in the German, two
                                      distinct meanings, one objective, a quality residing in the object,
                                      the other subjective, a mode of apprehension and creation. To avoid
                                      confusion, they have been distinguished in English as
                                      <mentioned>picturesque</mentioned> and
                                      <mentioned>painterly</mentioned> respectively.
                                      </note> style of the
                                      Dutch genre painters of the seventeenth century that drapery has this
                                      psychological significance.

                                      <!-- elsewhere in the document -->
                                      <respStmt xml:id="MDMH">
                                       <resp>translation from German to English</resp>
                                       <name>Hottinger, Marie Donald Mackie</name>
                                      </respStmt>

                                      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.

                                      Example

                                      The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

                                      Mevorakh b. Saadya's mother, the matriarch of the
                                      family during the second half of the eleventh century, <note n="126anchored="true"> The
                                      alleged 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. </note> is well known from Geniza documents
                                      published by Jacob Mann.

                                      However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <note>

                                      <note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd)
                                      Member of
                                      Contained by
                                      analysis: m phr s w
                                      dictionaries: form gen lang
                                      figures: cell figure table
                                      gaiji: glyph
                                      textcrit: app lem rdg rdgGrp wit
                                      May contain
                                      Example

                                      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
                                      in the great line of Italian renaissance art, but even in the
                                      painterly <note place="bottomtype="gloss"
                                       resp="#MDMH">

                                       <term xml:lang="de">Malerisch</term>. This word has, in the German, two
                                      distinct meanings, one objective, a quality residing in the object,
                                      the other subjective, a mode of apprehension and creation. To avoid
                                      confusion, they have been distinguished in English as
                                      <mentioned>picturesque</mentioned> and
                                      <mentioned>painterly</mentioned> respectively.
                                      </note> style of the
                                      Dutch genre painters of the seventeenth century that drapery has this
                                      psychological significance.

                                      <!-- elsewhere in the document -->
                                      <respStmt xml:id="MDMH">
                                       <resp>translation from German to English</resp>
                                       <name>Hottinger, Marie Donald Mackie</name>
                                      </respStmt>

                                      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.

                                      Example

                                      The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

                                      Mevorakh b. Saadya's mother, the matriarch of the
                                      family during the second half of the eleventh century, <note n="126anchored="true"> The
                                      alleged 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. </note> is well known from Geniza documents
                                      published by Jacob Mann.

                                      However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element note
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.written.attributes,
                                          tei_att.anchoring.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-noteGrp.html b/gl/dev/ref-noteGrp.html index 0b7075878..8ebf23c7e 100644 --- a/gl/dev/ref-noteGrp.html +++ b/gl/dev/ref-noteGrp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <noteGrp>

                                      <noteGrp> (note group) contains a group of notes [3.9.1.1. Encoding Grouped Notes]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd)
                                      Member of
                                      Contained by
                                      analysis: m phr s w
                                      dictionaries: form gen lang
                                      figures: cell figure table
                                      gaiji: glyph
                                      linking: ab seg
                                      textcrit: app lem rdg rdgGrp wit
                                      May contain
                                      Example

                                      In the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text:

                                      <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
                                      necnon episcopum in duplicibus Quatuortemporibus
                                      <noteGrp>
                                        <note xml:lang="en">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).
                                        </note>
                                        <note xml:lang="pl">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).
                                        </note>
                                       </noteGrp>
                                      totaliter expediui.
                                      </p>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="note"/>
                                         <elementRef key="noteGrp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <noteGrp>

                                      <noteGrp> (note group) contains a group of notes [3.9.1.1. Encoding Grouped Notes]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd)
                                      Member of
                                      Contained by
                                      analysis: m phr s w
                                      dictionaries: form gen lang
                                      figures: cell figure table
                                      gaiji: glyph
                                      linking: ab seg
                                      textcrit: app lem rdg rdgGrp wit
                                      May contain
                                      Example

                                      In the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text:

                                      <p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
                                      necnon episcopum in duplicibus Quatuortemporibus
                                      <noteGrp>
                                        <note xml:lang="en">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).
                                        </note>
                                        <note xml:lang="pl">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).
                                        </note>
                                       </noteGrp>
                                      totaliter expediui.
                                      </p>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="descminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="note"/>
                                         <elementRef key="noteGrp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element noteGrp
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.written.attributes,
                                          tei_att.anchoring.attributes,
                                          ( tei_desc*, ( tei_note | tei_noteGrp )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-notesStmt.html b/gl/dev/ref-notesStmt.html index 161573661..f2bc81d7b 100644 --- a/gl/dev/ref-notesStmt.html +++ b/gl/dev/ref-notesStmt.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <notesStmt>

                                      <notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      Information of different kinds should not be grouped together into the same note.

                                      Example
                                      <notesStmt>
                                       <note>Historical commentary provided by Mark Cohen</note>
                                       <note>OCR scanning done at University of Toronto</note>
                                      </notesStmt>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.noteLike"/>
                                        <elementRef key="relatedItem"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <notesStmt>

                                      <notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      Information of different kinds should not be grouped together into the same note.

                                      Example
                                      <notesStmt>
                                       <note>Historical commentary provided by Mark Cohen</note>
                                       <note>OCR scanning done at University of Toronto</note>
                                      </notesStmt>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.noteLike"/>
                                        <elementRef key="relatedItem"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element notesStmt
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.noteLike | tei_relatedItem )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-num.html b/gl/dev/ref-num.html index 1ce83dd63..3a64c22a3 100644 --- a/gl/dev/ref-num.html +++ b/gl/dev/ref-num.html @@ -22,7 +22,7 @@ }); });

                                      <num>

                                      <num> (number) contains a number, written in any form. [3.6.3. Numbers and -Measures]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.typed (type, @subtype)
                                      typeindicates the type of numeric value.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      cardinal
                                      absolute number, e.g. 21, 21.5
                                      ordinal
                                      ordinal number, e.g. 21st
                                      fraction
                                      fraction, e.g. one half or three-quarters
                                      percentage
                                      a percentage
                                      Note

                                      If a different typology is desired, other values can be used for this attribute.

                                      valuesupplies the value of the number in standard form.
                                      Status Optional
                                      Datatype teidata.numeric
                                      Values a numeric value.
                                      Note

                                      The standard form used is defined by the TEI datatype teidata.numeric.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The num element is intended for use in simple applications.

                                      Example
                                      <p>I reached <num type="cardinalvalue="21">twenty-one</num> on
                                      my <num type="ordinalvalue="21">twenty-first</num> birthday</p>
                                      <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
                                       </num> cm per second.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +Measures]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.typed (type, @subtype)
                                      typeindicates the type of numeric value.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      cardinal
                                      absolute number, e.g. 21, 21.5
                                      ordinal
                                      ordinal number, e.g. 21st
                                      fraction
                                      fraction, e.g. one half or three-quarters
                                      percentage
                                      a percentage
                                      Note

                                      If a different typology is desired, other values can be used for this attribute.

                                      valuesupplies the value of the number in standard form.
                                      Status Optional
                                      Datatype teidata.numeric
                                      Values a numeric value.
                                      Note

                                      The standard form used is defined by the TEI datatype teidata.numeric.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The num element is intended for use in simple applications.

                                      Example
                                      <p>I reached <num type="cardinalvalue="21">twenty-one</num> on
                                      my <num type="ordinalvalue="21">twenty-first</num> birthday</p>
                                      <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
                                       </num> cm per second.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element num
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                          }?,
                                          attribute value { teidata.numeric }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-nym.html b/gl/dev/ref-nym.html index 4d1dd3edf..5f22b5b05 100644 --- a/gl/dev/ref-nym.html +++ b/gl/dev/ref-nym.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <nym>

                                      <nym> (canonical name) contains the definition for a canonical name or name component of any kind. [13.3.6. Names and Nyms]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.sortable (@sortKey)
                                      partspoints to constituent nyms
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Contained by
                                      namesdates: listNym nym
                                      May contain
                                      core: p
                                      dictionaries: form
                                      header: idno
                                      linking: ab
                                      namesdates: nym
                                      Example
                                      <nym xml:id="J452">
                                       <form>
                                        <orth xml:lang="en-US">Ian</orth>
                                        <orth xml:lang="en-x-Scots">Iain</orth>
                                       </form>
                                      </nym>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="idnominOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.entryPart"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.pLikeminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="nymminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <nym>

                                      <nym> (canonical name) contains the definition for a canonical name or name component of any kind. [13.3.6. Names and Nyms]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.sortable (@sortKey)
                                      partspoints to constituent nyms
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Contained by
                                      namesdates: listNym nym
                                      May contain
                                      core: p
                                      dictionaries: form
                                      header: idno
                                      linking: ab
                                      namesdates: nym
                                      Example
                                      <nym xml:id="J452">
                                       <form>
                                        <orth xml:lang="en-US">Ian</orth>
                                        <orth xml:lang="en-x-Scots">Iain</orth>
                                       </form>
                                      </nym>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="idnominOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.entryPart"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.pLikeminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="nymminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element nym
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.sortable.attributes,
                                          attribute parts { list { teidata.pointer+ } }?,
                                          ( tei_idno*, tei_model.entryPart*, tei_model.pLike*, tei_nym* )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-object.html b/gl/dev/ref-object.html index 1adf437ef..9fca5c350 100644 --- a/gl/dev/ref-object.html +++ b/gl/dev/ref-object.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <object>

                                      <object> contains a description of a single identifiable physical object. [13.3.5. Objects]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype) att.declaring (@decls) att.docStatus (@status) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      namesdates: listObject object
                                      May contain
                                      Note

                                      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 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.

                                      Example
                                      <listObject>
                                       <object xml:id="Alfred_Jewel">
                                        <objectIdentifier>
                                         <country>United Kingdom</country>
                                         <region>Oxfordshire</region>
                                         <settlement>Oxford</settlement>
                                         <institution>University of Oxford</institution>
                                         <repository>Ashmolean Museum</repository>
                                         <collection>English Treasures</collection>
                                         <idno type="ashmolean">AN1836p.135.371</idno>
                                         <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>
                                         <objectName>Alfred Jewel</objectName>
                                        </objectIdentifier>
                                        <physDesc>
                                         <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>
                                             surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. 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'. </p>
                                        </physDesc>
                                        <history>
                                         <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and
                                             was most likely made in <origPlace>England</origPlace>. </origin>
                                         <provenance when="1693">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. </provenance>
                                         <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical
                                             Transactions of the Royal Society.</provenance>
                                         <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in
                                             the Ashmolean Museum in Oxford. </acquisition>
                                        </history>
                                       </object>
                                      </listObject>
                                      <!-- Elsewhere in document -->
                                      <p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the
                                      <objectName ref="#Alfred_Jewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster
                                         Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>.
                                      </p>
                                      Example
                                      <listObject>
                                       <object xml:id="MaskOfTutankhamun">
                                        <objectIdentifier>
                                         <objectName xml:lang="en">Mask of Tutankhamun</objectName>
                                         <idno type="carter">256a</idno>
                                         <idno type="JournalD'Entrée">60672</idno>
                                         <idno type="exhibition">220</idno>
                                         <institution>Museum of Egyptian Antiquities</institution>
                                         <address>
                                          <street>15 Meret Basha</street>
                                          <district>Ismailia</district>
                                          <settlement>Cairo</settlement>
                                          <country>Egypt</country>
                                          <location>
                                           <geo>30.047778, 31.233333</geo>
                                          </location>
                                         </address>
                                        </objectIdentifier>
                                        <msContents>
                                         <p>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 <title>Book of the Dead</title>.</p>
                                        </msContents>
                                        <physDesc>
                                         <p> 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.</p>
                                         <p>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.</p>
                                        </physDesc>
                                        <history>
                                         <origin>
                                          <p>The mask of Tutankhamun was created in <origPlace>Egypt</origPlace> around <origDate when="-1323type="circa">1323 BC</origDate>. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun
                                               who reigned 1332–1323 BC. </p>
                                         </origin>
                                         <provenance>
                                          <p>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: <quote> The pins removed, the lid was raised. The penultimate scene was disclosed –
                                                 a very neatly wrapped mummy of the young king, with golden mask of sad but tranquil expression, symbolizing
                                                 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. </quote>
                                          </p>
                                         </provenance>
                                         <acquisition> 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. </acquisition>
                                        </history>
                                        <additional>
                                         <adminInfo>
                                          <custodialHist>
                                           <custEvent when="1944">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.</custEvent>
                                           <custEvent when="2014-08"> 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. </custEvent>
                                           <custEvent when="2015-01">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.</custEvent>
                                          </custodialHist>
                                         </adminInfo>
                                        </additional>
                                       </object>
                                      </listObject>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="objectIdentifier"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                         </sequence>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                        </alternate>
                                        <elementRef key="objectminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <object>

                                      <object> contains a description of a single identifiable physical object. [13.3.5. Objects]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype) att.declaring (@decls) att.docStatus (@status) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      namesdates: listObject object
                                      May contain
                                      Note

                                      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 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.

                                      Example
                                      <listObject>
                                       <object xml:id="Alfred_Jewel">
                                        <objectIdentifier>
                                         <country>United Kingdom</country>
                                         <region>Oxfordshire</region>
                                         <settlement>Oxford</settlement>
                                         <institution>University of Oxford</institution>
                                         <repository>Ashmolean Museum</repository>
                                         <collection>English Treasures</collection>
                                         <idno type="ashmolean">AN1836p.135.371</idno>
                                         <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>
                                         <objectName>Alfred Jewel</objectName>
                                        </objectIdentifier>
                                        <physDesc>
                                         <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>
                                             surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. 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'. </p>
                                        </physDesc>
                                        <history>
                                         <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and
                                             was most likely made in <origPlace>England</origPlace>. </origin>
                                         <provenance when="1693">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. </provenance>
                                         <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical
                                             Transactions of the Royal Society.</provenance>
                                         <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in
                                             the Ashmolean Museum in Oxford. </acquisition>
                                        </history>
                                       </object>
                                      </listObject>
                                      <!-- Elsewhere in document -->
                                      <p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the
                                      <objectName ref="#Alfred_Jewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster
                                         Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>.
                                      </p>
                                      Example
                                      <listObject>
                                       <object xml:id="MaskOfTutankhamun">
                                        <objectIdentifier>
                                         <objectName xml:lang="en">Mask of Tutankhamun</objectName>
                                         <idno type="carter">256a</idno>
                                         <idno type="JournalD'Entrée">60672</idno>
                                         <idno type="exhibition">220</idno>
                                         <institution>Museum of Egyptian Antiquities</institution>
                                         <address>
                                          <street>15 Meret Basha</street>
                                          <district>Ismailia</district>
                                          <settlement>Cairo</settlement>
                                          <country>Egypt</country>
                                          <location>
                                           <geo>30.047778, 31.233333</geo>
                                          </location>
                                         </address>
                                        </objectIdentifier>
                                        <msContents>
                                         <p>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 <title>Book of the Dead</title>.</p>
                                        </msContents>
                                        <physDesc>
                                         <p> 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.</p>
                                         <p>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.</p>
                                        </physDesc>
                                        <history>
                                         <origin>
                                          <p>The mask of Tutankhamun was created in <origPlace>Egypt</origPlace> around <origDate when="-1323type="circa">1323 BC</origDate>. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun
                                               who reigned 1332–1323 BC. </p>
                                         </origin>
                                         <provenance>
                                          <p>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: <quote> The pins removed, the lid was raised. The penultimate scene was disclosed –
                                                 a very neatly wrapped mummy of the young king, with golden mask of sad but tranquil expression, symbolizing
                                                 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. </quote>
                                          </p>
                                         </provenance>
                                         <acquisition> 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. </acquisition>
                                        </history>
                                        <additional>
                                         <adminInfo>
                                          <custodialHist>
                                           <custEvent when="1944">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.</custEvent>
                                           <custEvent when="2014-08"> 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. </custEvent>
                                           <custEvent when="2015-01">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.</custEvent>
                                          </custodialHist>
                                         </adminInfo>
                                        </additional>
                                       </object>
                                      </listObject>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="objectIdentifier"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <sequence>
                                          <elementRef key="msContents"
                                           minOccurs="0"/>

                                          <elementRef key="physDesc"
                                           minOccurs="0"/>

                                          <elementRef key="historyminOccurs="0"/>
                                          <elementRef key="additional"
                                           minOccurs="0"/>

                                         </sequence>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                        </alternate>
                                        <elementRef key="objectminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element object
                                       {
                                          tei_att.global.attributes,
                                      @@ -40,4 +40,4 @@
                                             ( tei_model.noteLike | tei_model.biblLike | tei_linkGrp | tei_link )*,
                                             tei_object*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-objectDesc.html b/gl/dev/ref-objectDesc.html index f314897d1..03acdee8b 100644 --- a/gl/dev/ref-objectDesc.html +++ b/gl/dev/ref-objectDesc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <objectDesc>

                                      <objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      form(form) a short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      Definitions for the terms used may typically be provided by a <valList> element in the project schema specification.

                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: layoutDesc supportDesc
                                      Example
                                      <objectDesc form="codex">
                                       <supportDesc material="mixed">
                                        <p>Early modern
                                        <material>parchment</material> and
                                        <material>paper</material>.</p>
                                       </supportDesc>
                                       <layoutDesc>
                                        <layout ruledLines="25 32"/>
                                       </layoutDesc>
                                      </objectDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="supportDesc"
                                          minOccurs="0"/>

                                         <elementRef key="layoutDesc"
                                          minOccurs="0"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <objectDesc>

                                      <objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      form(form) a short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      Definitions for the terms used may typically be provided by a <valList> element in the project schema specification.

                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: layoutDesc supportDesc
                                      Example
                                      <objectDesc form="codex">
                                       <supportDesc material="mixed">
                                        <p>Early modern
                                        <material>parchment</material> and
                                        <material>paper</material>.</p>
                                       </supportDesc>
                                       <layoutDesc>
                                        <layout ruledLines="25 32"/>
                                       </layoutDesc>
                                      </objectDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="supportDesc"
                                          minOccurs="0"/>

                                         <elementRef key="layoutDesc"
                                          minOccurs="0"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element objectDesc
                                       {
                                          tei_att.global.attributes,
                                          attribute form { teidata.enumerated }?,
                                          ( tei_model.pLike+ | ( tei_supportDesc?, tei_layoutDesc? ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-objectIdentifier.html b/gl/dev/ref-objectIdentifier.html index 9fa2622c1..6c19d1490 100644 --- a/gl/dev/ref-objectIdentifier.html +++ b/gl/dev/ref-objectIdentifier.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <objectIdentifier>

                                      <objectIdentifier> (object identifier) groups one or more identifiers or pieces of locating information concerning a single object. [13.3.5. Objects]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl
                                      namesdates: object
                                      May contain
                                      Example
                                      <objectIdentifier>
                                       <country>United Kingdom</country>
                                       <region>Oxfordshire</region>
                                       <settlement>Oxford</settlement>
                                       <institution>University of Oxford</institution>
                                       <repository>Ashmolean Museum</repository>
                                       <collection>English Treasures</collection>
                                       <idno type="ashmolean">AN1836p.135.371</idno>
                                       <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>
                                       <objectName>Alfred Jewel</objectName>
                                      </objectIdentifier>
                                      Example
                                      <object xml:id="Excalibur-MultipleNames">
                                       <objectIdentifier>
                                        <objectName type="main">Excalibur</objectName>
                                        <objectName type="alt">Caliburn</objectName>
                                        <objectName xml:lang="cy">Caledfwlch</objectName>
                                        <objectName xml:lang="cnx">Calesvol</objectName>
                                        <objectName xml:lang="br">Kaledvoulc'h</objectName>
                                        <objectName xml:lang="la">Caliburnus</objectName>
                                        <country>Wales</country>
                                       </objectIdentifier>
                                       <p>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.
                                         In some versions Excalibur's blade was engraved with phrases on opposite sides which in translation read:
                                         "Take me up" and "Cast me away" (or similar).</p>
                                      </object>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.placeNamePart"/>
                                        <elementRef key="institution"/>
                                        <elementRef key="repository"/>
                                        <elementRef key="collection"/>
                                        <elementRef key="idno"/>
                                        <elementRef key="msName"/>
                                        <elementRef key="objectName"/>
                                        <elementRef key="altIdentifier"/>
                                        <elementRef key="address"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <objectIdentifier>

                                      <objectIdentifier> (object identifier) groups one or more identifiers or pieces of locating information concerning a single object. [13.3.5. Objects]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: bibl
                                      namesdates: object
                                      May contain
                                      Example
                                      <objectIdentifier>
                                       <country>United Kingdom</country>
                                       <region>Oxfordshire</region>
                                       <settlement>Oxford</settlement>
                                       <institution>University of Oxford</institution>
                                       <repository>Ashmolean Museum</repository>
                                       <collection>English Treasures</collection>
                                       <idno type="ashmolean">AN1836p.135.371</idno>
                                       <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>
                                       <objectName>Alfred Jewel</objectName>
                                      </objectIdentifier>
                                      Example
                                      <object xml:id="Excalibur-MultipleNames">
                                       <objectIdentifier>
                                        <objectName type="main">Excalibur</objectName>
                                        <objectName type="alt">Caliburn</objectName>
                                        <objectName xml:lang="cy">Caledfwlch</objectName>
                                        <objectName xml:lang="cnx">Calesvol</objectName>
                                        <objectName xml:lang="br">Kaledvoulc'h</objectName>
                                        <objectName xml:lang="la">Caliburnus</objectName>
                                        <country>Wales</country>
                                       </objectIdentifier>
                                       <p>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.
                                         In some versions Excalibur's blade was engraved with phrases on opposite sides which in translation read:
                                         "Take me up" and "Cast me away" (or similar).</p>
                                      </object>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.placeNamePart"/>
                                        <elementRef key="institution"/>
                                        <elementRef key="repository"/>
                                        <elementRef key="collection"/>
                                        <elementRef key="idno"/>
                                        <elementRef key="msName"/>
                                        <elementRef key="objectName"/>
                                        <elementRef key="altIdentifier"/>
                                        <elementRef key="address"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element objectIdentifier
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                           | tei_altIdentifier
                                           | tei_address
                                          )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-objectName.html b/gl/dev/ref-objectName.html index cae9c5bdc..096f393b6 100644 --- a/gl/dev/ref-objectName.html +++ b/gl/dev/ref-objectName.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <objectName>

                                      <objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [13.2.4. Object Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <p>
                                      The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the
                                      <objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster
                                         Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>.
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <objectName>

                                      <objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [13.2.4. Object Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <p>
                                      The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the
                                      <objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster
                                         Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>.
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element objectName
                                       {
                                          tei_att.datable.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-objectType.html b/gl/dev/ref-objectType.html index 339e79c0f..06d38e1dc 100644 --- a/gl/dev/ref-objectType.html +++ b/gl/dev/ref-objectType.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <objectType>

                                      <objectType> (object type) contains a word or phrase describing the type of object being referred to. [10.3.2. Material and Object Type]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The ref attribute may be used to point to one or more items within a taxonomy of types of object, defined either internally or externally.

                                      Example
                                      <physDesc>
                                       <p> Paper and vellum <objectType>codex</objectType> in modern cloth binding.</p>
                                      </physDesc>
                                      Example
                                      <physDesc>
                                       <p>Fragment of a re-used marble <objectType>funerary stele</objectType>.
                                       </p>
                                      </physDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <objectType>

                                      <objectType> (object type) contains a word or phrase describing the type of object being referred to. [10.3.2. Material and Object Type]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The ref attribute may be used to point to one or more items within a taxonomy of types of object, defined either internally or externally.

                                      Example
                                      <physDesc>
                                       <p> Paper and vellum <objectType>codex</objectType> in modern cloth binding.</p>
                                      </physDesc>
                                      Example
                                      <physDesc>
                                       <p>Fragment of a re-used marble <objectType>funerary stele</objectType>.
                                       </p>
                                      </physDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element objectType
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-offset.html b/gl/dev/ref-offset.html index f2d0b4a96..d56880493 100644 --- a/gl/dev/ref-offset.html +++ b/gl/dev/ref-offset.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <offset>

                                      <offset> (offset) marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or times involved in the expression. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName key="NRPA1">
                                       <offset>50 metres below the summit of</offset>
                                       <geogName>
                                        <geogFeat>Mount</geogFeat>
                                        <name>Sinai</name>
                                       </geogName>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <offset>

                                      <offset> (offset) marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or times involved in the expression. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName key="NRPA1">
                                       <offset>50 metres below the summit of</offset>
                                       <geogName>
                                        <geogFeat>Mount</geogFeat>
                                        <name>Sinai</name>
                                       </geogName>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element offset
                                       {
                                          tei_att.datable.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-org.html b/gl/dev/ref-org.html index 5b2f2d649..224725d52 100644 --- a/gl/dev/ref-org.html +++ b/gl/dev/ref-org.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <org>

                                      <org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [13.3.3. Organizational Data]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      rolespecifies a primary role or classification for the organization.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, familyGroup, or politicalParty, each of which should be associated with a definition. Such local definitions will typically be provided by a desc for each <valItem> element in the schema specification of the project's customization.

                                      Member of
                                      Contained by
                                      corpus: particDesc
                                      namesdates: listOrg listPerson org
                                      May contain
                                      Example
                                      <org xml:id="JAMs">
                                       <orgName>Justified Ancients of Mummu</orgName>
                                       <desc>An underground anarchist collective spearheaded by
                                       <persName>Hagbard Celine</persName>, who fight the Illuminati
                                         from a golden submarine, the <name>Leif Ericson</name>
                                       </desc>
                                       <bibl>
                                        <author>Robert Shea</author>
                                        <author>Robert Anton Wilson</author>
                                        <title>The Illuminatus! Trilogy</title>
                                       </bibl>
                                      </org>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.labelLike"/>
                                          <classRef key="model.nameLike"/>
                                          <classRef key="model.placeLike"/>
                                          <classRef key="model.orgPart"/>
                                          <classRef key="model.milestoneLike"/>
                                         </alternate>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                        <classRef key="model.personLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <org>

                                      <org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [13.3.3. Organizational Data]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      rolespecifies a primary role or classification for the organization.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, familyGroup, or politicalParty, each of which should be associated with a definition. Such local definitions will typically be provided by a desc for each <valItem> element in the schema specification of the project's customization.

                                      Member of
                                      Contained by
                                      corpus: particDesc
                                      namesdates: listOrg listPerson org
                                      May contain
                                      Example
                                      <org xml:id="JAMs">
                                       <orgName>Justified Ancients of Mummu</orgName>
                                       <desc>An underground anarchist collective spearheaded by
                                       <persName>Hagbard Celine</persName>, who fight the Illuminati
                                         from a golden submarine, the <name>Leif Ericson</name>
                                       </desc>
                                       <bibl>
                                        <author>Robert Shea</author>
                                        <author>Robert Anton Wilson</author>
                                        <title>The Illuminatus! Trilogy</title>
                                       </bibl>
                                      </org>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.labelLike"/>
                                          <classRef key="model.nameLike"/>
                                          <classRef key="model.placeLike"/>
                                          <classRef key="model.orgPart"/>
                                          <classRef key="model.milestoneLike"/>
                                         </alternate>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                        <classRef key="model.personLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element org
                                       {
                                          tei_att.global.attributes,
                                      @@ -50,4 +50,4 @@
                                             )*,
                                             tei_model.personLike*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-orgName.html b/gl/dev/ref-orgName.html index 6e58296cd..606e707e4 100644 --- a/gl/dev/ref-orgName.html +++ b/gl/dev/ref-orgName.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <orgName>

                                      <orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">
                                       <placeName key="PEN">Pennsyla.</placeName> Abolition Society
                                      </orgName> [...]
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <orgName>

                                      <orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">
                                       <placeName key="PEN">Pennsyla.</placeName> Abolition Society
                                      </orgName> [...]
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element orgName
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-orig.html b/gl/dev/ref-orig.html index c8c5a6e11..1a189ddc0 100644 --- a/gl/dev/ref-orig.html +++ b/gl/dev/ref-orig.html @@ -22,5 +22,5 @@ }); });

                                      <orig>

                                      <orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and -Normalization 12. Critical Apparatus]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      If all that is desired is to call attention to the original version in the copy text, orig may be used alone:

                                      <l>But this will be a <orig>meere</orig> confusion</l>
                                      <l>And hardly shall we all be <orig>vnderstoode</orig>
                                      </l>
                                      Example

                                      More usually, an orig will be combined with a regularized form within a choice element:

                                      <l>But this will be a <choice>
                                        <orig>meere</orig>
                                        <reg>mere</reg>
                                       </choice> confusion</l>
                                      <l>And hardly shall we all be <choice>
                                        <orig>vnderstoode</orig>
                                        <reg>understood</reg>
                                       </choice>
                                      </l>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      -element orig { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +Normalization 12. Critical Apparatus]ModulecoreAttributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) Member of
                                      model.choicePart model.pPart.transcriptional
                                      Contained by
                                      May contain
                                      analysis: c interp interpGrp m pc phr s w
                                      certainty: certainty precision
                                      dictionaries: lang
                                      gaiji: g
                                      header: biblFull idno
                                      textcrit: app listApp
                                      textstructure: floatingText
                                      character data
                                      Example

                                      If all that is desired is to call attention to the original version in the copy text, orig may be used alone:

                                      <l>But this will be a <orig>meere</orig> confusion</l>
                                      <l>And hardly shall we all be <orig>vnderstoode</orig>
                                      </l>
                                      Example

                                      More usually, an orig will be combined with a regularized form within a choice element:

                                      <l>But this will be a <choice>
                                        <orig>meere</orig>
                                        <reg>mere</reg>
                                       </choice> confusion</l>
                                      <l>And hardly shall we all be <choice>
                                        <orig>vnderstoode</orig>
                                        <reg>understood</reg>
                                       </choice>
                                      </l>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +element orig { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-origDate.html b/gl/dev/ref-origDate.html index 9e2ae0e4b..08cbdec11 100644 --- a/gl/dev/ref-origDate.html +++ b/gl/dev/ref-origDate.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <origDate>

                                      <origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype) att.editLike (evidence, @instant)
                                      evidence
                                      Status Optional
                                      Datatype 1–6 occurrences of teidata.word separated by whitespace
                                      Suggested values include:
                                      archaeological-context
                                      Dated by the archaeolgical context, stratigraphy or associated finds
                                      internal-date
                                      Dated by explicit internal date
                                      lettering
                                      Text dated palaeographically
                                      material-context
                                      Dated by the material, iconographic or other physical context of the object itself
                                      nomenclature
                                      Text dated by nomenclature or onomastics
                                      office
                                      Text dated by an office or rank, e.g. the reign of an emperor or other ruler
                                      prosopography
                                      Text dated by known persons named or implied within it
                                      textual-context
                                      Dated via textual or linguistic context (other than explicit date or titles)
                                      titulature
                                      Dated by the use of official titles
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <origDate notBefore="-0300"
                                       notAfter="-0200">
                                      3rd century BCE</origDate>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <origDate>

                                      <origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype) att.editLike (evidence, @instant)
                                      evidence
                                      Status Optional
                                      Datatype 1–6 occurrences of teidata.word separated by whitespace
                                      Suggested values include:
                                      archaeological-context
                                      Dated by the archaeolgical context, stratigraphy or associated finds
                                      internal-date
                                      Dated by explicit internal date
                                      lettering
                                      Text dated palaeographically
                                      material-context
                                      Dated by the material, iconographic or other physical context of the object itself
                                      nomenclature
                                      Text dated by nomenclature or onomastics
                                      office
                                      Text dated by an office or rank, e.g. the reign of an emperor or other ruler
                                      prosopography
                                      Text dated by known persons named or implied within it
                                      textual-context
                                      Dated via textual or linguistic context (other than explicit date or titles)
                                      titulature
                                      Dated by the use of official titles
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <origDate notBefore="-0300"
                                       notAfter="-0200">
                                      3rd century BCE</origDate>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element origDate
                                       {
                                          tei_att.global.attributes,
                                      @@ -108,4 +108,4 @@
                                             }
                                          }?,
                                          ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-origPlace.html b/gl/dev/ref-origPlace.html index e3cc3d02e..1b0a58c99 100644 --- a/gl/dev/ref-origPlace.html +++ b/gl/dev/ref-origPlace.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <origPlace>

                                      <origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.

                                      Example
                                      <origPlace>Birmingham</origPlace>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <origPlace>

                                      <origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.

                                      Example
                                      <origPlace>Birmingham</origPlace>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element origPlace
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.editLike.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-origin.html b/gl/dev/ref-origin.html index 459ea0139..fe7053a80 100644 --- a/gl/dev/ref-origin.html +++ b/gl/dev/ref-origin.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <origin>

                                      <origin> (origin) contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      msdescription: history
                                      May contain
                                      Example
                                      <origin notBefore="1802notAfter="1845"
                                       evidence="internalresp="#AMH">
                                      Copied in <name type="origPlace">Derby</name>, probably from an
                                      old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>.
                                      </origin>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <origin>

                                      <origin> (origin) contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      msdescription: history
                                      May contain
                                      Example
                                      <origin notBefore="1802notAfter="1845"
                                       evidence="internalresp="#AMH">
                                      Copied in <name type="origPlace">Derby</name>, probably from an
                                      old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>.
                                      </origin>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element origin
                                       {
                                          tei_att.global.attributes,
                                          tei_att.editLike.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-p.html b/gl/dev/ref-p.html index c346b7587..8eaf2fee6 100644 --- a/gl/dev/ref-p.html +++ b/gl/dev/ref-p.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <p>

                                      <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.fragmentable (@part) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
                                         done?</q>
                                      </p>
                                      <p>
                                       <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
                                      </p>
                                      <p>
                                       <q>Then you must mean that Thorvald is dead,</q> she said.
                                      </p>
                                      <p>
                                       <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
                                      </p>
                                      Schematron

                                      <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText +

                                      <p>

                                      <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.fragmentable (@part) att.written (@hand)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
                                         done?</q>
                                      </p>
                                      <p>
                                       <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
                                      </p>
                                      <p>
                                       <q>Then you must mean that Thorvald is dead,</q> she said.
                                      </p>
                                      <p>
                                       <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
                                      </p>
                                      Schematron

                                      <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText |parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
                                      </sch:report>
                                      Schematron

                                      <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText @@ -33,4 +33,4 @@ tei_att.fragmentable.attributes, tei_att.written.attributes, tei_macro.paraContent -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-particDesc.html b/gl/dev/ref-particDesc.html index f461c67aa..480451b3b 100644 --- a/gl/dev/ref-particDesc.html +++ b/gl/dev/ref-particDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <particDesc>

                                      <particDesc> (participation description) 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. [15.2. Contextual Information]
                                      Modulecorpus
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      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.

                                      Example
                                      <particDesc>
                                       <listPerson>
                                        <person xml:id="P-1234sex="2age="mid">
                                         <p>Female informant, well-educated, born in
                                             Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently.
                                             Socio-Economic status B2.</p>
                                        </person>
                                        <person xml:id="P-4332sex="1">
                                         <persName>
                                          <surname>Hancock</surname>
                                          <forename>Antony</forename>
                                          <forename>Aloysius</forename>
                                          <forename>St John</forename>
                                         </persName>
                                         <residence notAfter="1959">
                                          <address>
                                           <street>Railway Cuttings</street>
                                           <settlement>East Cheam</settlement>
                                          </address>
                                         </residence>
                                         <occupation>comedian</occupation>
                                        </person>
                                        <listRelation>
                                         <relation type="personalname="spouse"
                                          mutual="#P-1234 #P-4332"/>

                                        </listRelation>
                                       </listPerson>
                                      </particDesc>

                                      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.

                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personLike"/>
                                         <elementRef key="listPerson"/>
                                         <elementRef key="listOrg"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <particDesc>

                                      <particDesc> (participation description) 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. [15.2. Contextual Information]
                                      Modulecorpus
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      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.

                                      Example
                                      <particDesc>
                                       <listPerson>
                                        <person xml:id="P-1234sex="2age="mid">
                                         <p>Female informant, well-educated, born in
                                             Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently.
                                             Socio-Economic status B2.</p>
                                        </person>
                                        <person xml:id="P-4332sex="1">
                                         <persName>
                                          <surname>Hancock</surname>
                                          <forename>Antony</forename>
                                          <forename>Aloysius</forename>
                                          <forename>St John</forename>
                                         </persName>
                                         <residence notAfter="1959">
                                          <address>
                                           <street>Railway Cuttings</street>
                                           <settlement>East Cheam</settlement>
                                          </address>
                                         </residence>
                                         <occupation>comedian</occupation>
                                        </person>
                                        <listRelation>
                                         <relation type="personalname="spouse"
                                          mutual="#P-1234 #P-4332"/>

                                        </listRelation>
                                       </listPerson>
                                      </particDesc>

                                      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.

                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personLike"/>
                                         <elementRef key="listPerson"/>
                                         <elementRef key="listOrg"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element particDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                             tei_model.pLike+
                                           | ( tei_model.personLike | tei_listPerson | tei_listOrg )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-path.html b/gl/dev/ref-path.html index c338d342f..3190796c7 100644 --- a/gl/dev/ref-path.html +++ b/gl/dev/ref-path.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <path>

                                      <path> (path) defines any line passing through two or more points within a surface element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.written (@hand) att.coordinated (points, @start, @ulx, @uly, @lrx, @lry)
                                      pointsidentifies a line within the container or bounding box specified by the parent element by means of a series of two or more pairs of numbers, each of which gives the x,y coordinates of a point on the line.
                                      Derived fromatt.coordinated
                                      Status Optional
                                      Datatype 2–∞ occurrences of teidata.point separated by whitespace
                                      Member of
                                      Contained by
                                      transcr: line surface zone
                                      May containEmpty element
                                      Note

                                      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 the zone element rather than the path element.

                                      Example
                                      <surface ulx="0uly="0lrx="443lry="272">
                                       <graphic url="facs-fig3.jpg"/>
                                       <path points="74,73 171,244"/>
                                       <path points="71,203 173,116"/>
                                      </surface>
                                      Schematron

                                      <sch:rule context="tei:path[@points]">
                                      <sch:let name="firstPair"
                                       value="tokenize( normalize-space( @points ), ' ')[1]"/>

                                      <sch:let name="lastPair"
                                       value="tokenize( normalize-space( @points ), ' ')[last()]"/>

                                      <sch:let name="firstX"
                                       value="xs:float( substring-before( $firstPair, ',') )"/>

                                      <sch:let name="firstY"
                                       value="xs:float( substring-after( $firstPair, ',') )"/>

                                      <sch:let name="lastX"
                                       value="xs:float( substring-before( $lastPair, ',') )"/>

                                      <sch:let name="lastY"
                                       value="xs:float( substring-after( $lastPair, ',') )"/>

                                      <sch:report test="$firstX eq $lastX and $firstY eq $lastY">The first and
                                      last elements of this path are the same. To specify a closed polygon, use
                                      the zone element rather than the path element. </sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <path>

                                      <path> (path) defines any line passing through two or more points within a surface element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.written (@hand) att.coordinated (points, @start, @ulx, @uly, @lrx, @lry)
                                      pointsidentifies a line within the container or bounding box specified by the parent element by means of a series of two or more pairs of numbers, each of which gives the x,y coordinates of a point on the line.
                                      Derived fromatt.coordinated
                                      Status Optional
                                      Datatype 2–∞ occurrences of teidata.point separated by whitespace
                                      Member of
                                      Contained by
                                      transcr: line surface zone
                                      May containEmpty element
                                      Note

                                      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 the zone element rather than the path element.

                                      Example
                                      <surface ulx="0uly="0lrx="443lry="272">
                                       <graphic url="facs-fig3.jpg"/>
                                       <path points="74,73 171,244"/>
                                       <path points="71,203 173,116"/>
                                      </surface>
                                      Schematron

                                      <sch:rule context="tei:path[@points]">
                                      <sch:let name="firstPair"
                                       value="tokenize( normalize-space( @points ), ' ')[1]"/>

                                      <sch:let name="lastPair"
                                       value="tokenize( normalize-space( @points ), ' ')[last()]"/>

                                      <sch:let name="firstX"
                                       value="xs:float( substring-before( $firstPair, ',') )"/>

                                      <sch:let name="firstY"
                                       value="xs:float( substring-after( $firstPair, ',') )"/>

                                      <sch:let name="lastX"
                                       value="xs:float( substring-before( $lastPair, ',') )"/>

                                      <sch:let name="lastY"
                                       value="xs:float( substring-after( $lastPair, ',') )"/>

                                      <sch:report test="$firstX eq $lastX and $firstY eq $lastY">The first and
                                      last elements of this path are the same. To specify a closed polygon, use
                                      the zone element rather than the path element. </sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element path
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                          tei_att.written.attributes,
                                          attribute points { list { teidata.point, teidata.point, teidata.point* } }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-pb.html b/gl/dev/ref-pb.html index 546a9c418..80adf7948 100644 --- a/gl/dev/ref-pb.html +++ b/gl/dev/ref-pb.html @@ -22,7 +22,7 @@ }); });

                                      <pb>

                                      <pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone -Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself.

                                      The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives.

                                      Example

                                      Page numbers may vary in different editions of a text.

                                      <p> ... <pb n="145ed="ed2"/>
                                      <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283ed="ed1"/>
                                      <!-- Page 283 in edition "ed1" starts here--> ... </p>
                                      Example

                                      A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute

                                      <body>
                                       <pb n="1facs="page1.png"/>
                                      <!-- page1.png contains an image of the page; +Elements]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Note

                                      A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself.

                                      The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives.

                                      Example

                                      Page numbers may vary in different editions of a text.

                                      <p> ... <pb n="145ed="ed2"/>
                                      <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283ed="ed1"/>
                                      <!-- Page 283 in edition "ed1" starts here--> ... </p>
                                      Example

                                      A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute

                                      <body>
                                       <pb n="1facs="page1.png"/>
                                      <!-- page1.png contains an image of the page; the text it contains is encoded here -->
                                       <p>
                                      <!-- ... -->
                                       </p>
                                       <pb n="2facs="page2.png"/>
                                      <!-- similarly, for page 2 -->
                                       <p>
                                      <!-- ... -->
                                       </p>
                                      </body>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element pb
                                       {
                                      @@ -32,4 +32,4 @@
                                          tei_att.spanning.attributes,
                                          tei_att.breaking.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-pc.html b/gl/dev/ref-pc.html index 070270a32..1e865a681 100644 --- a/gl/dev/ref-pc.html +++ b/gl/dev/ref-pc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <pc>

                                      <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig))
                                      forceindicates the extent to which this punctuation mark conventionally separates words or phrases
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      strong
                                      the punctuation mark is a word separator
                                      weak
                                      the punctuation mark is not a word separator
                                      inter
                                      the punctuation mark may or may not be a word separator
                                      unitprovides a name for the kind of unit delimited by this punctuation mark.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      preindicates whether this punctuation mark precedes or follows the unit it delimits.
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <phr>
                                       <w>do</w>
                                       <w>you</w>
                                       <w>understand</w>
                                       <pc type="interrogative">?</pc>
                                      </phr>
                                      Example

                                      Example encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [ID AILALW in TEI Guidelines].

                                      <s>
                                       <w pos="PPERmsd="1.Pl.*.Nom">Wir</w>
                                       <w pos="VVFINmsd="1.Pl.Pres.Ind">fahren</w>
                                       <w pos="APPRmsd="--">in</w>
                                       <w pos="ARTmsd="Def.Masc.Akk.Sg.">den</w>
                                       <w pos="NNmsd="Masc.Akk.Sg.">Urlaub</w>
                                       <pc pos="$.msd="--join="left">.</pc>
                                      </s>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="c"/>
                                        <classRef key="model.pPart.edit"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <pc>

                                      <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig))
                                      forceindicates the extent to which this punctuation mark conventionally separates words or phrases
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      strong
                                      the punctuation mark is a word separator
                                      weak
                                      the punctuation mark is not a word separator
                                      inter
                                      the punctuation mark may or may not be a word separator
                                      unitprovides a name for the kind of unit delimited by this punctuation mark.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      preindicates whether this punctuation mark precedes or follows the unit it delimits.
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <phr>
                                       <w>do</w>
                                       <w>you</w>
                                       <w>understand</w>
                                       <pc type="interrogative">?</pc>
                                      </phr>
                                      Example

                                      Example encoding of the German sentence Wir fahren in den Urlaub., encoded with attributes from att.linguistic discussed in section [ID AILALW in TEI Guidelines].

                                      <s>
                                       <w pos="PPERmsd="1.Pl.*.Nom">Wir</w>
                                       <w pos="VVFINmsd="1.Pl.Pres.Ind">fahren</w>
                                       <w pos="APPRmsd="--">in</w>
                                       <w pos="ARTmsd="Def.Masc.Akk.Sg.">den</w>
                                       <w pos="NNmsd="Masc.Akk.Sg.">Urlaub</w>
                                       <pc pos="$.msd="--join="left">.</pc>
                                      </s>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="c"/>
                                        <classRef key="model.pPart.edit"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element pc
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          attribute unit { teidata.enumerated }?,
                                          attribute pre { teidata.truthValue }?,
                                          ( text | tei_model.gLike | tei_c | tei_model.pPart.edit )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-persName.html b/gl/dev/ref-persName.html index 9b094cfbd..c4b71b777 100644 --- a/gl/dev/ref-persName.html +++ b/gl/dev/ref-persName.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <persName>

                                      <persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <forename>Edward</forename>
                                       <forename>George</forename>
                                       <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
                                       <placeName>Knebworth</placeName>
                                       </roleName>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <persName>

                                      <persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <persName>
                                       <forename>Edward</forename>
                                       <forename>George</forename>
                                       <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
                                       <placeName>Knebworth</placeName>
                                       </roleName>
                                      </persName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element persName
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-persPronouns.html b/gl/dev/ref-persPronouns.html index d75a406fd..7a3d8de80 100644 --- a/gl/dev/ref-persPronouns.html +++ b/gl/dev/ref-persPronouns.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <persPronouns>

                                      <persPronouns> (personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described. [13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      evidence(evidence) indicates support for the listed personal pronouns.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      conjecture
                                      (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.
                                      selfIdentification
                                      (self identification) The given value has been explicitly stated or confirmed by the person to whom this pronoun applies.
                                      trustedThirdParty
                                      (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.
                                      value(value) supplies a regularized value for personal pronouns.
                                      Status Recommended
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Sample values include:
                                      e
                                      (e) e/eirs
                                      he
                                      (he) he/him/his
                                      she
                                      (she) she/her/hers
                                      they
                                      (they) they/them/theirs
                                      Note

                                      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, e.g. elle, il, and ils.

                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <person>
                                       <persName>
                                        <forename>SUE</forename>
                                        <addName>the T. rex</addName>
                                       </persName>
                                       <residence>The Field Museum. Chicago, Illinois, United States.</residence>
                                       <sex value="0"/>
                                       <persPronouns value="they">they/them</persPronouns>
                                       <note>
                                        <cit>
                                         <quote>Specimen FMNH PR 2081. Legendary Fossil. Apex
                                             Predator. National Treasure. <emph style="text-transform:uppercase; letter-spacing:0.25rem;">Murderbird.</emph>
                                         </quote>
                                         <bibl>SUEtheTrex, Twitter biography.
                                         <ptr target="https://twitter.com/SUEtheTrex"/>.
                                             Accessed <date when="2020-03-25">March 25th, 2020</date>.</bibl>
                                        </cit>
                                       </note>
                                      </person>
                                      Example
                                      <docAuthor>
                                       <persName>Lal Zimman</persName>
                                       <persPronouns value="he">(he/him/his)</persPronouns>
                                       <ref target="#Name">(FAQ)</ref>
                                       <persName type="IPA">[lɑɫ ˈzimn̩]</persName>
                                       <email>zimman at ucsb dot edu</email>
                                       <roleName>Assistant Professor of Linguistics</roleName>
                                       <roleName>Affiliated Faculty in Feminist Studies</roleName>
                                       <address>
                                        <addrLine>South Hall 3518</addrLine>
                                        <addrLine>University of California, Santa Barbara</addrLine>
                                       </address>
                                      </docAuthor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <persPronouns>

                                      <persPronouns> (personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described. [13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      evidence(evidence) indicates support for the listed personal pronouns.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      conjecture
                                      (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.
                                      selfIdentification
                                      (self identification) The given value has been explicitly stated or confirmed by the person to whom this pronoun applies.
                                      trustedThirdParty
                                      (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.
                                      value(value) supplies a regularized value for personal pronouns.
                                      Status Recommended
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Sample values include:
                                      e
                                      (e) e/eirs
                                      he
                                      (he) he/him/his
                                      she
                                      (she) she/her/hers
                                      they
                                      (they) they/them/theirs
                                      Note

                                      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, e.g. elle, il, and ils.

                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <person>
                                       <persName>
                                        <forename>SUE</forename>
                                        <addName>the T. rex</addName>
                                       </persName>
                                       <residence>The Field Museum. Chicago, Illinois, United States.</residence>
                                       <sex value="0"/>
                                       <persPronouns value="they">they/them</persPronouns>
                                       <note>
                                        <cit>
                                         <quote>Specimen FMNH PR 2081. Legendary Fossil. Apex
                                             Predator. National Treasure. <emph style="text-transform:uppercase; letter-spacing:0.25rem;">Murderbird.</emph>
                                         </quote>
                                         <bibl>SUEtheTrex, Twitter biography.
                                         <ptr target="https://twitter.com/SUEtheTrex"/>.
                                             Accessed <date when="2020-03-25">March 25th, 2020</date>.</bibl>
                                        </cit>
                                       </note>
                                      </person>
                                      Example
                                      <docAuthor>
                                       <persName>Lal Zimman</persName>
                                       <persPronouns value="he">(he/him/his)</persPronouns>
                                       <ref target="#Name">(FAQ)</ref>
                                       <persName type="IPA">[lɑɫ ˈzimn̩]</persName>
                                       <email>zimman at ucsb dot edu</email>
                                       <roleName>Assistant Professor of Linguistics</roleName>
                                       <roleName>Affiliated Faculty in Feminist Studies</roleName>
                                       <address>
                                        <addrLine>South Hall 3518</addrLine>
                                        <addrLine>University of California, Santa Barbara</addrLine>
                                       </address>
                                      </docAuthor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element persPronouns
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                          }?,
                                          attribute value { list { teidata.enumerated+ } }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-person.html b/gl/dev/ref-person.html index b887ecda4..290afffff 100644 --- a/gl/dev/ref-person.html +++ b/gl/dev/ref-person.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <person>

                                      <person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      rolespecifies a primary role or classification for the person.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Note

                                      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.

                                      sexspecifies the sex of the person.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.sex separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      genderspecifies the gender of the person.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      agespecifies an age group for the person.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      Member of
                                      Contained by
                                      corpus: particDesc
                                      namesdates: listPerson org
                                      May contain
                                      Note

                                      May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

                                      Example
                                      <person sex="Fage="adult">
                                       <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
                                         status B2.</p>
                                      </person>
                                      Example
                                      <person sex="intersexrole="god"
                                       age="immortal">

                                       <persName>Hermaphroditos</persName>
                                       <persName xml:lang="grc">Ἑρμαφρόδιτος</persName>
                                      </person>
                                      Example
                                      <person xml:id="Ovi01sex="Mrole="poet">
                                       <persName xml:lang="en">Ovid</persName>
                                       <persName xml:lang="la">Publius Ovidius Naso</persName>
                                       <birth when="-0044-03-20"> 20 March 43 BC <placeName>
                                         <settlement type="city">Sulmona</settlement>
                                         <country key="IT">Italy</country>
                                        </placeName>
                                       </birth>
                                       <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>
                                         <settlement type="city">Tomis (Constanta)</settlement>
                                         <country key="RO">Romania</country>
                                        </placeName>
                                       </death>
                                      </person>
                                      Example

                                      The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.

                                      <person xml:id="arielgender="U">
                                       <persName>Ariel</persName>
                                       <note>Character in <title level="m">The Tempest</title>.</note>
                                      </person>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personPart"/>
                                         <classRef key="model.global"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <person>

                                      <person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      rolespecifies a primary role or classification for the person.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Note

                                      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.

                                      sexspecifies the sex of the person.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.sex separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      genderspecifies the gender of the person.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      agespecifies an age group for the person.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      Member of
                                      Contained by
                                      corpus: particDesc
                                      namesdates: listPerson org
                                      May contain
                                      Note

                                      May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

                                      Example
                                      <person sex="Fage="adult">
                                       <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
                                         status B2.</p>
                                      </person>
                                      Example
                                      <person sex="intersexrole="god"
                                       age="immortal">

                                       <persName>Hermaphroditos</persName>
                                       <persName xml:lang="grc">Ἑρμαφρόδιτος</persName>
                                      </person>
                                      Example
                                      <person xml:id="Ovi01sex="Mrole="poet">
                                       <persName xml:lang="en">Ovid</persName>
                                       <persName xml:lang="la">Publius Ovidius Naso</persName>
                                       <birth when="-0044-03-20"> 20 March 43 BC <placeName>
                                         <settlement type="city">Sulmona</settlement>
                                         <country key="IT">Italy</country>
                                        </placeName>
                                       </birth>
                                       <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>
                                         <settlement type="city">Tomis (Constanta)</settlement>
                                         <country key="RO">Romania</country>
                                        </placeName>
                                       </death>
                                      </person>
                                      Example

                                      The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.

                                      <person xml:id="arielgender="U">
                                       <persName>Ariel</persName>
                                       <note>Character in <title level="m">The Tempest</title>.</note>
                                      </person>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personPart"/>
                                         <classRef key="model.global"/>
                                         <elementRef key="ptr"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element person
                                       {
                                          tei_att.global.attributes,
                                      @@ -35,4 +35,4 @@
                                             tei_model.pLike+
                                           | ( tei_model.personPart | tei_model.global | tei_ptr )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-personGrp.html b/gl/dev/ref-personGrp.html index 16b11e7c2..b9a6ec908 100644 --- a/gl/dev/ref-personGrp.html +++ b/gl/dev/ref-personGrp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <personGrp>

                                      <personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
                                      rolespecifies the role of this group of participants in the interaction.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      sexspecifies the sex of the participant group.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.sex separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      genderspecifies the gender of the participant group.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      agespecifies the age group of the participants.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      sizedescribes informally the size or approximate size of the group for example by means of a number and an indication of accuracy e.g. approx 200.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      corpus: particDesc
                                      namesdates: listPerson org
                                      May contain
                                      Note

                                      May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

                                      The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

                                      Example
                                      <personGrp xml:id="pg1role="audience"
                                       sex="mixedsize="approx 50"/>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personPart"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <personGrp>

                                      <personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [15.2.2. The Participant Description]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
                                      rolespecifies the role of this group of participants in the interaction.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      sexspecifies the sex of the participant group.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.sex separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      genderspecifies the gender of the participant group.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be defined locally by a project, or they may refer to an external standard.

                                      agespecifies the age group of the participants.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      sizedescribes informally the size or approximate size of the group for example by means of a number and an indication of accuracy e.g. approx 200.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      corpus: particDesc
                                      namesdates: listPerson org
                                      May contain
                                      Note

                                      May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

                                      The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

                                      Example
                                      <personGrp xml:id="pg1role="audience"
                                       sex="mixedsize="approx 50"/>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personPart"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element personGrp
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          attribute age { teidata.enumerated }?,
                                          attribute size { list { teidata.word+ } }?,
                                          ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-persona.html b/gl/dev/ref-persona.html index f01770030..9026d6ce0 100644 --- a/gl/dev/ref-persona.html +++ b/gl/dev/ref-persona.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <persona>

                                      <persona> provides information about one of the personalities identified for a given individual, where an individual has multiple personalities. [13.3.2. The Person Element]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      rolespecifies a primary role or classification for the persona.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Note

                                      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.

                                      sexspecifies the sex of the persona.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.sex separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, or may refer to an external standard.

                                      genderspecifies the gender of the persona.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, or they may refer to an external standard.

                                      agespecifies an age group for the persona.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      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.

                                      Example
                                      <person sex="Mage="adult">
                                       <persona sex="M">
                                        <persName>Dr Henry Jekyll</persName>
                                       </persona>
                                       <persona sex="Mage="youth">
                                        <persName>Edward Hyde</persName>
                                       </persona>
                                      </person>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personPart"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <persona>

                                      <persona> provides information about one of the personalities identified for a given individual, where an individual has multiple personalities. [13.3.2. The Person Element]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      rolespecifies a primary role or classification for the persona.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Note

                                      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.

                                      sexspecifies the sex of the persona.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.sex separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, or may refer to an external standard.

                                      genderspecifies the gender of the persona.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.gender separated by whitespace
                                      Note

                                      Values for this attribute may be locally defined by a project, or they may refer to an external standard.

                                      agespecifies an age group for the persona.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Note

                                      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.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      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.

                                      Example
                                      <person sex="Mage="adult">
                                       <persona sex="M">
                                        <persName>Dr Henry Jekyll</persName>
                                       </persona>
                                       <persona sex="Mage="youth">
                                        <persName>Edward Hyde</persName>
                                       </persona>
                                      </person>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.personPart"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element persona
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          attribute gender { list { teidata.gender+ } }?,
                                          attribute age { teidata.enumerated }?,
                                          ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-phr.html b/gl/dev/ref-phr.html index e310c7f5c..7ff1c53f4 100644 --- a/gl/dev/ref-phr.html +++ b/gl/dev/ref-phr.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <phr>

                                      <phr> (phrase) represents a grammatical phrase. [17.1. Linguistic Segment Categories]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to indicate the type of phrase, taking values such as noun, verb, preposition, etc. as appropriate.

                                      Example
                                      <phr type="verb"
                                       function="extraposted_modifier">
                                      To talk
                                      <phr type="preposition"
                                        function="complement">
                                      of
                                       <phr type="nounfunction="object">many things</phr>
                                       </phr>
                                      </phr>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <phr>

                                      <phr> (phrase) represents a grammatical phrase. [17.1. Linguistic Segment Categories]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The type attribute may be used to indicate the type of phrase, taking values such as noun, verb, preposition, etc. as appropriate.

                                      Example
                                      <phr type="verb"
                                       function="extraposted_modifier">
                                      To talk
                                      <phr type="preposition"
                                        function="complement">
                                      of
                                       <phr type="nounfunction="object">many things</phr>
                                       </phr>
                                      </phr>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element phr
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.notated.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-physDesc.html b/gl/dev/ref-physDesc.html index d8c56a949..c54cbcab1 100644 --- a/gl/dev/ref-physDesc.html +++ b/gl/dev/ref-physDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <physDesc>

                                      <physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      Example
                                      <physDesc>
                                       <objectDesc form="codex">
                                        <supportDesc material="perg">
                                         <support>Parchment.</support>
                                         <extent>i + 55 leaves
                                         <dimensions scope="alltype="leaf"
                                           unit="inch">

                                           <height></height>
                                           <width>5⅜</width>
                                          </dimensions>
                                         </extent>
                                        </supportDesc>
                                        <layoutDesc>
                                         <layout columns="2">In double columns.</layout>
                                        </layoutDesc>
                                       </objectDesc>
                                       <handDesc>
                                        <p>Written in more than one hand.</p>
                                       </handDesc>
                                       <decoDesc>
                                        <p>With a few coloured capitals.</p>
                                       </decoDesc>
                                      </physDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.pLikeminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.physDescPart"
                                         expand="sequenceOptional"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <physDesc>

                                      <physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: msDesc msFrag msPart
                                      namesdates: object
                                      May contain
                                      Example
                                      <physDesc>
                                       <objectDesc form="codex">
                                        <supportDesc material="perg">
                                         <support>Parchment.</support>
                                         <extent>i + 55 leaves
                                         <dimensions scope="alltype="leaf"
                                           unit="inch">

                                           <height></height>
                                           <width>5⅜</width>
                                          </dimensions>
                                         </extent>
                                        </supportDesc>
                                        <layoutDesc>
                                         <layout columns="2">In double columns.</layout>
                                        </layoutDesc>
                                       </objectDesc>
                                       <handDesc>
                                        <p>Written in more than one hand.</p>
                                       </handDesc>
                                       <decoDesc>
                                        <p>With a few coloured capitals.</p>
                                       </decoDesc>
                                      </physDesc>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.pLikeminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.physDescPart"
                                         expand="sequenceOptional"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element physDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -38,4 +38,4 @@
                                             tei_sealDesc?,
                                             tei_accMat?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-place.html b/gl/dev/ref-place.html index 043ac08c5..3e24fb683 100644 --- a/gl/dev/ref-place.html +++ b/gl/dev/ref-place.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <place>

                                      <place> (place) contains data about a geographic location [13.3.4. Places]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      corpus: settingDesc
                                      namesdates: listPlace org place
                                      May contain
                                      Example
                                      <place>
                                       <country>Lithuania</country>
                                       <country xml:lang="lt">Lietuva</country>
                                       <place>
                                        <settlement>Vilnius</settlement>
                                       </place>
                                       <place>
                                        <settlement>Kaunas</settlement>
                                       </place>
                                      </place>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.labelLike"/>
                                          <classRef key="model.placeStateLike"/>
                                          <classRef key="model.eventLike"/>
                                          <elementRef key="name"/>
                                         </alternate>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="idno"/>
                                         <elementRef key="ptr"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.placeLike"/>
                                         <elementRef key="listPlace"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <place>

                                      <place> (place) contains data about a geographic location [13.3.4. Places]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) att.sortable (@sortKey)
                                      Member of
                                      Contained by
                                      corpus: settingDesc
                                      namesdates: listPlace org place
                                      May contain
                                      Example
                                      <place>
                                       <country>Lithuania</country>
                                       <country xml:lang="lt">Lietuva</country>
                                       <place>
                                        <settlement>Vilnius</settlement>
                                       </place>
                                       <place>
                                        <settlement>Kaunas</settlement>
                                       </place>
                                      </place>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.headLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <alternate>
                                         <classRef key="model.pLike"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.labelLike"/>
                                          <classRef key="model.placeStateLike"/>
                                          <classRef key="model.eventLike"/>
                                          <elementRef key="name"/>
                                         </alternate>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.noteLike"/>
                                         <classRef key="model.biblLike"/>
                                         <elementRef key="idno"/>
                                         <elementRef key="ptr"/>
                                         <elementRef key="linkGrp"/>
                                         <elementRef key="link"/>
                                        </alternate>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.placeLike"/>
                                         <elementRef key="listPlace"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element place
                                       {
                                          tei_att.global.attributes,
                                      @@ -49,4 +49,4 @@
                                             )*,
                                             ( tei_model.placeLike | tei_listPlace )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-placeName.html b/gl/dev/ref-placeName.html index 7d9b8fdd7..0f38e46b5 100644 --- a/gl/dev/ref-placeName.html +++ b/gl/dev/ref-placeName.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <placeName>

                                      <placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <settlement>Rochester</settlement>
                                       <region>New York</region>
                                      </placeName>
                                      Example
                                      <placeName>
                                       <geogName>Arrochar Alps</geogName>
                                       <region>Argylshire</region>
                                      </placeName>
                                      Example
                                      <placeName>
                                       <measure>10 miles</measure>
                                       <offset>Northeast of</offset>
                                       <settlement>Attica</settlement>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <placeName>

                                      <placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <settlement>Rochester</settlement>
                                       <region>New York</region>
                                      </placeName>
                                      Example
                                      <placeName>
                                       <geogName>Arrochar Alps</geogName>
                                       <region>Argylshire</region>
                                      </placeName>
                                      Example
                                      <placeName>
                                       <measure>10 miles</measure>
                                       <offset>Northeast of</offset>
                                       <settlement>Attica</settlement>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element placeName
                                       {
                                          tei_att.datable.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-postBox.html b/gl/dev/ref-postBox.html index 2ef7b06a3..1d6a9750b 100644 --- a/gl/dev/ref-postBox.html +++ b/gl/dev/ref-postBox.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <postBox>

                                      <postBox> (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May containCharacter data only
                                      Note

                                      The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

                                      Example
                                      <postBox>P.O. Box 280</postBox>
                                      Example
                                      <postBox>Postbus 532</postBox>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      -element postBox { tei_att.global.attributes, text }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <postBox>

                                      <postBox> (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May containCharacter data only
                                      Note

                                      The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

                                      Example
                                      <postBox>P.O. Box 280</postBox>
                                      Example
                                      <postBox>Postbus 532</postBox>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      +element postBox { tei_att.global.attributes, text }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-postCode.html b/gl/dev/ref-postCode.html index 6798312ba..cb30b14f6 100644 --- a/gl/dev/ref-postCode.html +++ b/gl/dev/ref-postCode.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <postCode>

                                      <postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May containCharacter data only
                                      Note

                                      The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

                                      Example
                                      <postCode>HR1 3LR</postCode>
                                      Example
                                      <postCode>60142-7</postCode>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      -element postCode { tei_att.global.attributes, text }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <postCode>

                                      <postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May containCharacter data only
                                      Note

                                      The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

                                      Example
                                      <postCode>HR1 3LR</postCode>
                                      Example
                                      <postCode>60142-7</postCode>
                                      Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Schema Declaration
                                      +element postCode { tei_att.global.attributes, text }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-precision.html b/gl/dev/ref-precision.html index 88eb6478e..c658783d9 100644 --- a/gl/dev/ref-precision.html +++ b/gl/dev/ref-precision.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <precision>

                                      <precision> indicates the numerical accuracy or precision associated with some aspect of the text markup. [21.2. Indications of Precision]
                                      Modulecertainty
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.scoping (@target, @match) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      precisioncharacterizes the precision of the element or attribute pointed to by the precision element.
                                      Status Optional
                                      Datatype teidata.certainty
                                      stdDeviationsupplies a standard deviation associated with the value in question
                                      Status Optional
                                      Datatype teidata.numeric
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example
                                      <date xml:id="date001notBefore="0014"
                                       notAfter="0064">
                                      Within about 50
                                      years of the death of Augustus</date>
                                      <precision target="#date001"
                                       match="@notBeforeprecision="high"/>

                                      <precision target="#date001"
                                       match="@notAfterprecision="low"/>
                                      Example
                                      <date notBefore="1632notAfter="1642">Not more than ten years before the start of the Civil War
                                      <precision match="@notBefore"
                                        precision="low"/>

                                       <precision match="@notAfter"
                                        precision="high"/>

                                      </date>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <precision>

                                      <precision> indicates the numerical accuracy or precision associated with some aspect of the text markup. [21.2. Indications of Precision]
                                      Modulecertainty
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.scoping (@target, @match) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      precisioncharacterizes the precision of the element or attribute pointed to by the precision element.
                                      Status Optional
                                      Datatype teidata.certainty
                                      stdDeviationsupplies a standard deviation associated with the value in question
                                      Status Optional
                                      Datatype teidata.numeric
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example
                                      <date xml:id="date001notBefore="0014"
                                       notAfter="0064">
                                      Within about 50
                                      years of the death of Augustus</date>
                                      <precision target="#date001"
                                       match="@notBeforeprecision="high"/>

                                      <precision target="#date001"
                                       match="@notAfterprecision="low"/>
                                      Example
                                      <date notBefore="1632notAfter="1642">Not more than ten years before the start of the Civil War
                                      <precision match="@notBefore"
                                        precision="low"/>

                                       <precision match="@notAfter"
                                        precision="high"/>

                                      </date>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element precision
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          attribute precision { teidata.certainty }?,
                                          attribute stdDeviation { teidata.numeric }?,
                                          ( tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-prefixDef.html b/gl/dev/ref-prefixDef.html index 91af08b1a..3964e637e 100644 --- a/gl/dev/ref-prefixDef.html +++ b/gl/dev/ref-prefixDef.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <prefixDef>

                                      <prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.patternReplacement (@matchPattern, @replacementPattern)
                                      identsupplies 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.
                                      Status Required
                                      Datatype teidata.prefix
                                      Note

                                      The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

                                      Example
                                      <prefixDef ident="ref"
                                       matchPattern="([a-z]+)"
                                       replacementPattern="../../references/references.xml#$1">

                                       <p> In the context of this project, private URIs with
                                         the prefix "ref" point to <gi>div</gi> elements in
                                         the project's global references.xml file.
                                       </p>
                                      </prefixDef>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <prefixDef>

                                      <prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.patternReplacement (@matchPattern, @replacementPattern)
                                      identsupplies 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.
                                      Status Required
                                      Datatype teidata.prefix
                                      Note

                                      The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

                                      Example
                                      <prefixDef ident="ref"
                                       matchPattern="([a-z]+)"
                                       replacementPattern="../../references/references.xml#$1">

                                       <p> In the context of this project, private URIs with
                                         the prefix "ref" point to <gi>div</gi> elements in
                                         the project's global references.xml file.
                                       </p>
                                      </prefixDef>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element prefixDef
                                       {
                                          tei_att.global.attributes,
                                          tei_att.patternReplacement.attributes,
                                          attribute ident { teidata.prefix },
                                          tei_model.pLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-principal.html b/gl/dev/ref-principal.html index 6e5a571d4..47366b50c 100644 --- a/gl/dev/ref-principal.html +++ b/gl/dev/ref-principal.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <principal>

                                      <principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msItem
                                      May contain
                                      Example
                                      <principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <principal>

                                      <principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      core: bibl
                                      msdescription: msItem
                                      May contain
                                      Example
                                      <principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element principal
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-profileDesc.html b/gl/dev/ref-profileDesc.html index 8a669d6ff..74cd7798f 100644 --- a/gl/dev/ref-profileDesc.html +++ b/gl/dev/ref-profileDesc.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <profileDesc>

                                      <profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts.

                                      Example
                                      <profileDesc>
                                       <langUsage>
                                        <language ident="fr">French</language>
                                       </langUsage>
                                       <textDesc n="novel">
                                        <channel mode="w">print; part issues</channel>
                                        <constitution type="single"/>
                                        <derivation type="original"/>
                                        <domain type="art"/>
                                        <factuality type="fiction"/>
                                        <interaction type="none"/>
                                        <preparedness type="prepared"/>
                                        <purpose type="entertaindegree="high"/>
                                        <purpose type="informdegree="medium"/>
                                       </textDesc>
                                       <settingDesc>
                                        <setting>
                                         <name>Paris, France</name>
                                         <time>Late 19th century</time>
                                        </setting>
                                       </settingDesc>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <classRef key="model.profileDescPart"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      -element profileDesc { tei_att.global.attributes, tei_model.profileDescPart* }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <profileDesc>

                                      <profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts.

                                      Example
                                      <profileDesc>
                                       <langUsage>
                                        <language ident="fr">French</language>
                                       </langUsage>
                                       <textDesc n="novel">
                                        <channel mode="w">print; part issues</channel>
                                        <constitution type="single"/>
                                        <derivation type="original"/>
                                        <domain type="art"/>
                                        <factuality type="fiction"/>
                                        <interaction type="none"/>
                                        <preparedness type="prepared"/>
                                        <purpose type="entertaindegree="high"/>
                                        <purpose type="informdegree="medium"/>
                                       </textDesc>
                                       <settingDesc>
                                        <setting>
                                         <name>Paris, France</name>
                                         <time>Late 19th century</time>
                                        </setting>
                                       </settingDesc>
                                      </profileDesc>
                                      Content model
                                      <content>
                                       <classRef key="model.profileDescPart"
                                        minOccurs="0maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +element profileDesc { tei_att.global.attributes, tei_model.profileDescPart* }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-projectDesc.html b/gl/dev/ref-projectDesc.html index 7f853700f..9e7b3dc49 100644 --- a/gl/dev/ref-projectDesc.html +++ b/gl/dev/ref-projectDesc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <projectDesc>

                                      <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <projectDesc>
                                       <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
                                      </projectDesc>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <projectDesc>

                                      <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <projectDesc>
                                       <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
                                      </projectDesc>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element projectDesc
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-provenance.html b/gl/dev/ref-provenance.html index cf80f8cc3..35d464d16 100644 --- a/gl/dev/ref-provenance.html +++ b/gl/dev/ref-provenance.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <provenance>

                                      <provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: history
                                      May contain
                                      Example
                                      <provenance>Listed as the property of Lawrence Sterne in 1788.</provenance>
                                      <provenance>Sold at Sothebys in 1899.</provenance>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <provenance>

                                      <provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
                                      Contained by
                                      msdescription: history
                                      May contain
                                      Example
                                      <provenance>Listed as the property of Lawrence Sterne in 1788.</provenance>
                                      <provenance>Sold at Sothebys in 1899.</provenance>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element provenance
                                       {
                                          tei_att.global.attributes,
                                          tei_att.datable.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-ptr.html b/gl/dev/ref-ptr.html index 477ad3951..e60418005 100644 --- a/gl/dev/ref-ptr.html +++ b/gl/dev/ref-ptr.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <ptr>

                                      <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
                                      Modulecore
                                      Attributesatt.cReferencing (@cRef) att.declaring (@decls) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <ptr target="#p143 #p144"/>
                                      <ptr target="http://www.tei-c.org"/>
                                      <ptr cRef="1.3.4"/>
                                      Schematron

                                      <s:report test="@target and @cRef">Only one of the
                                      attributes @target and @cRef may be supplied on <s:name/>.</s:report>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <ptr>

                                      <ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
                                      Modulecore
                                      Attributesatt.cReferencing (@cRef) att.declaring (@decls) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <ptr target="#p143 #p144"/>
                                      <ptr target="http://www.tei-c.org"/>
                                      <ptr cRef="1.3.4"/>
                                      Schematron

                                      <s:report test="@target and @cRef">Only one of the
                                      attributes @target and @cRef may be supplied on <s:name/>.</s:report>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element ptr
                                       {
                                          tei_att.cReferencing.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.pointing.attributes,
                                          tei_att.typed.attributes,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-pubPlace.html b/gl/dev/ref-pubPlace.html index 904b147b8..e11aee6c9 100644 --- a/gl/dev/ref-pubPlace.html +++ b/gl/dev/ref-pubPlace.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <pubPlace>

                                      <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      Member of
                                      Contained by
                                      textstructure: docImprint
                                      May contain
                                      Example
                                      <publicationStmt>
                                       <publisher>Oxford University Press</publisher>
                                       <pubPlace>Oxford</pubPlace>
                                       <date>1989</date>
                                      </publicationStmt>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <pubPlace>

                                      <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      Member of
                                      Contained by
                                      textstructure: docImprint
                                      May contain
                                      Example
                                      <publicationStmt>
                                       <publisher>Oxford University Press</publisher>
                                       <pubPlace>Oxford</pubPlace>
                                       <date>1989</date>
                                      </publicationStmt>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element pubPlace
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-publicationStmt.html b/gl/dev/ref-publicationStmt.html index 67c7ba658..6cabaf14a 100644 --- a/gl/dev/ref-publicationStmt.html +++ b/gl/dev/ref-publicationStmt.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <publicationStmt>

                                      <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

                                      Example
                                      <publicationStmt>
                                       <publisher>C. Muquardt </publisher>
                                       <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
                                       <date when="1846"/>
                                      </publicationStmt>
                                      Example
                                      <publicationStmt>
                                       <publisher>Chadwyck Healey</publisher>
                                       <pubPlace>Cambridge</pubPlace>
                                       <availability>
                                        <p>Available under licence only</p>
                                       </availability>
                                       <date when="1992">1992</date>
                                      </publicationStmt>
                                      Example
                                      <publicationStmt>
                                       <publisher>Zea Books</publisher>
                                       <pubPlace>Lincoln, NE</pubPlace>
                                       <date>2017</date>
                                       <availability>
                                        <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
                                       </availability>
                                       <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
                                      </publicationStmt>
                                      Content model
                                      <content>
                                       <alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.publicationStmtPart.agency"/>
                                         <classRef key="model.publicationStmtPart.detail"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <publicationStmt>

                                      <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

                                      Example
                                      <publicationStmt>
                                       <publisher>C. Muquardt </publisher>
                                       <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
                                       <date when="1846"/>
                                      </publicationStmt>
                                      Example
                                      <publicationStmt>
                                       <publisher>Chadwyck Healey</publisher>
                                       <pubPlace>Cambridge</pubPlace>
                                       <availability>
                                        <p>Available under licence only</p>
                                       </availability>
                                       <date when="1992">1992</date>
                                      </publicationStmt>
                                      Example
                                      <publicationStmt>
                                       <publisher>Zea Books</publisher>
                                       <pubPlace>Lincoln, NE</pubPlace>
                                       <date>2017</date>
                                       <availability>
                                        <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
                                       </availability>
                                       <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
                                      </publicationStmt>
                                      Content model
                                      <content>
                                       <alternate>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.publicationStmtPart.agency"/>
                                         <classRef key="model.publicationStmtPart.detail"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element publicationStmt
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                             )+
                                           | tei_model.pLike+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-publisher.html b/gl/dev/ref-publisher.html index e3c0a07f4..0d1730f40 100644 --- a/gl/dev/ref-publisher.html +++ b/gl/dev/ref-publisher.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <publisher>

                                      <publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      textstructure: docImprint
                                      May contain
                                      Note

                                      Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

                                      Example
                                      <imprint>
                                       <pubPlace>Oxford</pubPlace>
                                       <publisher>Clarendon Press</publisher>
                                       <date>1987</date>
                                      </imprint>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <publisher>

                                      <publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      textstructure: docImprint
                                      May contain
                                      Note

                                      Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

                                      Example
                                      <imprint>
                                       <pubPlace>Oxford</pubPlace>
                                       <publisher>Clarendon Press</publisher>
                                       <date>1987</date>
                                      </imprint>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element publisher
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-punctuation.html b/gl/dev/ref-punctuation.html index 3d93d9783..306ed0647 100644 --- a/gl/dev/ref-punctuation.html +++ b/gl/dev/ref-punctuation.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <punctuation>

                                      <punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
                                      Moduleheader
                                      Attributesatt.declarable (@default) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      marksindicates whether or not punctation marks have been retained as content within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      none
                                      no punctuation marks have been retained
                                      some
                                      some punctuation marks have been retained
                                      all
                                      all punctuation marks have been retained
                                      placementindicates 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.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      internal
                                      punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
                                      external
                                      punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <punctuation marks="all"
                                       placement="internal">

                                       <p>All punctuation marks in the source text have been retained and represented using the
                                         appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey
                                         the same information (for example, a sentence ends with a question mark and is also tagged
                                         as <gi>s</gi>) the punctuation mark is captured as content within the element.</p>
                                      </punctuation>
                                      Example

                                      External placement of punctuation:

                                      <p>I would agree with Saint Augustine that “<quote>An unjust law is no law at all</quote>.”</p>
                                      Example

                                      Internal placement of punctuation:

                                      <p>I would agree with Saint Augustine that <quote>“An unjust law is no law at all.”</quote>
                                      </p>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <punctuation>

                                      <punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
                                      Moduleheader
                                      Attributesatt.declarable (@default) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      marksindicates whether or not punctation marks have been retained as content within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      none
                                      no punctuation marks have been retained
                                      some
                                      some punctuation marks have been retained
                                      all
                                      all punctuation marks have been retained
                                      placementindicates 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.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      internal
                                      punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
                                      external
                                      punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <punctuation marks="all"
                                       placement="internal">

                                       <p>All punctuation marks in the source text have been retained and represented using the
                                         appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey
                                         the same information (for example, a sentence ends with a question mark and is also tagged
                                         as <gi>s</gi>) the punctuation mark is captured as content within the element.</p>
                                      </punctuation>
                                      Example

                                      External placement of punctuation:

                                      <p>I would agree with Saint Augustine that “<quote>An unjust law is no law at all</quote>.”</p>
                                      Example

                                      Internal placement of punctuation:

                                      <p>I would agree with Saint Augustine that <quote>“An unjust law is no law at all.”</quote>
                                      </p>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element punctuation
                                       {
                                          tei_att.declarable.attributes,
                                      @@ -29,4 +29,4 @@
                                          attribute marks { "none" | "some" | "all" }?,
                                          attribute placement { "internal" | "external" }?,
                                          tei_model.pLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-q.html b/gl/dev/ref-q.html index 3e662c88c..52c4bc561 100644 --- a/gl/dev/ref-q.html +++ b/gl/dev/ref-q.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <q>

                                      <q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
                                      type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      spoken
                                      (spoken) representation of speech
                                      thought
                                      (thought) representation of thought, e.g. internal monologue
                                      written
                                      (written) quotation from a written source
                                      soCalled
                                      (so called) authorial distance
                                      foreign
                                      (foreign)
                                      distinct
                                      (distinct) linguistically distinct
                                      term
                                      technical term
                                      emph
                                      (emph) rhetorically emphasized
                                      mentioned
                                      (mentioned) refering to itself, not its normal referent
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, q may be thought of as syntactic sugar for hi with a value of rend that indicates the use of such mechanisms as quotation marks.

                                      Example
                                      It is spelled <q>Tübingen</q> — to enter the
                                      letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
                                      <q>0 0 f c</q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <q>

                                      <q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
                                      type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      spoken
                                      (spoken) representation of speech
                                      thought
                                      (thought) representation of thought, e.g. internal monologue
                                      written
                                      (written) quotation from a written source
                                      soCalled
                                      (so called) authorial distance
                                      foreign
                                      (foreign)
                                      distinct
                                      (distinct) linguistically distinct
                                      term
                                      technical term
                                      emph
                                      (emph) rhetorically emphasized
                                      mentioned
                                      (mentioned) refering to itself, not its normal referent
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, q may be thought of as syntactic sugar for hi with a value of rend that indicates the use of such mechanisms as quotation marks.

                                      Example
                                      It is spelled <q>Tübingen</q> — to enter the
                                      letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
                                      <q>0 0 f c</q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element q
                                       {
                                          tei_att.global.attributes,
                                      @@ -40,4 +40,4 @@
                                           | teidata.enumerated
                                          }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-quotation.html b/gl/dev/ref-quotation.html index ebeaf4b4c..a2d9f1cef 100644 --- a/gl/dev/ref-quotation.html +++ b/gl/dev/ref-quotation.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <quotation>

                                      <quotation> (quotation) specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      none
                                      no quotation marks have been retained
                                      some
                                      some quotation marks have been retained
                                      all
                                      all quotation marks have been retained
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <quotation marks="none">
                                       <p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the
                                       <gi>q</gi> element is used to specify what kinds of quotation mark was used, according
                                         to the following list: <list type="gloss">
                                         <label>dq</label>
                                         <item>double quotes, open and close</item>
                                         <label>sq</label>
                                         <item>single quotes, open and close</item>
                                         <label>dash</label>
                                         <item>long dash open, no close</item>
                                         <label>dg</label>
                                         <item>double guillemets, open and close</item>
                                        </list>
                                       </p>
                                      </quotation>
                                      Example
                                      <quotation marks="all">
                                       <p>All quotation marks are retained in the text and are represented by appropriate Unicode
                                         characters.</p>
                                      </quotation>
                                      Schematron

                                      <s:report test="not(@marks) and not (tei:p)">On <s:name/>, either the @marks attribute should be used, or a paragraph of description provided</s:report>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <quotation>

                                      <quotation> (quotation) specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      none
                                      no quotation marks have been retained
                                      some
                                      some quotation marks have been retained
                                      all
                                      all quotation marks have been retained
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <quotation marks="none">
                                       <p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the
                                       <gi>q</gi> element is used to specify what kinds of quotation mark was used, according
                                         to the following list: <list type="gloss">
                                         <label>dq</label>
                                         <item>double quotes, open and close</item>
                                         <label>sq</label>
                                         <item>single quotes, open and close</item>
                                         <label>dash</label>
                                         <item>long dash open, no close</item>
                                         <label>dg</label>
                                         <item>double guillemets, open and close</item>
                                        </list>
                                       </p>
                                      </quotation>
                                      Example
                                      <quotation marks="all">
                                       <p>All quotation marks are retained in the text and are represented by appropriate Unicode
                                         characters.</p>
                                      </quotation>
                                      Schematron

                                      <s:report test="not(@marks) and not (tei:p)">On <s:name/>, either the @marks attribute should be used, or a paragraph of description provided</s:report>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element quotation
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          attribute marks { "none" | "some" | "all" }?,
                                          tei_model.pLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-quote.html b/gl/dev/ref-quote.html index 8870f1f73..0aec1f7fe 100644 --- a/gl/dev/ref-quote.html +++ b/gl/dev/ref-quote.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <quote>

                                      <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the cit element.

                                      Example
                                      Lexicography has shown little sign of being affected by the
                                      work of followers of J.R. Firth, probably best summarized in his
                                      slogan, <quote>You shall know a word by the company it
                                      keeps</quote>
                                      <ref>(Firth, 1957)</ref>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <quote>

                                      <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the cit element.

                                      Example
                                      Lexicography has shown little sign of being affected by the
                                      work of followers of J.R. Firth, probably best summarized in his
                                      slogan, <quote>You shall know a word by the company it
                                      keeps</quote>
                                      <ref>(Firth, 1957)</ref>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element quote
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.msExcerpt.attributes,
                                          tei_att.notated.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rb.html b/gl/dev/ref-rb.html index ea303a4a8..dd49ab6c8 100644 --- a/gl/dev/ref-rb.html +++ b/gl/dev/ref-rb.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rb>

                                      <rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      core: ruby
                                      May contain
                                      Example

                                      The word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.

                                      <p xml:lang="zh">
                                      <!--...-->
                                       <ruby>
                                        <rb></rb>
                                        <rt place="above"></rt>
                                       </ruby>
                                       <ruby>
                                        <rb></rb>
                                        <rt place="above">hǎo</rt>
                                       </ruby>
                                      <!--...-->
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rb>

                                      <rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Contained by
                                      core: ruby
                                      May contain
                                      Example

                                      The word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.

                                      <p xml:lang="zh">
                                      <!--...-->
                                       <ruby>
                                        <rb></rb>
                                        <rt place="above"></rt>
                                       </ruby>
                                       <ruby>
                                        <rb></rb>
                                        <rt place="above">hǎo</rt>
                                       </ruby>
                                      <!--...-->
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element rb
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rdg.html b/gl/dev/ref-rdg.html index 83c0064d5..2c7fe8e25 100644 --- a/gl/dev/ref-rdg.html +++ b/gl/dev/ref-rdg.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rdg>

                                      <rdg> (reading) contains a single reading within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.textCritical (@type, @cause, @varSeq, @require) (att.written (@hand)) att.witnessed (@wit)
                                      Member of
                                      Contained by
                                      textcrit: app rdgGrp
                                      May contain
                                      Example
                                      <rdg wit="#Ra2">Eryment</rdg>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.divLike"/>
                                        <classRef key="model.divPart"/>
                                        <elementRef key="titlePage"/>
                                        <elementRef key="argument"/>
                                        <elementRef key="byline"/>
                                        <elementRef key="docAuthor"/>
                                        <elementRef key="docDate"/>
                                        <elementRef key="docEdition"/>
                                        <elementRef key="docImprint"/>
                                        <elementRef key="docTitle"/>
                                        <elementRef key="epigraph"/>
                                        <elementRef key="imprimatur"/>
                                        <elementRef key="titlePart"/>
                                        <elementRef key="epilogue"/>
                                        <elementRef key="performance"/>
                                        <elementRef key="prologue"/>
                                        <elementRef key="set"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.rdgPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rdg>

                                      <rdg> (reading) contains a single reading within a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.textCritical (@type, @cause, @varSeq, @require) (att.written (@hand)) att.witnessed (@wit)
                                      Member of
                                      Contained by
                                      textcrit: app rdgGrp
                                      May contain
                                      Example
                                      <rdg wit="#Ra2">Eryment</rdg>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.divLike"/>
                                        <classRef key="model.divPart"/>
                                        <elementRef key="titlePage"/>
                                        <elementRef key="argument"/>
                                        <elementRef key="byline"/>
                                        <elementRef key="docAuthor"/>
                                        <elementRef key="docDate"/>
                                        <elementRef key="docEdition"/>
                                        <elementRef key="docImprint"/>
                                        <elementRef key="docTitle"/>
                                        <elementRef key="epigraph"/>
                                        <elementRef key="imprimatur"/>
                                        <elementRef key="titlePart"/>
                                        <elementRef key="epilogue"/>
                                        <elementRef key="performance"/>
                                        <elementRef key="prologue"/>
                                        <elementRef key="set"/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.inter"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.rdgPart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element rdg
                                       {
                                          tei_att.global.attributes,
                                      @@ -52,4 +52,4 @@
                                           | tei_model.global
                                           | tei_model.rdgPart
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rdgGrp.html b/gl/dev/ref-rdgGrp.html index 75541a7fd..ee44e09a1 100644 --- a/gl/dev/ref-rdgGrp.html +++ b/gl/dev/ref-rdgGrp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rdgGrp>

                                      <rdgGrp> (reading group) within a textual variation, groups two or more readings perceived to have a genetic relationship or other affinity. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.textCritical (@type, @cause, @varSeq, @require) (att.written (@hand))
                                      Contained by
                                      textcrit: app rdgGrp
                                      May contain
                                      textcrit: lem rdg rdgGrp wit
                                      Note

                                      May contain readings and nested reading groups.

                                      Usually, only one lem element should appear within a single apparatus entry, whether it appears outside a rdgGrp element or within it.

                                      Example
                                      <app>
                                       <lem wit="#El #Ra2">though</lem>
                                       <rdgGrp type="orthographic">
                                        <rdg wit="#Hg">thogh</rdg>
                                        <rdg wit="#La">thouhe</rdg>
                                       </rdgGrp>
                                      </app>
                                      Schematron

                                      <sch:assert test="count(tei:lem) < 2">Only one <lem> element may appear within a <rdgGrp></sch:assert>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="lemminOccurs="0"/>
                                        <alternate maxOccurs="unbounded"
                                         minOccurs="0">

                                         <classRef key="model.rdgLike"/>
                                         <classRef key="model.noteLike"/>
                                         <elementRef key="witDetail"/>
                                         <elementRef key="wit"/>
                                         <elementRef key="rdgGrp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rdgGrp>

                                      <rdgGrp> (reading group) within a textual variation, groups two or more readings perceived to have a genetic relationship or other affinity. [12.1. The Apparatus Entry, Readings, and Witnesses]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.textCritical (@type, @cause, @varSeq, @require) (att.written (@hand))
                                      Contained by
                                      textcrit: app rdgGrp
                                      May contain
                                      textcrit: lem rdg rdgGrp wit
                                      Note

                                      May contain readings and nested reading groups.

                                      Usually, only one lem element should appear within a single apparatus entry, whether it appears outside a rdgGrp element or within it.

                                      Example
                                      <app>
                                       <lem wit="#El #Ra2">though</lem>
                                       <rdgGrp type="orthographic">
                                        <rdg wit="#Hg">thogh</rdg>
                                        <rdg wit="#La">thouhe</rdg>
                                       </rdgGrp>
                                      </app>
                                      Schematron

                                      <sch:assert test="count(tei:lem) < 2">Only one <lem> element may appear within a <rdgGrp></sch:assert>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="lemminOccurs="0"/>
                                        <alternate maxOccurs="unbounded"
                                         minOccurs="0">

                                         <classRef key="model.rdgLike"/>
                                         <classRef key="model.noteLike"/>
                                         <elementRef key="witDetail"/>
                                         <elementRef key="wit"/>
                                         <elementRef key="rdgGrp"/>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element rdgGrp
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                              | tei_rdgGrp
                                             )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-recordHist.html b/gl/dev/ref-recordHist.html index df7749ec6..d8360e526 100644 --- a/gl/dev/ref-recordHist.html +++ b/gl/dev/ref-recordHist.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <recordHist>

                                      <recordHist> (recorded history) provides information about the source and revision status of the parent manuscript or object description itself. [10.9.1. Administrative Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: adminInfo
                                      May contain
                                      core: p
                                      header: change
                                      linking: ab
                                      msdescription: source
                                      Example
                                      <recordHist>
                                       <source>
                                        <p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research
                                           by P.M.W.Robinson</p>
                                       </source>
                                       <change when="1999-06-23">
                                        <name>LDB</name> (editor)
                                         checked examples against DTD version 3.6
                                       </change>
                                      </recordHist>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="source"/>
                                         <elementRef key="changeminOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <recordHist>

                                      <recordHist> (recorded history) provides information about the source and revision status of the parent manuscript or object description itself. [10.9.1. Administrative Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: adminInfo
                                      May contain
                                      core: p
                                      header: change
                                      linking: ab
                                      msdescription: source
                                      Example
                                      <recordHist>
                                       <source>
                                        <p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research
                                           by P.M.W.Robinson</p>
                                       </source>
                                       <change when="1999-06-23">
                                        <name>LDB</name> (editor)
                                         checked examples against DTD version 3.6
                                       </change>
                                      </recordHist>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="source"/>
                                         <elementRef key="changeminOccurs="0"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element recordHist
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | ( tei_source, tei_change* ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-redo.html b/gl/dev/ref-redo.html index 0e393f713..89e3b5cef 100644 --- a/gl/dev/ref-redo.html +++ b/gl/dev/ref-redo.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <redo>

                                      <redo> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.spanning (@spanTo) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      targetpoints to one or more elements representing the interventions which are being reasserted.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <line>
                                       <redo hand="#g_ttarget="#redo-1"
                                        cause="fix"/>

                                       <mod xml:id="redo-1rend="strikethrough"
                                        spanTo="#anchor-1hand="#g_bl"/>
                                      Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken
                                      </line>
                                      <line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/>
                                      </line>

                                      This encoding represents the following sequence of events:

                                      • "Ihr hagren, triſten, krummgezog nenener Nacken/ Wenn ihr nur piepſet iſt die Welt ſchon matt." is written
                                      • the redundant letters "nen" in "nenener" are deleted
                                      • the whole passage is deleted by hand g_bl using strikethrough
                                      • the deletion is reasserted by another hand (identified here as g_t)
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <redo>

                                      <redo> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.spanning (@spanTo) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      targetpoints to one or more elements representing the interventions which are being reasserted.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <line>
                                       <redo hand="#g_ttarget="#redo-1"
                                        cause="fix"/>

                                       <mod xml:id="redo-1rend="strikethrough"
                                        spanTo="#anchor-1hand="#g_bl"/>
                                      Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken
                                      </line>
                                      <line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/>
                                      </line>

                                      This encoding represents the following sequence of events:

                                      • "Ihr hagren, triſten, krummgezog nenener Nacken/ Wenn ihr nur piepſet iſt die Welt ſchon matt." is written
                                      • the redundant letters "nen" in "nenener" are deleted
                                      • the whole passage is deleted by hand g_bl using strikethrough
                                      • the deletion is reasserted by another hand (identified here as g_t)
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element redo
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.dimensions.attributes,
                                          attribute target { list { teidata.pointer+ } }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-ref.html b/gl/dev/ref-ref.html index dcbad0107..d8e37f7bf 100644 --- a/gl/dev/ref-ref.html +++ b/gl/dev/ref-ref.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <ref>

                                      <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
                                      Modulecore
                                      Attributesatt.cReferencing (@cRef) att.declaring (@decls) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The target and cRef attributes are mutually exclusive.

                                      Example
                                      See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
                                      sentence</ref>
                                      Example
                                      See also <ref target="#locution">s.v. <term>locution</term>
                                      </ref>.
                                      Schematron

                                      <s:report test="@target and @cRef">Only one of the
                                      attributes @target' and @cRef' may be supplied on <s:name/>
                                      </s:report>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <ref>

                                      <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
                                      Modulecore
                                      Attributesatt.cReferencing (@cRef) att.declaring (@decls) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The target and cRef attributes are mutually exclusive.

                                      Example
                                      See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
                                      sentence</ref>
                                      Example
                                      See also <ref target="#locution">s.v. <term>locution</term>
                                      </ref>.
                                      Schematron

                                      <s:report test="@target and @cRef">Only one of the
                                      attributes @target' and @cRef' may be supplied on <s:name/>
                                      </s:report>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element ref
                                       {
                                          tei_att.cReferencing.attributes,
                                      @@ -31,4 +31,4 @@
                                          tei_att.pointing.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-refState.html b/gl/dev/ref-refState.html index d20a271a5..ba404047b 100644 --- a/gl/dev/ref-refState.html +++ b/gl/dev/ref-refState.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <refState>

                                      <refState> (reference state) specifies one component of a canonical reference defined by the milestone method. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.milestoneUnit (@unit) att.edition (@ed, @edRef)
                                      lengthspecifies the fixed length of the reference component.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      When constructing a reference, if the reference component found is of numeric type, the length is made up by inserting leading zeros; if it is not, by inserting trailing blanks. In either case, reference components are truncated if necessary at the right hand side.

                                      When seeking a reference, the length indicates the number of characters which should be compared. Values longer than this will be regarded as matching, if they start correctly. If no value is provided, the length is unlimited and goes to the next delimiter or to the end of the value.

                                      delim(delimiter) supplies a delimiting string following the reference component.
                                      Status Optional
                                      Datatype teidata.text
                                      Contained by
                                      header: refsDecl
                                      May containEmpty element
                                      Example
                                      <refState unit="bookdelim=":"/>
                                      <refState unit="linelength="4"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <refState>

                                      <refState> (reference state) specifies one component of a canonical reference defined by the milestone method. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.milestoneUnit (@unit) att.edition (@ed, @edRef)
                                      lengthspecifies the fixed length of the reference component.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      When constructing a reference, if the reference component found is of numeric type, the length is made up by inserting leading zeros; if it is not, by inserting trailing blanks. In either case, reference components are truncated if necessary at the right hand side.

                                      When seeking a reference, the length indicates the number of characters which should be compared. Values longer than this will be regarded as matching, if they start correctly. If no value is provided, the length is unlimited and goes to the next delimiter or to the end of the value.

                                      delim(delimiter) supplies a delimiting string following the reference component.
                                      Status Optional
                                      Datatype teidata.text
                                      Contained by
                                      header: refsDecl
                                      May containEmpty element
                                      Example
                                      <refState unit="bookdelim=":"/>
                                      <refState unit="linelength="4"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element refState
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute length { teidata.count }?,
                                          attribute delim { teidata.text }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-refsDecl.html b/gl/dev/ref-refsDecl.html index 18971db1b..8657ce60e 100644 --- a/gl/dev/ref-refsDecl.html +++ b/gl/dev/ref-refsDecl.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <refsDecl>

                                      <refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <refsDecl>
                                       <cRefPattern matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"
                                        replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/>

                                      </refsDecl>

                                      This example is a formal representation for the referencing scheme described informally in the following example.

                                      Example
                                      <refsDecl>
                                       <p>References are made up by concatenating the value for the
                                       <att>n</att> attribute on the highest level <gi>div</gi>
                                         element, followed by a space, followed by the sequential
                                         number of the next level <gi>div</gi> followed by a colon
                                         followed by the sequential number of the next (and lowest)
                                         level <gi>div</gi>.</p>
                                      </refsDecl>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="citeStructure"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <elementRef key="cRefPattern"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <elementRef key="refStateminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <refsDecl>

                                      <refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <refsDecl>
                                       <cRefPattern matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"
                                        replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/>

                                      </refsDecl>

                                      This example is a formal representation for the referencing scheme described informally in the following example.

                                      Example
                                      <refsDecl>
                                       <p>References are made up by concatenating the value for the
                                       <att>n</att> attribute on the highest level <gi>div</gi>
                                         element, followed by a space, followed by the sequential
                                         number of the next level <gi>div</gi> followed by a colon
                                         followed by the sequential number of the next (and lowest)
                                         level <gi>div</gi>.</p>
                                      </refsDecl>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="citeStructure"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <elementRef key="cRefPattern"
                                         minOccurs="1maxOccurs="unbounded"/>

                                        <elementRef key="refStateminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element refsDecl
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          ( tei_model.pLike+ | tei_citeStructure+ | tei_cRefPattern+ | tei_refState+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-reg.html b/gl/dev/ref-reg.html index e46c1e631..bbf71a264 100644 --- a/gl/dev/ref-reg.html +++ b/gl/dev/ref-reg.html @@ -22,11 +22,11 @@ }); });

                                      <reg>

                                      <reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and -Normalization 12. Critical Apparatus]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      If all that is desired is to call attention to the fact that the copy text has been regularized, reg may be used alone:

                                      <q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
                                      </q>
                                      Example

                                      It is also possible to identify the individual responsible for the regularization, and, using the choice and orig elements, to provide both the original and regularized readings:

                                      <q>Please <choice>
                                        <reg resp="#LB">knock</reg>
                                        <orig>cnk</orig>
                                       </choice> if an <choice>
                                        <reg>answer</reg>
                                        <orig>nsr</orig>
                                       </choice> is <choice>
                                        <reg>required</reg>
                                        <orig>reqd</orig>
                                       </choice>
                                      </q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +Normalization 12. Critical Apparatus]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      If all that is desired is to call attention to the fact that the copy text has been regularized, reg may be used alone:

                                      <q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
                                      </q>
                                      Example

                                      It is also possible to identify the individual responsible for the regularization, and, using the choice and orig elements, to provide both the original and regularized readings:

                                      <q>Please <choice>
                                        <reg resp="#LB">knock</reg>
                                        <orig>cnk</orig>
                                       </choice> if an <choice>
                                        <reg>answer</reg>
                                        <orig>nsr</orig>
                                       </choice> is <choice>
                                        <reg>required</reg>
                                        <orig>reqd</orig>
                                       </choice>
                                      </q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element reg
                                       {
                                          tei_att.global.attributes,
                                          tei_att.editLike.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-region.html b/gl/dev/ref-region.html index 9dddfc173..16d988141 100644 --- a/gl/dev/ref-region.html +++ b/gl/dev/ref-region.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <region>

                                      <region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <region type="staten="IL">Illinois</region>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <region>

                                      <region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <region type="staten="IL">Illinois</region>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element region
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-relatedItem.html b/gl/dev/ref-relatedItem.html index 205c09ec8..828aefe4f 100644 --- a/gl/dev/ref-relatedItem.html +++ b/gl/dev/ref-relatedItem.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <relatedItem>

                                      <relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      targetpoints to the related bibliographic element by means of an absolute or relative URI reference
                                      Status Optional
                                      Datatype teidata.pointer
                                      Member of
                                      Contained by
                                      May contain
                                      header: biblFull
                                      msdescription: msDesc
                                      Note

                                      If the target attribute is used to reference the related bibliographic item, the element must be empty.

                                      Example
                                      <biblStruct>
                                       <monogr>
                                        <author>Shirley, James</author>
                                        <title type="main">The gentlemen of Venice</title>
                                        <imprint>
                                         <pubPlace>New York</pubPlace>
                                         <publisher>Readex Microprint</publisher>
                                         <date>1953</date>
                                        </imprint>
                                        <extent>1 microprint card, 23 x 15 cm.</extent>
                                       </monogr>
                                       <series>
                                        <title>Three centuries of drama: English, 1642–1700</title>
                                       </series>
                                       <relatedItem type="otherForm">
                                        <biblStruct>
                                         <monogr>
                                          <author>Shirley, James</author>
                                          <title type="main">The gentlemen of Venice</title>
                                          <title type="sub">a tragi-comedie presented at the private house in Salisbury
                                               Court by Her Majesties servants</title>
                                          <imprint>
                                           <pubPlace>London</pubPlace>
                                           <publisher>H. Moseley</publisher>
                                           <date>1655</date>
                                          </imprint>
                                          <extent>78 p.</extent>
                                         </monogr>
                                        </biblStruct>
                                       </relatedItem>
                                      </biblStruct>
                                      Schematron

                                      <sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the
                                      relatedItem element must be empty</sch:report>
                                      <sch:assert test="@target or child::*">A relatedItem element should have either a 'target' attribute
                                      or a child element to indicate the related bibliographic item</sch:assert>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0">
                                        <classRef key="model.biblLike"/>
                                        <classRef key="model.ptrLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <relatedItem>

                                      <relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      targetpoints to the related bibliographic element by means of an absolute or relative URI reference
                                      Status Optional
                                      Datatype teidata.pointer
                                      Member of
                                      Contained by
                                      May contain
                                      header: biblFull
                                      msdescription: msDesc
                                      Note

                                      If the target attribute is used to reference the related bibliographic item, the element must be empty.

                                      Example
                                      <biblStruct>
                                       <monogr>
                                        <author>Shirley, James</author>
                                        <title type="main">The gentlemen of Venice</title>
                                        <imprint>
                                         <pubPlace>New York</pubPlace>
                                         <publisher>Readex Microprint</publisher>
                                         <date>1953</date>
                                        </imprint>
                                        <extent>1 microprint card, 23 x 15 cm.</extent>
                                       </monogr>
                                       <series>
                                        <title>Three centuries of drama: English, 1642–1700</title>
                                       </series>
                                       <relatedItem type="otherForm">
                                        <biblStruct>
                                         <monogr>
                                          <author>Shirley, James</author>
                                          <title type="main">The gentlemen of Venice</title>
                                          <title type="sub">a tragi-comedie presented at the private house in Salisbury
                                               Court by Her Majesties servants</title>
                                          <imprint>
                                           <pubPlace>London</pubPlace>
                                           <publisher>H. Moseley</publisher>
                                           <date>1655</date>
                                          </imprint>
                                          <extent>78 p.</extent>
                                         </monogr>
                                        </biblStruct>
                                       </relatedItem>
                                      </biblStruct>
                                      Schematron

                                      <sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the
                                      relatedItem element must be empty</sch:report>
                                      <sch:assert test="@target or child::*">A relatedItem element should have either a 'target' attribute
                                      or a child element to indicate the related bibliographic item</sch:assert>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0">
                                        <classRef key="model.biblLike"/>
                                        <classRef key="model.ptrLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element relatedItem
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          attribute target { teidata.pointer }?,
                                          ( tei_model.biblLike | tei_model.ptrLike )?
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-relation.html b/gl/dev/ref-relation.html index d2e92d036..8f735d5f6 100644 --- a/gl/dev/ref-relation.html +++ b/gl/dev/ref-relation.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <relation>

                                      <relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.canonical (@key, @ref) att.sortable (@sortKey) att.typed (@type, @subtype)
                                      namesupplies a name for the kind of relationship of which this is an instance.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      mutualsupplies a list of participants amongst all of whom the relationship holds equally.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      passiveidentifies the ‘passive’ participants in a non-mutual relationship.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.

                                      Example
                                      <relation type="socialname="supervisor"
                                       active="#p1passive="#p2 #p3 #p4"/>

                                      This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.

                                      Example
                                      <relation type="personalname="friends"
                                       mutual="#p2 #p3 #p4"/>

                                      This indicates that p2, p3, and p4 are all friends.

                                      Example
                                      <relation type="CRM"
                                       name="P89_falls_within"
                                       active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"
                                       passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>

                                      This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.

                                      Example
                                      <relation resp="http://viaf.org/viaf/44335536/"
                                       ref="http://purl.org/saws/ontology#isVariantOf"
                                       active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"
                                       passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>

                                      This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).

                                      Schematron

                                      <s:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</s:assert>
                                      Schematron

                                      <s:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</s:report>
                                      Schematron

                                      <s:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</s:report>
                                      Content model
                                      <content>
                                       <elementRef key="descminOccurs="0"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <relation>

                                      <relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.canonical (@key, @ref) att.sortable (@sortKey) att.typed (@type, @subtype)
                                      namesupplies a name for the kind of relationship of which this is an instance.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      mutualsupplies a list of participants amongst all of whom the relationship holds equally.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      passiveidentifies the ‘passive’ participants in a non-mutual relationship.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Contained by
                                      May contain
                                      core: desc
                                      Note

                                      Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.

                                      Example
                                      <relation type="socialname="supervisor"
                                       active="#p1passive="#p2 #p3 #p4"/>

                                      This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.

                                      Example
                                      <relation type="personalname="friends"
                                       mutual="#p2 #p3 #p4"/>

                                      This indicates that p2, p3, and p4 are all friends.

                                      Example
                                      <relation type="CRM"
                                       name="P89_falls_within"
                                       active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"
                                       passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>

                                      This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.

                                      Example
                                      <relation resp="http://viaf.org/viaf/44335536/"
                                       ref="http://purl.org/saws/ontology#isVariantOf"
                                       active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"
                                       passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>

                                      This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).

                                      Schematron

                                      <s:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</s:assert>
                                      Schematron

                                      <s:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</s:report>
                                      Schematron

                                      <s:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</s:report>
                                      Content model
                                      <content>
                                       <elementRef key="descminOccurs="0"/>
                                      </content>
                                      Schema Declaration
                                       element relation
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                          ),
                                          attribute passive { list { teidata.pointer+ } }?,
                                          tei_desc?
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rendition.html b/gl/dev/ref-rendition.html index 7f6d78235..a5e8592b4 100644 --- a/gl/dev/ref-rendition.html +++ b/gl/dev/ref-rendition.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rendition>

                                      <rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.styleDef (@scheme, @schemeVersion)
                                      scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      first-line
                                      styling applies to the first line of the target element
                                      first-letter
                                      styling applies to the first letter of the target element
                                      before
                                      styling should be applied immediately before the content of the target element
                                      after
                                      styling should be applied immediately after the content of the target element
                                      selectorcontains 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.
                                      Status Optional
                                      Datatype teidata.text
                                      <rendition scheme="css"
                                       selector="text, front, back, body, div, p, ab">

                                      display: block;
                                      </rendition>
                                      <rendition scheme="css"
                                       selector="*[rend*=italic]">
                                      font-style: italic;
                                      </rendition>
                                      Note

                                      Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.

                                      While rendition is used to point from an element in the transcribed source to a rendition element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a rendition in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

                                      Contained by
                                      header: tagsDecl
                                      May contain
                                      Example
                                      <tagsDecl>
                                       <rendition xml:id="r-centerscheme="css">text-align: center;</rendition>
                                       <rendition xml:id="r-smallscheme="css">font-size: small;</rendition>
                                       <rendition xml:id="r-largescheme="css">font-size: large;</rendition>
                                       <rendition xml:id="initcaps"
                                        scope="first-letterscheme="css">
                                      font-size: xx-large</rendition>
                                      </tagsDecl>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rendition>

                                      <rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.styleDef (@scheme, @schemeVersion)
                                      scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      first-line
                                      styling applies to the first line of the target element
                                      first-letter
                                      styling applies to the first letter of the target element
                                      before
                                      styling should be applied immediately before the content of the target element
                                      after
                                      styling should be applied immediately after the content of the target element
                                      selectorcontains 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.
                                      Status Optional
                                      Datatype teidata.text
                                      <rendition scheme="css"
                                       selector="text, front, back, body, div, p, ab">

                                      display: block;
                                      </rendition>
                                      <rendition scheme="css"
                                       selector="*[rend*=italic]">
                                      font-style: italic;
                                      </rendition>
                                      Note

                                      Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.

                                      While rendition is used to point from an element in the transcribed source to a rendition element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a rendition in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

                                      Contained by
                                      header: tagsDecl
                                      May contain
                                      Example
                                      <tagsDecl>
                                       <rendition xml:id="r-centerscheme="css">text-align: center;</rendition>
                                       <rendition xml:id="r-smallscheme="css">font-size: small;</rendition>
                                       <rendition xml:id="r-largescheme="css">font-size: large;</rendition>
                                       <rendition xml:id="initcaps"
                                        scope="first-letterscheme="css">
                                      font-size: xx-large</rendition>
                                      </tagsDecl>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                       element rendition
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          attribute scope { teidata.enumerated }?,
                                          attribute selector { teidata.text }?,
                                          tei_macro.limitedContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-repository.html b/gl/dev/ref-repository.html index b337beb5a..e62300250 100644 --- a/gl/dev/ref-repository.html +++ b/gl/dev/ref-repository.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <repository>

                                      <repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      Contained by
                                      namesdates: objectIdentifier
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <settlement>Oxford</settlement>
                                       <institution>University of Oxford</institution>
                                       <repository>Bodleian Library</repository>
                                       <idno>MS. Bodley 406</idno>
                                      </msIdentifier>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <repository>

                                      <repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
                                      Contained by
                                      namesdates: objectIdentifier
                                      May contain
                                      Example
                                      <msIdentifier>
                                       <settlement>Oxford</settlement>
                                       <institution>University of Oxford</institution>
                                       <repository>Bodleian Library</repository>
                                       <idno>MS. Bodley 406</idno>
                                      </msIdentifier>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element repository
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-resp.html b/gl/dev/ref-resp.html index bec8c1f00..afb75eee1 100644 --- a/gl/dev/ref-resp.html +++ b/gl/dev/ref-resp.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <resp>

                                      <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      core: respStmt
                                      May contain
                                      Note

                                      The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

                                      Example
                                      <respStmt>
                                       <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
                                       <name>Edward Child</name>
                                      </respStmt>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <resp>

                                      <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Contained by
                                      core: respStmt
                                      May contain
                                      Note

                                      The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

                                      Example
                                      <respStmt>
                                       <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
                                       <name>Edward Child</name>
                                      </respStmt>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element resp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-respStmt.html b/gl/dev/ref-respStmt.html index b8af49147..832421af5 100644 --- a/gl/dev/ref-respStmt.html +++ b/gl/dev/ref-respStmt.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <respStmt>

                                      <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      May contain
                                      core: name note resp
                                      namesdates: orgName persName
                                      Example
                                      <respStmt>
                                       <resp>transcribed from original ms</resp>
                                       <persName>Claus Huitfeldt</persName>
                                      </respStmt>
                                      Example
                                      <respStmt>
                                       <resp>converted to XML encoding</resp>
                                       <name>Alan Morrison</name>
                                      </respStmt>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate>
                                         <sequence>
                                          <elementRef key="respminOccurs="1"
                                           maxOccurs="unbounded"/>

                                          <classRef key="model.nameLike.agent"
                                           minOccurs="1maxOccurs="unbounded"/>

                                         </sequence>
                                         <sequence>
                                          <classRef key="model.nameLike.agent"
                                           minOccurs="1maxOccurs="unbounded"/>

                                          <elementRef key="respminOccurs="1"
                                           maxOccurs="unbounded"/>

                                         </sequence>
                                        </alternate>
                                        <elementRef key="noteminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <respStmt>

                                      <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
                                      Member of
                                      Contained by
                                      May contain
                                      core: name note resp
                                      namesdates: orgName persName
                                      Example
                                      <respStmt>
                                       <resp>transcribed from original ms</resp>
                                       <persName>Claus Huitfeldt</persName>
                                      </respStmt>
                                      Example
                                      <respStmt>
                                       <resp>converted to XML encoding</resp>
                                       <name>Alan Morrison</name>
                                      </respStmt>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate>
                                         <sequence>
                                          <elementRef key="respminOccurs="1"
                                           maxOccurs="unbounded"/>

                                          <classRef key="model.nameLike.agent"
                                           minOccurs="1maxOccurs="unbounded"/>

                                         </sequence>
                                         <sequence>
                                          <classRef key="model.nameLike.agent"
                                           minOccurs="1maxOccurs="unbounded"/>

                                          <elementRef key="respminOccurs="1"
                                           maxOccurs="unbounded"/>

                                         </sequence>
                                        </alternate>
                                        <elementRef key="noteminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element respStmt
                                       {
                                          tei_att.global.attributes,
                                      @@ -33,4 +33,4 @@
                                             ),
                                             tei_note*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-retrace.html b/gl/dev/ref-retrace.html index 837f0f2be..40b317ee8 100644 --- a/gl/dev/ref-retrace.html +++ b/gl/dev/ref-retrace.html @@ -29,4 +29,4 @@ tei_att.transcriptional.attributes, tei_att.dimensions.attributes, tei_macro.paraContent -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-revisionDesc.html b/gl/dev/ref-revisionDesc.html index 6bb8c8bc9..a1d37964a 100644 --- a/gl/dev/ref-revisionDesc.html +++ b/gl/dev/ref-revisionDesc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <revisionDesc>

                                      <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.docStatus (@status)
                                      Contained by
                                      header: teiHeader
                                      linking: annotation
                                      May contain
                                      core: list
                                      Note

                                      If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any change to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list.

                                      Example
                                      <revisionDesc status="embargoed">
                                       <change when="1991-11-11who="#LB"> deleted chapter 10 </change>
                                      </revisionDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <elementRef key="list"/>
                                        <elementRef key="listChange"/>
                                        <elementRef key="changeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <revisionDesc>

                                      <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.docStatus (@status)
                                      Contained by
                                      header: teiHeader
                                      linking: annotation
                                      May contain
                                      core: list
                                      Note

                                      If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any change to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list.

                                      Example
                                      <revisionDesc status="embargoed">
                                       <change when="1991-11-11who="#LB"> deleted chapter 10 </change>
                                      </revisionDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <elementRef key="list"/>
                                        <elementRef key="listChange"/>
                                        <elementRef key="changeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element revisionDesc
                                       {
                                          tei_att.global.attributes,
                                          tei_att.docStatus.attributes,
                                          ( tei_list | tei_listChange | tei_change+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-roleName.html b/gl/dev/ref-roleName.html index dfaafa4d9..916aa9c61 100644 --- a/gl/dev/ref-roleName.html +++ b/gl/dev/ref-roleName.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <roleName>

                                      <roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      A roleName may be distinguished from an addName by virtue of the fact that, like a title, it typically exists independently of its holder.

                                      Example
                                      <persName>
                                       <forename>William</forename>
                                       <surname>Poulteny</surname>
                                       <roleName>Earl of Bath</roleName>
                                      </persName>
                                      Example
                                      <p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
                                      including the Supreme Court justices, required by statute to be “learned in the law.”</p>
                                      Example
                                      <p>
                                       <persName ref="#NJF">
                                        <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
                                      representing the administration, asserted in rebuttal that there was nothing to disavow (...)
                                      <persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
                                      the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
                                      alike, have repeatedly said they must honor.
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <roleName>

                                      <roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      A roleName may be distinguished from an addName by virtue of the fact that, like a title, it typically exists independently of its holder.

                                      Example
                                      <persName>
                                       <forename>William</forename>
                                       <surname>Poulteny</surname>
                                       <roleName>Earl of Bath</roleName>
                                      </persName>
                                      Example
                                      <p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official,
                                      including the Supreme Court justices, required by statute to be “learned in the law.”</p>
                                      Example
                                      <p>
                                       <persName ref="#NJF">
                                        <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>,
                                      representing the administration, asserted in rebuttal that there was nothing to disavow (...)
                                      <persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and
                                      the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations
                                      alike, have repeatedly said they must honor.
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element roleName
                                       {
                                          tei_att.global.attributes,
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-row.html b/gl/dev/ref-row.html index 544e8cb07..9b842c9d6 100644 --- a/gl/dev/ref-row.html +++ b/gl/dev/ref-row.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <row>

                                      <row> (row) contains one row of a table. [14.1.1. TEI Tables]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.tableDecoration (@role, @rows, @cols)
                                      Contained by
                                      figures: table
                                      May contain
                                      figures: cell
                                      Example
                                      <row role="data">
                                       <cell role="label">Classics</cell>
                                       <cell>Idle listless and unimproving</cell>
                                      </row>
                                      Content model
                                      <content>
                                       <elementRef key="cellminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <row>

                                      <row> (row) contains one row of a table. [14.1.1. TEI Tables]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.tableDecoration (@role, @rows, @cols)
                                      Contained by
                                      figures: table
                                      May contain
                                      figures: cell
                                      Example
                                      <row role="data">
                                       <cell role="label">Classics</cell>
                                       <cell>Idle listless and unimproving</cell>
                                      </row>
                                      Content model
                                      <content>
                                       <elementRef key="cellminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element row
                                       {
                                          tei_att.global.attributes,
                                          tei_att.tableDecoration.attributes,
                                          tei_cell+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rs.html b/gl/dev/ref-rs.html index 788fc6094..ed6e2dc9d 100644 --- a/gl/dev/ref-rs.html +++ b/gl/dev/ref-rs.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rs>

                                      <rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs>
                                      to him one day,
                                      <q>have you heard that <rs type="place">Netherfield Park</rs> is let at
                                      last?</q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rs>

                                      <rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs>
                                      to him one day,
                                      <q>have you heard that <rs type="place">Netherfield Park</rs> is let at
                                      last?</q>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element rs
                                       {
                                          tei_att.global.attributes,
                                          tei_att.naming.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rt.html b/gl/dev/ref-rt.html index 99eab5e9c..de8f2a4c2 100644 --- a/gl/dev/ref-rt.html +++ b/gl/dev/ref-rt.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rt>

                                      <rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand))
                                      targetsupplies a pointer to the base being glossed by this ruby text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.

                                      <sch:report test="../@from | ../@to">When target= is
                                      present, neither from= nor to= should be.</sch:report>
                                      Note

                                      Should point to a single rb or an element that is inside an rb. To refer to multiple elements or text nodes at once use from and to.

                                      frompoints to the starting point of the span of text being glossed by this ruby text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronEnforce the presence of to iff there is a from.

                                      <sch:assert test="../@to">When from= is present, the to=
                                      attribute of <sch:name/> is required.</sch:assert>
                                      topoints to the ending point of the span of text being glossed.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronEnforce the presence of from iff there is a to.

                                      <sch:assert test="../@from">When to= is present, the from=
                                      attribute of <sch:name/> is required.</sch:assert>
                                      Contained by
                                      core: ruby
                                      May contain
                                      Note

                                      Where the place attribute is not provided on the rt element, the default assumption is that the ruby gloss is above where the text is horizontal, and to the right of the text where it is vertical.

                                      Example

                                      The word 大統領 daitōryō (president) is glossed character by character in hiragana to provide a pronunciation guide.

                                      <p style="writing-mode: vertical-rl"
                                       xml:lang="ja">

                                      <!--...-->
                                       <ruby>
                                        <rb></rb>
                                        <rt place="right">だい</rt>
                                       </ruby>
                                       <ruby>
                                        <rb></rb>
                                        <rt place="right">とう</rt>
                                       </ruby>
                                       <ruby>
                                        <rb></rb>
                                        <rt place="right">りょう</rt>
                                       </ruby>
                                      <!--...-->
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rt>

                                      <rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand))
                                      targetsupplies a pointer to the base being glossed by this ruby text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.

                                      <sch:report test="../@from | ../@to">When target= is
                                      present, neither from= nor to= should be.</sch:report>
                                      Note

                                      Should point to a single rb or an element that is inside an rb. To refer to multiple elements or text nodes at once use from and to.

                                      frompoints to the starting point of the span of text being glossed by this ruby text.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronEnforce the presence of to iff there is a from.

                                      <sch:assert test="../@to">When from= is present, the to=
                                      attribute of <sch:name/> is required.</sch:assert>
                                      topoints to the ending point of the span of text being glossed.
                                      Status Optional
                                      Datatype teidata.pointer
                                      SchematronEnforce the presence of from iff there is a to.

                                      <sch:assert test="../@from">When to= is present, the from=
                                      attribute of <sch:name/> is required.</sch:assert>
                                      Contained by
                                      core: ruby
                                      May contain
                                      Note

                                      Where the place attribute is not provided on the rt element, the default assumption is that the ruby gloss is above where the text is horizontal, and to the right of the text where it is vertical.

                                      Example

                                      The word 大統領 daitōryō (president) is glossed character by character in hiragana to provide a pronunciation guide.

                                      <p style="writing-mode: vertical-rl"
                                       xml:lang="ja">

                                      <!--...-->
                                       <ruby>
                                        <rb></rb>
                                        <rt place="right">だい</rt>
                                       </ruby>
                                       <ruby>
                                        <rb></rb>
                                        <rt place="right">とう</rt>
                                       </ruby>
                                       <ruby>
                                        <rb></rb>
                                        <rt place="right">りょう</rt>
                                       </ruby>
                                      <!--...-->
                                      </p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element rt
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          attribute from { teidata.pointer }?,
                                          attribute to { teidata.pointer }?,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-rubric.html b/gl/dev/ref-rubric.html index dcc4ab425..20337cee8 100644 --- a/gl/dev/ref-rubric.html +++ b/gl/dev/ref-rubric.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <rubric>

                                      <rubric> (rubric) contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a manuscript or other object signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, typically in red ink, or by use of different size or type of script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric>
                                      <rubric>Incipit liber de consciencia humana a beatissimo Bernardo editus.</rubric>
                                      <rubric>
                                       <locus>16. f. 28v in margin: </locus>Dicta Cassiodori
                                      </rubric>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <rubric>

                                      <rubric> (rubric) contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a manuscript or other object signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, typically in red ink, or by use of different size or type of script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
                                      Member of
                                      Contained by
                                      msdescription: msItem msItemStruct
                                      May contain
                                      Example
                                      <rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric>
                                      <rubric>Incipit liber de consciencia humana a beatissimo Bernardo editus.</rubric>
                                      <rubric>
                                       <locus>16. f. 28v in margin: </locus>Dicta Cassiodori
                                      </rubric>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element rubric
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.msExcerpt.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-ruby.html b/gl/dev/ref-ruby.html index 35993b866..2ee870c2a 100644 --- a/gl/dev/ref-ruby.html +++ b/gl/dev/ref-ruby.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <ruby>

                                      <ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      core: rb rt
                                      Example

                                      The word 入学試験 nyūgakushiken (university entrance exam) is glossed with a hiragana phonation guide.

                                      <p xml:lang="ja">
                                      <!--...-->
                                       <ruby>
                                        <rb>入学試験</rb>
                                        <rt place="above">にゅうがくしけん</rt>
                                       </ruby>
                                      <!--...-->
                                      </p>
                                      Example

                                      This fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.

                                      <ruby>
                                       <rb>T</rb>
                                       <rt>ti:</rt>
                                      </ruby>
                                      <ruby>
                                       <rb>E</rb>
                                       <rt>i:</rt>
                                      </ruby>
                                      <ruby>
                                       <rb>I</rb>
                                       <rt></rt>
                                      </ruby>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="rbminOccurs="1"
                                         maxOccurs="1"/>

                                        <elementRef key="rtminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <ruby>

                                      <ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      core: rb rt
                                      Example

                                      The word 入学試験 nyūgakushiken (university entrance exam) is glossed with a hiragana phonation guide.

                                      <p xml:lang="ja">
                                      <!--...-->
                                       <ruby>
                                        <rb>入学試験</rb>
                                        <rt place="above">にゅうがくしけん</rt>
                                       </ruby>
                                      <!--...-->
                                      </p>
                                      Example

                                      This fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.

                                      <ruby>
                                       <rb>T</rb>
                                       <rt>ti:</rt>
                                      </ruby>
                                      <ruby>
                                       <rb>E</rb>
                                       <rt>i:</rt>
                                      </ruby>
                                      <ruby>
                                       <rb>I</rb>
                                       <rt></rt>
                                      </ruby>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="rbminOccurs="1"
                                         maxOccurs="1"/>

                                        <elementRef key="rtminOccurs="1"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element ruby
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          ( tei_rb, tei_rt+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-s.html b/gl/dev/ref-s.html index 7a7ba8114..b661cec07 100644 --- a/gl/dev/ref-s.html +++ b/gl/dev/ref-s.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <s>

                                      <s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The s element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the seg should be used instead.

                                      The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology.

                                      Example
                                      <head>
                                       <s>A short affair</s>
                                      </head>
                                      <s>When are you leaving?</s>
                                      <s>Tomorrow.</s>
                                      Schematron

                                      <s:report test="tei:s">You may not nest one s element within
                                      another: use seg instead</s:report>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <s>

                                      <s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The s element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the seg should be used instead.

                                      The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology.

                                      Example
                                      <head>
                                       <s>A short affair</s>
                                      </head>
                                      <s>When are you leaving?</s>
                                      <s>Tomorrow.</s>
                                      Schematron

                                      <s:report test="tei:s">You may not nest one s element within
                                      another: use seg instead</s:report>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element s
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.notated.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-said.html b/gl/dev/ref-said.html index fb5d68768..fa322eed3 100644 --- a/gl/dev/ref-said.html +++ b/gl/dev/ref-said.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <said>

                                      <said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
                                      aloudmay be used to indicate whether the quoted matter is regarded as having been vocalized or signed.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      <p> Celia thought privately, <said aloud="false">Dorothea quite despises Sir James Chettam;
                                         I believe she would not accept him.</said> Celia felt that this was a pity.

                                      <!-- ... -->
                                      </p>
                                      Note

                                      The value true indicates the encoded passage was expressed outwardly (whether spoken, signed, sung, screamed, chanted, etc.); the value false indicates that the encoded passage was thought, but not outwardly expressed.

                                      directmay be used to indicate whether the quoted matter is regarded as direct or indirect speech.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Default true

                                      <!-- in the header --><editorialDecl>
                                       <quotation marks="none"/>
                                      </editorialDecl>
                                      <!-- ... -->
                                      <p>Tantripp had brought a card, and said that <said direct="false">there was a gentleman waiting in the lobby</said>.
                                      The courier had told him that <said direct="false">only Mrs. Casaubon was at home</said>,
                                      but he said <said direct="false">he was a relation of Mr. Casaubon's: would she see him?</said>
                                      </p>
                                      Note

                                      The value true indicates the speech or thought is represented directly; the value false that speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.

                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      <!-- in the header --><editorialDecl>
                                       <quotation marks="all"/>
                                      </editorialDecl>
                                      <!-- ... -->
                                      <p>
                                       <said>"Our minstrel here will warm the old man's heart with song, dazzle him with jewels and
                                         gold"</said>, a troublemaker simpered. <said>"He'll trample on the Duke's camellias, spill
                                         his wine, and blunt his sword, and say his name begins with X, and in the end the Duke
                                         will say, <said>'Take Saralinda, with my blessing, O lordly Prince of Rags and Tags, O
                                           rider of the sun!'</said>"</said>
                                      </p>
                                      Example
                                      <p>
                                       <said aloud="truerend="pre(“) post(”)">Hmmm</said>, said a small voice in his ear.
                                      <said aloud="truerend="pre(“) post(”)">Difficult. Very difficult. Plenty of courage, I see.
                                         Not a bad mind either. there's talent, oh my goodness, yes — and a nice thirst to prove
                                         yourself, now that's interesting. … So where shall I put you?</said>
                                      </p>
                                      <p>Harry gripped the edges of the stool and thought, <said aloud="falserend="italic">Not
                                         Slytherin, not Slytherin</said>.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <said>

                                      <said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
                                      aloudmay be used to indicate whether the quoted matter is regarded as having been vocalized or signed.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      <p> Celia thought privately, <said aloud="false">Dorothea quite despises Sir James Chettam;
                                         I believe she would not accept him.</said> Celia felt that this was a pity.

                                      <!-- ... -->
                                      </p>
                                      Note

                                      The value true indicates the encoded passage was expressed outwardly (whether spoken, signed, sung, screamed, chanted, etc.); the value false indicates that the encoded passage was thought, but not outwardly expressed.

                                      directmay be used to indicate whether the quoted matter is regarded as direct or indirect speech.
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Default true

                                      <!-- in the header --><editorialDecl>
                                       <quotation marks="none"/>
                                      </editorialDecl>
                                      <!-- ... -->
                                      <p>Tantripp had brought a card, and said that <said direct="false">there was a gentleman waiting in the lobby</said>.
                                      The courier had told him that <said direct="false">only Mrs. Casaubon was at home</said>,
                                      but he said <said direct="false">he was a relation of Mr. Casaubon's: would she see him?</said>
                                      </p>
                                      Note

                                      The value true indicates the speech or thought is represented directly; the value false that speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.

                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      <!-- in the header --><editorialDecl>
                                       <quotation marks="all"/>
                                      </editorialDecl>
                                      <!-- ... -->
                                      <p>
                                       <said>"Our minstrel here will warm the old man's heart with song, dazzle him with jewels and
                                         gold"</said>, a troublemaker simpered. <said>"He'll trample on the Duke's camellias, spill
                                         his wine, and blunt his sword, and say his name begins with X, and in the end the Duke
                                         will say, <said>'Take Saralinda, with my blessing, O lordly Prince of Rags and Tags, O
                                           rider of the sun!'</said>"</said>
                                      </p>
                                      Example
                                      <p>
                                       <said aloud="truerend="pre(“) post(”)">Hmmm</said>, said a small voice in his ear.
                                      <said aloud="truerend="pre(“) post(”)">Difficult. Very difficult. Plenty of courage, I see.
                                         Not a bad mind either. there's talent, oh my goodness, yes — and a nice thirst to prove
                                         yourself, now that's interesting. … So where shall I put you?</said>
                                      </p>
                                      <p>Harry gripped the edges of the stool and thought, <said aloud="falserend="italic">Not
                                         Slytherin, not Slytherin</said>.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element said
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          attribute aloud { teidata.xTruthValue }?,
                                          attribute direct { teidata.xTruthValue }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-samplingDecl.html b/gl/dev/ref-samplingDecl.html index 1f60dc209..cfd7ad505 100644 --- a/gl/dev/ref-samplingDecl.html +++ b/gl/dev/ref-samplingDecl.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <samplingDecl>

                                      <samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

                                      Example
                                      <samplingDecl>
                                       <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each
                                         text identified as relevant by respondents.</p>
                                      </samplingDecl>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <samplingDecl>

                                      <samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Note

                                      This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

                                      Example
                                      <samplingDecl>
                                       <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each
                                         text identified as relevant by respondents.</p>
                                      </samplingDecl>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element samplingDecl
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-schemaRef.html b/gl/dev/ref-schemaRef.html index 14f6da64a..c28c8bae9 100644 --- a/gl/dev/ref-schemaRef.html +++ b/gl/dev/ref-schemaRef.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <schemaRef>

                                      <schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.10. The Schema Specification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.resourced (@url)
                                      keythe identifier used for the customization or schema
                                      Status Optional
                                      Datatype teidata.xmlName
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: desc
                                      Example
                                      <schemaRef type="interchangeODD"
                                       url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/>

                                      <schemaRef type="interchangeRNG"
                                       url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/>

                                      <schemaRef type="projectODD"
                                       url="file:///schema/project.odd"/>
                                      Content model
                                      <content>
                                       <classRef key="model.descLike"
                                        minOccurs="0"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <schemaRef>

                                      <schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.10. The Schema Specification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.resourced (@url)
                                      keythe identifier used for the customization or schema
                                      Status Optional
                                      Datatype teidata.xmlName
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: desc
                                      Example
                                      <schemaRef type="interchangeODD"
                                       url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/>

                                      <schemaRef type="interchangeRNG"
                                       url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/>

                                      <schemaRef type="projectODD"
                                       url="file:///schema/project.odd"/>
                                      Content model
                                      <content>
                                       <classRef key="model.descLike"
                                        minOccurs="0"/>

                                      </content>
                                      Schema Declaration
                                       element schemaRef
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.resourced.attributes,
                                          attribute key { teidata.xmlName }?,
                                          tei_model.descLike?
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-scriptDesc.html b/gl/dev/ref-scriptDesc.html index 1492363fe..d4e5d3d5c 100644 --- a/gl/dev/ref-scriptDesc.html +++ b/gl/dev/ref-scriptDesc.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <scriptDesc>

                                      <scriptDesc> (script description) contains a description of the scripts used in a manuscript or other object. [10.7.2.1. Writing]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      header: scriptNote
                                      linking: ab
                                      msdescription: summary
                                      Example
                                      <scriptDesc>
                                       <p/>
                                      </scriptDesc>
                                      Example
                                      <scriptDesc>
                                       <summary>Contains two distinct styles of scripts </summary>
                                       <scriptNote xml:id="style-1">.</scriptNote>
                                       <scriptNote xml:id="style-2">.</scriptNote>
                                      </scriptDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="scriptNote"
                                          minOccurs="1maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <scriptDesc>

                                      <scriptDesc> (script description) contains a description of the scripts used in a manuscript or other object. [10.7.2.1. Writing]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      header: scriptNote
                                      linking: ab
                                      msdescription: summary
                                      Example
                                      <scriptDesc>
                                       <p/>
                                      </scriptDesc>
                                      Example
                                      <scriptDesc>
                                       <summary>Contains two distinct styles of scripts </summary>
                                       <scriptNote xml:id="style-1">.</scriptNote>
                                       <scriptNote xml:id="style-2">.</scriptNote>
                                      </scriptDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="scriptNote"
                                          minOccurs="1maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element scriptDesc
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | ( tei_summary?, tei_scriptNote+ ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-scriptNote.html b/gl/dev/ref-scriptNote.html index a00bbb1b0..360294033 100644 --- a/gl/dev/ref-scriptNote.html +++ b/gl/dev/ref-scriptNote.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <scriptNote>

                                      <scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [10.7.2. Writing, Decoration, and Other Notations]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      Contained by
                                      msdescription: scriptDesc
                                      May contain
                                      Example
                                      <scriptNote scope="sole"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <scriptNote>

                                      <scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [10.7.2. Writing, Decoration, and Other Notations]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      Contained by
                                      msdescription: scriptDesc
                                      May contain
                                      Example
                                      <scriptNote scope="sole"/>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element scriptNote
                                       {
                                          tei_att.global.attributes,
                                          tei_att.handFeatures.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-seal.html b/gl/dev/ref-seal.html index 377a62451..111cdb0b1 100644 --- a/gl/dev/ref-seal.html +++ b/gl/dev/ref-seal.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <seal>

                                      <seal> (seal) contains a description of one seal or similar applied to the object described [10.7.3.2. Seals]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      contemporary(contemporary) specifies whether or not the seal is contemporary with the item to which it is affixed
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Contained by
                                      msdescription: sealDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: decoNote
                                      Example
                                      <seal n="2type="pendant"
                                       subtype="cauda_duplex">

                                       <p>The seal of <name>Jens Olufsen</name> in black wax.
                                         (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.
                                         Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p>
                                      </seal>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <elementRef key="decoNote"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <seal>

                                      <seal> (seal) contains a description of one seal or similar applied to the object described [10.7.3.2. Seals]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      contemporary(contemporary) specifies whether or not the seal is contemporary with the item to which it is affixed
                                      Status Optional
                                      Datatype teidata.xTruthValue
                                      Contained by
                                      msdescription: sealDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: decoNote
                                      Example
                                      <seal n="2type="pendant"
                                       subtype="cauda_duplex">

                                       <p>The seal of <name>Jens Olufsen</name> in black wax.
                                         (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.
                                         Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p>
                                      </seal>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.pLike"/>
                                        <elementRef key="decoNote"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element seal
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.datable.attributes,
                                          attribute contemporary { teidata.xTruthValue }?,
                                          ( tei_model.pLike | tei_decoNote )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-sealDesc.html b/gl/dev/ref-sealDesc.html index 1ca89b535..a9ea4a75f 100644 --- a/gl/dev/ref-sealDesc.html +++ b/gl/dev/ref-sealDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <sealDesc>

                                      <sealDesc> (seal description) describes the seals or similar items related to the object described, either as a series of paragraphs or as a series of seal elements. [10.7.3.2. Seals]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <sealDesc>
                                       <seal type="pendantcontemporary="true">
                                        <p>Green wax vertical oval seal attached at base.</p>
                                       </seal>
                                      </sealDesc>
                                      Example
                                      <sealDesc>
                                       <p>Parchment strip for seal in place; seal missing.</p>
                                      </sealDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="decoNote"/>
                                          <elementRef key="seal"/>
                                          <elementRef key="condition"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <sealDesc>

                                      <sealDesc> (seal description) describes the seals or similar items related to the object described, either as a series of paragraphs or as a series of seal elements. [10.7.3.2. Seals]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <sealDesc>
                                       <seal type="pendantcontemporary="true">
                                        <p>Green wax vertical oval seal attached at base.</p>
                                       </seal>
                                      </sealDesc>
                                      Example
                                      <sealDesc>
                                       <p>Parchment strip for seal in place; seal missing.</p>
                                      </sealDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="decoNote"/>
                                          <elementRef key="seal"/>
                                          <elementRef key="condition"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element sealDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                             tei_model.pLike+
                                           | ( tei_summary?, ( tei_decoNote | tei_seal | tei_condition )+ )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-secFol.html b/gl/dev/ref-secFol.html index 2d27c2e4b..dc57eebce 100644 --- a/gl/dev/ref-secFol.html +++ b/gl/dev/ref-secFol.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <secFol>

                                      <secFol> (second folio) marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. [10.3.7. Catchwords, Signatures, Secundo Folio]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <secFol>(con-)versio morum</secFol>
                                      Schematron

                                      <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element secFol { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <secFol>

                                      <secFol> (second folio) marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. [10.3.7. Catchwords, Signatures, Secundo Folio]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <secFol>(con-)versio morum</secFol>
                                      Schematron

                                      <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element secFol { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-secl.html b/gl/dev/ref-secl.html index 4037624c7..998413ea5 100644 --- a/gl/dev/ref-secl.html +++ b/gl/dev/ref-secl.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <secl>

                                      <secl> (secluded text) Secluded. Marks text present in the source which the editor believes to be genuine but out of its original place (which is unknown). [11.3.1.7. Text Omitted from or Supplied in the Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      reasonone or more words indicating why this text has been secluded, e.g. interpolated etc.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <rdg source="#Pescani">
                                       <secl>
                                        <l n="15xml:id="l15">Alphesiboea suos ulta est pro coniuge fratres,</l>
                                        <l n="16xml:id="l16">sanguinis et cari vincula rupit amor.</l>
                                       </secl>
                                      </rdg>
                                      <note>secl. Pescani</note>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <secl>

                                      <secl> (secluded text) Secluded. Marks text present in the source which the editor believes to be genuine but out of its original place (which is unknown). [11.3.1.7. Text Omitted from or Supplied in the Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      reasonone or more words indicating why this text has been secluded, e.g. interpolated etc.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <rdg source="#Pescani">
                                       <secl>
                                        <l n="15xml:id="l15">Alphesiboea suos ulta est pro coniuge fratres,</l>
                                        <l n="16xml:id="l16">sanguinis et cari vincula rupit amor.</l>
                                       </secl>
                                      </rdg>
                                      <note>secl. Pescani</note>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element secl
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.dimensions.attributes,
                                          attribute reason { list { teidata.word+ } }?,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-seg.html b/gl/dev/ref-seg.html index f08eee39d..67e5980e3 100644 --- a/gl/dev/ref-seg.html +++ b/gl/dev/ref-seg.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <seg>

                                      <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.written (@hand) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a ptr or other similar element.

                                      Example
                                      <seg>When are you leaving?</seg>
                                      <seg>Tomorrow.</seg>
                                      Example
                                      <s>
                                       <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield.
                                      </s>
                                      Example
                                      <seg type="preamble">
                                       <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
                                       <seg>Sinfiotli was the eldest of his sons ...</seg>
                                       <seg>Borghild, Sigmund's wife, had a brother ... </seg>
                                      </seg>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <seg>

                                      <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.written (@hand) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a ptr or other similar element.

                                      Example
                                      <seg>When are you leaving?</seg>
                                      <seg>Tomorrow.</seg>
                                      Example
                                      <s>
                                       <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield.
                                      </s>
                                      Example
                                      <seg type="preamble">
                                       <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
                                       <seg>Sinfiotli was the eldest of his sons ...</seg>
                                       <seg>Borghild, Sigmund's wife, had a brother ... </seg>
                                      </seg>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element seg
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.written.attributes,
                                          tei_att.notated.attributes,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-segmentation.html b/gl/dev/ref-segmentation.html index 21ce2a48f..d1821cbf3 100644 --- a/gl/dev/ref-segmentation.html +++ b/gl/dev/ref-segmentation.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <segmentation>

                                      <segmentation> (segmentation) describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <segmentation>
                                       <p>
                                        <gi>s</gi> elements mark orthographic sentences and are numbered sequentially within
                                         their parent <gi>div</gi> element </p>
                                      </segmentation>
                                      Example
                                      <p>
                                       <gi>seg</gi> elements are used to mark functional constituents of various types within each
                                      <gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus
                                      header <gi>classDecl</gi>
                                      </p>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <segmentation>

                                      <segmentation> (segmentation) describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <segmentation>
                                       <p>
                                        <gi>s</gi> elements mark orthographic sentences and are numbered sequentially within
                                         their parent <gi>div</gi> element </p>
                                      </segmentation>
                                      Example
                                      <p>
                                       <gi>seg</gi> elements are used to mark functional constituents of various types within each
                                      <gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus
                                      header <gi>classDecl</gi>
                                      </p>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element segmentation
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-series.html b/gl/dev/ref-series.html index 5a2863043..655ecc75b 100644 --- a/gl/dev/ref-series.html +++ b/gl/dev/ref-series.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <series>

                                      <series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <series xml:lang="de">
                                       <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
                                       <respStmt>
                                        <resp>Herausgegeben von</resp>
                                        <name type="person">Manfred Thaller</name>
                                        <name type="org">Max-Planck-Institut für Geschichte</name>
                                       </respStmt>
                                       <title level="s">Serie A: Historische Quellenkunden</title>
                                       <biblScope>Band 11</biblScope>
                                      </series>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="title"/>
                                        <classRef key="model.ptrLike"/>
                                        <elementRef key="editor"/>
                                        <elementRef key="respStmt"/>
                                        <elementRef key="biblScope"/>
                                        <elementRef key="idno"/>
                                        <elementRef key="textLang"/>
                                        <classRef key="model.global"/>
                                        <elementRef key="availability"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <series>

                                      <series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <series xml:lang="de">
                                       <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
                                       <respStmt>
                                        <resp>Herausgegeben von</resp>
                                        <name type="person">Manfred Thaller</name>
                                        <name type="org">Max-Planck-Institut für Geschichte</name>
                                       </respStmt>
                                       <title level="s">Serie A: Historische Quellenkunden</title>
                                       <biblScope>Band 11</biblScope>
                                      </series>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="title"/>
                                        <classRef key="model.ptrLike"/>
                                        <elementRef key="editor"/>
                                        <elementRef key="respStmt"/>
                                        <elementRef key="biblScope"/>
                                        <elementRef key="idno"/>
                                        <elementRef key="textLang"/>
                                        <classRef key="model.global"/>
                                        <elementRef key="availability"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element series
                                       {
                                          tei_att.global.attributes,
                                      @@ -38,4 +38,4 @@
                                           | tei_model.global
                                           | tei_availability
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-seriesStmt.html b/gl/dev/ref-seriesStmt.html index e47d4ae5c..da746f015 100644 --- a/gl/dev/ref-seriesStmt.html +++ b/gl/dev/ref-seriesStmt.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <seriesStmt>

                                      <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Contained by
                                      May contain
                                      header: idno
                                      linking: ab
                                      Example
                                      <seriesStmt>
                                       <title>Machine-Readable Texts for the Study of Indian Literature</title>
                                       <respStmt>
                                        <resp>ed. by</resp>
                                        <name>Jan Gonda</name>
                                       </respStmt>
                                       <biblScope unit="volume">1.2</biblScope>
                                       <idno type="ISSN">0 345 6789</idno>
                                      </seriesStmt>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="titleminOccurs="1"
                                          maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="editor"/>
                                          <elementRef key="respStmt"/>
                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="idno"/>
                                          <elementRef key="biblScope"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <seriesStmt>

                                      <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Contained by
                                      May contain
                                      header: idno
                                      linking: ab
                                      Example
                                      <seriesStmt>
                                       <title>Machine-Readable Texts for the Study of Indian Literature</title>
                                       <respStmt>
                                        <resp>ed. by</resp>
                                        <name>Jan Gonda</name>
                                       </respStmt>
                                       <biblScope unit="volume">1.2</biblScope>
                                       <idno type="ISSN">0 345 6789</idno>
                                      </seriesStmt>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="titleminOccurs="1"
                                          maxOccurs="unbounded"/>

                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="editor"/>
                                          <elementRef key="respStmt"/>
                                         </alternate>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="idno"/>
                                          <elementRef key="biblScope"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element seriesStmt
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                                ( tei_idno | tei_biblScope )*
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-settingDesc.html b/gl/dev/ref-settingDesc.html index 9a71c5278..6f45d80dc 100644 --- a/gl/dev/ref-settingDesc.html +++ b/gl/dev/ref-settingDesc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <settingDesc>

                                      <settingDesc> (setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata. [15.2. Contextual Information 2.4. The Profile Description]
                                      Modulecorpus
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      namesdates: listPlace place
                                      Note

                                      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.

                                      Example
                                      <settingDesc>
                                       <p>Texts recorded in the
                                         Canadian Parliament building in Ottawa, between April and November 1988 </p>
                                      </settingDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="setting"/>
                                         <classRef key="model.placeLike"/>
                                         <elementRef key="listPlace"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <settingDesc>

                                      <settingDesc> (setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata. [15.2. Contextual Information 2.4. The Profile Description]
                                      Modulecorpus
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      namesdates: listPlace place
                                      Note

                                      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.

                                      Example
                                      <settingDesc>
                                       <p>Texts recorded in the
                                         Canadian Parliament building in Ottawa, between April and November 1988 </p>
                                      </settingDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <elementRef key="setting"/>
                                         <classRef key="model.placeLike"/>
                                         <elementRef key="listPlace"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element settingDesc
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          ( tei_model.pLike+ | ( setting | tei_model.placeLike | tei_listPlace )+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-settlement.html b/gl/dev/ref-settlement.html index d851bda5b..dbb28bbfe 100644 --- a/gl/dev/ref-settlement.html +++ b/gl/dev/ref-settlement.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <settlement>

                                      <settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <settlement type="town">Glasgow</settlement>
                                       <region>Scotland</region>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <settlement>

                                      <settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <placeName>
                                       <settlement type="town">Glasgow</settlement>
                                       <region>Scotland</region>
                                      </placeName>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element settlement
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.typed.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-sic.html b/gl/dev/ref-sic.html index 99bc710b2..52c09f341 100644 --- a/gl/dev/ref-sic.html +++ b/gl/dev/ref-sic.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <sic>

                                      <sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      for his nose was as sharp as
                                      a pen, and <sic>a Table</sic> of green fields.
                                      Example

                                      If all that is desired is to call attention to the apparent problem in the copy text, sic may be used alone:

                                      I don't know, Juan. It's so far in the past now
                                      — how <sic>we can</sic> prove or disprove anyone's theories?
                                      Example

                                      It is also possible, using the choice and corr elements, to provide a corrected reading:

                                      I don't know, Juan. It's so far in the past now
                                      — how <choice>
                                       <sic>we can</sic>
                                       <corr>can we</corr>
                                      </choice> prove or disprove anyone's theories?
                                      Example
                                      for his nose was as sharp as
                                      a pen, and <choice>
                                       <sic>a Table</sic>
                                       <corr>a' babbld</corr>
                                      </choice> of green fields.
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      -element sic { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <sic>

                                      <sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      for his nose was as sharp as
                                      a pen, and <sic>a Table</sic> of green fields.
                                      Example

                                      If all that is desired is to call attention to the apparent problem in the copy text, sic may be used alone:

                                      I don't know, Juan. It's so far in the past now
                                      — how <sic>we can</sic> prove or disprove anyone's theories?
                                      Example

                                      It is also possible, using the choice and corr elements, to provide a corrected reading:

                                      I don't know, Juan. It's so far in the past now
                                      — how <choice>
                                       <sic>we can</sic>
                                       <corr>can we</corr>
                                      </choice> prove or disprove anyone's theories?
                                      Example
                                      for his nose was as sharp as
                                      a pen, and <choice>
                                       <sic>a Table</sic>
                                       <corr>a' babbld</corr>
                                      </choice> of green fields.
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +element sic { tei_att.global.attributes, tei_macro.paraContent }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-signatures.html b/gl/dev/ref-signatures.html index 51414e098..81e0ca7aa 100644 --- a/gl/dev/ref-signatures.html +++ b/gl/dev/ref-signatures.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <signatures>

                                      <signatures> (signatures) contains discussion of the leaf or quire signatures found within a codex or similar object. [10.3.7. Catchwords, Signatures, Secundo Folio]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <signatures>Quire and leaf signatures in letters, [b]-v, and roman
                                      numerals; those in quires 10 (1) and 17 (s) in red ink and different
                                      from others; every third quire also signed with red crayon in arabic
                                      numerals in the center 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).</signatures>
                                      Schematron

                                      <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element signatures { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <signatures>

                                      <signatures> (signatures) contains discussion of the leaf or quire signatures found within a codex or similar object. [10.3.7. Catchwords, Signatures, Secundo Folio]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <signatures>Quire and leaf signatures in letters, [b]-v, and roman
                                      numerals; those in quires 10 (1) and 17 (s) in red ink and different
                                      from others; every third quire also signed with red crayon in arabic
                                      numerals in the center 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).</signatures>
                                      Schematron

                                      <sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element signatures { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-soCalled.html b/gl/dev/ref-soCalled.html index 3540b5ed8..ad7af4481 100644 --- a/gl/dev/ref-soCalled.html +++ b/gl/dev/ref-soCalled.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <soCalled>

                                      <soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      To edge his way along
                                      the crowded paths of life, warning all human sympathy to keep its distance, was what the
                                      knowing ones call <soCalled>nuts</soCalled> to Scrooge.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element soCalled { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <soCalled>

                                      <soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      To edge his way along
                                      the crowded paths of life, warning all human sympathy to keep its distance, was what the
                                      knowing ones call <soCalled>nuts</soCalled> to Scrooge.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element soCalled { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-source.html b/gl/dev/ref-source.html index 43b8a5720..f62d79bff 100644 --- a/gl/dev/ref-source.html +++ b/gl/dev/ref-source.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <source>

                                      <source> (source) describes the original source for the information contained with a manuscript or object description. [10.9.1.1. Record History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: recordHist
                                      May contain
                                      Example
                                      <source>Derived from <ref>Stanley (1960)</ref>
                                      </source>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element source { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <source>

                                      <source> (source) describes the original source for the information contained with a manuscript or object description. [10.9.1.1. Record History]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: recordHist
                                      May contain
                                      Example
                                      <source>Derived from <ref>Stanley (1960)</ref>
                                      </source>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element source { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-sourceDesc.html b/gl/dev/ref-sourceDesc.html index 1b1271758..53fd9d3ae 100644 --- a/gl/dev/ref-sourceDesc.html +++ b/gl/dev/ref-sourceDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <sourceDesc>

                                      <sourceDesc> (source description) 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. [2.2.7. The Source Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Contained by
                                      May contain
                                      Example
                                      <sourceDesc>
                                       <bibl>
                                        <title level="a">The Interesting story of the Children in the Wood</title>. In
                                       <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
                                       <publisher>OUP</publisher>
                                        <date>1968</date>. </bibl>
                                      </sourceDesc>
                                      Example
                                      <sourceDesc>
                                       <p>Born digital: no previous source exists.</p>
                                      </sourceDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.biblLike"/>
                                         <classRef key="model.sourceDescPart"/>
                                         <classRef key="model.listLike"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <sourceDesc>

                                      <sourceDesc> (source description) 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. [2.2.7. The Source Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Contained by
                                      May contain
                                      Example
                                      <sourceDesc>
                                       <bibl>
                                        <title level="a">The Interesting story of the Children in the Wood</title>. In
                                       <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
                                       <publisher>OUP</publisher>
                                        <date>1968</date>. </bibl>
                                      </sourceDesc>
                                      Example
                                      <sourceDesc>
                                       <p>Born digital: no previous source exists.</p>
                                      </sourceDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <alternate minOccurs="1"
                                         maxOccurs="unbounded">

                                         <classRef key="model.biblLike"/>
                                         <classRef key="model.sourceDescPart"/>
                                         <classRef key="model.listLike"/>
                                        </alternate>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element sourceDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                             tei_model.pLike+
                                           | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-sourceDoc.html b/gl/dev/ref-sourceDoc.html index af75f883d..d53daf9c1 100644 --- a/gl/dev/ref-sourceDoc.html +++ b/gl/dev/ref-sourceDoc.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <sourceDoc>

                                      <sourceDoc> contains a transcription or other representation of a single source document potentially forming part of a dossier génétique or collection of sources. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      Note

                                      This element may be used as an alternative to facsimile for TEI documents containing only page images, or for documents containing both images and transcriptions. Transcriptions may be provided within the surface elements making up a source document, in parallel with them as part of a text element, or in both places if the encoder wishes to distinguish these two modes of transcription.

                                      Example
                                      <sourceDoc>
                                       <surfaceGrp n="leaf1">
                                        <surface facs="page1.png">
                                         <zone>All the writing on page 1</zone>
                                        </surface>
                                        <surface>
                                         <graphic url="page2-highRes.png"/>
                                         <graphic url="page2-lowRes.png"/>
                                         <zone>
                                          <line>A line of writing on page 2</line>
                                          <line>Another line of writing on page 2</line>
                                         </zone>
                                        </surface>
                                       </surfaceGrp>
                                      </sourceDoc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.global"/>
                                        <classRef key="model.graphicLike"/>
                                        <elementRef key="surface"/>
                                        <elementRef key="surfaceGrp"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <sourceDoc>

                                      <sourceDoc> contains a transcription or other representation of a single source document potentially forming part of a dossier génétique or collection of sources. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      Note

                                      This element may be used as an alternative to facsimile for TEI documents containing only page images, or for documents containing both images and transcriptions. Transcriptions may be provided within the surface elements making up a source document, in parallel with them as part of a text element, or in both places if the encoder wishes to distinguish these two modes of transcription.

                                      Example
                                      <sourceDoc>
                                       <surfaceGrp n="leaf1">
                                        <surface facs="page1.png">
                                         <zone>All the writing on page 1</zone>
                                        </surface>
                                        <surface>
                                         <graphic url="page2-highRes.png"/>
                                         <graphic url="page2-lowRes.png"/>
                                         <zone>
                                          <line>A line of writing on page 2</line>
                                          <line>Another line of writing on page 2</line>
                                         </zone>
                                        </surface>
                                       </surfaceGrp>
                                      </sourceDoc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.global"/>
                                        <classRef key="model.graphicLike"/>
                                        <elementRef key="surface"/>
                                        <elementRef key="surfaceGrp"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element sourceDoc
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declaring.attributes,
                                          ( tei_model.global | tei_model.graphicLike | tei_surface | tei_surfaceGrp )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-sp.html b/gl/dev/ref-sp.html index f18d19250..4c8fe0474 100644 --- a/gl/dev/ref-sp.html +++ b/gl/dev/ref-sp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <sp>

                                      <sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The who attribute on this element may be used either in addition to the speaker element or as an alternative.

                                      Example
                                      <sp>
                                       <speaker>The reverend Doctor Opimian</speaker>
                                       <p>I do not think I have named a single unpresentable fish.</p>
                                      </sp>
                                      <sp>
                                       <speaker>Mr Gryll</speaker>
                                       <p>Bream, Doctor: there is not much to be said for bream.</p>
                                      </sp>
                                      <sp>
                                       <speaker>The Reverend Doctor Opimian</speaker>
                                       <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p>
                                       <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I
                                         will forbear [...]</p>
                                      </sp>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="speaker"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate>
                                          <elementRef key="lg"/>
                                          <classRef key="model.lLike"/>
                                          <classRef key="model.pLike"/>
                                          <classRef key="model.listLike"/>
                                          <classRef key="model.stageLike"/>
                                          <classRef key="model.attributable"/>
                                         </alternate>
                                         <alternate>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="q"/>
                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <sp>

                                      <sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The who attribute on this element may be used either in addition to the speaker element or as an alternative.

                                      Example
                                      <sp>
                                       <speaker>The reverend Doctor Opimian</speaker>
                                       <p>I do not think I have named a single unpresentable fish.</p>
                                      </sp>
                                      <sp>
                                       <speaker>Mr Gryll</speaker>
                                       <p>Bream, Doctor: there is not much to be said for bream.</p>
                                      </sp>
                                      <sp>
                                       <speaker>The Reverend Doctor Opimian</speaker>
                                       <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p>
                                       <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I
                                         will forbear [...]</p>
                                      </sp>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="speaker"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <sequence minOccurs="1"
                                         maxOccurs="unbounded">

                                         <alternate>
                                          <elementRef key="lg"/>
                                          <classRef key="model.lLike"/>
                                          <classRef key="model.pLike"/>
                                          <classRef key="model.listLike"/>
                                          <classRef key="model.stageLike"/>
                                          <classRef key="model.attributable"/>
                                         </alternate>
                                         <alternate>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <elementRef key="q"/>
                                         </alternate>
                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element sp
                                       {
                                          tei_att.global.attributes,
                                      @@ -41,4 +41,4 @@
                                                ( tei_model.global* | tei_q )
                                             )+
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-space.html b/gl/dev/ref-space.html index fdde41045..4f0e27489 100644 --- a/gl/dev/ref-space.html +++ b/gl/dev/ref-space.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <space>

                                      <space> (space) indicates the location of a significant space in the text. [11.4.1. Space]
                                      Moduletranscr
                                      Attributesatt.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (resp, @cert) att.global.source (@source)
                                      resp(responsible party) (responsible party) indicates the individual responsible for identifying and measuring the space
                                      Derived fromatt.global.responsibility
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      dim(dimension) indicates whether the space is horizontal or vertical.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      horizontal
                                      the space is horizontal.
                                      vertical
                                      the space is vertical.
                                      Note

                                      For irregular shapes in two dimensions, the value for this attribute should reflect the more important of the two dimensions. In conventional left-right scripts, a space with both vertical and horizontal components should be classed as vertical.

                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Note

                                      This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like.

                                      Example
                                      By god if wommen had writen storyes
                                      As <space quantity="7unit="minims"/> han within her oratoryes
                                      Example
                                      στρατηλάτ<space quantity="1unit="chars"/>ου
                                      Schematron

                                      <sch:rule context="tei:space">
                                      <sch:report test="@quantity and @extent">space may have @quantity (a
                                      figure) or @extent (a descriptive text value) but not
                                      both</sch:report>
                                      <sch:report test="@quantity and not(@unit)">If space has @quantity
                                      then @unit is required</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <space>

                                      <space> (space) indicates the location of a significant space in the text. [11.4.1. Space]
                                      Moduletranscr
                                      Attributesatt.typed (@type, @subtype) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (resp, @cert) att.global.source (@source)
                                      resp(responsible party) (responsible party) indicates the individual responsible for identifying and measuring the space
                                      Derived fromatt.global.responsibility
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      dim(dimension) indicates whether the space is horizontal or vertical.
                                      Status Recommended
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      horizontal
                                      the space is horizontal.
                                      vertical
                                      the space is vertical.
                                      Note

                                      For irregular shapes in two dimensions, the value for this attribute should reflect the more important of the two dimensions. In conventional left-right scripts, a space with both vertical and horizontal components should be classed as vertical.

                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Note

                                      This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like.

                                      Example
                                      By god if wommen had writen storyes
                                      As <space quantity="7unit="minims"/> han within her oratoryes
                                      Example
                                      στρατηλάτ<space quantity="1unit="chars"/>ου
                                      Schematron

                                      <sch:rule context="tei:space">
                                      <sch:report test="@quantity and @extent">space may have @quantity (a
                                      figure) or @extent (a descriptive text value) but not
                                      both</sch:report>
                                      <sch:report test="@quantity and not(@unit)">If space has @quantity
                                      then @unit is required</sch:report>
                                      </sch:rule>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element space
                                       {
                                          tei_att.global.attribute.xmlid,
                                      @@ -50,4 +50,4 @@
                                          attribute resp { list { teidata.pointer+ } }?,
                                          attribute dim { "horizontal" | "vertical" }?,
                                          ( tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-speaker.html b/gl/dev/ref-speaker.html index 075b48758..e3183eede 100644 --- a/gl/dev/ref-speaker.html +++ b/gl/dev/ref-speaker.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <speaker>

                                      <speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: sp
                                      May contain
                                      Example
                                      <sp who="#ni #rsa">
                                       <speaker>Nancy and Robert</speaker>
                                       <stage type="delivery">(speaking simultaneously)</stage>
                                       <p>The future? ...</p>
                                      </sp>
                                      <list type="speakers">
                                       <item xml:id="ni"/>
                                       <item xml:id="rsa"/>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element speaker { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <speaker>

                                      <speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: sp
                                      May contain
                                      Example
                                      <sp who="#ni #rsa">
                                       <speaker>Nancy and Robert</speaker>
                                       <stage type="delivery">(speaking simultaneously)</stage>
                                       <p>The future? ...</p>
                                      </sp>
                                      <list type="speakers">
                                       <item xml:id="ni"/>
                                       <item xml:id="rsa"/>
                                      </list>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element speaker { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-sponsor.html b/gl/dev/ref-sponsor.html index 71affb042..23f3a899c 100644 --- a/gl/dev/ref-sponsor.html +++ b/gl/dev/ref-sponsor.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -
                                      <sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      msdescription: msItem
                                      May contain
                                      Note

                                      Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element funder), who provide the funding but do not necessarily take intellectual responsibility.

                                      Example
                                      <sponsor>Association for Computers and the Humanities</sponsor>
                                      <sponsor>Association for Computational Linguistics</sponsor>
                                      <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                      +    
                                      <sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      core: bibl monogr
                                      msdescription: msItem
                                      May contain
                                      Note

                                      Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element funder), who provide the funding but do not necessarily take intellectual responsibility.

                                      Example
                                      <sponsor>Association for Computers and the Humanities</sponsor>
                                      <sponsor>Association for Computational Linguistics</sponsor>
                                      <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq.limited"/>
                                      </content>
                                      Schema Declaration
                                       element sponsor
                                       {
                                          tei_att.global.attributes,
                                          tei_att.canonical.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq.limited
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-stage.html b/gl/dev/ref-stage.html index 01dfef59a..527875083 100644 --- a/gl/dev/ref-stage.html +++ b/gl/dev/ref-stage.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <stage>

                                      <stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions]
                                      Modulecore
                                      Attributesatt.ascribed.directed (@toWhom) (att.ascribed (@who)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.written (@hand)
                                      typeindicates the kind of stage direction.
                                      Status Recommended
                                      Datatype 0–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      setting
                                      describes a setting.
                                      entrance
                                      describes an entrance.
                                      exit
                                      describes an exit.
                                      business
                                      describes stage business.
                                      novelistic
                                      is a narrative, motivating stage direction.
                                      delivery
                                      describes how a character speaks.
                                      modifier
                                      gives some detail about a character.
                                      location
                                      describes a location.
                                      mixed
                                      more than one of the above
                                      Note

                                      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.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

                                      Example
                                      <stage type="setting">A curtain being drawn.</stage>
                                      <stage type="setting">Music</stage>
                                      <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage>
                                      <!-- Middleton : Yorkshire Tragedy -->
                                      <stage type="exit">Exit pursued by a bear.</stage>
                                      <stage type="business">He quickly takes the stone out.</stage>
                                      <stage type="delivery">To Lussurioso.</stage>
                                      <stage type="novelistic">Having had enough, and embarrassed for the family.</stage>
                                      <!-- Lorraine Hansbury : a raisin in in the sun -->
                                      <stage type="modifier">Disguised as Ansaldo.</stage>
                                      <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage>
                                      <!-- Middleton: The Widow -->
                                      <stage type="location">At a window.</stage>
                                      <stage rend="inlinetype="delivery">Aside.</stage>
                                      Example
                                      <l>Behold. <stage n="*place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when
                                         straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on
                                         two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the
                                       <hi>Prologue</hi> was spoken, which being ended, they descended in
                                         order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our
                                      Poet knowing our free hearts</l>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <stage>

                                      <stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions]
                                      Modulecore
                                      Attributesatt.ascribed.directed (@toWhom) (att.ascribed (@who)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.written (@hand)
                                      typeindicates the kind of stage direction.
                                      Status Recommended
                                      Datatype 0–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      setting
                                      describes a setting.
                                      entrance
                                      describes an entrance.
                                      exit
                                      describes an exit.
                                      business
                                      describes stage business.
                                      novelistic
                                      is a narrative, motivating stage direction.
                                      delivery
                                      describes how a character speaks.
                                      modifier
                                      gives some detail about a character.
                                      location
                                      describes a location.
                                      mixed
                                      more than one of the above
                                      Note

                                      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.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

                                      Example
                                      <stage type="setting">A curtain being drawn.</stage>
                                      <stage type="setting">Music</stage>
                                      <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage>
                                      <!-- Middleton : Yorkshire Tragedy -->
                                      <stage type="exit">Exit pursued by a bear.</stage>
                                      <stage type="business">He quickly takes the stone out.</stage>
                                      <stage type="delivery">To Lussurioso.</stage>
                                      <stage type="novelistic">Having had enough, and embarrassed for the family.</stage>
                                      <!-- Lorraine Hansbury : a raisin in in the sun -->
                                      <stage type="modifier">Disguised as Ansaldo.</stage>
                                      <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage>
                                      <!-- Middleton: The Widow -->
                                      <stage type="location">At a window.</stage>
                                      <stage rend="inlinetype="delivery">Aside.</stage>
                                      Example
                                      <l>Behold. <stage n="*place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when
                                         straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on
                                         two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the
                                       <hi>Prologue</hi> was spoken, which being ended, they descended in
                                         order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our
                                      Poet knowing our free hearts</l>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element stage
                                       {
                                          tei_att.ascribed.directed.attributes,
                                      @@ -47,4 +47,4 @@
                                             }
                                          }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-stamp.html b/gl/dev/ref-stamp.html index cb0818b93..2a2a80e83 100644 --- a/gl/dev/ref-stamp.html +++ b/gl/dev/ref-stamp.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <stamp>

                                      <stamp> (stamp) contains a word or phrase describing a stamp or similar device. [10.3.3. Watermarks and Stamps]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/>
                                      SI NON LICET<lb/>
                                      NOBIS RO<lb/>
                                      manii imperii <stamp>Bodleian stamp</stamp>
                                       <lb/>
                                      </rubric>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <stamp>

                                      <stamp> (stamp) contains a word or phrase describing a stamp or similar device. [10.3.3. Watermarks and Stamps]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/>
                                      SI NON LICET<lb/>
                                      NOBIS RO<lb/>
                                      manii imperii <stamp>Bodleian stamp</stamp>
                                       <lb/>
                                      </rubric>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element stamp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.datable.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-standOff.html b/gl/dev/ref-standOff.html index 278a0c5e2..6fe1300b0 100644 --- a/gl/dev/ref-standOff.html +++ b/gl/dev/ref-standOff.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <standOff>

                                      <standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      Example

                                      This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).

                                      <TEI xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                      <!-- ... -->
                                       </teiHeader>
                                       <text>
                                        <body>
                                      <!-- ... -->
                                         <p>
                                          <w xml:id="w51">I</w>
                                          <w xml:id="w52">wanna</w>
                                          <w xml:id="w53">put</w>
                                          <w xml:id="w54">up</w>
                                          <w xml:id="w55">new</w>
                                          <w xml:id="w56">wallpaper</w>
                                          <pc>.</pc>
                                         </p>
                                      <!-- ... -->
                                        </body>
                                       </text>
                                       <standOff type="morphosyntax">
                                        <spanGrp type="wordForm">
                                         <span target="#w51ana="#fs01"/>
                                         <span target="#w52ana="#fs02"/>
                                         <span target="#w52ana="#fs03"/>
                                         <span target="#w53 #w54ana="#fs04"/>
                                         <span target="#w55ana="#fs05"/>
                                         <span target="#w56ana="#fs06"/>
                                        </spanGrp>
                                        <fs xml:id="fs01">
                                         <f name="lemma">
                                          <string>I</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="PP"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs02">
                                         <f name="lemma">
                                          <string>want</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="VBP"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs03">
                                         <f name="lemma">
                                          <string>to</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="TO"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs04">
                                         <f name="lemma">
                                          <string>put up</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="VB"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs05">
                                         <f name="lemma">
                                          <string>new</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="JJ"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs06">
                                         <f name="lemma">
                                          <string>wallpaper</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="NN"/>
                                         </f>
                                        </fs>
                                       </standOff>
                                      </TEI>
                                      Example

                                      This example shows an encoding of contextual information which is referred to from the main text.

                                      <TEI xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                      <!-- ... -->
                                       </teiHeader>
                                       <standOff>
                                        <listPlace>
                                         <place xml:id="LATL">
                                          <placeName>Atlanta</placeName>
                                          <location>
                                           <region key="US-GA">Georgia</region>
                                           <country key="USA">United States of America</country>
                                           <geo>33.755 -84.39</geo>
                                          </location>
                                          <population when="1963"
                                           type="interpolatedCensusquantity="489359"
                                           source="https://www.biggestuscities.com/city/atlanta-georgia"/>

                                         </place>
                                         <place xml:id="LBHM">
                                          <placeName>Birmingham</placeName>
                                          <location>
                                           <region key="US-AL">Alabama</region>
                                           <country key="USA">United States of America</country>
                                           <geo>33.653333 -86.808889</geo>
                                          </location>
                                          <population when="1963"
                                           type="interpolatedCensusquantity="332891"
                                           source="https://www.biggestuscities.com/city/birmingham-alabama"/>

                                         </place>
                                        </listPlace>
                                       </standOff>
                                       <text>
                                        <body>
                                      <!-- ... -->
                                         <p>Moreover, I am <choice>
                                           <sic>congnizant</sic>
                                           <corr>cognizant</corr>
                                          </choice> of the interrelatedness of all communities and
                                         <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens
                                         <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We
                                         <lb/>are caught in an inescapable network of mutuality, tied in a single garment
                                         <lb/>of destiny. Whatever affects one directly affects all indirectly. Never
                                         <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>
                                          <lb/>idea. Anyone who lives inside the United States can never be considered
                                         <lb/>an outsider anywhere in this country.</p>
                                      <!-- ... -->
                                        </body>
                                       </text>
                                      </TEI>
                                      Schematron

                                      <sch:assert test="@type or not(ancestor::tei:standOff)">This
                                      <sch:name/> element must have a @type attribute, since it is
                                      nested inside a <sch:name/>
                                      </sch:assert>
                                      Content model
                                      <content>
                                       <classRef key="model.standOffPart"
                                        minOccurs="1maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <standOff>

                                      <standOff> Functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [16.10. The standOff Container]
                                      Modulelinking
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.declaring (@decls)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      Example

                                      This example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).

                                      <TEI xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                      <!-- ... -->
                                       </teiHeader>
                                       <text>
                                        <body>
                                      <!-- ... -->
                                         <p>
                                          <w xml:id="w51">I</w>
                                          <w xml:id="w52">wanna</w>
                                          <w xml:id="w53">put</w>
                                          <w xml:id="w54">up</w>
                                          <w xml:id="w55">new</w>
                                          <w xml:id="w56">wallpaper</w>
                                          <pc>.</pc>
                                         </p>
                                      <!-- ... -->
                                        </body>
                                       </text>
                                       <standOff type="morphosyntax">
                                        <spanGrp type="wordForm">
                                         <span target="#w51ana="#fs01"/>
                                         <span target="#w52ana="#fs02"/>
                                         <span target="#w52ana="#fs03"/>
                                         <span target="#w53 #w54ana="#fs04"/>
                                         <span target="#w55ana="#fs05"/>
                                         <span target="#w56ana="#fs06"/>
                                        </spanGrp>
                                        <fs xml:id="fs01">
                                         <f name="lemma">
                                          <string>I</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="PP"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs02">
                                         <f name="lemma">
                                          <string>want</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="VBP"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs03">
                                         <f name="lemma">
                                          <string>to</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="TO"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs04">
                                         <f name="lemma">
                                          <string>put up</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="VB"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs05">
                                         <f name="lemma">
                                          <string>new</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="JJ"/>
                                         </f>
                                        </fs>
                                        <fs xml:id="fs06">
                                         <f name="lemma">
                                          <string>wallpaper</string>
                                         </f>
                                         <f name="pos">
                                          <symbol value="NN"/>
                                         </f>
                                        </fs>
                                       </standOff>
                                      </TEI>
                                      Example

                                      This example shows an encoding of contextual information which is referred to from the main text.

                                      <TEI xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                      <!-- ... -->
                                       </teiHeader>
                                       <standOff>
                                        <listPlace>
                                         <place xml:id="LATL">
                                          <placeName>Atlanta</placeName>
                                          <location>
                                           <region key="US-GA">Georgia</region>
                                           <country key="USA">United States of America</country>
                                           <geo>33.755 -84.39</geo>
                                          </location>
                                          <population when="1963"
                                           type="interpolatedCensusquantity="489359"
                                           source="https://www.biggestuscities.com/city/atlanta-georgia"/>

                                         </place>
                                         <place xml:id="LBHM">
                                          <placeName>Birmingham</placeName>
                                          <location>
                                           <region key="US-AL">Alabama</region>
                                           <country key="USA">United States of America</country>
                                           <geo>33.653333 -86.808889</geo>
                                          </location>
                                          <population when="1963"
                                           type="interpolatedCensusquantity="332891"
                                           source="https://www.biggestuscities.com/city/birmingham-alabama"/>

                                         </place>
                                        </listPlace>
                                       </standOff>
                                       <text>
                                        <body>
                                      <!-- ... -->
                                         <p>Moreover, I am <choice>
                                           <sic>congnizant</sic>
                                           <corr>cognizant</corr>
                                          </choice> of the interrelatedness of all communities and
                                         <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens
                                         <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We
                                         <lb/>are caught in an inescapable network of mutuality, tied in a single garment
                                         <lb/>of destiny. Whatever affects one directly affects all indirectly. Never
                                         <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>
                                          <lb/>idea. Anyone who lives inside the United States can never be considered
                                         <lb/>an outsider anywhere in this country.</p>
                                      <!-- ... -->
                                        </body>
                                       </text>
                                      </TEI>
                                      Schematron

                                      <sch:assert test="@type or not(ancestor::tei:standOff)">This
                                      <sch:name/> element must have a @type attribute, since it is
                                      nested inside a <sch:name/>
                                      </sch:assert>
                                      Content model
                                      <content>
                                       <classRef key="model.standOffPart"
                                        minOccurs="1maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element standOff
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.declaring.attributes,
                                          tei_model.standOffPart+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-state.html b/gl/dev/ref-state.html index 8858b6d1a..bce576787 100644 --- a/gl/dev/ref-state.html +++ b/gl/dev/ref-state.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <state>

                                      <state> (state) 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. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: precision
                                      header: biblFull
                                      linking: ab
                                      msdescription: msDesc
                                      namesdates: state
                                      Note

                                      Where there is confusion between <trait> and state the more general purpose element state should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The state element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

                                      Example
                                      <state ref="#SCHOLtype="status">
                                       <label>scholar</label>
                                      </state>
                                      Example
                                      <org>
                                       <orgName notAfter="1960">The Silver Beetles</orgName>
                                       <orgName notBefore="1960">The Beatles</orgName>
                                       <state type="membershipfrom="1960-08"
                                        to="1962-05">

                                        <desc>
                                         <persName>John Lennon</persName>
                                         <persName>Paul McCartney</persName>
                                         <persName>George Harrison</persName>
                                         <persName>Stuart Sutcliffe</persName>
                                         <persName>Pete Best</persName>
                                        </desc>
                                       </state>
                                       <state type="membershipnotBefore="1963">
                                        <desc>
                                         <persName>John Lennon</persName>
                                         <persName>Paul McCartney</persName>
                                         <persName>George Harrison</persName>
                                         <persName>Ringo Starr</persName>
                                        </desc>
                                       </state>
                                      </org>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="precisionminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate>
                                         <elementRef key="stateminOccurs="1"
                                          maxOccurs="unbounded"/>

                                         <sequence>
                                          <classRef key="model.headLike"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <classRef key="model.pLike"
                                           minOccurs="1maxOccurs="unbounded"/>

                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.noteLike"/>
                                           <classRef key="model.biblLike"/>
                                          </alternate>
                                         </sequence>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.labelLike"/>
                                          <classRef key="model.noteLike"/>
                                          <classRef key="model.biblLike"/>
                                         </alternate>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <state>

                                      <state> (state) 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. [13.3.1. Basic Principles 13.3.2.1. Personal Characteristics]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @instant) att.typed (@type, @subtype) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: precision
                                      header: biblFull
                                      linking: ab
                                      msdescription: msDesc
                                      namesdates: state
                                      Note

                                      Where there is confusion between <trait> and state the more general purpose element state should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The state element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

                                      Example
                                      <state ref="#SCHOLtype="status">
                                       <label>scholar</label>
                                      </state>
                                      Example
                                      <org>
                                       <orgName notAfter="1960">The Silver Beetles</orgName>
                                       <orgName notBefore="1960">The Beatles</orgName>
                                       <state type="membershipfrom="1960-08"
                                        to="1962-05">

                                        <desc>
                                         <persName>John Lennon</persName>
                                         <persName>Paul McCartney</persName>
                                         <persName>George Harrison</persName>
                                         <persName>Stuart Sutcliffe</persName>
                                         <persName>Pete Best</persName>
                                        </desc>
                                       </state>
                                       <state type="membershipnotBefore="1963">
                                        <desc>
                                         <persName>John Lennon</persName>
                                         <persName>Paul McCartney</persName>
                                         <persName>George Harrison</persName>
                                         <persName>Ringo Starr</persName>
                                        </desc>
                                       </state>
                                      </org>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="precisionminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <alternate>
                                         <elementRef key="stateminOccurs="1"
                                          maxOccurs="unbounded"/>

                                         <sequence>
                                          <classRef key="model.headLike"
                                           minOccurs="0maxOccurs="unbounded"/>

                                          <classRef key="model.pLike"
                                           minOccurs="1maxOccurs="unbounded"/>

                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <classRef key="model.noteLike"/>
                                           <classRef key="model.biblLike"/>
                                          </alternate>
                                         </sequence>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <classRef key="model.labelLike"/>
                                          <classRef key="model.noteLike"/>
                                          <classRef key="model.biblLike"/>
                                         </alternate>
                                        </alternate>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element state
                                       {
                                          tei_att.global.attributes,
                                      @@ -42,4 +42,4 @@
                                              | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-stdVals.html b/gl/dev/ref-stdVals.html index 836ba7013..fee6fd16a 100644 --- a/gl/dev/ref-stdVals.html +++ b/gl/dev/ref-stdVals.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <stdVals>

                                      <stdVals> (standard values) specifies the format used when standardized date or number values are supplied. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <stdVals>
                                       <p>All integer numbers are left-filled with zeroes to 8 digits.</p>
                                      </stdVals>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <stdVals>

                                      <stdVals> (standard values) specifies the format used when standardized date or number values are supplied. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <stdVals>
                                       <p>All integer numbers are left-filled with zeroes to 8 digits.</p>
                                      </stdVals>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element stdVals
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          tei_model.pLike+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-street.html b/gl/dev/ref-street.html index b1d2c2eac..84d125cfb 100644 --- a/gl/dev/ref-street.html +++ b/gl/dev/ref-street.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <street>

                                      <street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May contain
                                      Note

                                      The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned.

                                      Example
                                      <street>via della Faggiola, 36</street>
                                      Example
                                      <street>
                                       <name>Duntaggin</name>, 110 Southmoor Road
                                      </street>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element street { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <street>

                                      <street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      core: address
                                      May contain
                                      Note

                                      The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned.

                                      Example
                                      <street>via della Faggiola, 36</street>
                                      Example
                                      <street>
                                       <name>Duntaggin</name>, 110 Southmoor Road
                                      </street>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element street { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-styleDefDecl.html b/gl/dev/ref-styleDefDecl.html index 95880a60c..a0933c9b1 100644 --- a/gl/dev/ref-styleDefDecl.html +++ b/gl/dev/ref-styleDefDecl.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <styleDefDecl>

                                      <styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.styleDef (@scheme, @schemeVersion)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <styleDefDecl scheme="css"
                                       schemeVersion="2.1"/>

                                      <!-- ... -->
                                      <tagsDecl>
                                       <rendition xml:id="boldface">font-weight: bold;</rendition>
                                       <rendition xml:id="italicstyle">font-style: italic;</rendition>
                                      </tagsDecl>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <styleDefDecl>

                                      <styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.styleDef (@scheme, @schemeVersion)
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      Example
                                      <styleDefDecl scheme="css"
                                       schemeVersion="2.1"/>

                                      <!-- ... -->
                                      <tagsDecl>
                                       <rendition xml:id="boldface">font-weight: bold;</rendition>
                                       <rendition xml:id="italicstyle">font-style: italic;</rendition>
                                      </tagsDecl>
                                      Content model
                                      <content>
                                       <classRef key="model.pLikeminOccurs="0"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element styleDefDecl
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          tei_att.styleDef.attributes,
                                          tei_model.pLike*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-subst.html b/gl/dev/ref-subst.html index 0e104bd27..74a14cdc7 100644 --- a/gl/dev/ref-subst.html +++ b/gl/dev/ref-subst.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <subst>

                                      <subst> (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      linking: anchor
                                      transcr: fw surplus
                                      Example
                                      ... are all included. <del hand="#RG">It is</del>
                                      <subst>
                                       <add>T</add>
                                       <del>t</del>
                                      </subst>he expressed
                                      Example
                                      that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>
                                       <del>very</del>
                                       <lb/>
                                       <add>principally</add>
                                      </subst> remembered in her Will.
                                      Example
                                      <ab>τ<subst>
                                        <add place="above">ῶν</add>
                                        <del>α</del>
                                       </subst>
                                      συνκυρόντ<subst>
                                        <add place="above">ων</add>
                                        <del>α</del>
                                       </subst>
                                      ἐργαστηρί<subst>
                                        <add place="above">ων</add>
                                        <del>α</del>
                                       </subst>
                                      </ab>
                                      Example
                                      <subst>
                                       <del>
                                        <gap reason="illegiblequantity="5"
                                         unit="character"/>

                                       </del>
                                       <add>apple</add>
                                      </subst>
                                      Schematron

                                      <s:assert test="child::tei:add and (child::tei:del or child::tei:surplus)">
                                      <s:name/> must have at least one child add and at least one child del or surplus</s:assert>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <elementRef key="add"/>
                                        <elementRef key="surplus"/>
                                        <elementRef key="del"/>
                                        <classRef key="model.milestoneLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <subst>

                                      <subst> (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      linking: anchor
                                      transcr: fw surplus
                                      Example
                                      ... are all included. <del hand="#RG">It is</del>
                                      <subst>
                                       <add>T</add>
                                       <del>t</del>
                                      </subst>he expressed
                                      Example
                                      that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>
                                       <del>very</del>
                                       <lb/>
                                       <add>principally</add>
                                      </subst> remembered in her Will.
                                      Example
                                      <ab>τ<subst>
                                        <add place="above">ῶν</add>
                                        <del>α</del>
                                       </subst>
                                      συνκυρόντ<subst>
                                        <add place="above">ων</add>
                                        <del>α</del>
                                       </subst>
                                      ἐργαστηρί<subst>
                                        <add place="above">ων</add>
                                        <del>α</del>
                                       </subst>
                                      </ab>
                                      Example
                                      <subst>
                                       <del>
                                        <gap reason="illegiblequantity="5"
                                         unit="character"/>

                                       </del>
                                       <add>apple</add>
                                      </subst>
                                      Schematron

                                      <s:assert test="child::tei:add and (child::tei:del or child::tei:surplus)">
                                      <s:name/> must have at least one child add and at least one child del or surplus</s:assert>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <elementRef key="add"/>
                                        <elementRef key="surplus"/>
                                        <elementRef key="del"/>
                                        <classRef key="model.milestoneLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element subst
                                       {
                                          tei_att.global.attributes,
                                          tei_att.transcriptional.attributes,
                                          tei_att.dimensions.attributes,
                                          ( tei_add | tei_surplus | tei_del | tei_model.milestoneLike )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-substJoin.html b/gl/dev/ref-substJoin.html index bcbc25322..0d4efcf68 100644 --- a/gl/dev/ref-substJoin.html +++ b/gl/dev/ref-substJoin.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <substJoin>

                                      <substJoin> (substitution join) identifies a series of possibly fragmented additions, deletions, or other revisions on a manuscript that combine to make up a single intervention in the text [11.3.1.5. Substitutions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example
                                      While <del xml:id="r112">pondering</del> thus <add xml:id="r113">she mus'd</add>, her pinions fann'd
                                      <substJoin target="#r112 #r113"/>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <substJoin>

                                      <substJoin> (substitution join) identifies a series of possibly fragmented additions, deletions, or other revisions on a manuscript that combine to make up a single intervention in the text [11.3.1.5. Substitutions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      certainty: certainty precision
                                      core: desc
                                      Example
                                      While <del xml:id="r112">pondering</del> thus <add xml:id="r113">she mus'd</add>, her pinions fann'd
                                      <substJoin target="#r112 #r113"/>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.descLike"/>
                                        <classRef key="model.certLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element substJoin
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.transcriptional.attributes,
                                          tei_att.dimensions.attributes,
                                          ( tei_model.descLike | tei_model.certLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-summary.html b/gl/dev/ref-summary.html index b6f2a7e96..72c202ec3 100644 --- a/gl/dev/ref-summary.html +++ b/gl/dev/ref-summary.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <summary>

                                      <summary> contains an overview of the available information concerning some aspect of an item or object (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [10.6. Intellectual Content]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <summary>This item consists of three books with a prologue and an epilogue.
                                      </summary>
                                      Example
                                      <typeDesc>
                                       <summary>Uses a mixture of Roman and Black Letter types.</summary>
                                       <typeNote>Antiqua typeface, showing influence of Jenson's Venetian
                                         fonts.</typeNote>
                                       <typeNote>The black letter face is a variant of Schwabacher.</typeNote>
                                      </typeDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element summary { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <summary>

                                      <summary> contains an overview of the available information concerning some aspect of an item or object (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [10.6. Intellectual Content]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <summary>This item consists of three books with a prologue and an epilogue.
                                      </summary>
                                      Example
                                      <typeDesc>
                                       <summary>Uses a mixture of Roman and Black Letter types.</summary>
                                       <typeNote>Antiqua typeface, showing influence of Jenson's Venetian
                                         fonts.</typeNote>
                                       <typeNote>The black letter face is a variant of Schwabacher.</typeNote>
                                      </typeDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element summary { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-supplied.html b/gl/dev/ref-supplied.html index 353e38aca..edf838516 100644 --- a/gl/dev/ref-supplied.html +++ b/gl/dev/ref-supplied.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <supplied>

                                      <supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (evidence, @instant)
                                      evidence
                                      Status Optional
                                      Datatype teidata.word
                                      Suggested values include:
                                      parallel
                                      Characters supplied from a parallel version of this text, absent from this one
                                      previouseditor
                                      Characters visible to a previous editor, now lost/unclear due to damage
                                      reason
                                      Status Required
                                      Legal values are:
                                      lost
                                      Restoration of text completely lost from the surface
                                      omitted
                                      Supplement of text erroneously omitted from the surface by the scribe/cutter
                                      subaudible
                                      Editorial supplement of words subaudible to the native reader
                                      explanation
                                      Editorial explanation of oblique text in original
                                      undefined
                                      Text restored (e.g. from earlier witness or alternate copy) without specification of current state of this text
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The damage, gap, del, unclear and supplied elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      Example
                                      I am dr Sr yr
                                      <supplied reason="illegible"
                                       source="#amanuensis_copy">
                                      very humble Servt</supplied>
                                      Sydney Smith
                                      Example
                                      <supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <supplied>

                                      <supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (evidence, @instant)
                                      evidence
                                      Status Optional
                                      Datatype teidata.word
                                      Suggested values include:
                                      parallel
                                      Characters supplied from a parallel version of this text, absent from this one
                                      previouseditor
                                      Characters visible to a previous editor, now lost/unclear due to damage
                                      reason
                                      Status Required
                                      Legal values are:
                                      lost
                                      Restoration of text completely lost from the surface
                                      omitted
                                      Supplement of text erroneously omitted from the surface by the scribe/cutter
                                      subaudible
                                      Editorial supplement of words subaudible to the native reader
                                      explanation
                                      Editorial explanation of oblique text in original
                                      undefined
                                      Text restored (e.g. from earlier witness or alternate copy) without specification of current state of this text
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The damage, gap, del, unclear and supplied elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      Example
                                      I am dr Sr yr
                                      <supplied reason="illegible"
                                       source="#amanuensis_copy">
                                      very humble Servt</supplied>
                                      Sydney Smith
                                      Example
                                      <supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element supplied
                                       {
                                          tei_att.global.attributes,
                                      @@ -33,4 +33,4 @@
                                             "lost" | "omitted" | "subaudible" | "explanation" | "undefined"
                                          },
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-support.html b/gl/dev/ref-support.html index cad256c42..9243691da 100644 --- a/gl/dev/ref-support.html +++ b/gl/dev/ref-support.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <support>

                                      <support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <objectDesc form="roll">
                                       <supportDesc>
                                        <support> Parchment roll with <material>silk</material> ribbons.
                                        </support>
                                       </supportDesc>
                                      </objectDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element support { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <support>

                                      <support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: supportDesc
                                      May contain
                                      Example
                                      <objectDesc form="roll">
                                       <supportDesc>
                                        <support> Parchment roll with <material>silk</material> ribbons.
                                        </support>
                                       </supportDesc>
                                      </objectDesc>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element support { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-supportDesc.html b/gl/dev/ref-supportDesc.html index 4cb37c565..465dbc6c3 100644 --- a/gl/dev/ref-supportDesc.html +++ b/gl/dev/ref-supportDesc.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <supportDesc>

                                      <supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      material(material) a short project-defined name for the material composing the majority of the support
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      paper
                                      parch
                                      (parchment)
                                      mixed
                                      Contained by
                                      msdescription: objectDesc
                                      May contain
                                      core: p
                                      header: extent
                                      linking: ab
                                      Example
                                      <supportDesc>
                                       <support> Parchment roll with <material>silk</material> ribbons.
                                       </support>
                                      </supportDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="supportminOccurs="0"/>
                                         <elementRef key="extentminOccurs="0"/>
                                         <elementRef key="foliation"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="collation"
                                          minOccurs="0"/>

                                         <elementRef key="condition"
                                          minOccurs="0"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <supportDesc>

                                      <supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      material(material) a short project-defined name for the material composing the majority of the support
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Suggested values include:
                                      paper
                                      parch
                                      (parchment)
                                      mixed
                                      Contained by
                                      msdescription: objectDesc
                                      May contain
                                      core: p
                                      header: extent
                                      linking: ab
                                      Example
                                      <supportDesc>
                                       <support> Parchment roll with <material>silk</material> ribbons.
                                       </support>
                                      </supportDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="supportminOccurs="0"/>
                                         <elementRef key="extentminOccurs="0"/>
                                         <elementRef key="foliation"
                                          minOccurs="0maxOccurs="unbounded"/>

                                         <elementRef key="collation"
                                          minOccurs="0"/>

                                         <elementRef key="condition"
                                          minOccurs="0"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element supportDesc
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                                tei_condition?
                                             )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-surface.html b/gl/dev/ref-surface.html index 6889fde81..6ea345252 100644 --- a/gl/dev/ref-surface.html +++ b/gl/dev/ref-surface.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <surface>

                                      <surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.declaring (@decls) att.typed (@type, @subtype)
                                      attachmentdescribes the method by which this surface is or was connected to the main surface
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      glued
                                      glued in place
                                      pinned
                                      pinned or stapled in place
                                      sewn
                                      sewn in place
                                      flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Contained by
                                      May contain
                                      Note

                                      The surface element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

                                      The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

                                      The surface element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every zone element contained by this element are to be understood with reference to the same grid.

                                      Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the surfaceGrp element.

                                      Example
                                      <facsimile>
                                       <surface ulx="0uly="0lrx="200lry="300">
                                        <graphic url="Bovelles-49r.png"/>
                                       </surface>
                                      </facsimile>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.global"/>
                                         <classRef key="model.labelLike"/>
                                         <classRef key="model.graphicLike"/>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <alternate>
                                          <elementRef key="zone"/>
                                          <elementRef key="line"/>
                                          <elementRef key="path"/>
                                          <elementRef key="surface"/>
                                          <elementRef key="surfaceGrp"/>
                                         </alternate>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <surface>

                                      <surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.declaring (@decls) att.typed (@type, @subtype)
                                      attachmentdescribes the method by which this surface is or was connected to the main surface
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      glued
                                      glued in place
                                      pinned
                                      pinned or stapled in place
                                      sewn
                                      sewn in place
                                      flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
                                      Status Optional
                                      Datatype teidata.truthValue
                                      Contained by
                                      May contain
                                      Note

                                      The surface element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

                                      The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

                                      The surface element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every zone element contained by this element are to be understood with reference to the same grid.

                                      Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the surfaceGrp element.

                                      Example
                                      <facsimile>
                                       <surface ulx="0uly="0lrx="200lry="300">
                                        <graphic url="Bovelles-49r.png"/>
                                       </surface>
                                      </facsimile>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.global"/>
                                         <classRef key="model.labelLike"/>
                                         <classRef key="model.graphicLike"/>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <alternate>
                                          <elementRef key="zone"/>
                                          <elementRef key="line"/>
                                          <elementRef key="path"/>
                                          <elementRef key="surface"/>
                                          <elementRef key="surfaceGrp"/>
                                         </alternate>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element surface
                                       {
                                          tei_att.global.attributes,
                                      @@ -37,4 +37,4 @@
                                                tei_model.global*
                                             )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-surfaceGrp.html b/gl/dev/ref-surfaceGrp.html index 91c56f64f..7df5d71da 100644 --- a/gl/dev/ref-surfaceGrp.html +++ b/gl/dev/ref-surfaceGrp.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <surfaceGrp>

                                      <surfaceGrp> (surface group) defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
                                      Contained by
                                      May contain
                                      Note

                                      Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the surfaceGrp elements.

                                      Example
                                      <sourceDoc>
                                       <surfaceGrp>
                                        <surface ulx="0uly="0lrx="200"
                                         lry="300">

                                         <graphic url="Bovelles-49r.png"/>
                                        </surface>
                                        <surface ulx="0uly="0lrx="200"
                                         lry="300">

                                         <graphic url="Bovelles-49v.png"/>
                                        </surface>
                                       </surfaceGrp>
                                      </sourceDoc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.global"/>
                                        <elementRef key="surface"/>
                                        <elementRef key="surfaceGrp"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <surfaceGrp>

                                      <surfaceGrp> (surface group) defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
                                      Contained by
                                      May contain
                                      Note

                                      Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the surfaceGrp elements.

                                      Example
                                      <sourceDoc>
                                       <surfaceGrp>
                                        <surface ulx="0uly="0lrx="200"
                                         lry="300">

                                         <graphic url="Bovelles-49r.png"/>
                                        </surface>
                                        <surface ulx="0uly="0lrx="200"
                                         lry="300">

                                         <graphic url="Bovelles-49v.png"/>
                                        </surface>
                                       </surfaceGrp>
                                      </sourceDoc>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.global"/>
                                        <elementRef key="surface"/>
                                        <elementRef key="surfaceGrp"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element surfaceGrp
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declaring.attributes,
                                          tei_att.typed.attributes,
                                          ( tei_model.global | tei_surface | tei_surfaceGrp )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-surname.html b/gl/dev/ref-surname.html index b0b041785..635f2dc63 100644 --- a/gl/dev/ref-surname.html +++ b/gl/dev/ref-surname.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <surname>

                                      <surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <surname type="combine">St John Stevas</surname>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <surname>

                                      <surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
                                      Modulenamesdates
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <surname type="combine">St John Stevas</surname>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element surname
                                       {
                                          tei_att.global.attributes,
                                          tei_att.personal.attributes,
                                          tei_att.typed.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-surplus.html b/gl/dev/ref-surplus.html index 38343ced9..4738184f1 100644 --- a/gl/dev/ref-surplus.html +++ b/gl/dev/ref-surplus.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <surplus>

                                      <surplus> (surplus) marks text present in the source which the editor believes to be superfluous or redundant. [11.3.3.1. Damage, Illegibility, and Supplied Text]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      reasonone or more words indicating why this text is believed to be superfluous, e.g. repeated, interpolated etc.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      I am dr Sr yrs
                                      <surplus reason="repeated">yrs</surplus>
                                      Sydney Smith
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <surplus>

                                      <surplus> (surplus) marks text present in the source which the editor believes to be superfluous or redundant. [11.3.3.1. Damage, Illegibility, and Supplied Text]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      reasonone or more words indicating why this text is believed to be superfluous, e.g. repeated, interpolated etc.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.word separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      I am dr Sr yrs
                                      <surplus reason="repeated">yrs</surplus>
                                      Sydney Smith
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element surplus
                                       {
                                          tei_att.global.attributes,
                                      @@ -29,4 +29,4 @@
                                          tei_att.dimensions.attributes,
                                          attribute reason { list { teidata.word+ } }?,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-surrogates.html b/gl/dev/ref-surrogates.html index af7223b00..785dd0cd1 100644 --- a/gl/dev/ref-surrogates.html +++ b/gl/dev/ref-surrogates.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <surrogates>

                                      <surrogates> (surrogates) contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere. [10.9. Additional Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: additional
                                      May contain
                                      Example
                                      <surrogates>
                                       <bibl>
                                        <title type="gmd">diapositive</title>
                                        <idno>AM 74 a, fol.</idno>
                                        <date>May 1984</date>
                                       </bibl>
                                       <bibl>
                                        <title type="gmd">b/w prints</title>
                                        <idno>AM 75 a, fol.</idno>
                                        <date>1972</date>
                                       </bibl>
                                      </surrogates>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      -element surrogates { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <surrogates>

                                      <surrogates> (surrogates) contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere. [10.9. Additional Information]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      msdescription: additional
                                      May contain
                                      Example
                                      <surrogates>
                                       <bibl>
                                        <title type="gmd">diapositive</title>
                                        <idno>AM 74 a, fol.</idno>
                                        <date>May 1984</date>
                                       </bibl>
                                       <bibl>
                                        <title type="gmd">b/w prints</title>
                                        <idno>AM 75 a, fol.</idno>
                                        <date>1972</date>
                                       </bibl>
                                      </surrogates>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +element surrogates { tei_att.global.attributes, tei_macro.specialPara }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-table.html b/gl/dev/ref-table.html index 5a351e16d..2bbcac17e 100644 --- a/gl/dev/ref-table.html +++ b/gl/dev/ref-table.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <table>

                                      <table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      rows(rows) indicates the number of rows in the table.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      If no number is supplied, an application must calculate the number of rows.

                                      Rows should be presented from top to bottom.

                                      cols(columns) indicates the number of columns in each row of the table.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      If no number is supplied, an application must calculate the number of columns.

                                      Within each row, columns should be presented left to right.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Contains an optional heading and a series of rows.

                                      Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

                                      Example
                                      <table rows="4cols="4">
                                       <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
                                       <row role="label">
                                        <cell role="data"/>
                                        <cell role="data">Dossing Cribs or Lodging Houses</cell>
                                        <cell role="data">Beds</cell>
                                        <cell role="data">Needys or Nightly Lodgers</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Bury St Edmund's</cell>
                                        <cell role="data">5</cell>
                                        <cell role="data">8</cell>
                                        <cell role="data">128</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Thetford</cell>
                                        <cell role="data">3</cell>
                                        <cell role="data">6</cell>
                                        <cell role="data">36</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Attleboro'</cell>
                                        <cell role="data">3</cell>
                                        <cell role="data">5</cell>
                                        <cell role="data">20</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Wymondham</cell>
                                        <cell role="data">1</cell>
                                        <cell role="data">11</cell>
                                        <cell role="data">22</cell>
                                       </row>
                                      </table>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.headLike"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <alternate>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="row"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.graphicLike"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <table>

                                      <table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
                                      Modulefigures
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      rows(rows) indicates the number of rows in the table.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      If no number is supplied, an application must calculate the number of rows.

                                      Rows should be presented from top to bottom.

                                      cols(columns) indicates the number of columns in each row of the table.
                                      Status Optional
                                      Datatype teidata.count
                                      Note

                                      If no number is supplied, an application must calculate the number of columns.

                                      Within each row, columns should be presented left to right.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      Contains an optional heading and a series of rows.

                                      Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

                                      Example
                                      <table rows="4cols="4">
                                       <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
                                       <row role="label">
                                        <cell role="data"/>
                                        <cell role="data">Dossing Cribs or Lodging Houses</cell>
                                        <cell role="data">Beds</cell>
                                        <cell role="data">Needys or Nightly Lodgers</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Bury St Edmund's</cell>
                                        <cell role="data">5</cell>
                                        <cell role="data">8</cell>
                                        <cell role="data">128</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Thetford</cell>
                                        <cell role="data">3</cell>
                                        <cell role="data">6</cell>
                                        <cell role="data">36</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Attleboro'</cell>
                                        <cell role="data">3</cell>
                                        <cell role="data">5</cell>
                                        <cell role="data">20</cell>
                                       </row>
                                       <row role="data">
                                        <cell role="label">Wymondham</cell>
                                        <cell role="data">1</cell>
                                        <cell role="data">11</cell>
                                        <cell role="data">22</cell>
                                       </row>
                                      </table>
                                      Content model
                                      <content>
                                       <sequence>
                                        <alternate minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.headLike"/>
                                         <classRef key="model.global"/>
                                        </alternate>
                                        <alternate>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="row"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                         <sequence minOccurs="1"
                                          maxOccurs="unbounded">

                                          <classRef key="model.graphicLike"/>
                                          <classRef key="model.global"
                                           minOccurs="0maxOccurs="unbounded"/>

                                         </sequence>
                                        </alternate>
                                        <sequence minOccurs="0"
                                         maxOccurs="unbounded">

                                         <classRef key="model.divBottom"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element table
                                       {
                                          tei_att.global.attributes,
                                      @@ -36,4 +36,4 @@
                                             ),
                                             ( tei_model.divBottom, tei_model.global* )*
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-tagUsage.html b/gl/dev/ref-tagUsage.html index 4fde78941..32e03d002 100644 --- a/gl/dev/ref-tagUsage.html +++ b/gl/dev/ref-tagUsage.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <tagUsage>

                                      <tagUsage> (element usage) documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datcat (@datcat, @valueDatcat, @targetDatcat)
                                      gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent namespace element.
                                      Status Required
                                      Datatype teidata.name
                                      occursspecifies the number of occurrences of this element within the text.
                                      Status Recommended
                                      Datatype teidata.count
                                      withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
                                      Status Recommended
                                      Datatype teidata.count
                                      Contained by
                                      header: namespace
                                      May contain
                                      Example
                                      <tagsDecl partial="true">
                                       <rendition xml:id="itscheme="css"
                                        selector="foreign, hi">
                                      font-style: italic; </rendition>
                                      <!-- ... -->
                                       <namespace name="http://www.tei-c.org/ns/1.0">
                                        <tagUsage gi="hioccurs="28withId="2"> Used to mark English words italicized in the copy text.</tagUsage>
                                        <tagUsage gi="foreign">Used to mark non-English words in the copy text.</tagUsage>
                                      <!-- ... -->
                                       </namespace>
                                      </tagsDecl>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <tagUsage>

                                      <tagUsage> (element usage) documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datcat (@datcat, @valueDatcat, @targetDatcat)
                                      gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent namespace element.
                                      Status Required
                                      Datatype teidata.name
                                      occursspecifies the number of occurrences of this element within the text.
                                      Status Recommended
                                      Datatype teidata.count
                                      withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
                                      Status Recommended
                                      Datatype teidata.count
                                      Contained by
                                      header: namespace
                                      May contain
                                      Example
                                      <tagsDecl partial="true">
                                       <rendition xml:id="itscheme="css"
                                        selector="foreign, hi">
                                      font-style: italic; </rendition>
                                      <!-- ... -->
                                       <namespace name="http://www.tei-c.org/ns/1.0">
                                        <tagUsage gi="hioccurs="28withId="2"> Used to mark English words italicized in the copy text.</tagUsage>
                                        <tagUsage gi="foreign">Used to mark non-English words in the copy text.</tagUsage>
                                      <!-- ... -->
                                       </namespace>
                                      </tagsDecl>
                                      Content model
                                      <content>
                                       <macroRef key="macro.limitedContent"/>
                                      </content>
                                      Schema Declaration
                                       element tagUsage
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          attribute occurs { teidata.count }?,
                                          attribute withId { teidata.count }?,
                                          tei_macro.limitedContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-tagsDecl.html b/gl/dev/ref-tagsDecl.html index f874ce777..97d122f22 100644 --- a/gl/dev/ref-tagsDecl.html +++ b/gl/dev/ref-tagsDecl.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <tagsDecl>

                                      <tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      partialindicates whether the element types listed exhaustively include all those found within text, or represent only a subset.
                                      Status Recommended
                                      Datatype teidata.truthValue
                                      Note

                                      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. When the tagUsage elements inside tagsDecl are used to provide usage information or default renditions for only a subset of the elements types within the associated text, the value should be true.

                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      Example
                                      <tagsDecl partial="true">
                                       <rendition xml:id="rend-itscheme="css"
                                        selector="emph, hi, name, title">
                                      font-style: italic;</rendition>
                                       <namespace name="http://www.tei-c.org/ns/1.0">
                                        <tagUsage gi="hioccurs="467"/>
                                        <tagUsage gi="titleoccurs="45"/>
                                       </namespace>
                                       <namespace name="http://docbook.org/ns/docbook">
                                        <tagUsage gi="paraoccurs="10"/>
                                       </namespace>
                                      </tagsDecl>

                                      If the partial attribute were not specified here, the implication would be that the document in question contains only hi, title, and <para> elements.

                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="renditionminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="namespaceminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <tagsDecl>

                                      <tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      partialindicates whether the element types listed exhaustively include all those found within text, or represent only a subset.
                                      Status Recommended
                                      Datatype teidata.truthValue
                                      Note

                                      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. When the tagUsage elements inside tagsDecl are used to provide usage information or default renditions for only a subset of the elements types within the associated text, the value should be true.

                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      Example
                                      <tagsDecl partial="true">
                                       <rendition xml:id="rend-itscheme="css"
                                        selector="emph, hi, name, title">
                                      font-style: italic;</rendition>
                                       <namespace name="http://www.tei-c.org/ns/1.0">
                                        <tagUsage gi="hioccurs="467"/>
                                        <tagUsage gi="titleoccurs="45"/>
                                       </namespace>
                                       <namespace name="http://docbook.org/ns/docbook">
                                        <tagUsage gi="paraoccurs="10"/>
                                       </namespace>
                                      </tagsDecl>

                                      If the partial attribute were not specified here, the implication would be that the document in question contains only hi, title, and <para> elements.

                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="renditionminOccurs="0"
                                         maxOccurs="unbounded"/>

                                        <elementRef key="namespaceminOccurs="0"
                                         maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element tagsDecl
                                       {
                                          tei_att.global.attributes,
                                          attribute partial { teidata.truthValue }?,
                                          ( tei_rendition*, tei_namespace* )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-taxonomy.html b/gl/dev/ref-taxonomy.html index 8a21c20a9..28a597df9 100644 --- a/gl/dev/ref-taxonomy.html +++ b/gl/dev/ref-taxonomy.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <taxonomy>

                                      <taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      Nested taxonomies are common in many fields, so the taxonomy element can be nested.

                                      Example
                                      <taxonomy xml:id="tax.b">
                                       <bibl>Brown Corpus</bibl>
                                       <category xml:id="tax.b.a">
                                        <catDesc>Press Reportage</catDesc>
                                        <category xml:id="tax.b.a1">
                                         <catDesc>Daily</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a2">
                                         <catDesc>Sunday</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a3">
                                         <catDesc>National</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a4">
                                         <catDesc>Provincial</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a5">
                                         <catDesc>Political</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a6">
                                         <catDesc>Sports</catDesc>
                                        </category>
                                       </category>
                                       <category xml:id="tax.b.d">
                                        <catDesc>Religion</catDesc>
                                        <category xml:id="tax.b.d1">
                                         <catDesc>Books</catDesc>
                                        </category>
                                        <category xml:id="tax.b.d2">
                                         <catDesc>Periodicals and tracts</catDesc>
                                        </category>
                                       </category>
                                      </taxonomy>
                                      Example
                                      <taxonomy>
                                       <category xml:id="literature">
                                        <catDesc>Literature</catDesc>
                                        <category xml:id="poetry">
                                         <catDesc>Poetry</catDesc>
                                         <category xml:id="sonnet">
                                          <catDesc>Sonnet</catDesc>
                                          <category xml:id="shakesSonnet">
                                           <catDesc>Shakespearean Sonnet</catDesc>
                                          </category>
                                          <category xml:id="petraSonnet">
                                           <catDesc>Petrarchan Sonnet</catDesc>
                                          </category>
                                         </category>
                                         <category xml:id="haiku">
                                          <catDesc>Haiku</catDesc>
                                         </category>
                                        </category>
                                        <category xml:id="drama">
                                         <catDesc>Drama</catDesc>
                                        </category>
                                       </category>
                                       <category xml:id="meter">
                                        <catDesc>Metrical Categories</catDesc>
                                        <category xml:id="feet">
                                         <catDesc>Metrical Feet</catDesc>
                                         <category xml:id="iambic">
                                          <catDesc>Iambic</catDesc>
                                         </category>
                                         <category xml:id="trochaic">
                                          <catDesc>trochaic</catDesc>
                                         </category>
                                        </category>
                                        <category xml:id="feetNumber">
                                         <catDesc>Number of feet</catDesc>
                                         <category xml:id="pentameter">
                                          <catDesc>>Pentameter</catDesc>
                                         </category>
                                         <category xml:id="tetrameter">
                                          <catDesc>>Tetrameter</catDesc>
                                         </category>
                                        </category>
                                       </category>
                                      </taxonomy>
                                      <!-- elsewhere in document -->
                                      <lg ana="#shakesSonnet #iambic #pentameter">
                                       <l>Shall I compare thee to a summer's day</l>
                                      <!-- ... -->
                                      </lg>
                                      Content model
                                      <content>
                                       <alternate>
                                        <alternate>
                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="category"/>
                                          <elementRef key="taxonomy"/>
                                         </alternate>
                                         <sequence>
                                          <alternate minOccurs="1"
                                           maxOccurs="unbounded">

                                           <classRef key="model.descLike"
                                            minOccurs="1maxOccurs="1"/>

                                           <elementRef key="equivminOccurs="1"
                                            maxOccurs="1"/>

                                           <elementRef key="glossminOccurs="1"
                                            maxOccurs="1"/>

                                          </alternate>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="category"/>
                                           <elementRef key="taxonomy"/>
                                          </alternate>
                                         </sequence>
                                        </alternate>
                                        <sequence>
                                         <classRef key="model.biblLike"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="category"/>
                                          <elementRef key="taxonomy"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <taxonomy>

                                      <taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Note

                                      Nested taxonomies are common in many fields, so the taxonomy element can be nested.

                                      Example
                                      <taxonomy xml:id="tax.b">
                                       <bibl>Brown Corpus</bibl>
                                       <category xml:id="tax.b.a">
                                        <catDesc>Press Reportage</catDesc>
                                        <category xml:id="tax.b.a1">
                                         <catDesc>Daily</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a2">
                                         <catDesc>Sunday</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a3">
                                         <catDesc>National</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a4">
                                         <catDesc>Provincial</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a5">
                                         <catDesc>Political</catDesc>
                                        </category>
                                        <category xml:id="tax.b.a6">
                                         <catDesc>Sports</catDesc>
                                        </category>
                                       </category>
                                       <category xml:id="tax.b.d">
                                        <catDesc>Religion</catDesc>
                                        <category xml:id="tax.b.d1">
                                         <catDesc>Books</catDesc>
                                        </category>
                                        <category xml:id="tax.b.d2">
                                         <catDesc>Periodicals and tracts</catDesc>
                                        </category>
                                       </category>
                                      </taxonomy>
                                      Example
                                      <taxonomy>
                                       <category xml:id="literature">
                                        <catDesc>Literature</catDesc>
                                        <category xml:id="poetry">
                                         <catDesc>Poetry</catDesc>
                                         <category xml:id="sonnet">
                                          <catDesc>Sonnet</catDesc>
                                          <category xml:id="shakesSonnet">
                                           <catDesc>Shakespearean Sonnet</catDesc>
                                          </category>
                                          <category xml:id="petraSonnet">
                                           <catDesc>Petrarchan Sonnet</catDesc>
                                          </category>
                                         </category>
                                         <category xml:id="haiku">
                                          <catDesc>Haiku</catDesc>
                                         </category>
                                        </category>
                                        <category xml:id="drama">
                                         <catDesc>Drama</catDesc>
                                        </category>
                                       </category>
                                       <category xml:id="meter">
                                        <catDesc>Metrical Categories</catDesc>
                                        <category xml:id="feet">
                                         <catDesc>Metrical Feet</catDesc>
                                         <category xml:id="iambic">
                                          <catDesc>Iambic</catDesc>
                                         </category>
                                         <category xml:id="trochaic">
                                          <catDesc>trochaic</catDesc>
                                         </category>
                                        </category>
                                        <category xml:id="feetNumber">
                                         <catDesc>Number of feet</catDesc>
                                         <category xml:id="pentameter">
                                          <catDesc>>Pentameter</catDesc>
                                         </category>
                                         <category xml:id="tetrameter">
                                          <catDesc>>Tetrameter</catDesc>
                                         </category>
                                        </category>
                                       </category>
                                      </taxonomy>
                                      <!-- elsewhere in document -->
                                      <lg ana="#shakesSonnet #iambic #pentameter">
                                       <l>Shall I compare thee to a summer's day</l>
                                      <!-- ... -->
                                      </lg>
                                      Content model
                                      <content>
                                       <alternate>
                                        <alternate>
                                         <alternate minOccurs="1"
                                          maxOccurs="unbounded">

                                          <elementRef key="category"/>
                                          <elementRef key="taxonomy"/>
                                         </alternate>
                                         <sequence>
                                          <alternate minOccurs="1"
                                           maxOccurs="unbounded">

                                           <classRef key="model.descLike"
                                            minOccurs="1maxOccurs="1"/>

                                           <elementRef key="equivminOccurs="1"
                                            maxOccurs="1"/>

                                           <elementRef key="glossminOccurs="1"
                                            maxOccurs="1"/>

                                          </alternate>
                                          <alternate minOccurs="0"
                                           maxOccurs="unbounded">

                                           <elementRef key="category"/>
                                           <elementRef key="taxonomy"/>
                                          </alternate>
                                         </sequence>
                                        </alternate>
                                        <sequence>
                                         <classRef key="model.biblLike"/>
                                         <alternate minOccurs="0"
                                          maxOccurs="unbounded">

                                          <elementRef key="category"/>
                                          <elementRef key="taxonomy"/>
                                         </alternate>
                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element taxonomy
                                       {
                                          tei_att.global.attributes,
                                      @@ -35,4 +35,4 @@
                                             )
                                           | ( tei_model.biblLike, ( tei_category | tei_taxonomy )* )
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teiCorpus.html b/gl/dev/ref-teiCorpus.html index 92e21a34d..ac8766e99 100644 --- a/gl/dev/ref-teiCorpus.html +++ b/gl/dev/ref-teiCorpus.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <teiCorpus>

                                      <teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more TEI elements, each containing a single text header and a text. [4. Default Text Structure 15.1. Varieties of Composite Text]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      version(version) specifies the version number of the TEI Guidelines against which this document is valid.
                                      Status Optional
                                      Datatype teidata.version
                                      Note

                                      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 releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      May contain
                                      core: teiCorpus
                                      header: teiHeader
                                      linking: standOff
                                      textstructure: TEI text
                                      Note

                                      Should contain one TEI header for the corpus, and a series of TEI elements, one for each text.

                                      Example
                                      <teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                      <!-- header for corpus -->
                                       </teiHeader>
                                       <TEI>
                                        <teiHeader>
                                      <!-- header for first text -->
                                        </teiHeader>
                                        <text>
                                      <!-- content of first text -->
                                        </text>
                                       </TEI>
                                       <TEI>
                                        <teiHeader>
                                      <!-- header for second text -->
                                        </teiHeader>
                                        <text>
                                      <!-- content of second text -->
                                        </text>
                                       </TEI>
                                      <!-- more TEI elements here -->
                                      </teiCorpus>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="teiHeader"/>
                                        <classRef key="model.resource"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.describedResource"
                                         minOccurs="1maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <teiCorpus>

                                      <teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more TEI elements, each containing a single text header and a text. [4. Default Text Structure 15.1. Varieties of Composite Text]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
                                      version(version) specifies the version number of the TEI Guidelines against which this document is valid.
                                      Status Optional
                                      Datatype teidata.version
                                      Note

                                      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 releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      May contain
                                      core: teiCorpus
                                      header: teiHeader
                                      linking: standOff
                                      textstructure: TEI text
                                      Note

                                      Should contain one TEI header for the corpus, and a series of TEI elements, one for each text.

                                      Example
                                      <teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
                                       <teiHeader>
                                      <!-- header for corpus -->
                                       </teiHeader>
                                       <TEI>
                                        <teiHeader>
                                      <!-- header for first text -->
                                        </teiHeader>
                                        <text>
                                      <!-- content of first text -->
                                        </text>
                                       </TEI>
                                       <TEI>
                                        <teiHeader>
                                      <!-- header for second text -->
                                        </teiHeader>
                                        <text>
                                      <!-- content of second text -->
                                        </text>
                                       </TEI>
                                      <!-- more TEI elements here -->
                                      </teiCorpus>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="teiHeader"/>
                                        <classRef key="model.resource"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <classRef key="model.describedResource"
                                         minOccurs="1maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element teiCorpus
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          attribute version { teidata.version }?,
                                          ( tei_teiHeader, tei_model.resource*, tei_model.describedResource+ )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teiHeader.html b/gl/dev/ref-teiHeader.html index aa7d36ad9..9a051adb5 100644 --- a/gl/dev/ref-teiHeader.html +++ b/gl/dev/ref-teiHeader.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <teiHeader>

                                      <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      Note

                                      One of the few elements unconditionally required in any TEI document.

                                      Example
                                      <teiHeader>
                                       <fileDesc>
                                        <titleStmt>
                                         <title>Shakespeare: the first folio (1623) in electronic form</title>
                                         <author>Shakespeare, William (1564–1616)</author>
                                         <respStmt>
                                          <resp>Originally prepared by</resp>
                                          <name>Trevor Howard-Hill</name>
                                         </respStmt>
                                         <respStmt>
                                          <resp>Revised and edited by</resp>
                                          <name>Christine Avern-Carr</name>
                                         </respStmt>
                                        </titleStmt>
                                        <publicationStmt>
                                         <distributor>Oxford Text Archive</distributor>
                                         <address>
                                          <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
                                         </address>
                                         <idno type="OTA">119</idno>
                                         <availability>
                                          <p>Freely available on a non-commercial basis.</p>
                                         </availability>
                                         <date when="1968">1968</date>
                                        </publicationStmt>
                                        <sourceDesc>
                                         <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
                                             1968)</bibl>
                                        </sourceDesc>
                                       </fileDesc>
                                       <encodingDesc>
                                        <projectDesc>
                                         <p>Originally prepared for use in the production of a series of old-spelling
                                             concordances in 1968, this text was extensively checked and revised for use during the
                                             editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
                                        </projectDesc>
                                        <editorialDecl>
                                         <correction>
                                          <p>Turned letters are silently corrected.</p>
                                         </correction>
                                         <normalization>
                                          <p>Original spelling and typography is retained, except that long s and ligatured
                                               forms are not encoded.</p>
                                         </normalization>
                                        </editorialDecl>
                                        <refsDecl xml:id="ASLREF">
                                         <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
                                          replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">

                                          <p>A reference is created by assembling the following, in the reverse order as that
                                               listed here: <list>
                                            <item>the <att>n</att> value of the preceding <gi>lb</gi>
                                            </item>
                                            <item>a period</item>
                                            <item>the <att>n</att> value of the ancestor <gi>div2</gi>
                                            </item>
                                            <item>a space</item>
                                            <item>the <att>n</att> value of the parent <gi>div1</gi>
                                            </item>
                                           </list>
                                          </p>
                                         </cRefPattern>
                                        </refsDecl>
                                       </encodingDesc>
                                       <revisionDesc>
                                        <list>
                                         <item>
                                          <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
                                         <item>
                                          <date when="1989-03-01">1 Mar 89</date> LB made new file</item>
                                        </list>
                                       </revisionDesc>
                                      </teiHeader>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="fileDesc"/>
                                        <classRef key="model.teiHeaderPart"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="revisionDesc"
                                         minOccurs="0"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <teiHeader>

                                      <teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI
                                      May contain
                                      Note

                                      One of the few elements unconditionally required in any TEI document.

                                      Example
                                      <teiHeader>
                                       <fileDesc>
                                        <titleStmt>
                                         <title>Shakespeare: the first folio (1623) in electronic form</title>
                                         <author>Shakespeare, William (1564–1616)</author>
                                         <respStmt>
                                          <resp>Originally prepared by</resp>
                                          <name>Trevor Howard-Hill</name>
                                         </respStmt>
                                         <respStmt>
                                          <resp>Revised and edited by</resp>
                                          <name>Christine Avern-Carr</name>
                                         </respStmt>
                                        </titleStmt>
                                        <publicationStmt>
                                         <distributor>Oxford Text Archive</distributor>
                                         <address>
                                          <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
                                         </address>
                                         <idno type="OTA">119</idno>
                                         <availability>
                                          <p>Freely available on a non-commercial basis.</p>
                                         </availability>
                                         <date when="1968">1968</date>
                                        </publicationStmt>
                                        <sourceDesc>
                                         <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
                                             1968)</bibl>
                                        </sourceDesc>
                                       </fileDesc>
                                       <encodingDesc>
                                        <projectDesc>
                                         <p>Originally prepared for use in the production of a series of old-spelling
                                             concordances in 1968, this text was extensively checked and revised for use during the
                                             editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
                                        </projectDesc>
                                        <editorialDecl>
                                         <correction>
                                          <p>Turned letters are silently corrected.</p>
                                         </correction>
                                         <normalization>
                                          <p>Original spelling and typography is retained, except that long s and ligatured
                                               forms are not encoded.</p>
                                         </normalization>
                                        </editorialDecl>
                                        <refsDecl xml:id="ASLREF">
                                         <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
                                          replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">

                                          <p>A reference is created by assembling the following, in the reverse order as that
                                               listed here: <list>
                                            <item>the <att>n</att> value of the preceding <gi>lb</gi>
                                            </item>
                                            <item>a period</item>
                                            <item>the <att>n</att> value of the ancestor <gi>div2</gi>
                                            </item>
                                            <item>a space</item>
                                            <item>the <att>n</att> value of the parent <gi>div1</gi>
                                            </item>
                                           </list>
                                          </p>
                                         </cRefPattern>
                                        </refsDecl>
                                       </encodingDesc>
                                       <revisionDesc>
                                        <list>
                                         <item>
                                          <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
                                         <item>
                                          <date when="1989-03-01">1 Mar 89</date> LB made new file</item>
                                        </list>
                                       </revisionDesc>
                                      </teiHeader>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="fileDesc"/>
                                        <classRef key="model.teiHeaderPart"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <elementRef key="revisionDesc"
                                         minOccurs="0"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element teiHeader
                                       {
                                          tei_att.global.attributes,
                                          ( tei_fileDesc, tei_model.teiHeaderPart*, tei_revisionDesc? )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.certainty.html b/gl/dev/ref-teidata.certainty.html index 158711533..a089e0830 100644 --- a/gl/dev/ref-teidata.certainty.html +++ b/gl/dev/ref-teidata.certainty.html @@ -34,4 +34,4 @@ Note

                                      Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.count.html b/gl/dev/ref-teidata.count.html index 18dd70980..c5e51bee7 100644 --- a/gl/dev/ref-teidata.count.html +++ b/gl/dev/ref-teidata.count.html @@ -34,4 +34,4 @@ Note

                                      Any positive integer value or zero is permitted

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.duration.iso.html b/gl/dev/ref-teidata.duration.iso.html index a4378f42d..648b47542 100644 --- a/gl/dev/ref-teidata.duration.iso.html +++ b/gl/dev/ref-teidata.duration.iso.html @@ -30,14 +30,14 @@ Content model
                                      <content>
                                       <dataRef name="token"
                                        restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>

                                      </content>
                                      Declaration
                                       tei_teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
                                      - Example
                                      <time dur-iso="PT0,75H">three-quarters of an hour</time>
                                      - Example
                                      <date dur-iso="P1,5D">a day and a half</date>
                                      - Example
                                      <date dur-iso="P14D">a fortnight</date>
                                      + Example
                                      <time dur-iso="PT0,75H">three-quarters of an hour</time>
                                      + Example
                                      <date dur-iso="P1,5D">a day and a half</date>
                                      + Example
                                      <date dur-iso="P14D">a fortnight</date>
                                      - Example
                                      <time dur-iso="PT0.02S">20 ms</time>
                                      + Example
                                      <time dur-iso="PT0.02S">20 ms</time>
                                      Note

                                      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; the latter is preferred). If any number is 0, then that number-letter 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 interchange — Representation of dates and times.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.duration.w3c.html b/gl/dev/ref-teidata.duration.w3c.html index c56422d39..c850a82b7 100644 --- a/gl/dev/ref-teidata.duration.w3c.html +++ b/gl/dev/ref-teidata.duration.w3c.html @@ -30,14 +30,14 @@ Content model
                                      <content>
                                       <dataRef name="duration"/>
                                      </content>
                                      Declaration
                                       tei_teidata.duration.w3c = xsd:duration
                                      - Example
                                      <time dur="PT45M">forty-five minutes</time>
                                      - Example
                                      <date dur="P1DT12H">a day and a half</date>
                                      - Example
                                      <date dur="P7D">a week</date>
                                      + Example
                                      <time dur="PT45M">forty-five minutes</time>
                                      + Example
                                      <date dur="P1DT12H">a day and a half</date>
                                      + Example
                                      <date dur="P7D">a week</date>
                                      - Example
                                      <time dur="PT0.02S">20 ms</time>
                                      + Example
                                      <time dur="PT0.02S">20 ms</time>
                                      Note

                                      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 S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter 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 the W3C specification.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.enumerated.html b/gl/dev/ref-teidata.enumerated.html index 720c0d505..78fe3ecdc 100644 --- a/gl/dev/ref-teidata.enumerated.html +++ b/gl/dev/ref-teidata.enumerated.html @@ -34,4 +34,4 @@ Note

                                      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 list in the associated attribute specification, expressed with a <valList> element.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.gender.html b/gl/dev/ref-teidata.gender.html index 5473f9ce8..095982e5a 100644 --- a/gl/dev/ref-teidata.gender.html +++ b/gl/dev/ref-teidata.gender.html @@ -26,4 +26,4 @@ Content model
                                      <content>
                                       <dataRef key="teidata.enumerated"/>
                                      </content>
                                      Declaration
                                       tei_teidata.gender = teidata.enumerated
                                      Note

                                      Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

                                      Values for this datatype should not be used to encode morphological gender (cf. gen, msd as defined in att.linguistic, and 9.3.1. Information on Written and Spoken Forms).

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.language.html b/gl/dev/ref-teidata.language.html index 0fcc8c4d2..f7482b5db 100644 --- a/gl/dev/ref-teidata.language.html +++ b/gl/dev/ref-teidata.language.html @@ -35,4 +35,4 @@ -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.name.html b/gl/dev/ref-teidata.name.html index 3d69a3776..deabad9d7 100644 --- a/gl/dev/ref-teidata.name.html +++ b/gl/dev/ref-teidata.name.html @@ -34,4 +34,4 @@ Note

                                      Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.namespace.html b/gl/dev/ref-teidata.namespace.html index 9923890d9..495fd5f1c 100644 --- a/gl/dev/ref-teidata.namespace.html +++ b/gl/dev/ref-teidata.namespace.html @@ -34,4 +34,4 @@ Note

                                      The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.numeric.html b/gl/dev/ref-teidata.numeric.html index 8a88e6663..69d8f2920 100644 --- a/gl/dev/ref-teidata.numeric.html +++ b/gl/dev/ref-teidata.numeric.html @@ -35,4 +35,4 @@ Note

                                      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 (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.outputMeasurement.html b/gl/dev/ref-teidata.outputMeasurement.html index fe60f337a..922526bbb 100644 --- a/gl/dev/ref-teidata.outputMeasurement.html +++ b/gl/dev/ref-teidata.outputMeasurement.html @@ -35,10 +35,10 @@ { pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)" } - Example
                                      <figure>
                                       <head>The TEI Logo</head>
                                       <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
                                         between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
                                         background.</figDesc>
                                       <graphic height="600pxwidth="600px"
                                        url="http://www.tei-c.org/logos/TEI-600.jpg"/>

                                      </figure>
                                      + Example
                                      <figure>
                                       <head>The TEI Logo</head>
                                       <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
                                         between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
                                         background.</figDesc>
                                       <graphic height="600pxwidth="600px"
                                        url="http://www.tei-c.org/logos/TEI-600.jpg"/>

                                      </figure>
                                      Note

                                      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.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.pattern.html b/gl/dev/ref-teidata.pattern.html index 3139f7321..88777e1f8 100644 --- a/gl/dev/ref-teidata.pattern.html +++ b/gl/dev/ref-teidata.pattern.html @@ -35,4 +35,4 @@ Note

                                      : A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)

                                      This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.point.html b/gl/dev/ref-teidata.point.html index f72472d9c..63999835c 100644 --- a/gl/dev/ref-teidata.point.html +++ b/gl/dev/ref-teidata.point.html @@ -26,6 +26,6 @@ Content model
                                      <content>
                                       <dataRef name="token"
                                        restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>

                                      </content>
                                      Declaration
                                       tei_teidata.point =
                                          token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
                                      - Example
                                      <facsimile>
                                       <surface ulx="0uly="0lrx="400lry="280">
                                        <zone points="220,100 300,210 170,250 123,234">
                                         <graphic url="handwriting.png"/>
                                        </zone>
                                       </surface>
                                      </facsimile>
                                      + Example
                                      <facsimile>
                                       <surface ulx="0uly="0lrx="400lry="280">
                                        <zone points="220,100 300,210 170,250 123,234">
                                         <graphic url="handwriting.png"/>
                                        </zone>
                                       </surface>
                                      </facsimile>
                                      Note

                                      A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.pointer.html b/gl/dev/ref-teidata.pointer.html index 2bdb88e13..8cc7bd3a8 100644 --- a/gl/dev/ref-teidata.pointer.html +++ b/gl/dev/ref-teidata.pointer.html @@ -34,4 +34,4 @@ Note

                                      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 RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.prefix.html b/gl/dev/ref-teidata.prefix.html index 1091adfbe..9767634eb 100644 --- a/gl/dev/ref-teidata.prefix.html +++ b/gl/dev/ref-teidata.prefix.html @@ -26,4 +26,4 @@ Content model
                                      <content>
                                       <dataRef name="token"
                                        restriction="[a-z][a-z0-9\+\.\-]*"/>

                                      </content>
                                      Declaration
                                       tei_teidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }
                                      Note

                                      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 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.probCert.html b/gl/dev/ref-teidata.probCert.html index 60aaa87a5..dfe853a7a 100644 --- a/gl/dev/ref-teidata.probCert.html +++ b/gl/dev/ref-teidata.probCert.html @@ -26,4 +26,4 @@ Content model
                                      <content>
                                       <alternate>
                                        <dataRef key="teidata.probability"/>
                                        <dataRef key="teidata.certainty"/>
                                       </alternate>
                                      </content>
                                      Declaration
                                       tei_teidata.probCert = teidata.probability | teidata.certainty
                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.probability.html b/gl/dev/ref-teidata.probability.html index 60c4517bd..c5e40236e 100644 --- a/gl/dev/ref-teidata.probability.html +++ b/gl/dev/ref-teidata.probability.html @@ -34,4 +34,4 @@ Note

                                      Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.replacement.html b/gl/dev/ref-teidata.replacement.html index 34e0fb211..fee67e341 100644 --- a/gl/dev/ref-teidata.replacement.html +++ b/gl/dev/ref-teidata.replacement.html @@ -26,4 +26,4 @@ Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Declaration
                                       tei_teidata.replacement = text
                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.sex.html b/gl/dev/ref-teidata.sex.html index 074e9f0a6..b8ea8c605 100644 --- a/gl/dev/ref-teidata.sex.html +++ b/gl/dev/ref-teidata.sex.html @@ -33,4 +33,4 @@ tei_teidata.sex = teidata.enumerated Note

                                      Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.temporal.iso.html b/gl/dev/ref-teidata.temporal.iso.html index 393dbd4ee..096a0adaf 100644 --- a/gl/dev/ref-teidata.temporal.iso.html +++ b/gl/dev/ref-teidata.temporal.iso.html @@ -42,4 +42,4 @@ Note

                                      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 extended format, these Guidelines recommend use of the extended format.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.temporal.w3c.html b/gl/dev/ref-teidata.temporal.w3c.html index 7772e011a..05dff8279 100644 --- a/gl/dev/ref-teidata.temporal.w3c.html +++ b/gl/dev/ref-teidata.temporal.w3c.html @@ -41,4 +41,4 @@ Note

                                      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.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.text.html b/gl/dev/ref-teidata.text.html index 722aae22c..6c0179184 100644 --- a/gl/dev/ref-teidata.text.html +++ b/gl/dev/ref-teidata.text.html @@ -27,4 +27,4 @@ Content model
                                      <content>
                                       <dataRef name="string"/>
                                      </content>
                                      Declaration
                                       tei_teidata.text = string
                                      Note

                                      Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.truthValue.html b/gl/dev/ref-teidata.truthValue.html index ade69c3e5..cd30c96fc 100644 --- a/gl/dev/ref-teidata.truthValue.html +++ b/gl/dev/ref-teidata.truthValue.html @@ -34,4 +34,4 @@ Note

                                      The possible values of this datatype are 1 or true, or 0 or false.

                                      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.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.version.html b/gl/dev/ref-teidata.version.html index 9577dbfb8..857ebf57a 100644 --- a/gl/dev/ref-teidata.version.html +++ b/gl/dev/ref-teidata.version.html @@ -28,4 +28,4 @@ tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" } Note

                                      The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.versionNumber.html b/gl/dev/ref-teidata.versionNumber.html index 0d253d0bc..5887b9823 100644 --- a/gl/dev/ref-teidata.versionNumber.html +++ b/gl/dev/ref-teidata.versionNumber.html @@ -27,4 +27,4 @@ tei_teidata.versionNumber = token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" } -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.word.html b/gl/dev/ref-teidata.word.html index afd77a276..a97697791 100644 --- a/gl/dev/ref-teidata.word.html +++ b/gl/dev/ref-teidata.word.html @@ -34,4 +34,4 @@ Note

                                      Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.xTruthValue.html b/gl/dev/ref-teidata.xTruthValue.html index 0f762a395..2f37364c5 100644 --- a/gl/dev/ref-teidata.xTruthValue.html +++ b/gl/dev/ref-teidata.xTruthValue.html @@ -37,4 +37,4 @@ Note

                                      In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.xmlName.html b/gl/dev/ref-teidata.xmlName.html index 0c5ea89b7..3926226ac 100644 --- a/gl/dev/ref-teidata.xmlName.html +++ b/gl/dev/ref-teidata.xmlName.html @@ -26,4 +26,4 @@ Content model
                                      <content>
                                       <dataRef name="NCName"/>
                                      </content>
                                      Declaration
                                       tei_teidata.xmlName = xsd:NCName
                                      Note

                                      The rules defining an XML name form a part of the XML Specification.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-teidata.xpath.html b/gl/dev/ref-teidata.xpath.html index c5bc119f0..099ef7686 100644 --- a/gl/dev/ref-teidata.xpath.html +++ b/gl/dev/ref-teidata.xpath.html @@ -26,4 +26,4 @@ Content model
                                      <content>
                                       <textNode/>
                                      </content>
                                      Declaration
                                       tei_teidata.xpath = text
                                      Note

                                      Any XPath expression using the syntax defined in 6.2. .

                                      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.

                                      -

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-term.html b/gl/dev/ref-term.html index 73ed3f818..5525c3b1f 100644 --- a/gl/dev/ref-term.html +++ b/gl/dev/ref-term.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <term>

                                      <term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When this element appears within an index element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a gloss element by means of its ref attribute; alternatively a gloss element may point to a term element by means of its target attribute.

                                      In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The term element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the term element to be used by practitioners of any persuasion.

                                      As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

                                      Example
                                      A computational device that infers structure
                                      from grammatical strings of words is known as a <term>parser</term>, and much of the history
                                      of NLP over the last 20 years has been occupied with the design of parsers.
                                      Example
                                      We may define <term xml:id="TDPV1rend="sc">discoursal point of view</term> as
                                      <gloss target="#TDPV1">the relationship, expressed
                                      through discourse structure, between the implied author or some other addresser, and the
                                      fiction.</gloss>
                                      Example
                                      We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as
                                      <gloss xml:id="TDPV2">the relationship, expressed
                                      through discourse structure, between the implied author or some other addresser, and the
                                      fiction.</gloss>
                                      Example
                                      We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <term>

                                      <term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      When this element appears within an index element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a gloss element by means of its ref attribute; alternatively a gloss element may point to a term element by means of its target attribute.

                                      In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The term element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the term element to be used by practitioners of any persuasion.

                                      As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

                                      Example
                                      A computational device that infers structure
                                      from grammatical strings of words is known as a <term>parser</term>, and much of the history
                                      of NLP over the last 20 years has been occupied with the design of parsers.
                                      Example
                                      We may define <term xml:id="TDPV1rend="sc">discoursal point of view</term> as
                                      <gloss target="#TDPV1">the relationship, expressed
                                      through discourse structure, between the implied author or some other addresser, and the
                                      fiction.</gloss>
                                      Example
                                      We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as
                                      <gloss xml:id="TDPV2">the relationship, expressed
                                      through discourse structure, between the implied author or some other addresser, and the
                                      fiction.</gloss>
                                      Example
                                      We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element term
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          tei_att.sortable.attributes,
                                          tei_att.cReferencing.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-text.html b/gl/dev/ref-text.html index 6c6bc1f4a..7b13039f1 100644 --- a/gl/dev/ref-text.html +++ b/gl/dev/ref-text.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <text>

                                      <text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype) att.written (@hand)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI group
                                      May contain
                                      Note

                                      This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the floatingText is provided for this purpose.

                                      Example
                                      <text>
                                       <front>
                                        <docTitle>
                                         <titlePart>Autumn Haze</titlePart>
                                        </docTitle>
                                       </front>
                                       <body>
                                        <l>Is it a dragonfly or a maple leaf</l>
                                        <l>That settles softly down upon the water?</l>
                                       </body>
                                      </text>
                                      Example

                                      The body of a text may be replaced by a group of nested texts, as in the following schematic:

                                      <text>
                                       <front>
                                      <!-- front matter for the whole group -->
                                       </front>
                                       <group>
                                        <text>
                                      <!-- first text -->
                                        </text>
                                        <text>
                                      <!-- second text -->
                                        </text>
                                       </group>
                                      </text>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="front"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate>
                                         <elementRef key="body"/>
                                         <elementRef key="group"/>
                                        </alternate>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="back"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <text>

                                      <text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
                                      Moduletextstructure
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype) att.written (@hand)
                                      Member of
                                      Contained by
                                      core: teiCorpus
                                      textstructure: TEI group
                                      May contain
                                      Note

                                      This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the floatingText is provided for this purpose.

                                      Example
                                      <text>
                                       <front>
                                        <docTitle>
                                         <titlePart>Autumn Haze</titlePart>
                                        </docTitle>
                                       </front>
                                       <body>
                                        <l>Is it a dragonfly or a maple leaf</l>
                                        <l>That settles softly down upon the water?</l>
                                       </body>
                                      </text>
                                      Example

                                      The body of a text may be replaced by a group of nested texts, as in the following schematic:

                                      <text>
                                       <front>
                                      <!-- front matter for the whole group -->
                                       </front>
                                       <group>
                                        <text>
                                      <!-- first text -->
                                        </text>
                                        <text>
                                      <!-- second text -->
                                        </text>
                                       </group>
                                      </text>
                                      Content model
                                      <content>
                                       <sequence>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="front"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                        <alternate>
                                         <elementRef key="body"/>
                                         <elementRef key="group"/>
                                        </alternate>
                                        <classRef key="model.global"
                                         minOccurs="0maxOccurs="unbounded"/>

                                        <sequence minOccurs="0">
                                         <elementRef key="back"/>
                                         <classRef key="model.global"
                                          minOccurs="0maxOccurs="unbounded"/>

                                        </sequence>
                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element text
                                       {
                                          tei_att.global.attributes,
                                      @@ -35,4 +35,4 @@
                                             tei_model.global*,
                                             ( tei_back, tei_model.global* )?
                                          )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-textClass.html b/gl/dev/ref-textClass.html index b5a8282a4..27ce9ebe0 100644 --- a/gl/dev/ref-textClass.html +++ b/gl/dev/ref-textClass.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <textClass>

                                      <textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Example
                                      <taxonomy>
                                       <category xml:id="acprose">
                                        <catDesc>Academic prose</catDesc>
                                       </category>
                                      <!-- other categories here -->
                                      </taxonomy>
                                      <!-- ... -->
                                      <textClass>
                                       <catRef target="#acprose"/>
                                       <classCode scheme="http://www.udcc.org">001.9</classCode>
                                       <keywords scheme="http://authorities.loc.gov">
                                        <list>
                                         <item>End of the world</item>
                                         <item>History - philosophy</item>
                                        </list>
                                       </keywords>
                                      </textClass>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="classCode"/>
                                        <elementRef key="catRef"/>
                                        <elementRef key="keywords"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <textClass>

                                      <textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
                                      Member of
                                      Contained by
                                      header: profileDesc
                                      May contain
                                      Example
                                      <taxonomy>
                                       <category xml:id="acprose">
                                        <catDesc>Academic prose</catDesc>
                                       </category>
                                      <!-- other categories here -->
                                      </taxonomy>
                                      <!-- ... -->
                                      <textClass>
                                       <catRef target="#acprose"/>
                                       <classCode scheme="http://www.udcc.org">001.9</classCode>
                                       <keywords scheme="http://authorities.loc.gov">
                                        <list>
                                         <item>End of the world</item>
                                         <item>History - philosophy</item>
                                        </list>
                                       </keywords>
                                      </textClass>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <elementRef key="classCode"/>
                                        <elementRef key="catRef"/>
                                        <elementRef key="keywords"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element textClass
                                       {
                                          tei_att.global.attributes,
                                          tei_att.declarable.attributes,
                                          ( tei_classCode | tei_catRef | tei_keywords )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-textLang.html b/gl/dev/ref-textLang.html index f56447f82..321f4bf9b 100644 --- a/gl/dev/ref-textLang.html +++ b/gl/dev/ref-textLang.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <textLang>

                                      <textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
                                      Status Optional
                                      Datatype teidata.language
                                      otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
                                      Status Optional
                                      Datatype 0–∞ occurrences of teidata.language separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for 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 ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a language element in the TEI header.

                                      Example
                                      <textLang mainLang="enotherLangs="la"> Predominantly in English with Latin
                                      glosses</textLang>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <textLang>

                                      <textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
                                      Status Optional
                                      Datatype teidata.language
                                      otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
                                      Status Optional
                                      Datatype 0–∞ occurrences of teidata.language separated by whitespace
                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for 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 ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a language element in the TEI header.

                                      Example
                                      <textLang mainLang="enotherLangs="la"> Predominantly in English with Latin
                                      glosses</textLang>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element textLang
                                       {
                                          tei_att.global.attributes,
                                          attribute mainLang { teidata.language }?,
                                          attribute otherLangs { list { teidata.language* } }?,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-time.html b/gl/dev/ref-time.html index b8822d615..1b615379d 100644 --- a/gl/dev/ref-time.html +++ b/gl/dev/ref-time.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <time>

                                      <time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref) att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      As he sat smiling, the
                                      quarter struck — <time when="11:45:00">the quarter to twelve</time>.
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <time>

                                      <time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref) att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      As he sat smiling, the
                                      quarter struck — <time when="11:45:00">the quarter to twelve</time>.
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.phrase"/>
                                        <classRef key="model.global"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element time
                                       {
                                          tei_att.global.attributes,
                                      @@ -32,4 +32,4 @@
                                          tei_att.dimensions.attributes,
                                          tei_att.typed.attributes,
                                          ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-title.html b/gl/dev/ref-title.html index bb6069eb1..960b6ac64 100644 --- a/gl/dev/ref-title.html +++ b/gl/dev/ref-title.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <title>

                                      <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (type, @subtype)
                                      typeclassifies the title according to some convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      main
                                      main title
                                      sub
                                      (subordinate) subtitle, title of part
                                      alt
                                      (alternate) alternate title, often in another language, by which the work is also known
                                      short
                                      abbreviated form of title
                                      desc
                                      (descriptive) descriptive paraphrase of the work functioning as a title
                                      Note

                                      This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element.

                                      levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      a
                                      (analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
                                      m
                                      (monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
                                      j
                                      (journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
                                      s
                                      (series) the title applies to a series of otherwise distinct publications such as a collection
                                      u
                                      (unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
                                      Note

                                      The level of a title is sometimes implied by its context: for example, a title appearing directly within an analytic element is ipso facto of level ‘a’, and one appearing within a series element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

                                      Example
                                      <title>Information Technology and the Research Process: Proceedings of
                                      a conference held at Cranfield Institute of Technology, UK,
                                      18–21 July 1989</title>
                                      Example
                                      <title>Hardy's Tess of the D'Urbervilles: a machine readable
                                      edition</title>
                                      Example
                                      <title type="full">
                                       <title type="main">Synthèse</title>
                                       <title type="sub">an international journal for
                                         epistemology, methodology and history of
                                         science</title>
                                      </title>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <title>

                                      <title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (type, @subtype)
                                      typeclassifies the title according to some convenient typology.
                                      Derived fromatt.typed
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      main
                                      main title
                                      sub
                                      (subordinate) subtitle, title of part
                                      alt
                                      (alternate) alternate title, often in another language, by which the work is also known
                                      short
                                      abbreviated form of title
                                      desc
                                      (descriptive) descriptive paraphrase of the work functioning as a title
                                      Note

                                      This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element.

                                      levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      a
                                      (analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
                                      m
                                      (monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
                                      j
                                      (journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
                                      s
                                      (series) the title applies to a series of otherwise distinct publications such as a collection
                                      u
                                      (unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
                                      Note

                                      The level of a title is sometimes implied by its context: for example, a title appearing directly within an analytic element is ipso facto of level ‘a’, and one appearing within a series element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

                                      Member of
                                      Contained by
                                      May contain
                                      Note

                                      The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

                                      Example
                                      <title>Information Technology and the Research Process: Proceedings of
                                      a conference held at Cranfield Institute of Technology, UK,
                                      18–21 July 1989</title>
                                      Example
                                      <title>Hardy's Tess of the D'Urbervilles: a machine readable
                                      edition</title>
                                      Example
                                      <title type="full">
                                       <title type="main">Synthèse</title>
                                       <title type="sub">an international journal for
                                         epistemology, methodology and history of
                                         science</title>
                                      </title>
                                      Content model
                                      <content>
                                       <macroRef key="macro.paraContent"/>
                                      </content>
                                      Schema Declaration
                                       element title
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          attribute type { teidata.enumerated }?,
                                          attribute level { "a" | "m" | "j" | "s" | "u" }?,
                                          tei_macro.paraContent
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-titleStmt.html b/gl/dev/ref-titleStmt.html index e5ca75bee..22bb0d039 100644 --- a/gl/dev/ref-titleStmt.html +++ b/gl/dev/ref-titleStmt.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <titleStmt>

                                      <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <titleStmt>
                                       <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
                                       <respStmt>
                                        <resp>compiled by</resp>
                                        <name>P.J. Lucas</name>
                                       </respStmt>
                                      </titleStmt>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="titleminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.respLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <titleStmt>

                                      <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      May contain
                                      Example
                                      <titleStmt>
                                       <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
                                       <respStmt>
                                        <resp>compiled by</resp>
                                        <name>P.J. Lucas</name>
                                       </respStmt>
                                      </titleStmt>
                                      Content model
                                      <content>
                                       <sequence>
                                        <elementRef key="titleminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <classRef key="model.respLike"
                                         minOccurs="0maxOccurs="unbounded"/>

                                       </sequence>
                                      </content>
                                      Schema Declaration
                                       element titleStmt
                                       {
                                          tei_att.global.attributes,
                                          ( tei_title+, tei_model.respLike* )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-transcriptionDesc.html b/gl/dev/ref-transcriptionDesc.html index 86a4fb69d..8bf7d7959 100644 --- a/gl/dev/ref-transcriptionDesc.html +++ b/gl/dev/ref-transcriptionDesc.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <transcriptionDesc>

                                      <transcriptionDesc> (transcription description) describes the set of transcription conventions used, particularly for spoken material. [8.2. Documenting the Source of Transcribed Speech]
                                      Modulespoken
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      identsupplies an identifier for the encoding convention, independent of any version number.
                                      Status Required
                                      Datatype teidata.name
                                      versionsupplies a version number for the encoding conventions used, if any.
                                      Status Optional
                                      Datatype teidata.versionNumber
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      linking: ab
                                      Example
                                      <transcriptionDesc ident="HIAT"
                                       version="2004"/>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.labelLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <classRef key="model.pLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <transcriptionDesc>

                                      <transcriptionDesc> (transcription description) describes the set of transcription conventions used, particularly for spoken material. [8.2. Documenting the Source of Transcribed Speech]
                                      Modulespoken
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      identsupplies an identifier for the encoding convention, independent of any version number.
                                      Status Required
                                      Datatype teidata.name
                                      versionsupplies a version number for the encoding conventions used, if any.
                                      Status Optional
                                      Datatype teidata.versionNumber
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      linking: ab
                                      Example
                                      <transcriptionDesc ident="HIAT"
                                       version="2004"/>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <classRef key="model.labelLike"/>
                                        <classRef key="model.ptrLike"/>
                                        <classRef key="model.pLike"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element transcriptionDesc
                                       {
                                          tei_att.global.attributes,
                                          attribute ident { teidata.name },
                                          attribute version { teidata.versionNumber }?,
                                          ( tei_model.labelLike | tei_model.ptrLike | tei_model.pLike )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-transpose.html b/gl/dev/ref-transpose.html index 722f03ee5..33464d1bb 100644 --- a/gl/dev/ref-transpose.html +++ b/gl/dev/ref-transpose.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <transpose>

                                      <transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [11.3.4.5. Transpositions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      transcr: listTranspose
                                      May contain
                                      core: ptr
                                      Note

                                      Transposition is usually indicated in a document by a metamark such as a wavy line or numbering.

                                      The order in which ptr elements appear within a transpose element should correspond with the desired order, as indicated by the metamark.

                                      Example
                                      <transpose>
                                       <ptr target="#ib02"/>
                                       <ptr target="#ib01"/>
                                      </transpose>

                                      The transposition recorded here indicates that the content of the element with identifier ib02 should appear before the content of the element with identifier ib01.

                                      Content model
                                      <content>
                                       <elementRef key="ptrminOccurs="2"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      -element transpose { tei_att.global.attributes, ( tei_ptr, tei_ptr, tei_ptr* ) }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <transpose>

                                      <transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [11.3.4.5. Transpositions]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Contained by
                                      transcr: listTranspose
                                      May contain
                                      core: ptr
                                      Note

                                      Transposition is usually indicated in a document by a metamark such as a wavy line or numbering.

                                      The order in which ptr elements appear within a transpose element should correspond with the desired order, as indicated by the metamark.

                                      Example
                                      <transpose>
                                       <ptr target="#ib02"/>
                                       <ptr target="#ib01"/>
                                      </transpose>

                                      The transposition recorded here indicates that the content of the element with identifier ib02 should appear before the content of the element with identifier ib01.

                                      Content model
                                      <content>
                                       <elementRef key="ptrminOccurs="2"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +element transpose { tei_att.global.attributes, ( tei_ptr, tei_ptr, tei_ptr* ) }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-typeDesc.html b/gl/dev/ref-typeDesc.html index 95e5ff5a6..3627c7159 100644 --- a/gl/dev/ref-typeDesc.html +++ b/gl/dev/ref-typeDesc.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <typeDesc>

                                      <typeDesc> (typeface description) contains a description of the typefaces or other aspects of the printing of an incunable or other printed source. [10.7.2.1. Writing]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: summary typeNote
                                      Example
                                      <typeDesc>
                                       <p>Uses an unidentified black letter font, probably from the
                                         15th century</p>
                                      </typeDesc>
                                      Example
                                      <typeDesc>
                                       <summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>
                                       <typeNote xml:id="Frak1">Blackletter face, showing
                                         similarities to those produced in Wuerzburg after 1470.</typeNote>
                                       <typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote>
                                      </typeDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="typeNoteminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <typeDesc>

                                      <typeDesc> (typeface description) contains a description of the typefaces or other aspects of the printing of an incunable or other printed source. [10.7.2.1. Writing]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      msdescription: physDesc
                                      May contain
                                      core: p
                                      linking: ab
                                      msdescription: summary typeNote
                                      Example
                                      <typeDesc>
                                       <p>Uses an unidentified black letter font, probably from the
                                         15th century</p>
                                      </typeDesc>
                                      Example
                                      <typeDesc>
                                       <summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>
                                       <typeNote xml:id="Frak1">Blackletter face, showing
                                         similarities to those produced in Wuerzburg after 1470.</typeNote>
                                       <typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote>
                                      </typeDesc>
                                      Content model
                                      <content>
                                       <alternate>
                                        <classRef key="model.pLikeminOccurs="1"
                                         maxOccurs="unbounded"/>

                                        <sequence>
                                         <elementRef key="summaryminOccurs="0"/>
                                         <elementRef key="typeNoteminOccurs="1"
                                          maxOccurs="unbounded"/>

                                        </sequence>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element typeDesc
                                       {
                                          tei_att.global.attributes,
                                          ( tei_model.pLike+ | ( tei_summary?, tei_typeNote+ ) )
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-typeNote.html b/gl/dev/ref-typeNote.html index 06cada9e6..f541203c0 100644 --- a/gl/dev/ref-typeNote.html +++ b/gl/dev/ref-typeNote.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <typeNote>

                                      <typeNote> (typographic note) describes a particular font or other significant typographic feature distinguished within the description of a printed resource. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      Contained by
                                      msdescription: typeDesc
                                      May contain
                                      Example
                                      <typeNote scope="sole"> Printed in an Antiqua typeface showing strong Italianate influence.
                                      </typeNote>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <typeNote>

                                      <typeNote> (typographic note) describes a particular font or other significant typographic feature distinguished within the description of a printed resource. [10.7.2. Writing, Decoration, and Other Notations]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
                                      Contained by
                                      msdescription: typeDesc
                                      May contain
                                      Example
                                      <typeNote scope="sole"> Printed in an Antiqua typeface showing strong Italianate influence.
                                      </typeNote>
                                      Content model
                                      <content>
                                       <macroRef key="macro.specialPara"/>
                                      </content>
                                      Schema Declaration
                                       element typeNote
                                       {
                                          tei_att.global.attributes,
                                          tei_att.handFeatures.attributes,
                                          tei_macro.specialPara
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-unclear.html b/gl/dev/ref-unclear.html index 0bc8c92ea..3a1a9c182 100644 --- a/gl/dev/ref-unclear.html +++ b/gl/dev/ref-unclear.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <unclear>

                                      <unclear> (unclear) Character that cannot be identified unambiguously outside of its context. May contain character data and g only. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      reasonindicates why the material is hard to transcribe.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      illegible
                                      (illegible)
                                      inaudible
                                      (inaudible)
                                      faded
                                      (faded)
                                      background_noise
                                      (background noise)
                                      eccentric_ductus
                                      (eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
                                      <div>
                                       <head>Rx</head>
                                       <p>500 mg <unclear reason="illegible">placebo</unclear>
                                       </p>
                                      </div>
                                      Note

                                      One or more words may be used to describe the reason; usually each word will refer to a single cause.

                                      agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      rubbing
                                      damage results from rubbing of the leaf edges
                                      mildew
                                      damage results from mildew on the leaf surface
                                      smoke
                                      damage results from smoke
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.

                                      The damage, gap, del, unclear and supplied elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands.

                                      Example
                                      <u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <unclear>

                                      <unclear> (unclear) Character that cannot be identified unambiguously outside of its context. May contain character data and g only. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      reasonindicates why the material is hard to transcribe.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
                                      Suggested values include:
                                      illegible
                                      (illegible)
                                      inaudible
                                      (inaudible)
                                      faded
                                      (faded)
                                      background_noise
                                      (background noise)
                                      eccentric_ductus
                                      (eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
                                      <div>
                                       <head>Rx</head>
                                       <p>500 mg <unclear reason="illegible">placebo</unclear>
                                       </p>
                                      </div>
                                      Note

                                      One or more words may be used to describe the reason; usually each word will refer to a single cause.

                                      agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
                                      Status Optional
                                      Datatype teidata.enumerated
                                      Sample values include:
                                      rubbing
                                      damage results from rubbing of the leaf edges
                                      mildew
                                      damage results from mildew on the leaf surface
                                      smoke
                                      damage results from smoke
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.

                                      The damage, gap, del, unclear and supplied elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

                                      The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands.

                                      Example
                                      <u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element unclear
                                       {
                                          tei_att.global.attributes,
                                      @@ -43,4 +43,4 @@
                                          }?,
                                          attribute agent { teidata.enumerated }?,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-undo.html b/gl/dev/ref-undo.html index 2b873526e..154c8065d 100644 --- a/gl/dev/ref-undo.html +++ b/gl/dev/ref-undo.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <undo>

                                      <undo> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.spanning (@spanTo) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      targetpoints to one or more elements representing the interventions which are to be reverted or undone.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <line>This is <del change="#s2rend="overstrike">
                                        <seg xml:id="undo-a">just some</seg>
                                         sample <seg xml:id="undo-b">text</seg>,
                                         we need</del>
                                       <add change="#s2">not</add>
                                      a real example.</line>
                                      <undo target="#undo-a #undo-b"
                                       rend="dottedchange="#s3"/>

                                      This encoding represents the following sequence of events:

                                      • "This is just some sample text, we need a real example" is written
                                      • At stage s2, "just some sample text, we need" is deleted by overstriking, and "not" is added
                                      • At stage s3, parts of the deletion are cancelled by underdotting, thus reinstating the words "just some" and "text".
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <undo>

                                      <undo> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.spanning (@spanTo) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      targetpoints to one or more elements representing the interventions which are to be reverted or undone.
                                      Status Optional
                                      Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
                                      Member of
                                      Contained by
                                      May containEmpty element
                                      Example
                                      <line>This is <del change="#s2rend="overstrike">
                                        <seg xml:id="undo-a">just some</seg>
                                         sample <seg xml:id="undo-b">text</seg>,
                                         we need</del>
                                       <add change="#s2">not</add>
                                      a real example.</line>
                                      <undo target="#undo-a #undo-b"
                                       rend="dottedchange="#s3"/>

                                      This encoding represents the following sequence of events:

                                      • "This is just some sample text, we need a real example" is written
                                      • At stage s2, "just some sample text, we need" is deleted by overstriking, and "not" is added
                                      • At stage s3, parts of the deletion are cancelled by underdotting, thus reinstating the words "just some" and "text".
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element undo
                                       {
                                          tei_att.global.attributes,
                                      @@ -30,4 +30,4 @@
                                          tei_att.dimensions.attributes,
                                          attribute target { list { teidata.pointer+ } }?,
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-unicodeProp.html b/gl/dev/ref-unicodeProp.html index 682660b30..4e1a90284 100644 --- a/gl/dev/ref-unicodeProp.html +++ b/gl/dev/ref-unicodeProp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <unicodeProp>

                                      <unicodeProp> (unicode property) provides a Unicode property for a character (or glyph). [5.2.1. Character Properties]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
                                      namespecifies the normalized name of a Unicode property.
                                      Status Required
                                      Datatype teidata.xmlName
                                      Legal values are:
                                      Age
                                      AHex
                                      Alpha
                                      Alphabetic
                                      ASCII_Hex_Digit
                                      bc
                                      Bidi_C
                                      Bidi_Class
                                      Bidi_Control
                                      Bidi_M
                                      Bidi_Mirrored
                                      Bidi_Mirroring_Glyph
                                      Bidi_Paired_Bracket
                                      Bidi_Paired_Bracket_Type
                                      blk
                                      Block
                                      bmg
                                      bpb
                                      bpt
                                      Canonical_Combining_Class
                                      Case_Folding
                                      Case_Ignorable
                                      Cased
                                      ccc
                                      CE
                                      cf
                                      Changes_When_Casefolded
                                      Changes_When_Casemapped
                                      Changes_When_Lowercased
                                      Changes_When_NFKC_Casefolded
                                      Changes_When_Titlecased
                                      Changes_When_Uppercased
                                      CI
                                      Comp_Ex
                                      Composition_Exclusion
                                      CWCF
                                      CWCM
                                      CWKCF
                                      CWL
                                      CWT
                                      CWU
                                      Dash
                                      Decomposition_Mapping
                                      Decomposition_Type
                                      Default_Ignorable_Code_Point
                                      Dep
                                      Deprecated
                                      DI
                                      Dia
                                      Diacritic
                                      dm
                                      dt
                                      ea
                                      East_Asian_Width
                                      EqUIdeo
                                      Equivalent_Unified_Ideograph
                                      Expands_On_NFC
                                      Expands_On_NFD
                                      Expands_On_NFKC
                                      Expands_On_NFKD
                                      Ext
                                      Extender
                                      FC_NFKC
                                      FC_NFKC_Closure
                                      Full_Composition_Exclusion
                                      gc
                                      GCB
                                      General_Category
                                      Gr_Base
                                      Gr_Ext
                                      Gr_Link
                                      Grapheme_Base
                                      Grapheme_Cluster_Break
                                      Grapheme_Extend
                                      Grapheme_Link
                                      Hangul_Syllable_Type
                                      Hex
                                      Hex_Digit
                                      hst
                                      Hyphen
                                      ID_Continue
                                      ID_Start
                                      IDC
                                      Ideo
                                      Ideographic
                                      IDS
                                      IDS_Binary_Operator
                                      IDS_Trinary_Operator
                                      IDSB
                                      IDST
                                      Indic_Positional_Category
                                      Indic_Syllabic_Category
                                      InPC
                                      InSC
                                      isc
                                      ISO_Comment
                                      Jamo_Short_Name
                                      jg
                                      Join_C
                                      Join_Control
                                      Joining_Group
                                      Joining_Type
                                      JSN
                                      jt
                                      kAccountingNumeric
                                      kCompatibilityVariant
                                      kIICore
                                      kIRG_GSource
                                      kIRG_HSource
                                      kIRG_JSource
                                      kIRG_KPSource
                                      kIRG_KSource
                                      kIRG_MSource
                                      kIRG_TSource
                                      kIRG_USource
                                      kIRG_VSource
                                      kOtherNumeric
                                      kPrimaryNumeric
                                      kRSUnicode
                                      lb
                                      lc
                                      Line_Break
                                      LOE
                                      Logical_Order_Exception
                                      Lower
                                      Lowercase
                                      Lowercase_Mapping
                                      Math
                                      na
                                      na1
                                      Name
                                      Name_Alias
                                      NChar
                                      NFC_QC
                                      NFC_Quick_Check
                                      NFD_QC
                                      NFD_Quick_Check
                                      NFKC_Casefold
                                      NFKC_CF
                                      NFKC_QC
                                      NFKC_Quick_Check
                                      NFKD_QC
                                      NFKD_Quick_Check
                                      Noncharacter_Code_Point
                                      nt
                                      Numeric_Type
                                      Numeric_Value
                                      nv
                                      OAlpha
                                      ODI
                                      OGr_Ext
                                      OIDC
                                      OIDS
                                      OLower
                                      OMath
                                      Other_Alphabetic
                                      Other_Default_Ignorable_Code_Point
                                      Other_Grapheme_Extend
                                      Other_ID_Continue
                                      Other_ID_Start
                                      Other_Lowercase
                                      Other_Math
                                      Other_Uppercase
                                      OUpper
                                      Pat_Syn
                                      Pat_WS
                                      Pattern_Syntax
                                      Pattern_White_Space
                                      PCM
                                      Prepended_Concatenation_Mark
                                      QMark
                                      Quotation_Mark
                                      Radical
                                      Regional_Indicator
                                      RI
                                      SB
                                      sc
                                      scf
                                      Script
                                      Script_Extensions
                                      scx
                                      SD
                                      Sentence_Break
                                      Sentence_Terminal
                                      Simple_Case_Folding
                                      Simple_Lowercase_Mapping
                                      Simple_Titlecase_Mapping
                                      Simple_Uppercase_Mapping
                                      slc
                                      Soft_Dotted
                                      stc
                                      STerm
                                      suc
                                      tc
                                      Term
                                      Terminal_Punctuation
                                      Titlecase_Mapping
                                      uc
                                      UIdeo
                                      Unicode_1_Name
                                      Unified_Ideograph
                                      Upper
                                      Uppercase
                                      Uppercase_Mapping
                                      Variation_Selector
                                      Vertical_Orientation
                                      vo
                                      VS
                                      WB
                                      White_Space
                                      Word_Break
                                      WSpace
                                      XID_Continue
                                      XID_Start
                                      XIDC
                                      XIDS
                                      XO_NFC
                                      XO_NFD
                                      XO_NFKC
                                      XO_NFKD
                                      valuespecifies the value of a named Unicode property.
                                      Status Required
                                      Datatype teidata.text
                                      Contained by
                                      gaiji: glyph
                                      May containEmpty element
                                      Note

                                      A definitive list of current Unicode property names is provided in The Unicode Standard.

                                      Example
                                      <char xml:id="U4EBA_circled">
                                       <unicodeProp name="Decomposition_Mapping"
                                        value="circleversion="12.1"/>

                                       <localProp name="Name"
                                        value="CIRCLED IDEOGRAPH 4EBA"/>

                                       <localProp name="daikanwavalue="36"/>
                                       <mapping type="standard"></mapping>
                                      </char>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <unicodeProp>

                                      <unicodeProp> (unicode property) provides a Unicode property for a character (or glyph). [5.2.1. Character Properties]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
                                      namespecifies the normalized name of a Unicode property.
                                      Status Required
                                      Datatype teidata.xmlName
                                      Legal values are:
                                      Age
                                      AHex
                                      Alpha
                                      Alphabetic
                                      ASCII_Hex_Digit
                                      bc
                                      Bidi_C
                                      Bidi_Class
                                      Bidi_Control
                                      Bidi_M
                                      Bidi_Mirrored
                                      Bidi_Mirroring_Glyph
                                      Bidi_Paired_Bracket
                                      Bidi_Paired_Bracket_Type
                                      blk
                                      Block
                                      bmg
                                      bpb
                                      bpt
                                      Canonical_Combining_Class
                                      Case_Folding
                                      Case_Ignorable
                                      Cased
                                      ccc
                                      CE
                                      cf
                                      Changes_When_Casefolded
                                      Changes_When_Casemapped
                                      Changes_When_Lowercased
                                      Changes_When_NFKC_Casefolded
                                      Changes_When_Titlecased
                                      Changes_When_Uppercased
                                      CI
                                      Comp_Ex
                                      Composition_Exclusion
                                      CWCF
                                      CWCM
                                      CWKCF
                                      CWL
                                      CWT
                                      CWU
                                      Dash
                                      Decomposition_Mapping
                                      Decomposition_Type
                                      Default_Ignorable_Code_Point
                                      Dep
                                      Deprecated
                                      DI
                                      Dia
                                      Diacritic
                                      dm
                                      dt
                                      ea
                                      East_Asian_Width
                                      EqUIdeo
                                      Equivalent_Unified_Ideograph
                                      Expands_On_NFC
                                      Expands_On_NFD
                                      Expands_On_NFKC
                                      Expands_On_NFKD
                                      Ext
                                      Extender
                                      FC_NFKC
                                      FC_NFKC_Closure
                                      Full_Composition_Exclusion
                                      gc
                                      GCB
                                      General_Category
                                      Gr_Base
                                      Gr_Ext
                                      Gr_Link
                                      Grapheme_Base
                                      Grapheme_Cluster_Break
                                      Grapheme_Extend
                                      Grapheme_Link
                                      Hangul_Syllable_Type
                                      Hex
                                      Hex_Digit
                                      hst
                                      Hyphen
                                      ID_Continue
                                      ID_Start
                                      IDC
                                      Ideo
                                      Ideographic
                                      IDS
                                      IDS_Binary_Operator
                                      IDS_Trinary_Operator
                                      IDSB
                                      IDST
                                      Indic_Positional_Category
                                      Indic_Syllabic_Category
                                      InPC
                                      InSC
                                      isc
                                      ISO_Comment
                                      Jamo_Short_Name
                                      jg
                                      Join_C
                                      Join_Control
                                      Joining_Group
                                      Joining_Type
                                      JSN
                                      jt
                                      kAccountingNumeric
                                      kCompatibilityVariant
                                      kIICore
                                      kIRG_GSource
                                      kIRG_HSource
                                      kIRG_JSource
                                      kIRG_KPSource
                                      kIRG_KSource
                                      kIRG_MSource
                                      kIRG_TSource
                                      kIRG_USource
                                      kIRG_VSource
                                      kOtherNumeric
                                      kPrimaryNumeric
                                      kRSUnicode
                                      lb
                                      lc
                                      Line_Break
                                      LOE
                                      Logical_Order_Exception
                                      Lower
                                      Lowercase
                                      Lowercase_Mapping
                                      Math
                                      na
                                      na1
                                      Name
                                      Name_Alias
                                      NChar
                                      NFC_QC
                                      NFC_Quick_Check
                                      NFD_QC
                                      NFD_Quick_Check
                                      NFKC_Casefold
                                      NFKC_CF
                                      NFKC_QC
                                      NFKC_Quick_Check
                                      NFKD_QC
                                      NFKD_Quick_Check
                                      Noncharacter_Code_Point
                                      nt
                                      Numeric_Type
                                      Numeric_Value
                                      nv
                                      OAlpha
                                      ODI
                                      OGr_Ext
                                      OIDC
                                      OIDS
                                      OLower
                                      OMath
                                      Other_Alphabetic
                                      Other_Default_Ignorable_Code_Point
                                      Other_Grapheme_Extend
                                      Other_ID_Continue
                                      Other_ID_Start
                                      Other_Lowercase
                                      Other_Math
                                      Other_Uppercase
                                      OUpper
                                      Pat_Syn
                                      Pat_WS
                                      Pattern_Syntax
                                      Pattern_White_Space
                                      PCM
                                      Prepended_Concatenation_Mark
                                      QMark
                                      Quotation_Mark
                                      Radical
                                      Regional_Indicator
                                      RI
                                      SB
                                      sc
                                      scf
                                      Script
                                      Script_Extensions
                                      scx
                                      SD
                                      Sentence_Break
                                      Sentence_Terminal
                                      Simple_Case_Folding
                                      Simple_Lowercase_Mapping
                                      Simple_Titlecase_Mapping
                                      Simple_Uppercase_Mapping
                                      slc
                                      Soft_Dotted
                                      stc
                                      STerm
                                      suc
                                      tc
                                      Term
                                      Terminal_Punctuation
                                      Titlecase_Mapping
                                      uc
                                      UIdeo
                                      Unicode_1_Name
                                      Unified_Ideograph
                                      Upper
                                      Uppercase
                                      Uppercase_Mapping
                                      Variation_Selector
                                      Vertical_Orientation
                                      vo
                                      VS
                                      WB
                                      White_Space
                                      Word_Break
                                      WSpace
                                      XID_Continue
                                      XID_Start
                                      XIDC
                                      XIDS
                                      XO_NFC
                                      XO_NFD
                                      XO_NFKC
                                      XO_NFKD
                                      valuespecifies the value of a named Unicode property.
                                      Status Required
                                      Datatype teidata.text
                                      Contained by
                                      gaiji: glyph
                                      May containEmpty element
                                      Note

                                      A definitive list of current Unicode property names is provided in The Unicode Standard.

                                      Example
                                      <char xml:id="U4EBA_circled">
                                       <unicodeProp name="Decomposition_Mapping"
                                        value="circleversion="12.1"/>

                                       <localProp name="Name"
                                        value="CIRCLED IDEOGRAPH 4EBA"/>

                                       <localProp name="daikanwavalue="36"/>
                                       <mapping type="standard"></mapping>
                                      </char>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element unicodeProp
                                       {
                                          tei_att.global.attributes,
                                      @@ -251,4 +251,4 @@
                                          },
                                          attribute value { teidata.text },
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-unihanProp.html b/gl/dev/ref-unihanProp.html index d6b8118ac..947058042 100644 --- a/gl/dev/ref-unihanProp.html +++ b/gl/dev/ref-unihanProp.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <unihanProp>

                                      <unihanProp> (unihan property) holds the name and value of a normative or informative Unihan character (or glyph) property as part of its attributes. [5.2.1. Character Properties]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
                                      namespecifies the normalized name of a unicode han database (Unihan) property
                                      Status Required
                                      Datatype teidata.xmlName
                                      Legal values are:
                                      kZVariant
                                      kAccountingNumeric
                                      kBigFive
                                      kCCCII
                                      kCNS1986
                                      kCNS1992
                                      kCangjie
                                      kCantonese
                                      kCheungBauer
                                      kCheungBauerIndex
                                      kCihaiT
                                      kCompatibilityVariant
                                      kCowles
                                      kDaeJaweon
                                      kDefinition
                                      kEACC
                                      kFenn
                                      kFennIndex
                                      kFourCornerCode
                                      kFrequency
                                      kGB0
                                      kGB1
                                      kGB3
                                      kGB5
                                      kGB7
                                      kGB8
                                      kGSR
                                      kGradeLevel
                                      kHDZRadBreak
                                      kHKGlyph
                                      kHKSCS
                                      kHanYu
                                      kHangul
                                      kHanyuPinlu
                                      kHanyuPinyin
                                      kIBMJapan
                                      kIICore
                                      kIRGDaeJaweon
                                      kIRGDaiKanwaZiten
                                      kIRGHanyuDaZidian
                                      kIRGKangXi
                                      kIRG_GSource
                                      kIRG_HSource
                                      kIRG_JSource
                                      kIRG_KPSource
                                      kIRG_KSource
                                      kIRG_MSource
                                      kIRG_TSource
                                      kIRG_USource
                                      kIRG_VSource
                                      kJIS0213
                                      kJa
                                      kJapaneseKun
                                      kJapaneseOn
                                      kJinmeiyoKanji
                                      kJis0
                                      kJis1
                                      kJoyoKanji
                                      kKPS0
                                      kKPS1
                                      kKSC0
                                      kKSC1
                                      kKangXi
                                      kKarlgren
                                      kKorean
                                      kKoreanEducationHanja
                                      kKoreanName
                                      kLau
                                      kMainlandTelegraph
                                      kMandarin
                                      kMatthews
                                      kMeyerWempe
                                      kMorohashi
                                      kNelson
                                      kOtherNumeric
                                      kPhonetic
                                      kPrimaryNumeric
                                      kPseudoGB1
                                      kRSAdobe_Japan1_6
                                      kRSJapanese
                                      kRSKanWa
                                      kRSKangXi
                                      kRSKorean
                                      kRSUnicode
                                      kSBGY
                                      kSemanticVariant
                                      kSimplifiedVariant
                                      kSpecializedSemanticVariant
                                      kTGH
                                      kTaiwanTelegraph
                                      kTang
                                      kTotalStrokes
                                      kTraditionalVariant
                                      kVietnamese
                                      kXHC1983
                                      kXerox
                                      valuespecifies the value of a named Unihan property
                                      Status Required
                                      Datatype teidata.word
                                      Contained by
                                      gaiji: glyph
                                      May containEmpty element
                                      Note

                                      A definitive list of current Unihan property names is provided in the Unicode Han Database.

                                      Example
                                      <unihanProp name="kRSKangXivalue="120.5"
                                       version="12.1"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <unihanProp>

                                      <unihanProp> (unihan property) holds the name and value of a normative or informative Unihan character (or glyph) property as part of its attributes. [5.2.1. Character Properties]
                                      Modulegaiji
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.gaijiProp (name, value, @version)
                                      namespecifies the normalized name of a unicode han database (Unihan) property
                                      Status Required
                                      Datatype teidata.xmlName
                                      Legal values are:
                                      kZVariant
                                      kAccountingNumeric
                                      kBigFive
                                      kCCCII
                                      kCNS1986
                                      kCNS1992
                                      kCangjie
                                      kCantonese
                                      kCheungBauer
                                      kCheungBauerIndex
                                      kCihaiT
                                      kCompatibilityVariant
                                      kCowles
                                      kDaeJaweon
                                      kDefinition
                                      kEACC
                                      kFenn
                                      kFennIndex
                                      kFourCornerCode
                                      kFrequency
                                      kGB0
                                      kGB1
                                      kGB3
                                      kGB5
                                      kGB7
                                      kGB8
                                      kGSR
                                      kGradeLevel
                                      kHDZRadBreak
                                      kHKGlyph
                                      kHKSCS
                                      kHanYu
                                      kHangul
                                      kHanyuPinlu
                                      kHanyuPinyin
                                      kIBMJapan
                                      kIICore
                                      kIRGDaeJaweon
                                      kIRGDaiKanwaZiten
                                      kIRGHanyuDaZidian
                                      kIRGKangXi
                                      kIRG_GSource
                                      kIRG_HSource
                                      kIRG_JSource
                                      kIRG_KPSource
                                      kIRG_KSource
                                      kIRG_MSource
                                      kIRG_TSource
                                      kIRG_USource
                                      kIRG_VSource
                                      kJIS0213
                                      kJa
                                      kJapaneseKun
                                      kJapaneseOn
                                      kJinmeiyoKanji
                                      kJis0
                                      kJis1
                                      kJoyoKanji
                                      kKPS0
                                      kKPS1
                                      kKSC0
                                      kKSC1
                                      kKangXi
                                      kKarlgren
                                      kKorean
                                      kKoreanEducationHanja
                                      kKoreanName
                                      kLau
                                      kMainlandTelegraph
                                      kMandarin
                                      kMatthews
                                      kMeyerWempe
                                      kMorohashi
                                      kNelson
                                      kOtherNumeric
                                      kPhonetic
                                      kPrimaryNumeric
                                      kPseudoGB1
                                      kRSAdobe_Japan1_6
                                      kRSJapanese
                                      kRSKanWa
                                      kRSKangXi
                                      kRSKorean
                                      kRSUnicode
                                      kSBGY
                                      kSemanticVariant
                                      kSimplifiedVariant
                                      kSpecializedSemanticVariant
                                      kTGH
                                      kTaiwanTelegraph
                                      kTang
                                      kTotalStrokes
                                      kTraditionalVariant
                                      kVietnamese
                                      kXHC1983
                                      kXerox
                                      valuespecifies the value of a named Unihan property
                                      Status Required
                                      Datatype teidata.word
                                      Contained by
                                      gaiji: glyph
                                      May containEmpty element
                                      Note

                                      A definitive list of current Unihan property names is provided in the Unicode Han Database.

                                      Example
                                      <unihanProp name="kRSKangXivalue="120.5"
                                       version="12.1"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element unihanProp
                                       {
                                          tei_att.global.attributes,
                                      @@ -127,4 +127,4 @@
                                          },
                                          attribute value { teidata.word },
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-unit.html b/gl/dev/ref-unit.html index 107efc5f2..1e6b7ba4a 100644 --- a/gl/dev/ref-unit.html +++ b/gl/dev/ref-unit.html @@ -22,11 +22,11 @@ }); });

                                      <unit>

                                      <unit> contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. [3.6.3. Numbers and -Measures]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.measurement (@unit, @unitRef, @quantity, @commodity)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      Here is an example of a unit element holding a unitRef attribute that points to a definition of the unit in the TEI header.

                                      <measure>
                                       <num>3</num>
                                       <unit unitRef="#ell">ells</unit>
                                      </measure>
                                      <!-- In the TEI Header: -->
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="ell">
                                         <label>ell</label>
                                         <placeName ref="#iceland"/>
                                         <desc>A unit of measure for cloth, roughly equivalent to 18 inches, or from an adult male’s elbow to the tip of the middle finger.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <measure>
                                       <num>2</num>
                                       <unit>kg</unit>
                                      </measure>
                                      Example
                                      <measure type="value">
                                       <num>3</num>
                                       <unit type="timeunit="min">minute</unit>
                                      </measure>
                                      Example
                                      <measure type="interval">
                                       <num atLeast="1.2">1.2</num> to <num atMost="5.6">5.6</num>
                                       <unit type="velocityunit="km/h">km/h</unit>
                                      </measure>
                                      Example
                                      <p>Light travels at <num value="3E10">3×10^10</num>
                                       <unit type="rateunit="cm/s">
                                        <unit type="space">cm</unit> per <unit type="time">second</unit>
                                       </unit>.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +Measures]
                                      Modulecore
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.measurement (@unit, @unitRef, @quantity, @commodity)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      Here is an example of a unit element holding a unitRef attribute that points to a definition of the unit in the TEI header.

                                      <measure>
                                       <num>3</num>
                                       <unit unitRef="#ell">ells</unit>
                                      </measure>
                                      <!-- In the TEI Header: -->
                                      <encodingDesc>
                                       <unitDecl>
                                        <unitDef xml:id="ell">
                                         <label>ell</label>
                                         <placeName ref="#iceland"/>
                                         <desc>A unit of measure for cloth, roughly equivalent to 18 inches, or from an adult male’s elbow to the tip of the middle finger.</desc>
                                        </unitDef>
                                       </unitDecl>
                                      </encodingDesc>
                                      Example
                                      <measure>
                                       <num>2</num>
                                       <unit>kg</unit>
                                      </measure>
                                      Example
                                      <measure type="value">
                                       <num>3</num>
                                       <unit type="timeunit="min">minute</unit>
                                      </measure>
                                      Example
                                      <measure type="interval">
                                       <num atLeast="1.2">1.2</num> to <num atMost="5.6">5.6</num>
                                       <unit type="velocityunit="km/h">km/h</unit>
                                      </measure>
                                      Example
                                      <p>Light travels at <num value="3E10">3×10^10</num>
                                       <unit type="rateunit="cm/s">
                                        <unit type="space">cm</unit> per <unit type="time">second</unit>
                                       </unit>.</p>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element unit
                                       {
                                          tei_att.global.attributes,
                                          tei_att.typed.attributes,
                                          tei_att.measurement.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-unitDecl.html b/gl/dev/ref-unitDecl.html index 3c0a159b4..c2c8a382d 100644 --- a/gl/dev/ref-unitDecl.html +++ b/gl/dev/ref-unitDecl.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <unitDecl>

                                      <unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
                                      Moduleheader
                                      Attributesatt.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      header: unitDef
                                      Example
                                      <unitDecl>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">kin</label>
                                        <conversion fromUnit="#両toUnit="#斤"
                                         formula="16"/>

                                       </unitDef>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">ryo</label>
                                        <conversion fromUnit="#分toUnit="#両"
                                         formula="4"/>

                                       </unitDef>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">Bu</label>
                                        <conversion fromUnit="#銖toUnit="#分"
                                         formula="6"/>

                                       </unitDef>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">Shu</label>
                                       </unitDef>
                                      </unitDecl>
                                      Content model
                                      <content>
                                       <elementRef key="unitDefminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                      +    

                                      <unitDecl>

                                      <unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
                                      Moduleheader
                                      Attributesatt.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May contain
                                      header: unitDef
                                      Example
                                      <unitDecl>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">kin</label>
                                        <conversion fromUnit="#両toUnit="#斤"
                                         formula="16"/>

                                       </unitDef>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">ryo</label>
                                        <conversion fromUnit="#分toUnit="#両"
                                         formula="4"/>

                                       </unitDef>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">Bu</label>
                                        <conversion fromUnit="#銖toUnit="#分"
                                         formula="6"/>

                                       </unitDef>
                                       <unitDef xml:id="type="weight">
                                        <label xml:lang="ja"></label>
                                        <label xml:lang="ja-Latn">Shu</label>
                                       </unitDef>
                                      </unitDecl>
                                      Content model
                                      <content>
                                       <elementRef key="unitDefminOccurs="1"
                                        maxOccurs="unbounded"/>

                                      </content>
                                      Schema Declaration
                                       element unitDecl
                                       {
                                          tei_att.canonical.attributes,
                                          tei_att.datable.attributes,
                                          tei_att.global.attributes,
                                          tei_unitDef+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-unitDef.html b/gl/dev/ref-unitDef.html index afee8ea77..86df06b73 100644 --- a/gl/dev/ref-unitDef.html +++ b/gl/dev/ref-unitDef.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <unitDef>

                                      <unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref) att.typed (@type, @subtype)
                                      Contained by
                                      header: unitDecl
                                      May contain
                                      Example
                                      <unitDecl>
                                       <unitDef xml:id="pechystype="length">
                                        <label>πῆχυς</label>
                                        <placeName ref="#athens"/>
                                        <conversion fromUnit="#daktylos"
                                         toUnit="#pechysformula="$fromUnit div 24"/>

                                        <desc>Equivalent to a cubit or 24 daktyloi.</desc>
                                       </unitDef>
                                       <unitDef xml:id="daktylostype="length">
                                        <label>δάκτυλος</label>
                                        <placeName ref="#athens"/>
                                        <desc>A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece.</desc>
                                       </unitDef>
                                      </unitDecl>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.labelLike"
                                         minOccurs="1"/>

                                        <classRef key="model.placeNamePart"
                                         minOccurs="0"/>

                                        <elementRef key="conversion"
                                         minOccurs="0"/>

                                        <elementRef key="unitminOccurs="0"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <unitDef>

                                      <unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref) att.typed (@type, @subtype)
                                      Contained by
                                      header: unitDecl
                                      May contain
                                      Example
                                      <unitDecl>
                                       <unitDef xml:id="pechystype="length">
                                        <label>πῆχυς</label>
                                        <placeName ref="#athens"/>
                                        <conversion fromUnit="#daktylos"
                                         toUnit="#pechysformula="$fromUnit div 24"/>

                                        <desc>Equivalent to a cubit or 24 daktyloi.</desc>
                                       </unitDef>
                                       <unitDef xml:id="daktylostype="length">
                                        <label>δάκτυλος</label>
                                        <placeName ref="#athens"/>
                                        <desc>A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece.</desc>
                                       </unitDef>
                                      </unitDecl>
                                      Content model
                                      <content>
                                       <alternate minOccurs="1"
                                        maxOccurs="unbounded">

                                        <classRef key="model.labelLike"
                                         minOccurs="1"/>

                                        <classRef key="model.placeNamePart"
                                         minOccurs="0"/>

                                        <elementRef key="conversion"
                                         minOccurs="0"/>

                                        <elementRef key="unitminOccurs="0"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element unitDef
                                       {
                                          tei_att.global.attributes,
                                      @@ -34,4 +34,4 @@
                                           | tei_conversion?
                                           | tei_unit?
                                          )+
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-variantEncoding.html b/gl/dev/ref-variantEncoding.html index 1738e63b6..842d98282 100644 --- a/gl/dev/ref-variantEncoding.html +++ b/gl/dev/ref-variantEncoding.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <variantEncoding>

                                      <variantEncoding> (variant encoding) declares the method used to encode text-critical variants. [12.1.1. The Apparatus Entry]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      methodindicates which method is used to encode the apparatus of variants.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      location-referenced
                                      apparatus uses line numbers or other canonical reference scheme referenced in a base text.
                                      double-end-point
                                      apparatus indicates the precise locations of the beginning and ending of each lemma relative to a base text.
                                      parallel-segmentation
                                      alternate readings of a passage are given in parallel in the text; no notion of a base text is necessary.
                                      Note

                                      The value ‘parallel-segmentation’ requires in-line encoding of the apparatus.

                                      locationindicates whether the apparatus appears within the running text or external to it.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Schematron

                                      <sch:rule context="tei:variantEncoding">
                                      <sch:report test="@location eq 'external' and @method eq 'parallel-segmentation'"> The @location value "external" is inconsistent with the
                                      parallel-segmentation method of apparatus markup.</sch:report>
                                      </sch:rule>
                                      Legal values are:
                                      internal
                                      apparatus appears within the running text.
                                      external
                                      apparatus appears outside the base text.
                                      Note

                                      The value ‘external’ is inconsistent with the parallel-segmentation method of apparatus markup.

                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May containEmpty element
                                      Example
                                      <variantEncoding method="location-referenced"
                                       location="external"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <variantEncoding>

                                      <variantEncoding> (variant encoding) declares the method used to encode text-critical variants. [12.1.1. The Apparatus Entry]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      methodindicates which method is used to encode the apparatus of variants.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Legal values are:
                                      location-referenced
                                      apparatus uses line numbers or other canonical reference scheme referenced in a base text.
                                      double-end-point
                                      apparatus indicates the precise locations of the beginning and ending of each lemma relative to a base text.
                                      parallel-segmentation
                                      alternate readings of a passage are given in parallel in the text; no notion of a base text is necessary.
                                      Note

                                      The value ‘parallel-segmentation’ requires in-line encoding of the apparatus.

                                      locationindicates whether the apparatus appears within the running text or external to it.
                                      Status Required
                                      Datatype teidata.enumerated
                                      Schematron

                                      <sch:rule context="tei:variantEncoding">
                                      <sch:report test="@location eq 'external' and @method eq 'parallel-segmentation'"> The @location value "external" is inconsistent with the
                                      parallel-segmentation method of apparatus markup.</sch:report>
                                      </sch:rule>
                                      Legal values are:
                                      internal
                                      apparatus appears within the running text.
                                      external
                                      apparatus appears outside the base text.
                                      Note

                                      The value ‘external’ is inconsistent with the parallel-segmentation method of apparatus markup.

                                      Member of
                                      Contained by
                                      header: encodingDesc
                                      May containEmpty element
                                      Example
                                      <variantEncoding method="location-referenced"
                                       location="external"/>
                                      Content model
                                      <content>
                                       <empty/>
                                      </content>
                                      Schema Declaration
                                       element variantEncoding
                                       {
                                          tei_att.global.attributes,
                                      @@ -31,4 +31,4 @@
                                          },
                                          attribute location { "internal" | "external" },
                                          empty
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-w.html b/gl/dev/ref-w.html index ee56d7acf..3a73e5838 100644 --- a/gl/dev/ref-w.html +++ b/gl/dev/ref-w.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <w>

                                      <w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.4.2. Lightweight Linguistic Annotation]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      This example is adapted from the Folger Library’s Early Modern English Drama version of The Wits: a Comedy by William Davenant.

                                      <l>
                                       <w lemma="itpos="pn"
                                        xml:id="A19883-003-a-0100">
                                      IT</w>
                                       <w lemma="havepos="vvz"
                                        xml:id="A19883-003-a-0110">
                                      hath</w>
                                       <w lemma="bepos="vvn"
                                        xml:id="A19883-003-a-0120">
                                      been</w>
                                       <w lemma="saypos="vvn"
                                        xml:id="A19883-003-a-0130">
                                      said</w>
                                       <w lemma="ofpos="acp-p"
                                        xml:id="A19883-003-a-0140">
                                      of</w>
                                       <w lemma="oldpos="j"
                                        xml:id="A19883-003-a-0150">
                                      old</w>
                                       <pc xml:id="A19883-003-a-0160">,</pc>
                                       <w lemma="thatpos="cs"
                                        xml:id="A19883-003-a-0170">
                                      that</w>
                                       <w lemma="playpos="vvz"
                                        xml:id="A19883-003-a-0180">

                                        <choice>
                                         <orig>Playes</orig>
                                         <reg>Plays</reg>
                                        </choice>
                                       </w>
                                       <w lemma="bepos="vvb"
                                        xml:id="A19883-003-a-0190">
                                      are</w>
                                       <w lemma="feastpos="n2"
                                        xml:id="A19883-003-a-0200">
                                      Feasts</w>
                                       <pc xml:id="A19883-003-a-0210">,</pc>
                                      </l>
                                      <l xml:id="A19883-e100220">
                                       <w lemma="poetpos="n2"
                                        xml:id="A19883-003-a-0220">
                                      Poets</w>
                                       <w lemma="thepos="d"
                                        xml:id="A19883-003-a-0230">
                                      the</w>
                                       <w lemma="cookpos="n2"
                                        xml:id="A19883-003-a-0240">

                                        <choice>
                                         <orig>Cookes</orig>
                                         <reg>Cooks</reg>
                                        </choice>
                                       </w>
                                       <pc xml:id="A19883-003-a-0250">,</pc>
                                       <w lemma="andpos="cc"
                                        xml:id="A19883-003-a-0260">
                                      and</w>
                                       <w lemma="thepos="d"
                                        xml:id="A19883-003-a-0270">
                                      the</w>
                                       <w lemma="spectatorpos="n2"
                                        xml:id="A19883-003-a-0280">
                                      Spectators</w>
                                       <w lemma="guestpos="n2"
                                        xml:id="A19883-003-a-0290">
                                      Guests</w>
                                       <pc xml:id="A19883-003-a-0300">,</pc>
                                      </l>
                                      <l xml:id="A19883-e100230">
                                       <w lemma="thepos="d"
                                        xml:id="A19883-003-a-0310">
                                      The</w>
                                       <w lemma="actorpos="n2"
                                        xml:id="A19883-003-a-0320">
                                      Actors</w>
                                       <w lemma="waiterpos="n2"
                                        xml:id="A19883-003-a-0330">
                                      Waiters</w>
                                       <pc xml:id="A19883-003-a-0340">:</pc>
                                      <!-- ... -->
                                      </l>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="seg"/>
                                        <elementRef key="w"/>
                                        <elementRef key="m"/>
                                        <elementRef key="c"/>
                                        <elementRef key="pc"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.lPart"/>
                                        <classRef key="model.hiLike"/>
                                        <classRef key="model.pPart.edit"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <w>

                                      <w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.4.2. Lightweight Linguistic Annotation]
                                      Moduleanalysis
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.metrical (@met, @real, @rhyme)) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.linguistic (@lemma, @lemmaRef, @pos, @msd, @join) (att.lexicographic.normalized (@norm, @orig)) att.notated (@notation)
                                      Member of
                                      Contained by
                                      May contain
                                      Example

                                      This example is adapted from the Folger Library’s Early Modern English Drama version of The Wits: a Comedy by William Davenant.

                                      <l>
                                       <w lemma="itpos="pn"
                                        xml:id="A19883-003-a-0100">
                                      IT</w>
                                       <w lemma="havepos="vvz"
                                        xml:id="A19883-003-a-0110">
                                      hath</w>
                                       <w lemma="bepos="vvn"
                                        xml:id="A19883-003-a-0120">
                                      been</w>
                                       <w lemma="saypos="vvn"
                                        xml:id="A19883-003-a-0130">
                                      said</w>
                                       <w lemma="ofpos="acp-p"
                                        xml:id="A19883-003-a-0140">
                                      of</w>
                                       <w lemma="oldpos="j"
                                        xml:id="A19883-003-a-0150">
                                      old</w>
                                       <pc xml:id="A19883-003-a-0160">,</pc>
                                       <w lemma="thatpos="cs"
                                        xml:id="A19883-003-a-0170">
                                      that</w>
                                       <w lemma="playpos="vvz"
                                        xml:id="A19883-003-a-0180">

                                        <choice>
                                         <orig>Playes</orig>
                                         <reg>Plays</reg>
                                        </choice>
                                       </w>
                                       <w lemma="bepos="vvb"
                                        xml:id="A19883-003-a-0190">
                                      are</w>
                                       <w lemma="feastpos="n2"
                                        xml:id="A19883-003-a-0200">
                                      Feasts</w>
                                       <pc xml:id="A19883-003-a-0210">,</pc>
                                      </l>
                                      <l xml:id="A19883-e100220">
                                       <w lemma="poetpos="n2"
                                        xml:id="A19883-003-a-0220">
                                      Poets</w>
                                       <w lemma="thepos="d"
                                        xml:id="A19883-003-a-0230">
                                      the</w>
                                       <w lemma="cookpos="n2"
                                        xml:id="A19883-003-a-0240">

                                        <choice>
                                         <orig>Cookes</orig>
                                         <reg>Cooks</reg>
                                        </choice>
                                       </w>
                                       <pc xml:id="A19883-003-a-0250">,</pc>
                                       <w lemma="andpos="cc"
                                        xml:id="A19883-003-a-0260">
                                      and</w>
                                       <w lemma="thepos="d"
                                        xml:id="A19883-003-a-0270">
                                      the</w>
                                       <w lemma="spectatorpos="n2"
                                        xml:id="A19883-003-a-0280">
                                      Spectators</w>
                                       <w lemma="guestpos="n2"
                                        xml:id="A19883-003-a-0290">
                                      Guests</w>
                                       <pc xml:id="A19883-003-a-0300">,</pc>
                                      </l>
                                      <l xml:id="A19883-e100230">
                                       <w lemma="thepos="d"
                                        xml:id="A19883-003-a-0310">
                                      The</w>
                                       <w lemma="actorpos="n2"
                                        xml:id="A19883-003-a-0320">
                                      Actors</w>
                                       <w lemma="waiterpos="n2"
                                        xml:id="A19883-003-a-0330">
                                      Waiters</w>
                                       <pc xml:id="A19883-003-a-0340">:</pc>
                                      <!-- ... -->
                                      </l>
                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <elementRef key="seg"/>
                                        <elementRef key="w"/>
                                        <elementRef key="m"/>
                                        <elementRef key="c"/>
                                        <elementRef key="pc"/>
                                        <classRef key="model.global"/>
                                        <classRef key="model.lPart"/>
                                        <classRef key="model.hiLike"/>
                                        <classRef key="model.pPart.edit"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element w
                                       {
                                          tei_att.global.attributes,
                                      @@ -42,4 +42,4 @@
                                           | tei_model.hiLike
                                           | tei_model.pPart.edit
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-watermark.html b/gl/dev/ref-watermark.html index 7f12e94ed..98161a8dd 100644 --- a/gl/dev/ref-watermark.html +++ b/gl/dev/ref-watermark.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <watermark>

                                      <watermark> (watermark) contains a word or phrase describing a watermark or similar device. [10.3.3. Watermarks and Stamps]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <support>
                                       <p>
                                        <material>Rag paper</material> with <watermark>anchor</watermark> watermark</p>
                                      </support>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      -element watermark { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      <watermark>

                                      <watermark> (watermark) contains a word or phrase describing a watermark or similar device. [10.3.3. Watermarks and Stamps]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
                                      Member of
                                      Contained by
                                      May contain
                                      Example
                                      <support>
                                       <p>
                                        <material>Rag paper</material> with <watermark>anchor</watermark> watermark</p>
                                      </support>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +element watermark { tei_att.global.attributes, tei_macro.phraseSeq }

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-width.html b/gl/dev/ref-width.html index c3c76b7d6..99877391f 100644 --- a/gl/dev/ref-width.html +++ b/gl/dev/ref-width.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <width>

                                      <width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.

                                      Example
                                      <width unit="in">4</width>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <width>

                                      <width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
                                      Modulemsdescription
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@precision, @unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
                                      Member of
                                      Contained by
                                      May contain
                                      gaiji: g
                                      character data
                                      Note

                                      If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.

                                      Example
                                      <width unit="in">4</width>
                                      Content model
                                      <content>
                                       <macroRef key="macro.xtext"/>
                                      </content>
                                      Schema Declaration
                                       element width
                                       {
                                          tei_att.global.attributes,
                                          tei_att.dimensions.attributes,
                                          tei_macro.xtext
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-wit.html b/gl/dev/ref-wit.html index 3dea29f06..e721995a9 100644 --- a/gl/dev/ref-wit.html +++ b/gl/dev/ref-wit.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <wit>

                                      <wit> (wit) contains a list of one or more sigla of witnesses attesting a given reading, in a textual variation. [12.1.4. Witness Information]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.rdgPart (@wit)
                                      Member of
                                      Contained by
                                      textcrit: app lem rdg rdgGrp
                                      May contain
                                      Note

                                      This element represents the same information as that provided by the wit attribute of the reading; it may be used to record the exact form of the sigla given in the source edition, when that is of interest.

                                      Example
                                      <rdg wit="#El #Hg">Experience</rdg>
                                      <wit>Ellesmere, Hengwryt</wit>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <wit>

                                      <wit> (wit) contains a list of one or more sigla of witnesses attesting a given reading, in a textual variation. [12.1.4. Witness Information]
                                      Moduletextcrit
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.rdgPart (@wit)
                                      Member of
                                      Contained by
                                      textcrit: app lem rdg rdgGrp
                                      May contain
                                      Note

                                      This element represents the same information as that provided by the wit attribute of the reading; it may be used to record the exact form of the sigla given in the source edition, when that is of interest.

                                      Example
                                      <rdg wit="#El #Hg">Experience</rdg>
                                      <wit>Ellesmere, Hengwryt</wit>
                                      Content model
                                      <content>
                                       <macroRef key="macro.phraseSeq"/>
                                      </content>
                                      Schema Declaration
                                       element wit
                                       {
                                          tei_att.global.attributes,
                                          tei_att.rdgPart.attributes,
                                          tei_macro.phraseSeq
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-xenoData.html b/gl/dev/ref-xenoData.html index d775c08eb..47d2bc354 100644 --- a/gl/dev/ref-xenoData.html +++ b/gl/dev/ref-xenoData.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <xenoData>

                                      <xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      header: teiHeader
                                      May containANY
                                      Example

                                      This example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second xenoData block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the xenoData block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [ID SG-id in TEI Guidelines]). Do note, however, that if the contents of the xenoData block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.

                                      <xenoData>
                                       <rdf:RDF>
                                        <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">
                                         <dc:title>The description of a new world, called the blazing-world</dc:title>
                                         <dc:creator>The Duchess of Newcastle</dc:creator>
                                         <dc:date>1667</dc:date>
                                         <dc:identifier>British Library, 8407.h.10</dc:identifier>
                                         <dc:subject>utopian fiction</dc:subject>
                                        </rdf:Description>
                                       </rdf:RDF>
                                      </xenoData>
                                      <xenoData>
                                       <rdf:RDF>
                                        <rdf:Description rdf:about="">
                                         <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>
                                         <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>
                                         <dc:publisher>Women Writers Project</dc:publisher>
                                         <dc:date>2002-02-12</dc:date>
                                         <dc:subject>utopian fiction</dc:subject>
                                        </rdf:Description>
                                       </rdf:RDF>
                                      </xenoData>
                                      Example

                                      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/.

                                      <xenoData>
                                       <rdf:RDF>
                                        <cc:Work rdf:about="">
                                         <dc:title>Applied Software Project Management - review</dc:title>
                                         <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
                                         <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>
                                        </cc:Work>
                                        <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">
                                         <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
                                         <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
                                         <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
                                         <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
                                         <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
                                         <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>
                                        </cc:License>
                                       </rdf:RDF>
                                      </xenoData>
                                      Example

                                      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/.

                                      <xenoData>
                                       <oai_dc:dc>
                                        <dc:title>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)</dc:title>
                                        <dc:date>1858-11-12</dc:date>
                                        <dc:creator>Trevelyan</dc:creator>
                                        <dc:publisher>University of Victoria Humanities Computing and Media
                                           Centre, and UVic Libraries</dc:publisher>
                                        <dc:type>InteractiveResource</dc:type>
                                        <dc:format>application/xhtml+xml</dc:format>
                                        <dc:type>text</dc:type>
                                        <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>
                                        <dc:rights>This document is licensed under a Creative Commons …</dc:rights>
                                        <dc:language>(SCHEME=ISO639) en</dc:language>
                                        <dc:source>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.</dc:source>
                                        <dc:source>repository: CO</dc:source>
                                        <dc:source>coNumber: 60</dc:source>
                                        <dc:source>coVol: 2</dc:source>
                                        <dc:source>page: 291</dc:source>
                                        <dc:source>coRegistration: 11566</dc:source>
                                        <dc:source>received: received 13 November</dc:source>
                                        <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>
                                        <dc:subject>Merivale, Herman</dc:subject>
                                        <dc:subject>Elliot, T. Frederick</dc:subject>
                                        <dc:subject>Moody, Colonel Richard Clement</dc:subject>
                                        <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>
                                        <dc:subject>Jadis, Vane</dc:subject>
                                        <dc:subject>Carnarvon, Earl</dc:subject>
                                        <dc:subject>British Columbia</dc:subject>
                                        <dc:description>British Columbia correspondence: Public Offices
                                           document (normally correspondence between government
                                           departments)</dc:description>
                                       </oai_dc:dc>
                                      </xenoData>
                                      Example

                                      In this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.

                                      <xenoData>
                                       <mods:mods>
                                        <mods:titleInfo>
                                         <mods:title>Academic adaptation and cross-cultural
                                             learning experiences of Chinese students at American
                                             universities</mods:title>
                                         <mods:subTitle>a narrative inquiry</mods:subTitle>
                                        </mods:titleInfo>
                                        <mods:name type="personal"
                                         authority="local">

                                         <mods:namePart/>
                                         <mods:role>
                                          <mods:roleTerm authority="marcrelator"
                                           type="text">
                                      Author</mods:roleTerm>
                                         </mods:role>
                                         <mods:affiliation>Northeastern University</mods:affiliation>
                                         <mods:namePart type="given">Hong</mods:namePart>
                                         <mods:namePart type="family">Zhang</mods:namePart>
                                        </mods:name>
                                        <mods:name type="personal"
                                         authority="local">

                                         <mods:namePart/>
                                         <mods:role>
                                          <mods:roleTerm authority="local"
                                           type="text">
                                      Advisor</mods:roleTerm>
                                         </mods:role>
                                         <mods:namePart type="given">Liliana</mods:namePart>
                                         <mods:namePart type="family">Meneses</mods:namePart>
                                        </mods:name>
                                        
                                      <!-- ... -->
                                        <mods:typeOfResource>text</mods:typeOfResource>
                                        <mods:genre>doctoral theses</mods:genre>
                                        <mods:originInfo>
                                         <mods:place>
                                          <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>
                                         </mods:place>
                                         <mods:publisher>Northeastern University</mods:publisher>
                                         <mods:copyrightDate encoding="w3cdtf"
                                          keyDate="yes">
                                      2013</mods:copyrightDate>
                                        </mods:originInfo>
                                        <mods:language>
                                         <mods:languageTerm authority="iso639-2b"
                                          type="code">
                                      eng</mods:languageTerm>
                                        </mods:language>
                                        <mods:physicalDescription>
                                         <mods:form authority="marcform">electronic</mods:form>
                                         <mods:digitalOrigin>born digital</mods:digitalOrigin>
                                        </mods:physicalDescription>
                                      <!-- ... -->
                                       </mods:mods>
                                      </xenoData>
                                      Example

                                      This example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These 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.

                                      <xenoData xml:space="preserve"> +

                                      <xenoData>

                                      <xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
                                      Moduleheader
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype)
                                      Member of
                                      Contained by
                                      header: teiHeader
                                      May containANY
                                      Example

                                      This example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second xenoData block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the xenoData block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [ID SG-id in TEI Guidelines]). Do note, however, that if the contents of the xenoData block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.

                                      <xenoData>
                                       <rdf:RDF>
                                        <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">
                                         <dc:title>The description of a new world, called the blazing-world</dc:title>
                                         <dc:creator>The Duchess of Newcastle</dc:creator>
                                         <dc:date>1667</dc:date>
                                         <dc:identifier>British Library, 8407.h.10</dc:identifier>
                                         <dc:subject>utopian fiction</dc:subject>
                                        </rdf:Description>
                                       </rdf:RDF>
                                      </xenoData>
                                      <xenoData>
                                       <rdf:RDF>
                                        <rdf:Description rdf:about="">
                                         <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>
                                         <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>
                                         <dc:publisher>Women Writers Project</dc:publisher>
                                         <dc:date>2002-02-12</dc:date>
                                         <dc:subject>utopian fiction</dc:subject>
                                        </rdf:Description>
                                       </rdf:RDF>
                                      </xenoData>
                                      Example

                                      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/.

                                      <xenoData>
                                       <rdf:RDF>
                                        <cc:Work rdf:about="">
                                         <dc:title>Applied Software Project Management - review</dc:title>
                                         <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
                                         <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>
                                        </cc:Work>
                                        <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">
                                         <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
                                         <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
                                         <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
                                         <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
                                         <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
                                         <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>
                                        </cc:License>
                                       </rdf:RDF>
                                      </xenoData>
                                      Example

                                      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/.

                                      <xenoData>
                                       <oai_dc:dc>
                                        <dc:title>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)</dc:title>
                                        <dc:date>1858-11-12</dc:date>
                                        <dc:creator>Trevelyan</dc:creator>
                                        <dc:publisher>University of Victoria Humanities Computing and Media
                                           Centre, and UVic Libraries</dc:publisher>
                                        <dc:type>InteractiveResource</dc:type>
                                        <dc:format>application/xhtml+xml</dc:format>
                                        <dc:type>text</dc:type>
                                        <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>
                                        <dc:rights>This document is licensed under a Creative Commons …</dc:rights>
                                        <dc:language>(SCHEME=ISO639) en</dc:language>
                                        <dc:source>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.</dc:source>
                                        <dc:source>repository: CO</dc:source>
                                        <dc:source>coNumber: 60</dc:source>
                                        <dc:source>coVol: 2</dc:source>
                                        <dc:source>page: 291</dc:source>
                                        <dc:source>coRegistration: 11566</dc:source>
                                        <dc:source>received: received 13 November</dc:source>
                                        <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>
                                        <dc:subject>Merivale, Herman</dc:subject>
                                        <dc:subject>Elliot, T. Frederick</dc:subject>
                                        <dc:subject>Moody, Colonel Richard Clement</dc:subject>
                                        <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>
                                        <dc:subject>Jadis, Vane</dc:subject>
                                        <dc:subject>Carnarvon, Earl</dc:subject>
                                        <dc:subject>British Columbia</dc:subject>
                                        <dc:description>British Columbia correspondence: Public Offices
                                           document (normally correspondence between government
                                           departments)</dc:description>
                                       </oai_dc:dc>
                                      </xenoData>
                                      Example

                                      In this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.

                                      <xenoData>
                                       <mods:mods>
                                        <mods:titleInfo>
                                         <mods:title>Academic adaptation and cross-cultural
                                             learning experiences of Chinese students at American
                                             universities</mods:title>
                                         <mods:subTitle>a narrative inquiry</mods:subTitle>
                                        </mods:titleInfo>
                                        <mods:name type="personal"
                                         authority="local">

                                         <mods:namePart/>
                                         <mods:role>
                                          <mods:roleTerm authority="marcrelator"
                                           type="text">
                                      Author</mods:roleTerm>
                                         </mods:role>
                                         <mods:affiliation>Northeastern University</mods:affiliation>
                                         <mods:namePart type="given">Hong</mods:namePart>
                                         <mods:namePart type="family">Zhang</mods:namePart>
                                        </mods:name>
                                        <mods:name type="personal"
                                         authority="local">

                                         <mods:namePart/>
                                         <mods:role>
                                          <mods:roleTerm authority="local"
                                           type="text">
                                      Advisor</mods:roleTerm>
                                         </mods:role>
                                         <mods:namePart type="given">Liliana</mods:namePart>
                                         <mods:namePart type="family">Meneses</mods:namePart>
                                        </mods:name>
                                        
                                      <!-- ... -->
                                        <mods:typeOfResource>text</mods:typeOfResource>
                                        <mods:genre>doctoral theses</mods:genre>
                                        <mods:originInfo>
                                         <mods:place>
                                          <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>
                                         </mods:place>
                                         <mods:publisher>Northeastern University</mods:publisher>
                                         <mods:copyrightDate encoding="w3cdtf"
                                          keyDate="yes">
                                      2013</mods:copyrightDate>
                                        </mods:originInfo>
                                        <mods:language>
                                         <mods:languageTerm authority="iso639-2b"
                                          type="code">
                                      eng</mods:languageTerm>
                                        </mods:language>
                                        <mods:physicalDescription>
                                         <mods:form authority="marcform">electronic</mods:form>
                                         <mods:digitalOrigin>born digital</mods:digitalOrigin>
                                        </mods:physicalDescription>
                                      <!-- ... -->
                                       </mods:mods>
                                      </xenoData>
                                      Example

                                      This example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These 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.

                                      <xenoData xml:space="preserve"> <![CDATA[ {     "features": [ @@ -101,4 +101,4 @@ tei_att.declarable.attributes, tei_att.typed.attributes, ( text | anyElement-xenoData ) -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/ref-zone.html b/gl/dev/ref-zone.html index dd2d1d90a..b7821bbb8 100644 --- a/gl/dev/ref-zone.html +++ b/gl/dev/ref-zone.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      <zone>

                                      <zone> defines any two-dimensional area within a surface element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.typed (@type, @subtype) att.written (@hand)
                                      rotateindicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent surface element as implied by the dimensions given in the msDesc element or by the coordinates of the surface itself. The orientation is expressed in arc degrees.
                                      Status Optional
                                      Datatype teidata.count
                                      Default 0
                                      Member of
                                      Contained by
                                      linking: standOff
                                      transcr: line surface zone
                                      May contain
                                      Note

                                      The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.

                                      A graphic element contained by a zone represents the whole of the zone.

                                      A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

                                      A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the path element.

                                      Example
                                      <surface ulx="14.54uly="16.14lrx="0"
                                       lry="0">

                                       <graphic url="stone.jpg"/>
                                       <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 - 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/>
                                      </surface>

                                      This example defines a non-rectangular zone: see the illustration in section [ID PH-surfzone in TEI Guidelines].

                                      Example
                                      <facsimile>
                                       <surface ulx="50uly="20lrx="400"
                                        lry="280">

                                        <zone ulx="0uly="0lrx="500lry="321">
                                         <graphic url="graphic.png"/>
                                        </zone>
                                       </surface>
                                      </facsimile>

                                      This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.

                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.global"/>
                                        <elementRef key="surface"/>
                                        <classRef key="model.linePart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                      +    

                                      <zone>

                                      <zone> defines any two-dimensional area within a surface element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
                                      Moduletranscr
                                      Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.typed (@type, @subtype) att.written (@hand)
                                      rotateindicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent surface element as implied by the dimensions given in the msDesc element or by the coordinates of the surface itself. The orientation is expressed in arc degrees.
                                      Status Optional
                                      Datatype teidata.count
                                      Default 0
                                      Member of
                                      Contained by
                                      linking: standOff
                                      transcr: line surface zone
                                      May contain
                                      Note

                                      The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.

                                      A graphic element contained by a zone represents the whole of the zone.

                                      A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

                                      A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the path element.

                                      Example
                                      <surface ulx="14.54uly="16.14lrx="0"
                                       lry="0">

                                       <graphic url="stone.jpg"/>
                                       <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 + 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/>
                                      </surface>

                                      This example defines a non-rectangular zone: see the illustration in section [ID PH-surfzone in TEI Guidelines].

                                      Example
                                      <facsimile>
                                       <surface ulx="50uly="20lrx="400"
                                        lry="280">

                                        <zone ulx="0uly="0lrx="500lry="321">
                                         <graphic url="graphic.png"/>
                                        </zone>
                                       </surface>
                                      </facsimile>

                                      This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.

                                      Content model
                                      <content>
                                       <alternate minOccurs="0"
                                        maxOccurs="unbounded">

                                        <textNode/>
                                        <classRef key="model.gLike"/>
                                        <classRef key="model.graphicLike"/>
                                        <classRef key="model.global"/>
                                        <elementRef key="surface"/>
                                        <classRef key="model.linePart"/>
                                       </alternate>
                                      </content>
                                      Schema Declaration
                                       element zone
                                       {
                                          tei_att.global.attributes,
                                      @@ -38,4 +38,4 @@
                                           | tei_surface
                                           | tei_model.linePart
                                          )*
                                      -}

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +}

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-app-external-pt-br.html b/gl/dev/supp-app-external-pt-br.html index a8a6266af..3a0fbae55 100644 --- a/gl/dev/supp-app-external-pt-br.html +++ b/gl/dev/supp-app-external-pt-br.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Apparatus criticus externo

                                      2023-04-27

                                      Uma divisão externa de edição onde todos os elementos e notas do apparatus criticus recebem codificação específica.

                                      • TEI definition: listApp ; EpiDoc-specific +

                                        Apparatus criticus externo

                                        2024-03-05

                                        Uma divisão externa de edição onde todos os elementos e notas do apparatus criticus recebem codificação específica.

                                        • TEI definition: listApp ; EpiDoc-specific customization: listApp
                                        • TEI definition: app ; EpiDoc-specific customization: app
                                        • TEI definition: lem ; EpiDoc-specific customization: lem
                                        • TEI definition: rdg ; EpiDoc-specific customization: rdg
                                        • TEI definition: note ; EpiDoc-specific - customization: note

                                        A entrada mais simples em um apparatus criticus epigráfico ou papirológico é um comentário geral sobre o texto como um todo, sem uma referência específica a uma linha, sem característica textual descrita. (Como todos os elementos de apparatus externo descritos nesta página, este exemplo deveria aparecer no <div type="apparatus"> e talvez ser agrupado em um listApp.)

                                        <div type="apparatus">
                                         <listApp>
                                          <app>
                                           <note>The face is very weathered, all readings are uncertain.</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        O segundio exemplo é de um simples comentário, mas ligado a uma linha particular ou a um fragmento de texto (neste caso, utilizando o atributo loc, que contém uma citação legível por humanos, ou "canônica" da linha referente):

                                        <app loc="a 7">
                                         <note>The erasure in this line is ineffective but indubitably deliberate.</note>
                                        </app>

                                        Restaurações alternativas, registrando, talvez, a opinião de editores anteriores, ou atribuindo leituras atuais a estes, também podem ser explicitamente marcadas na divisão de apparatus externo:

                                        <app loc="i 3">
                                         <lem>καθο<supplied reason="lost">σίωσις</supplied>
                                         </lem>
                                         <rdg source="#tdb1971">καθ<supplied reason="lost">όλου</supplied>
                                         </rdg>
                                        </app>

                                        Um elemento app no apparatus externo também aponta diretamente a um elemento marcado dentro da transcrição do texto na divisão de transcrição, de modo a comentar sobre ele, ou simplesmente mostrar o elemento marcado sem duplicar a marcação. (Semelhante à prática de apparatus em linha discutida em outra página.)

                                        <choice xml:id="choice3">
                                         <corr>σύμπαντα</corr>
                                         <sic>σινπαταν</sic>
                                        </choice>
                                        <!-- ... -->
                                        <app loc="12from="#choice3">
                                         <note>so Mommsen, without comment.</note>
                                        </app>

                                        Leituras variantes também podem surgir, não de uma discordância entre editores, mas de uma genuína ambiguidade na leitura. Uma letra pouco clara com diversas interpretações possíveis pode aparecer no apparatus (ou no próprio texo) como:

                                        <choice xml:id="choice4">
                                         <unclear>τ</unclear>
                                         <unclear>γ</unclear>
                                         <unclear>ε</unclear>
                                         <unclear>ζ</unclear>
                                         <unclear>ξ</unclear>
                                         <unclear>π</unclear>
                                         <unclear>σ</unclear>
                                        </choice>
                                        <!-- ... -->
                                        <app loc="4from="#choice4">
                                         <note>What survives of the last letter before the break is consonant with Τ, Γ, Ε, Ζ, Ξ,
                                           Π, Σ</note>
                                        </app>

                                        O Apparatus externo também pode fornecer traduções quando e onde for necessário.

                                        Notas que fornecem traduções também podem aparecer em um apparatus dedicado

                                        <div type="translationxml:id="CSAI_415">
                                         <p>
                                          <lb n="1"/>Ṣbḥhmw son of ʿms²fq, of the family Rs²wn, <lb n="2"/>the one from Nashq,
                                           dedicated to ʾlmqh master of <lb n="3"/>Myfʿm the inscription and its support (?),
                                           all <lb n="4"/>his sons and all his properties in Nashqum and in its <lb n="5"/>territory, when he fought with Sabaʾ and Rkbn <lb n="6"/>on an expedition (?) and
                                           overcame the army of Maʿīn in the lower <lb n="7"/>part of ʾtmy; and when he fought
                                           with his tribe <lb n="8"/>Rkbn with the army of Sabaʾ into the land of <lb n="9"/>Ḥaḍramawt and they destroyed three [... ...] ..... </p>
                                        </div>
                                        <div type="apparatussubtype="translation"
                                         corresp="#CSAI_415">

                                         <listApp>
                                          <app loc="3">
                                           <note>hwṯb-hw: alternative translation "and set it".</note>
                                          </app>
                                          <app loc="5, 8">
                                           <note>rkbn: "soldats montés" (Robin).</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        Notas que discutem o significado de um item léxico ou uma frase podem receber a seguinte codificação

                                        <div type="translationxml:id="CSAI.415">
                                         <p> ... <lb n="13"/>and when he traded and led a caravan to Dedan and Gaza <lb n="14"/>and the towns of Judah; and when he was safe <lb n="15"/>and sound, he who went
                                           from Gaza to Kition, during the war <lb n="16"/>between Chaldea and Ionia; and when
                                           Ydʿʾl Byn <lb n="17"/>son of Yṯʿʾmr king of Sabaʾ appointed him and sent <lb n="18"/>him as a messenger to the land of Ḏkrm and <lb n="19"/>Lḥyn and ʾbʾs¹ and Ḥnk in
                                           those fourteen <lb n="20"/>expeditions (?) and he accomplished all with which <lb n="21"/>Ydʿʾl had charged him as a messenger and for which he had appointed him.
                                           ... </p>
                                        </div>
                                        <div type="apparatussubtype="translation"
                                         corresp="#CSAI.415">

                                         <listApp>
                                          <app loc="19-20">
                                           <note>ḥnk ʾlhn ʾrbʿ ʿs²r-hw ʾrglm: Bron translates "et il consacra au dieu
                                               quatorze fantassins", suggesting a parallel with the Heb. ḤNK "to
                                               consecrate". However, the verb in Heb. is used for the consecration of a
                                               temple to the god. Robin interprets the word a name of place and ʾlhn as a
                                               previously unattested form of the pronoun ʾln.</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        O apparatus pode ser utilizado como no exemplo a seguir para relatar uma tradução parcial dada pelos editores

                                        <div type="translationxml:id="CSAI_1268">
                                         <p>
                                          <lb n="1"/>qnt wkrm ḏ-Ḥrnm ḏ-yts¹yn W— <lb n="2"/>hbṯwn ḏ-Nḍḥm l-ʾlkrb ḏ-Qs²bn— <lb n="3"/>bn wkr b-ʿm-hw l-ḏ-Grfm w-k— <lb n="4"/>wn ḏn ʾs¹ynn l-wrḫ ḏ-Ks²bm <lb n="5"/>ḏ-ḫrf ʾbkrb bn Ḥyw bn Ḥ— <lb n="6"/>zfrm Whbṯwn w Mfḍg </p>
                                        </div>
                                        <div type="apparatussubtype="translation"
                                         corresp="#CSAI_1268">

                                         <listApp>
                                          <app loc="1-3">
                                           <note>Ein qnt(=Maßeinheit) Sorghum (nach dem Maß) des (Tempels) Ḥrnm, welches
                                               Whbṯwn aus (der Sippe) Nḍḥm dem ʾlkrb aus (der Sippe) Qs²bn garantiert, von
                                               dem Sorghum, welches bei ihm (=zu seinen Lasten) ist zugunsten der (Sippe)
                                               ḏ-Grfm" (Stein).</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        Observe que, quando traduções completamente diferentes estão disponíveis, elas devem ser inseridas utilizando <div type="apparatus">.

                                        Responsabilidade por esta seção

                                        1. Gabriel Bodard, autor
                                        2. Daniele Marotta, autor
                                        3. Assunção Medeiros, traduzido para o Português por

                                        EpiDoc version: post-9.5

                                        Date: 2023-04-27

                                        \ No newline at end of file + customization: note

                                      A entrada mais simples em um apparatus criticus epigráfico ou papirológico é um comentário geral sobre o texto como um todo, sem uma referência específica a uma linha, sem característica textual descrita. (Como todos os elementos de apparatus externo descritos nesta página, este exemplo deveria aparecer no <div type="apparatus"> e talvez ser agrupado em um listApp.)

                                      <div type="apparatus">
                                       <listApp>
                                        <app>
                                         <note>The face is very weathered, all readings are uncertain.</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      O segundio exemplo é de um simples comentário, mas ligado a uma linha particular ou a um fragmento de texto (neste caso, utilizando o atributo loc, que contém uma citação legível por humanos, ou "canônica" da linha referente):

                                      <app loc="a 7">
                                       <note>The erasure in this line is ineffective but indubitably deliberate.</note>
                                      </app>

                                      Restaurações alternativas, registrando, talvez, a opinião de editores anteriores, ou atribuindo leituras atuais a estes, também podem ser explicitamente marcadas na divisão de apparatus externo:

                                      <app loc="i 3">
                                       <lem>καθο<supplied reason="lost">σίωσις</supplied>
                                       </lem>
                                       <rdg source="#tdb1971">καθ<supplied reason="lost">όλου</supplied>
                                       </rdg>
                                      </app>

                                      Um elemento app no apparatus externo também aponta diretamente a um elemento marcado dentro da transcrição do texto na divisão de transcrição, de modo a comentar sobre ele, ou simplesmente mostrar o elemento marcado sem duplicar a marcação. (Semelhante à prática de apparatus em linha discutida em outra página.)

                                      <choice xml:id="choice3">
                                       <corr>σύμπαντα</corr>
                                       <sic>σινπαταν</sic>
                                      </choice>
                                      <!-- ... -->
                                      <app loc="12from="#choice3">
                                       <note>so Mommsen, without comment.</note>
                                      </app>

                                      Leituras variantes também podem surgir, não de uma discordância entre editores, mas de uma genuína ambiguidade na leitura. Uma letra pouco clara com diversas interpretações possíveis pode aparecer no apparatus (ou no próprio texo) como:

                                      <choice xml:id="choice4">
                                       <unclear>τ</unclear>
                                       <unclear>γ</unclear>
                                       <unclear>ε</unclear>
                                       <unclear>ζ</unclear>
                                       <unclear>ξ</unclear>
                                       <unclear>π</unclear>
                                       <unclear>σ</unclear>
                                      </choice>
                                      <!-- ... -->
                                      <app loc="4from="#choice4">
                                       <note>What survives of the last letter before the break is consonant with Τ, Γ, Ε, Ζ, Ξ,
                                         Π, Σ</note>
                                      </app>

                                      O Apparatus externo também pode fornecer traduções quando e onde for necessário.

                                      Notas que fornecem traduções também podem aparecer em um apparatus dedicado

                                      <div type="translationxml:id="CSAI_415">
                                       <p>
                                        <lb n="1"/>Ṣbḥhmw son of ʿms²fq, of the family Rs²wn, <lb n="2"/>the one from Nashq,
                                         dedicated to ʾlmqh master of <lb n="3"/>Myfʿm the inscription and its support (?),
                                         all <lb n="4"/>his sons and all his properties in Nashqum and in its <lb n="5"/>territory, when he fought with Sabaʾ and Rkbn <lb n="6"/>on an expedition (?) and
                                         overcame the army of Maʿīn in the lower <lb n="7"/>part of ʾtmy; and when he fought
                                         with his tribe <lb n="8"/>Rkbn with the army of Sabaʾ into the land of <lb n="9"/>Ḥaḍramawt and they destroyed three [... ...] ..... </p>
                                      </div>
                                      <div type="apparatussubtype="translation"
                                       corresp="#CSAI_415">

                                       <listApp>
                                        <app loc="3">
                                         <note>hwṯb-hw: alternative translation "and set it".</note>
                                        </app>
                                        <app loc="5, 8">
                                         <note>rkbn: "soldats montés" (Robin).</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      Notas que discutem o significado de um item léxico ou uma frase podem receber a seguinte codificação

                                      <div type="translationxml:id="CSAI.415">
                                       <p> ... <lb n="13"/>and when he traded and led a caravan to Dedan and Gaza <lb n="14"/>and the towns of Judah; and when he was safe <lb n="15"/>and sound, he who went
                                         from Gaza to Kition, during the war <lb n="16"/>between Chaldea and Ionia; and when
                                         Ydʿʾl Byn <lb n="17"/>son of Yṯʿʾmr king of Sabaʾ appointed him and sent <lb n="18"/>him as a messenger to the land of Ḏkrm and <lb n="19"/>Lḥyn and ʾbʾs¹ and Ḥnk in
                                         those fourteen <lb n="20"/>expeditions (?) and he accomplished all with which <lb n="21"/>Ydʿʾl had charged him as a messenger and for which he had appointed him.
                                         ... </p>
                                      </div>
                                      <div type="apparatussubtype="translation"
                                       corresp="#CSAI.415">

                                       <listApp>
                                        <app loc="19-20">
                                         <note>ḥnk ʾlhn ʾrbʿ ʿs²r-hw ʾrglm: Bron translates "et il consacra au dieu
                                             quatorze fantassins", suggesting a parallel with the Heb. ḤNK "to
                                             consecrate". However, the verb in Heb. is used for the consecration of a
                                             temple to the god. Robin interprets the word a name of place and ʾlhn as a
                                             previously unattested form of the pronoun ʾln.</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      O apparatus pode ser utilizado como no exemplo a seguir para relatar uma tradução parcial dada pelos editores

                                      <div type="translationxml:id="CSAI_1268">
                                       <p>
                                        <lb n="1"/>qnt wkrm ḏ-Ḥrnm ḏ-yts¹yn W— <lb n="2"/>hbṯwn ḏ-Nḍḥm l-ʾlkrb ḏ-Qs²bn— <lb n="3"/>bn wkr b-ʿm-hw l-ḏ-Grfm w-k— <lb n="4"/>wn ḏn ʾs¹ynn l-wrḫ ḏ-Ks²bm <lb n="5"/>ḏ-ḫrf ʾbkrb bn Ḥyw bn Ḥ— <lb n="6"/>zfrm Whbṯwn w Mfḍg </p>
                                      </div>
                                      <div type="apparatussubtype="translation"
                                       corresp="#CSAI_1268">

                                       <listApp>
                                        <app loc="1-3">
                                         <note>Ein qnt(=Maßeinheit) Sorghum (nach dem Maß) des (Tempels) Ḥrnm, welches
                                             Whbṯwn aus (der Sippe) Nḍḥm dem ʾlkrb aus (der Sippe) Qs²bn garantiert, von
                                             dem Sorghum, welches bei ihm (=zu seinen Lasten) ist zugunsten der (Sippe)
                                             ḏ-Grfm" (Stein).</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      Observe que, quando traduções completamente diferentes estão disponíveis, elas devem ser inseridas utilizando <div type="apparatus">.

                                      Responsabilidade por esta seção

                                      1. Gabriel Bodard, autor
                                      2. Daniele Marotta, autor
                                      3. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-app-external.html b/gl/dev/supp-app-external.html index 14108c551..d005a53f5 100644 --- a/gl/dev/supp-app-external.html +++ b/gl/dev/supp-app-external.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      External apparatus criticus

                                      2023-04-27

                                      An external division of the edition in which all apparatus criticus features and notes are explicitly tagged.

                                      • TEI definition: listApp ; EpiDoc-specific +

                                        External apparatus criticus

                                        2024-03-05

                                        An external division of the edition in which all apparatus criticus features and notes are explicitly tagged.

                                        • TEI definition: listApp ; EpiDoc-specific customization: listApp
                                        • TEI definition: app ; EpiDoc-specific customization: app
                                        • TEI definition: lem ; EpiDoc-specific customization: lem
                                        • TEI definition: rdg ; EpiDoc-specific customization: rdg
                                        • TEI definition: note ; EpiDoc-specific - customization: note

                                        The simplest entry in an epigraphic or papyrological apparatus criticus is a general comment on the text as a whole, with no specific line reference or textual feature described. (Like all external apparatus features described in this page, this example should appear in the <div type="apparatus">, and perhaps be grouped together in a listApp.)

                                        <div type="apparatus">
                                         <listApp>
                                          <app>
                                           <note>The face is very weathered, all readings are uncertain.</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        The second example is of a simple comment, but tied to a particular line or text fragment (using in this case the attribute loc, which contains a human-readable or "canonical" citation for the line referenced):

                                        <app loc="a 7">
                                         <note>The erasure in this line is ineffective but indubitably deliberate.</note>
                                        </app>

                                        Alternative restorations, perhaps recording the opinion of previous editors or attributing current readings to them, may also be tagged explicitly in the external apparatus division:

                                        <app loc="i 3">
                                         <lem>καθο<supplied reason="lost">σίωσις</supplied>
                                         </lem>
                                         <rdg source="#tdb1971">καθ<supplied reason="lost">όλου</supplied>
                                         </rdg>
                                        </app>

                                        An app element in the external apparatus may also point directly to a feature tagged within the text transcription division, in order to comment upon it, or simply to display the marked-up feature without duplicating the markup. (Similar to the practice of inline apparatus discussed elsewhere.)

                                        <choice xml:id="choice3">
                                         <corr>σύμπαντα</corr>
                                         <sic>σινπαταν</sic>
                                        </choice>
                                        <!-- ... -->
                                        <app loc="12from="#choice3">
                                         <note>so Mommsen, without comment.</note>
                                        </app>

                                        Variant readings may also arise not from a disagreement among editors, but from genuine ambiguity in reading. An unclear letter with several possible interpretations might appear in the apparatus (or in the text itself) as:

                                        <choice xml:id="choice4">
                                         <unclear>τ</unclear>
                                         <unclear>γ</unclear>
                                         <unclear>ε</unclear>
                                         <unclear>ζ</unclear>
                                         <unclear>ξ</unclear>
                                         <unclear>π</unclear>
                                         <unclear>σ</unclear>
                                        </choice>
                                        <!-- ... -->
                                        <app loc="4from="#choice4">
                                         <note>What survives of the last letter before the break is consonant with Τ, Γ, Ε, Ζ, Ξ, Π, Σ</note>
                                        </app>

                                        External Apparatus can also be provided for translations when and where necessary.

                                        Notes that provide alternative translations, can also be provided in a dedicated apparatus

                                        <div type="translationxml:id="CSAI_415">
                                         <p>
                                          <lb n="1"/>Ṣbḥhmw son of ʿms²fq, of the family Rs²wn,
                                         <lb n="2"/>the one from Nashq, dedicated to ʾlmqh master of
                                         <lb n="3"/>Myfʿm the inscription and its support (?), all
                                         <lb n="4"/>his sons and all his properties in Nashqum and in its
                                         <lb n="5"/>territory, when he fought with Sabaʾ and Rkbn
                                         <lb n="6"/>on an expedition (?) and overcame the army of Maʿīn in the lower
                                         <lb n="7"/>part of ʾtmy; and when he fought with his tribe
                                         <lb n="8"/>Rkbn with the army of Sabaʾ into the land of
                                         <lb n="9"/>Ḥaḍramawt and they destroyed three [... ...]
                                           .....
                                         </p>
                                        </div>
                                        <div type="apparatussubtype="translation"
                                         corresp="#CSAI_415">

                                         <listApp>
                                          <app loc="3">
                                           <note>hwṯb-hw: alternative translation "and set it".</note>
                                          </app>
                                          <app loc="5, 8">
                                           <note>rkbn: "soldats montés" (Robin).</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        Notes that discuss the meaning of a lexical item or a sentence might be encoded as follows

                                        <div type="translationxml:id="CSAI-415">
                                         <p> ...
                                         <lb n="13"/>and when he traded and led a caravan to Dedan and Gaza
                                         <lb n="14"/>and the towns of Judah; and when he was safe
                                         <lb n="15"/>and sound, he who went from Gaza to Kition, during the war
                                         <lb n="16"/>between Chaldea and Ionia; and when Ydʿʾl Byn
                                         <lb n="17"/>son of Yṯʿʾmr king of Sabaʾ appointed him and sent
                                         <lb n="18"/>him as a messenger to the land of Ḏkrm and
                                         <lb n="19"/>Lḥyn and ʾbʾs¹ and Ḥnk in those fourteen
                                         <lb n="20"/>expeditions (?) and he accomplished all with which
                                         <lb n="21"/>Ydʿʾl had charged him as a messenger and for which he had appointed him.
                                           ...
                                         </p>
                                        </div>
                                        <div type="apparatussubtype="translation"
                                         corresp="#CSAI-415">

                                         <listApp>
                                          <app loc="19-20">
                                           <note>ḥnk ʾlhn ʾrbʿ ʿs²r-hw ʾrglm: Bron translates "et il consacra au dieu quatorze fantassins", suggesting a parallel with the Heb. ḤNK "to consecrate". However, the verb in Heb. is used for the consecration of a temple to the god. Robin interprets the word a name of place and ʾlhn as a previously unattested form of the pronoun ʾln.</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        Apparatus might be used as in the following example also to report partial translations provided by the editors

                                        <div type="translationxml:id="CSAI_1268">
                                         <p>
                                          <lb n="1"/>qnt wkrm ḏ-Ḥrnm ḏ-yts¹yn W—
                                         <lb n="2"/>hbṯwn ḏ-Nḍḥm l-ʾlkrb ḏ-Qs²bn—
                                         <lb n="3"/>bn wkr b-ʿm-hw l-ḏ-Grfm w-k—
                                         <lb n="4"/>wn ḏn ʾs¹ynn l-wrḫ ḏ-Ks²bm
                                         <lb n="5"/>ḏ-ḫrf ʾbkrb bn Ḥyw bn Ḥ—
                                         <lb n="6"/>zfrm Whbṯwn w Mfḍg
                                         </p>
                                        </div>
                                        <div type="apparatussubtype="translation"
                                         corresp="#CSAI_1268">

                                         <listApp>
                                          <app loc="1-3">
                                           <note>Ein qnt(=Maßeinheit) Sorghum (nach dem Maß) des (Tempels) Ḥrnm, welches Whbṯwn aus (der Sippe) Nḍḥm dem ʾlkrb aus (der Sippe) Qs²bn garantiert, von dem Sorghum, welches bei ihm (=zu seinen Lasten) ist zugunsten der (Sippe) ḏ-Grfm" (Stein).</note>
                                          </app>
                                         </listApp>
                                        </div>

                                        Note that when entirely different translations are available, they should be inserted using a <div type="apparatus">.

                                        Responsibility for this section

                                        1. Gabriel Bodard, author
                                        2. Daniele Marotta, author

                                        EpiDoc version: post-9.5

                                        Date: 2023-04-27

                                        \ No newline at end of file + customization: note

                                      The simplest entry in an epigraphic or papyrological apparatus criticus is a general comment on the text as a whole, with no specific line reference or textual feature described. (Like all external apparatus features described in this page, this example should appear in the <div type="apparatus">, and perhaps be grouped together in a listApp.)

                                      <div type="apparatus">
                                       <listApp>
                                        <app>
                                         <note>The face is very weathered, all readings are uncertain.</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      The second example is of a simple comment, but tied to a particular line or text fragment (using in this case the attribute loc, which contains a human-readable or "canonical" citation for the line referenced):

                                      <app loc="a 7">
                                       <note>The erasure in this line is ineffective but indubitably deliberate.</note>
                                      </app>

                                      Alternative restorations, perhaps recording the opinion of previous editors or attributing current readings to them, may also be tagged explicitly in the external apparatus division:

                                      <app loc="i 3">
                                       <lem>καθο<supplied reason="lost">σίωσις</supplied>
                                       </lem>
                                       <rdg source="#tdb1971">καθ<supplied reason="lost">όλου</supplied>
                                       </rdg>
                                      </app>

                                      An app element in the external apparatus may also point directly to a feature tagged within the text transcription division, in order to comment upon it, or simply to display the marked-up feature without duplicating the markup. (Similar to the practice of inline apparatus discussed elsewhere.)

                                      <choice xml:id="choice3">
                                       <corr>σύμπαντα</corr>
                                       <sic>σινπαταν</sic>
                                      </choice>
                                      <!-- ... -->
                                      <app loc="12from="#choice3">
                                       <note>so Mommsen, without comment.</note>
                                      </app>

                                      Variant readings may also arise not from a disagreement among editors, but from genuine ambiguity in reading. An unclear letter with several possible interpretations might appear in the apparatus (or in the text itself) as:

                                      <choice xml:id="choice4">
                                       <unclear>τ</unclear>
                                       <unclear>γ</unclear>
                                       <unclear>ε</unclear>
                                       <unclear>ζ</unclear>
                                       <unclear>ξ</unclear>
                                       <unclear>π</unclear>
                                       <unclear>σ</unclear>
                                      </choice>
                                      <!-- ... -->
                                      <app loc="4from="#choice4">
                                       <note>What survives of the last letter before the break is consonant with Τ, Γ, Ε, Ζ, Ξ, Π, Σ</note>
                                      </app>

                                      External Apparatus can also be provided for translations when and where necessary.

                                      Notes that provide alternative translations, can also be provided in a dedicated apparatus

                                      <div type="translationxml:id="CSAI_415">
                                       <p>
                                        <lb n="1"/>Ṣbḥhmw son of ʿms²fq, of the family Rs²wn,
                                       <lb n="2"/>the one from Nashq, dedicated to ʾlmqh master of
                                       <lb n="3"/>Myfʿm the inscription and its support (?), all
                                       <lb n="4"/>his sons and all his properties in Nashqum and in its
                                       <lb n="5"/>territory, when he fought with Sabaʾ and Rkbn
                                       <lb n="6"/>on an expedition (?) and overcame the army of Maʿīn in the lower
                                       <lb n="7"/>part of ʾtmy; and when he fought with his tribe
                                       <lb n="8"/>Rkbn with the army of Sabaʾ into the land of
                                       <lb n="9"/>Ḥaḍramawt and they destroyed three [... ...]
                                         .....
                                       </p>
                                      </div>
                                      <div type="apparatussubtype="translation"
                                       corresp="#CSAI_415">

                                       <listApp>
                                        <app loc="3">
                                         <note>hwṯb-hw: alternative translation "and set it".</note>
                                        </app>
                                        <app loc="5, 8">
                                         <note>rkbn: "soldats montés" (Robin).</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      Notes that discuss the meaning of a lexical item or a sentence might be encoded as follows

                                      <div type="translationxml:id="CSAI-415">
                                       <p> ...
                                       <lb n="13"/>and when he traded and led a caravan to Dedan and Gaza
                                       <lb n="14"/>and the towns of Judah; and when he was safe
                                       <lb n="15"/>and sound, he who went from Gaza to Kition, during the war
                                       <lb n="16"/>between Chaldea and Ionia; and when Ydʿʾl Byn
                                       <lb n="17"/>son of Yṯʿʾmr king of Sabaʾ appointed him and sent
                                       <lb n="18"/>him as a messenger to the land of Ḏkrm and
                                       <lb n="19"/>Lḥyn and ʾbʾs¹ and Ḥnk in those fourteen
                                       <lb n="20"/>expeditions (?) and he accomplished all with which
                                       <lb n="21"/>Ydʿʾl had charged him as a messenger and for which he had appointed him.
                                         ...
                                       </p>
                                      </div>
                                      <div type="apparatussubtype="translation"
                                       corresp="#CSAI-415">

                                       <listApp>
                                        <app loc="19-20">
                                         <note>ḥnk ʾlhn ʾrbʿ ʿs²r-hw ʾrglm: Bron translates "et il consacra au dieu quatorze fantassins", suggesting a parallel with the Heb. ḤNK "to consecrate". However, the verb in Heb. is used for the consecration of a temple to the god. Robin interprets the word a name of place and ʾlhn as a previously unattested form of the pronoun ʾln.</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      Apparatus might be used as in the following example also to report partial translations provided by the editors

                                      <div type="translationxml:id="CSAI_1268">
                                       <p>
                                        <lb n="1"/>qnt wkrm ḏ-Ḥrnm ḏ-yts¹yn W—
                                       <lb n="2"/>hbṯwn ḏ-Nḍḥm l-ʾlkrb ḏ-Qs²bn—
                                       <lb n="3"/>bn wkr b-ʿm-hw l-ḏ-Grfm w-k—
                                       <lb n="4"/>wn ḏn ʾs¹ynn l-wrḫ ḏ-Ks²bm
                                       <lb n="5"/>ḏ-ḫrf ʾbkrb bn Ḥyw bn Ḥ—
                                       <lb n="6"/>zfrm Whbṯwn w Mfḍg
                                       </p>
                                      </div>
                                      <div type="apparatussubtype="translation"
                                       corresp="#CSAI_1268">

                                       <listApp>
                                        <app loc="1-3">
                                         <note>Ein qnt(=Maßeinheit) Sorghum (nach dem Maß) des (Tempels) Ḥrnm, welches Whbṯwn aus (der Sippe) Nḍḥm dem ʾlkrb aus (der Sippe) Qs²bn garantiert, von dem Sorghum, welches bei ihm (=zu seinen Lasten) ist zugunsten der (Sippe) ḏ-Grfm" (Stein).</note>
                                        </app>
                                       </listApp>
                                      </div>

                                      Note that when entirely different translations are available, they should be inserted using a <div type="apparatus">.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Daniele Marotta, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-app-inline-pt-br.html b/gl/dev/supp-app-inline-pt-br.html index 4b1bbb5b8..0d6b160ef 100644 --- a/gl/dev/supp-app-inline-pt-br.html +++ b/gl/dev/supp-app-inline-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Apparatus criticus em linha

                                      2023-04-27

                                      As tags que podem ser utilizadas dentro da divisão de transcrição de texto, a partir das quais um apparatus criticus pode ser gerado em pós-processamento.

                                      <app type="editorial">
                                       <lem source="#BL_3.8"><supplied reason="lost">
                                         <expan>προγ<ex>εγραμμένη</ex>
                                         </expan>
                                        </supplied>
                                       </lem>
                                       <rdg><supplied reason="lost">ς <expan>
                                          <ex>ἐτῶν</ex>
                                         </expan> ιϛ</supplied>
                                       </rdg>
                                      </app>
                                      (DDbDP: bgu.1.154)
                                      Note: generates aparatus: 23. BL 3.8 : ὡ[ς (ἐτῶν) ιϛ] prev. ed.
                                      <app type="alternative">
                                       <lem>
                                        <expan>Λευκ<ex>ο</ex>γ<ex>ίου</ex>
                                        </expan>
                                       </lem>
                                       <rdg>Λευκῶ<add place="above">ν</add>
                                       </rdg>
                                      </app>
                                      (DDbDP: cpr.4.171)
                                      Note: generates apparatus: r.17. or Λευκῶ\ν/

                                      Apenas alguns projetos EpiDoc usam marcação em linha para gerar um apparatus criticus. DDbDP contribuiu com o XSLT para os Exemplos de Folhas de Estilo EpiDoc que dão suporte a isto. Esta página explica as opções que você pode usar nos Exemplos de Folhas de Estilo EpiDoc e o que tem cobertura no momento.

                                      Responsabilidade por esta seção

                                      1. Gabriel Bodard, autor
                                      2. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-app-inline.html b/gl/dev/supp-app-inline.html index 8b3709977..332bd1b3c 100644 --- a/gl/dev/supp-app-inline.html +++ b/gl/dev/supp-app-inline.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Inline apparatus criticus

                                      2023-04-27

                                      The tags that may be used within the transcribed text division itself, and from which an apparatus criticus can be generated in post-processing.

                                      <app type="editorial">
                                       <lem source="#BL_3.8"><supplied reason="lost">
                                         <expan>προγ<ex>εγραμμένη</ex>
                                         </expan>
                                        </supplied>
                                       </lem>
                                       <rdg><supplied reason="lost">ς <expan>
                                          <ex>ἐτῶν</ex>
                                         </expan> ιϛ</supplied>
                                       </rdg>
                                      </app>
                                      (DDbDP: bgu.1.154)
                                      Note: generates apparatus: 23. BL 3.8 : ὡ[ς (ἐτῶν) ιϛ] prev. ed.
                                      <app type="alternative">
                                       <lem>
                                        <expan>Λευκ<ex>ο</ex>γ<ex>ίου</ex>
                                        </expan>
                                       </lem>
                                       <rdg>Λευκῶ<add place="above">ν</add>
                                       </rdg>
                                      </app>
                                      (DDbDP: cpr.4.171)
                                      Note: generates apparatus: r.17. or Λευκῶ\ν/

                                      Only few EpiDoc project use inline tagging to generate apparatus criticus. DDbDP has contributed the XSLT to the EpiDoc Example Stylesheets which supports this. This page explains the options you may use in the EpiDoc Example Stylesheets and what is covered at the moment.

                                      Responsibility for this section

                                      1. Gabriel Bodard, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-app-stylesheets-pt-br.html b/gl/dev/supp-app-stylesheets-pt-br.html index 5899114c5..2f6437e36 100644 --- a/gl/dev/supp-app-stylesheets-pt-br.html +++ b/gl/dev/supp-app-stylesheets-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      O que os Exemplos de Folhas de Estilo EpiDoc podem fazer por seu apparatus

                                      2023-04-27

                                      Aqui discutimos as opções de suporte para a renderização do seu apparatus no Exemplo de XSLT EpiDoc, para que você decida de modo informado a codificação relativa às notas de apparatus e elementos que você pode querer ter registrados em um apparatus no nível de visualização.

                                      Sua primeira opção é ter tudo que você realmente quer em seu apparatus explicitamente codificado no seu <div[@type='apparatus']>, como descrito no método de apparatus externo. O conteúdo deste div é renderizado de modo default pelo Exemplo de XSLT EpiDoc.

                                      Entretanto, se você deseja publicar, também no apparatus, por exemplo, elementos do texto que você tenha codificado com choice ou del, estes só estarão lá se você disser ao seu processador para mostrá-los. O Exemplo de XSLT EpiDoc pode produzir uma seção de apparatus, adicional e separada, além daquela codificada <div[@type='apparatus']>.

                                      featureexampleiospeminexfullexddbdp
                                      Correction Without Specification
                                      <w part="I">τ<corr>ι</corr>μο</w>
                                      l.1 ι corr.
                                      Erroneous Substitution
                                      <w>α<supplied reason="lost"></supplied>θ<supplied reason="lost">έν</supplied>τ<choice>
                                        <corr>ο</corr>
                                        <sic>α</sic>
                                       </choice>υ</w>
                                      3: orig. Α.Θ..ΤΑΥl.3 sic, orig. αl.3 sic, orig. α3. l. ο (corr)
                                      Regularization
                                      <choice>
                                       <reg>τιμὴν</reg>
                                       <orig>τειμην</orig>
                                      </choice>
                                      l.4 τειμην orig., reg. τιμὴνl.4 τειμην orig., reg. τιμὴν4. l. τιμὴν
                                      Ambiguous Characters with Alternatives offered
                                      <choice>
                                       <unclear>Γ</unclear>
                                       <unclear>Ε</unclear>
                                       <unclear>Ζ</unclear>
                                      </choice>
                                      l.5 Γ aut Ε aut Ζ aut Ξ aut Π aut Σ aut Τ
                                      Ancient Corrections (Where Both Old And New Text Can Be Read)
                                      <subst>
                                       <add place="inline">τέσσαρας</add>
                                       <del rend="corrected">τεσσαρες</del>
                                      </subst>
                                      6: corr. ex ΤΕΣΣΑΡΕΣl.6 del τεσσαρες6. corr. ex τεσσαρες
                                      Ancient Corrections (Old Text Lost)
                                      public<add place="overstrike">a</add>e
                                      l.7 a overstrike
                                      Addition By Ancient Hand
                                      <add place="above">αβ</add>
                                      l.8 αβ add above
                                      Raised/Lowered Characters
                                      <expan>πρ<hi rend="superscript">οσ</hi>
                                       <ex>γίνεται</ex>
                                      </expan>
                                      9: οσ s.l.l.9 οσ superscript
                                      Omitted Letters
                                      Valent<supplied reason="omitted">in</supplied>iani
                                      13: orig. VALENTIANIl.13 in omitted
                                      Text cancelled with strokes
                                      <del rend="cross-strokes">
                                       <handShift new="m4"/>
                                       <gap reason="lost"
                                        extent="unknown"
                                        unit="line"/>

                                      </del>
                                      (DDbDP: p.lips.1.98)
                                      l.14 cross-strokes14. Text canceled with cross-strokes
                                      Parallel Segementation Apparatus note / Editorial notes
                                      <app type="editorial">
                                       <lem source="#BL_3.8"><supplied reason="lost">
                                         <expan>προγ<ex>εγραμμένη</ex>
                                         </expan>
                                        </supplied>
                                       </lem>
                                       <rdg><supplied reason="lost">ς <expan>
                                          <ex>ἐτῶν</ex>
                                         </expan>
                                           ιϛ</supplied>
                                       </rdg>
                                      </app>
                                      (DDbDP: bgu.1.154)
                                      l.10 #BL_3.8, ὡ[ς (ἐτῶν) ιϛ]l.10 #BL_3.8, ὡ[ς (ἐτῶν) ιϛ]10. ὡ[ς (ἐτῶν) ιϛ] prev. ed.
                                      Parallel Segementation Apparatus note / Alternative readings
                                      <app type="alternative">
                                       <lem>
                                        <expan>Λευκ<ex>ο</ex>γ<ex>ίου</ex>
                                        </expan>
                                       </lem>
                                       <rdg>Λευκῶ<add place="above">ν</add>
                                       </rdg>
                                      </app>
                                      (DDbDP: cpr.4.171)
                                      l.11 or Λευκῶ`ν´l.11 or Λευκῶ`ν´11. or Λευκῶ`ν´

                                      Algumas destas opções de valores para a variável vão também criar um output em uma seção separada das notas de apparatus em linha.

                                      Portanto, você pode, usando o Exemplo de XSLT EpiDoc, ter duas seções separadas, com suas notações em linha e no <div[@type="apparatus"]>. Você pode, entretanto, desejar misturar as duas formas de exibição, tendo apenas uma seção de apparatus que contenha as duas formas de informação. Isto recebe suporte no Exemplo de XSLT EpiDoc através da $mixed-app-style, que vai produzir, com os mesmos valores opcionais que $internal-app-style, um apparatus que tenha uma nota separada para cada linha, com um elemento app com atributo loc ou um dos elementos selecionados na linha correspondente.

                                      E então, como você codifica seu apparatus? A escolha é sua, mas a escolha feita com mais frequência pelos projetos até hoje é usar o método de apparatus externo.

                                      Responsabilidade por esta seção

                                      1. Pietro Maria Liuzzo, autor
                                      2. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-app-stylesheets.html b/gl/dev/supp-app-stylesheets.html index 2c763994f..09467f661 100644 --- a/gl/dev/supp-app-stylesheets.html +++ b/gl/dev/supp-app-stylesheets.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      What the EpiDoc Example Stylesheet can do for your apparatus

                                      2023-04-27

                                      We discuss here what the EpiDoc Example XSLT support as options to render your apparatus, in order to inform your encoding decisions about apparatus notes and features you may want to be recorded in an apparatus at the visualization level.

                                      Your first option is to have all what you actually want in your apparatus encoded explicitly in your <div[@type='apparatus']>, as described in the external apparatus method. The content of this div is always rendered by default by the EpiDoc Example XSLT.

                                      If, however, you wish to have in the apparatus you want to publish also, for example, features of the text which you may have encoded in the text with choice or del these will not be there unless you tell your processor to show them. EpiDoc Example XSLT can produce a separate, additional apparatus section beside your encoded <div[@type='apparatus']>.

                                      featureexampleiospeminexfullexddbdp
                                      Correction Without Specification
                                      <w part="I">τ<corr>ι</corr>μο</w>
                                      l.1 ι corr.
                                      Erroneous Substitution
                                      <w>α<supplied reason="lost"></supplied>θ<supplied reason="lost">έν</supplied>τ<choice>
                                        <corr>ο</corr>
                                        <sic>α</sic>
                                       </choice>υ</w>
                                      3: orig. Α.Θ..ΤΑΥl.3 sic, orig. αl.3 sic, orig. α3. l. ο (corr)
                                      Regularization
                                      <choice>
                                       <reg>τιμὴν</reg>
                                       <orig>τειμην</orig>
                                      </choice>
                                      l.4 τειμην orig., reg. τιμὴνl.4 τειμην orig., reg. τιμὴν4. l. τιμὴν
                                      Ambiguous Characters with Alternatives offered
                                      <choice>
                                       <unclear>Γ</unclear>
                                       <unclear>Ε</unclear>
                                       <unclear>Ζ</unclear>
                                      </choice>
                                      l.5 Γ aut Ε aut Ζ aut Ξ aut Π aut Σ aut Τ
                                      Ancient Corrections (Where Both Old And New Text Can Be Read)
                                      <subst>
                                       <add place="inline">τέσσαρας</add>
                                       <del rend="corrected">τεσσαρες</del>
                                      </subst>
                                      6: corr. ex ΤΕΣΣΑΡΕΣl.6 del τεσσαρες6. corr. ex τεσσαρες
                                      Ancient Corrections (Old Text Lost)
                                      public<add place="overstrike">a</add>e
                                      l.7 a overstrike
                                      Addition By Ancient Hand
                                      <add place="above">αβ</add>
                                      l.8 αβ add above
                                      Raised/Lowered Characters
                                      <expan>πρ<hi rend="superscript">οσ</hi>
                                       <ex>γίνεται</ex>
                                      </expan>
                                      9: οσ s.l.l.9 οσ superscript
                                      Omitted Letters
                                      Valent<supplied reason="omitted">in</supplied>iani
                                      13: orig. VALENTIANIl.13 in omitted
                                      Text cancelled with strokes
                                      <del rend="cross-strokes">
                                       <handShift new="m4"/>
                                       <gap reason="lost"
                                        extent="unknown"
                                        unit="line"/>

                                      </del>
                                      (DDbDP: p.lips.1.98)
                                      l.14 cross-strokes14. Text canceled with cross-strokes
                                      Parallel Segementation Apparatus note / Editorial notes
                                      <app type="editorial">
                                       <lem source="#BL_3.8"><supplied reason="lost">
                                         <expan>προγ<ex>εγραμμένη</ex>
                                         </expan>
                                        </supplied>
                                       </lem>
                                       <rdg><supplied reason="lost">ς <expan>
                                          <ex>ἐτῶν</ex>
                                         </expan> ιϛ</supplied>
                                       </rdg>
                                      </app>
                                      (DDbDP: bgu.1.154)
                                      l.10 #BL_3.8, ὡ[ς (ἐτῶν) ιϛ]l.10 #BL_3.8, ὡ[ς (ἐτῶν) ιϛ]10. ὡ[ς (ἐτῶν) ιϛ] prev. ed.
                                      Parallel Segementation Apparatus note / Alternative readings
                                      <app type="alternative">
                                       <lem>
                                        <expan>Λευκ<ex>ο</ex>γ<ex>ίου</ex>
                                        </expan>
                                       </lem>
                                       <rdg>Λευκῶ<add place="above">ν</add>
                                       </rdg>
                                      </app>
                                      (DDbDP: cpr.4.171)
                                      l.11 or Λευκῶ`ν´l.11 or Λευκῶ`ν´11. or Λευκῶ`ν´

                                      So you can have using the EpiDoc Example XSLT two separate sections, with your annotations inline and in the <div[@type="apparatus"]>.

                                      So, how to encode your apparatus? It is your choice, but the most frequent choice made by projects so far is to use the external apparatus method.

                                      Responsibility for this section

                                      1. Pietro Maria Liuzzo, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-apparatus-pt-br.html b/gl/dev/supp-apparatus-pt-br.html index 0a8a71ef0..283f71cf5 100644 --- a/gl/dev/supp-apparatus-pt-br.html +++ b/gl/dev/supp-apparatus-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Apparatus criticus

                                      2023-04-27

                                      O aparato crítico é um elemento padrão de edições acadêmicas no qual leituras variantes e outros comentários filológicos são apresentados aos leitores como uma lista comprimida logo após o texto, organizado por número de linha deste.

                                      • TEI definition: div ; EpiDoc-specific - customization: div

                                      A forma e o conteúdo do apparatus varia, de uma disciplina para outra, nas humanidades. No estudo de manuscritos e na filologia literária, o app. crit. é geralmente diferenciado de um comentário linha-a-linha separado, e se dedica de maneira mais estrita à documentação das leituras variantes encontradas nos testemunhos existentes. Na prática epigráfica e papirológica, onde normalmente existe apenas um testemunho da antiguidade para cada texto, o apparatus normalmente trata das leituras divergentes ou erradas publicadas por editores anteriores, restaurações alternativas e emendas, comentários sobre forma e aparência (como, por exemplo, trasnposição de letras) que não podem ser claramente representadas no texto em si. Epígrafos e papirólogos muitas vezes também incluem um comentário (linha-a-linha ou não) com uma discussão mais extensa sobre o texto, onde sua interpretação e significância histórica podem ser tratadas.

                                      EpiDoc recomenda que se escolha entre dois métodos de codificação do tipo de informação que é tradicionalmente colocada no aparato crítico:

                                      O método mais utilizado em projetos EpiDoc é a abordagem externa (veja TEI "location-referenced"), no qual o apparatus é codificado separadamente em um elemento <div type="apparatus">. As entradas individuais do apparatus nesta divisão externa são relacionadas ao texto com o uso de atributos de linkagem padrão TEI (geralmente loc apontando para o número da linha). Este método requer um XSLT relativamente simples para produzir output aceitável, mas atualmente o Exemplo de XSLT EpiDoc não trata deste elemento fora da caixa.

                                      A abordagem em linha (veja TEI "parallel segmentation method") faz uso de tags colocadas diretamente no texto, que podem então ser interpretadas durante o pós-processamento para que apareçam numa forma linha-a-linha. Até hoje, o único projeto EpiDoc que implementou isto foi o Duke Databank of Documentary Papyri; qualquer outro projeto que deseje trabalhar assim vai precisar modificar significativamente o Exemplo de XSLT EpiDoc para conseguir o comportamenteo desejado.

                                      Existem vários elementos que você pode querer que sejam exibidos no seu apparatus ou em uma seção separada de apparatus, que não são codificados explicitamente como notas de apparatus em nenhum dos dois métodos descritos acima. Os Exemplos de Folhas de Estilo EpiDoc dão algum suporte para renderizar estes elementos de diversas formas.

                                      É muito importante decidir qual método você vai querer utlizar e ser consistente nesta escolha; os dois métodos são aceitáveis e independentes do modo como você vai querer ou não mostrar estes elementos nas suas notas de apparatus. O fato de você utilizar app no texto, seguindo a abordagem em linha, não determina automaticamente que você deseja um apparatus que inclua outros elementos, nem o fato de você utilizar a abordagem externa determina que você não deseja que uma outra coisa que tenha sido codificada diretamente no texto apareça impressa em uma seção apparatus. Estas coisas são determinadas durante a renderização, não na codificação, e você pode escolher o que fazer, desde que seja uma escolha consistente.

                                      Apesar da abordagem externa de apparatus ser o método recomendado para a codificação de notas de apparatus, você pode desejar não ter que produzir uma nota em um <div[@type='apparatus']> para cada elemento choice que você codificou e deseja em um apparatus. Para tomar sua decisão de codificação de modo bem informado, aqui você encontra uma lista das possibilidades atualmente oferecidas pelos Exemplos de Folhas de Estilo EpiDoc.

                                      Normas específicas para cada abordagem se encontram nestas seções:

                                      Responsabilidade por esta seção

                                      1. Gabriel Bodard, autor
                                      2. Tom Elliott, autor
                                      3. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Apparatus criticus

                                      2024-03-05

                                      O aparato crítico é um elemento padrão de edições acadêmicas no qual leituras variantes e outros comentários filológicos são apresentados aos leitores como uma lista comprimida logo após o texto, organizado por número de linha deste.

                                      • TEI definition: div ; EpiDoc-specific + customization: div

                                      A forma e o conteúdo do apparatus varia, de uma disciplina para outra, nas humanidades. No estudo de manuscritos e na filologia literária, o app. crit. é geralmente diferenciado de um comentário linha-a-linha separado, e se dedica de maneira mais estrita à documentação das leituras variantes encontradas nos testemunhos existentes. Na prática epigráfica e papirológica, onde normalmente existe apenas um testemunho da antiguidade para cada texto, o apparatus normalmente trata das leituras divergentes ou erradas publicadas por editores anteriores, restaurações alternativas e emendas, comentários sobre forma e aparência (como, por exemplo, trasnposição de letras) que não podem ser claramente representadas no texto em si. Epígrafos e papirólogos muitas vezes também incluem um comentário (linha-a-linha ou não) com uma discussão mais extensa sobre o texto, onde sua interpretação e significância histórica podem ser tratadas.

                                      EpiDoc recomenda que se escolha entre dois métodos de codificação do tipo de informação que é tradicionalmente colocada no aparato crítico:

                                      O método mais utilizado em projetos EpiDoc é a abordagem externa (veja TEI "location-referenced"), no qual o apparatus é codificado separadamente em um elemento <div type="apparatus">. As entradas individuais do apparatus nesta divisão externa são relacionadas ao texto com o uso de atributos de linkagem padrão TEI (geralmente loc apontando para o número da linha). Este método requer um XSLT relativamente simples para produzir output aceitável, mas atualmente o Exemplo de XSLT EpiDoc não trata deste elemento fora da caixa.

                                      A abordagem em linha (veja TEI "parallel segmentation method") faz uso de tags colocadas diretamente no texto, que podem então ser interpretadas durante o pós-processamento para que apareçam numa forma linha-a-linha. Até hoje, o único projeto EpiDoc que implementou isto foi o Duke Databank of Documentary Papyri; qualquer outro projeto que deseje trabalhar assim vai precisar modificar significativamente o Exemplo de XSLT EpiDoc para conseguir o comportamenteo desejado.

                                      Existem vários elementos que você pode querer que sejam exibidos no seu apparatus ou em uma seção separada de apparatus, que não são codificados explicitamente como notas de apparatus em nenhum dos dois métodos descritos acima. Os Exemplos de Folhas de Estilo EpiDoc dão algum suporte para renderizar estes elementos de diversas formas.

                                      É muito importante decidir qual método você vai querer utlizar e ser consistente nesta escolha; os dois métodos são aceitáveis e independentes do modo como você vai querer ou não mostrar estes elementos nas suas notas de apparatus. O fato de você utilizar app no texto, seguindo a abordagem em linha, não determina automaticamente que você deseja um apparatus que inclua outros elementos, nem o fato de você utilizar a abordagem externa determina que você não deseja que uma outra coisa que tenha sido codificada diretamente no texto apareça impressa em uma seção apparatus. Estas coisas são determinadas durante a renderização, não na codificação, e você pode escolher o que fazer, desde que seja uma escolha consistente.

                                      Apesar da abordagem externa de apparatus ser o método recomendado para a codificação de notas de apparatus, você pode desejar não ter que produzir uma nota em um <div[@type='apparatus']> para cada elemento choice que você codificou e deseja em um apparatus. Para tomar sua decisão de codificação de modo bem informado, aqui você encontra uma lista das possibilidades atualmente oferecidas pelos Exemplos de Folhas de Estilo EpiDoc.

                                      Normas específicas para cada abordagem se encontram nestas seções:

                                      Responsabilidade por esta seção

                                      1. Gabriel Bodard, autor
                                      2. Tom Elliott, autor
                                      3. Assunção Medeiros, traduzido para o Português por

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-apparatus.html b/gl/dev/supp-apparatus.html index ace765056..b7e9d0747 100644 --- a/gl/dev/supp-apparatus.html +++ b/gl/dev/supp-apparatus.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Apparatus criticus

                                      2023-04-27

                                      Critical apparatus is a standard feature of scholarly editions in which variant readings and other philological comments are presented to readers as a compressed list immediately following the text, organized by line numbers therein.

                                      • TEI definition: div ; EpiDoc-specific - customization: div

                                      Form and content of the apparatus varies from one discipline to another in the humanities. In manuscript studies and literary philology, the app. crit. is generally differentiated from a separate line-by-line commentary, and is devoted narrowly to the documentation of variant readings found in extant witnesses. In epigraphic and papyrological practice, where there is normally only one ancient witness to a text, the apparatus regularly treats divergeant or erroneous readings published by prior editors, alternative restorations and emendations, and comments on form and appearance (e.g., transposition of letters) that cannot be clearly represented in the text itself. Epigraphers and papyrologists often also include a commentary (line-by-line or otherwise) in which more extended discussion of the text and its interpretation and historical significance can be addressed.

                                      EpiDoc recommends choosing between two methods of encoding the sort of information that is traditionally placed in the critical apparatus:

                                      Probably the most commonly used in EpiDoc projects is the external approach (cf. TEI "location-referenced"), in which the apparatus is encoded explicitly in a separate <div type="apparatus"> element. The individual apparatus entries in such an external division are tied back to the text using standard TEI linking attributes (generally loc pointing to line numbers). This method requires relatively simple XSLT to produce acceptable output, but the EpiDoc Example XSLT does not currently cater for this out of the box.

                                      The in-line approach (cf. TEI "parallel segmentation method") makes use of tags placed directly in the text, which can then be interpreted during post-processing for display in a line-by-line form. Currently the only EpiDoc project to have implemented this is the Duke Databank of Documentary Papyri, and any other project wishing to do so would need some significant work on the EpiDoc Example XSLT to get the behaviour it required.

                                      There are a number of features which you may want to appear in your apparatus or in a separate apparatus section, which are not explicitly encoded as apparatus notes with either of the above methods. The EpiDoc example Stylesheets provide some support to render these in several ways.

                                      It is very important to decide on the approach you want to follow and remain consistent to that, to avoid inconsistencies, although both methods are acceptable and independent of the way you may want to display or not your apparatus notes. The fact that you decide to use app in the text, following the in-line approach, does not dictate automatically that you want an apparatus which includes also other features, as the fact that you use the external approach does not dictate that you do not want anything which you have actually encoded in the text to be printed in an apparatus section. These things are determined at the level of the rendering, not with the encoding, and you may chose what to do, as far as you are consistent with yourself.

                                      Although the external-apparatus approach is the recommended way to encode apparatus notes, you may wish not to have to produce one such note in <div[@type='apparatus']> for each choice element you encoded and want in an apparatus. To inform your encoding decision, here you can find a list of the possibilities currently offered by the The EpiDoc example Stylesheets.

                                      Specific guidance for each approach is provided in its own section as follows:

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Tom Elliott, author

                                      EpiDoc version: post-9.5

                                      Date: 2023-04-27

                                      \ No newline at end of file +

                                      Apparatus criticus

                                      2024-03-05

                                      Critical apparatus is a standard feature of scholarly editions in which variant readings and other philological comments are presented to readers as a compressed list immediately following the text, organized by line numbers therein.

                                      • TEI definition: div ; EpiDoc-specific + customization: div

                                      Form and content of the apparatus varies from one discipline to another in the humanities. In manuscript studies and literary philology, the app. crit. is generally differentiated from a separate line-by-line commentary, and is devoted narrowly to the documentation of variant readings found in extant witnesses. In epigraphic and papyrological practice, where there is normally only one ancient witness to a text, the apparatus regularly treats divergeant or erroneous readings published by prior editors, alternative restorations and emendations, and comments on form and appearance (e.g., transposition of letters) that cannot be clearly represented in the text itself. Epigraphers and papyrologists often also include a commentary (line-by-line or otherwise) in which more extended discussion of the text and its interpretation and historical significance can be addressed.

                                      EpiDoc recommends choosing between two methods of encoding the sort of information that is traditionally placed in the critical apparatus:

                                      Probably the most commonly used in EpiDoc projects is the external approach (cf. TEI "location-referenced"), in which the apparatus is encoded explicitly in a separate <div type="apparatus"> element. The individual apparatus entries in such an external division are tied back to the text using standard TEI linking attributes (generally loc pointing to line numbers). This method requires relatively simple XSLT to produce acceptable output, but the EpiDoc Example XSLT does not currently cater for this out of the box.

                                      The in-line approach (cf. TEI "parallel segmentation method") makes use of tags placed directly in the text, which can then be interpreted during post-processing for display in a line-by-line form. Currently the only EpiDoc project to have implemented this is the Duke Databank of Documentary Papyri, and any other project wishing to do so would need some significant work on the EpiDoc Example XSLT to get the behaviour it required.

                                      There are a number of features which you may want to appear in your apparatus or in a separate apparatus section, which are not explicitly encoded as apparatus notes with either of the above methods. The EpiDoc example Stylesheets provide some support to render these in several ways.

                                      It is very important to decide on the approach you want to follow and remain consistent to that, to avoid inconsistencies, although both methods are acceptable and independent of the way you may want to display or not your apparatus notes. The fact that you decide to use app in the text, following the in-line approach, does not dictate automatically that you want an apparatus which includes also other features, as the fact that you use the external approach does not dictate that you do not want anything which you have actually encoded in the text to be printed in an apparatus section. These things are determined at the level of the rendering, not with the encoding, and you may chose what to do, as far as you are consistent with yourself.

                                      Although the external-apparatus approach is the recommended way to encode apparatus notes, you may wish not to have to produce one such note in <div[@type='apparatus']> for each choice element you encoded and want in an apparatus. To inform your encoding decision, here you can find a list of the possibilities currently offered by the The EpiDoc example Stylesheets.

                                      Specific guidance for each approach is provided in its own section as follows:

                                      Responsibility for this section

                                      1. Gabriel Bodard, author
                                      2. Tom Elliott, author

                                      EpiDoc version: post-9.5

                                      Date: 2024-03-05

                                      \ No newline at end of file diff --git a/gl/dev/supp-bibliography-pt-br.html b/gl/dev/supp-bibliography-pt-br.html index f40b74857..20ee3dc25 100644 --- a/gl/dev/supp-bibliography-pt-br.html +++ b/gl/dev/supp-bibliography-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                      Codificando a Bibliografia

                                      2023-04-27

                                      As citações bibliográficas que estão dentro de uma edição epigráfica/papirológica (distintas da bibliografia master de um projeto ou publicação).

                                      • TEI definition: listBibl ; EpiDoc-specific +

                                        Codificando a Bibliografia

                                        2024-03-05

                                        As citações bibliográficas que estão dentro de uma edição epigráfica/papirológica (distintas da bibliografia master de um projeto ou publicação).

                                        http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBI

                                        Bibliografia Master

                                        Geralmente se recomenda que uma bibliografia master, contendo todos os trabalhos citados em uma publicação ou projeto (sejam elas discussões ou apenas publicações prévias de textos), seja codificada em um arquivo único separado. Este arquivo pode ser validado pelo schema EpiDoc ou por um schema bibliográfico TEI genérico, ou pode até mesmo ser um banco de dados independente, ou uma página HTML com um id para cada entrada bibliográfica.

                                        Se a codificação for em TEI, a bibliografia deve compreender uma lista estruturada, seja de elementos bibl (recomendado) ou elementos biblStruct (o que provavelmente seria um excesso para a maioria dos projetos, mas veja o segundo exemplo abaixo). Um xml:id em cada item permitirá que seja feita a referência ou o link para as citações bibliográficas locais em textos separados.

                                        <listBibl>
                                         <bibl xml:id="applebaum1979">
                                          <author>Shimon <surname>Applebaum</surname>
                                          </author>,
                                         <date>1979</date>, <title level="m">Jews and Greeks in Ancient
                                             Cyrene</title>, <pubPlace>Leuven</pubPlace>.</bibl>
                                         <bibl xml:id="jmr1971a">
                                          <author>Joyce M. <surname>Reynolds</surname>
                                          </author>,
                                         <date>1971</date>, <title level="a">Zawiet Msus</title>, <title level="j">Libya Antiqua</title>
                                          <biblScope unit="issue">8</biblScope>, <biblScope unit="page">39-42</biblScope>
                                         </bibl>
                                        </listBibl>
                                        <listBibl>
                                         <biblStruct xml:id="b0290">
                                          <analytic>
                                           <author>
                                            <surname>Feissel</surname>
                                            <forename>D.</forename>
                                           </author>
                                           <title level="a">Inscriptions byzantines de Ténos</title>
                                          </analytic>
                                          <monogr>
                                           <title level="j">BCH</title>
                                           <imprint>
                                            <date>1980</date>
                                           </imprint>
                                           <biblScope unit="issue">104</biblScope>
                                           <biblScope unit="page">477-518</biblScope>
                                          </monogr>
                                         </biblStruct>
                                        </listBibl>

                                        Bibliografia Master no Zotero

                                        Você pode desejar manter sua bibliografia em uma biblioteca grupal Zotero ou na sua biblioteca pessoal Zotero, e usá-la dentro do seu projeto EpiDoc.

                                        Você pode exportar uma bibliografia master em TEI do Zotero para trabalhar seguindo as normas acima.

                                        Você também pode utilizar diretamente o API do Zotero para imprimir sua bibliografia usando os exemplos de Folhas de Estilo.

                                        Para executar esta última tarefa, você precisa:

                                        1. Inserir dados da forma correta no Zotero
                                        2. Inserir citações em seu arquivo (veja abaixo)
                                        3. Compilar a bibliografia e dar estilo às citações com o CLS Style (é muito sensato utilizar os estilos disponíveis, mas você pode criar o seu)

                                        Para utilizar esta função dos Exemplos de Folha de Estilo, você precisa selecionar um valor para o parâmetro bibliography.

                                        • none: (default), se aplica a qualquer outro template específico e não executa nenhuma das funções seguintes
                                        • localTEI: a path para o arquivo de bibliografia xml TEI precisa ser indicada no parâmetro localBibl, com uma path relativa, desde o xslt (local default, o diretório principal do xslt). Esta função vai localizar para cada bibl o valor dado a qualquer ptr/@target e imprimir o autor ou editor e data vindos da bibliografia TEI
                                        • zotero: selecionar este valor vai usar os exemplos de folhas de estilo para acionar o API Zotero. Aqui temos uma série de outros parâmetros que devem ser determinados
                                          • parâmetro ZoteroUorG : que define se a biblioteca alvo em zotero é uma biblioteca grupal (default) ou uma biblioteca de usuário
                                          • parâmetro ZoteroKey : que dá a chave para a biblioteca (por enquanto a localização default é a biblioteca grupal EAGLE)
                                          • parâmetro ZoteroNS : especifica um namespace, se as tags na biblioteca Zotero library usarem um (configuração default é none)
                                          • parâmetro ZoteroStyle : especifica o Estilo Zotero a ser utilizado para o output (o default é chicago-author-date, como eu acho que o Zotero faz de qualquer modo)

                                        Os pressupostos aqui são que você tem uma biblioteca no Zotero, aberta e acessível, e que você designou uma tag para cada registro que deseja utilizar, talvez com um prefixo, no caso da mesma biblioteca ser utilizada por vários projetos.

                                        Dados os defaults acima, se nada for especificado a não ser bibliography=zotero, a transformação examinará, então, a biblioteca grupal EAGLE, procurando por itens com tags equivalentes àquelas dadas a cada ptr com target de cada bibl, e dará o retorno dos elementos bibl presentes em um <div[@type='bibliography']> como citações integrais, e desta forma fará a impressão de uma citação formatada para os outros bibl, toda vez que ocorrerem. A tag designada em Zotero DEVE ser única na biblioteca.

                                        Isto pode ser testado com o uso do parâmetro edn-structure=eagle.

                                        O exemplo a seguir, adaptado do projeto Beta Maṣāḥǝft, mostra a codificação usandobibl e um ptr com target igual à tag do Zotero, em dois contextos diferentes, na bibliografia e em uma citação dentro da edição. A explicação logo depois esclarecerá as configurações e o output.

                                        <div type="edition">
                                         <bibl>
                                          <ptr target="RIE1"/>
                                          <citedRange unit="page">279-280</citedRange>
                                         </bibl>
                                        </div>
                                        <div type="bibliography">
                                         <bibl>
                                          <ptr target="RIE1"/>
                                         </bibl>
                                        </div>

                                        O projeto faz uso de uma biblioteca grupal no Zotero, portanto ZoteroUorG=group permaneceu como valor default, ZoteroKey foi configurado com a chave de grupo 358366 para o grupo EthioStudies.

                                        Esta Biblioteca Grupal é utilizada por diversos projetos, portanto o parâmetro ZoteroNS foi configurado como aquele usado por este projeto, bm:. O projeto também tem seu próprio estilo, e portanto o parâmetro ZoteroStyle foi configurado como hiob-ludolf-centre-for-ethiopian-studies, o short name do estilo salvo no repositório CSL.

                                        As normas completas utilizadas neste projeto para inserção de dados na bibliografia e as utilizadas para especificação de estilo podem ser vistas aqui Zotero HLCES bibliography workflow.

                                        Esta transformação, portanto, buscará cada entrada de API Zotero para gravar com a tag zotero bm:RIE1 e imprimirá para o primeiro bibl Bernard et al. 1991, 279-280, para o segundo "RIE I. Bernard, É., A.J. Drewes, and R. Schneider 1991. Recueil des Inscriptions de l’Éthiopie des périodes pré-axoumite et axoumite, Introduction de Fr. Anfray, I: Les documents (Paris: Diffusion de Boccard, 1991)."

                                        Citações bibliográficas

                                        Cada texto muitas vezes conterá múltiplas citações bibliográficas, como, por exemplo, de trabalhos citados em um comentário, a fonte das traduções ou fotos e, mais importante, de publicações prévias do mesmo texto por outros pesquisadores. Dentro de uma edição EpiDoc, tais citações devem ficar em um <div type="bibliography">, seja num p desestruturado (se a bibliografia for um parágrafo de texto livre com ligação com um texto como "Primeira publicação em ..., de anotações; reimpresos em ...; desta forma ... . Depois reeditado de uma autópsia por..." etc.) ou em um listBibl se as citações forem listas simples ou numeradas.

                                        Alguns projetos preferem criar seções múltiplas de <div type="bibliography"> para cada texto, de modo a agrupar tematicamente citações bibliográficas (por exemplo: edições anteriores, ilustrações disponíveis e assim por diante). O atributo subtype pode ser utilizado para fazer a distinção entre elas e facilitar o processamento. Em particular, listas de imagens publicadas online ou impressas por terceiros às vezes são codificadas dentro de um <div type="bibliography" subtype="illustrations">, e a respeito disto veja mais em Imagens, figuras e facsimile.

                                        Cada citação bibliográfica pode ser codificada de modo relativamente simples em um elemento bibl na forma desejada para a edição online ou impressa, seja ela uma referência bibliográfica completa, autor abreviado + data ou similar. Muitas vezes é util, entretanto, fazer um link para a entrada na autoridade bibliográfica (geralmente a bibliografia master), para que:

                                        1. a edição possa fazer o hiperlink de uma chamada abreviada para uma bibliografia completa ou até comentada;
                                        2. citações bibliográficas (completas ou abreviadas) possam ser geradas automaticamente da bibliografia principal, dando maior consistência e reduzindo a necessidade de entradas múltiplas da mesma informação;
                                        3. uma concordância bibliográfica que pode ser gerada com o uso de idno da edição atual, o xml:id do item bibliográfico e o citedRange da citação bibliográfica na edição.

                                        Presumindo uma bibliografia master em TEI, contendo as entradas do primeiro exemplo acima, a citação bibliográfica abaixo iria (a) apontar para o título Reynolds 1971 dentro dela, e (b) declarar sem ambiguidade que o texto no qual esta citação aparece foi publicado anteriormente como número 3 em sua edição.

                                        <bibl>
                                         <ptr target="biblio.xml#jmr1971a"/>
                                         <citedRange>3</citedRange>
                                        </bibl>

                                        Isto permite, primeiro, que a edição mostre textos como ‘Reynolds 1971, 3’ ou ‘Reynolds, 'Zawiet Msus' (1971), no. 3’ ou similar; segunto, uma concordância bibliográfica seria gerada que listasse todas as incrições em cada publicação anterior, mostrando qual inscrição na coleção atual corresponde a cada publicação. (Veja, por exemplo, a InsAph concordance para um artigo de Reynolds.)

                                        O seguinte exemplo, adaptado de Ancient Inscriptions of the Northern Black Sea (IOSPE), demonstra o uso de um único <div type="bibliography"> com duas listas de edições biliográficas internas, uma para cada um dos dois textos num único suporte. Note o uso de ptr como referência a itens bibliográficos em uma lista bibliográfica externa, como descrito acima.

                                        <div type="bibliography">
                                         <listBibl n="1corresp="#text-1">
                                          <bibl n="L1">
                                        <!-- Сборник -->
                                           <ptr target="bib:b0132"/>, 70, № <citedRange>64</citedRange>
                                          </bibl>
                                          <bibl n="2">
                                        <!-- Латышев 1898a -->
                                           <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                          </bibl>
                                         </listBibl>
                                         <listBibl n="2corresp="#text-2">
                                          <bibl n="L1">
                                        <!-- Латышев 1898a -->
                                           <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                          </bibl>
                                         </listBibl>
                                        </div>

                                        Este exemplo, adaptado do Corpus of the Inscriptions of Campā, demonstra o uso de duas seções subtyped <div type="bibliography">, uma listando as edições anteriores do texto e outra listando outros trabalhos secundários sobre o texto. O exemplo também demonstra o uso de uma descrição bibliográfica em prosa, no lugar de uma simples lista, de modo a fornecer aos usuários informação a respeito da relação entre as edições citadas.

                                        <div type="bibliographysubtype="edition">
                                         <ab>A summary of this inscription was presented in <bibl>
                                           <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                          </bibl>. The present edition and translation after
                                         <bibl>
                                           <ptr target="cic-bibl:ECIC-III"/>: <citedRange unit="item">464</citedRange>
                                          </bibl>.</ab>
                                        </div>
                                        <div type="bibliography"
                                         subtype="secondary">

                                         <listBibl>
                                          <bibl>
                                           <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                          </bibl>
                                          <bibl>
                                           <ptr target="cic-bibl:schweyer-2005a"/>: <citedRange unit="item">106</citedRange>.</bibl>
                                         </listBibl>
                                        </div>

                                        See also:

                                        Other pages describing <listBibl>:

                                          Other pages describing <bibl>:

                                          Other pages describing <biblStruct>:

                                            Other pages describing <citedRange>:

                                              Responsabilidade por esta seção

                                              1. Gabriel Bodard, autor
                                              2. Pietro Liuzzo, autor
                                              3. Assunção Medeiros, traduzido para o Português por

                                              EpiDoc version: post-9.5

                                              Date: 2023-04-27

                                              \ No newline at end of file + customization: citedRange
                                            http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBI

                                            Bibliografia Master

                                            Geralmente se recomenda que uma bibliografia master, contendo todos os trabalhos citados em uma publicação ou projeto (sejam elas discussões ou apenas publicações prévias de textos), seja codificada em um arquivo único separado. Este arquivo pode ser validado pelo schema EpiDoc ou por um schema bibliográfico TEI genérico, ou pode até mesmo ser um banco de dados independente, ou uma página HTML com um id para cada entrada bibliográfica.

                                            Se a codificação for em TEI, a bibliografia deve compreender uma lista estruturada, seja de elementos bibl (recomendado) ou elementos biblStruct (o que provavelmente seria um excesso para a maioria dos projetos, mas veja o segundo exemplo abaixo). Um xml:id em cada item permitirá que seja feita a referência ou o link para as citações bibliográficas locais em textos separados.

                                            <listBibl>
                                             <bibl xml:id="applebaum1979">
                                              <author>Shimon <surname>Applebaum</surname>
                                              </author>,
                                             <date>1979</date>, <title level="m">Jews and Greeks in Ancient
                                                 Cyrene</title>, <pubPlace>Leuven</pubPlace>.</bibl>
                                             <bibl xml:id="jmr1971a">
                                              <author>Joyce M. <surname>Reynolds</surname>
                                              </author>,
                                             <date>1971</date>, <title level="a">Zawiet Msus</title>, <title level="j">Libya Antiqua</title>
                                              <biblScope unit="issue">8</biblScope>, <biblScope unit="page">39-42</biblScope>
                                             </bibl>
                                            </listBibl>
                                            <listBibl>
                                             <biblStruct xml:id="b0290">
                                              <analytic>
                                               <author>
                                                <surname>Feissel</surname>
                                                <forename>D.</forename>
                                               </author>
                                               <title level="a">Inscriptions byzantines de Ténos</title>
                                              </analytic>
                                              <monogr>
                                               <title level="j">BCH</title>
                                               <imprint>
                                                <date>1980</date>
                                               </imprint>
                                               <biblScope unit="issue">104</biblScope>
                                               <biblScope unit="page">477-518</biblScope>
                                              </monogr>
                                             </biblStruct>
                                            </listBibl>

                                            Bibliografia Master no Zotero

                                            Você pode desejar manter sua bibliografia em uma biblioteca grupal Zotero ou na sua biblioteca pessoal Zotero, e usá-la dentro do seu projeto EpiDoc.

                                            Você pode exportar uma bibliografia master em TEI do Zotero para trabalhar seguindo as normas acima.

                                            Você também pode utilizar diretamente o API do Zotero para imprimir sua bibliografia usando os exemplos de Folhas de Estilo.

                                            Para executar esta última tarefa, você precisa:

                                            1. Inserir dados da forma correta no Zotero
                                            2. Inserir citações em seu arquivo (veja abaixo)
                                            3. Compilar a bibliografia e dar estilo às citações com o CLS Style (é muito sensato utilizar os estilos disponíveis, mas você pode criar o seu)

                                            Para utilizar esta função dos Exemplos de Folha de Estilo, você precisa selecionar um valor para o parâmetro bibliography.

                                            • none: (default), se aplica a qualquer outro template específico e não executa nenhuma das funções seguintes
                                            • localTEI: a path para o arquivo de bibliografia xml TEI precisa ser indicada no parâmetro localBibl, com uma path relativa, desde o xslt (local default, o diretório principal do xslt). Esta função vai localizar para cada bibl o valor dado a qualquer ptr/@target e imprimir o autor ou editor e data vindos da bibliografia TEI
                                            • zotero: selecionar este valor vai usar os exemplos de folhas de estilo para acionar o API Zotero. Aqui temos uma série de outros parâmetros que devem ser determinados
                                              • parâmetro ZoteroUorG : que define se a biblioteca alvo em zotero é uma biblioteca grupal (default) ou uma biblioteca de usuário
                                              • parâmetro ZoteroKey : que dá a chave para a biblioteca (por enquanto a localização default é a biblioteca grupal EAGLE)
                                              • parâmetro ZoteroNS : especifica um namespace, se as tags na biblioteca Zotero library usarem um (configuração default é none)
                                              • parâmetro ZoteroStyle : especifica o Estilo Zotero a ser utilizado para o output (o default é chicago-author-date, como eu acho que o Zotero faz de qualquer modo)

                                            Os pressupostos aqui são que você tem uma biblioteca no Zotero, aberta e acessível, e que você designou uma tag para cada registro que deseja utilizar, talvez com um prefixo, no caso da mesma biblioteca ser utilizada por vários projetos.

                                            Dados os defaults acima, se nada for especificado a não ser bibliography=zotero, a transformação examinará, então, a biblioteca grupal EAGLE, procurando por itens com tags equivalentes àquelas dadas a cada ptr com target de cada bibl, e dará o retorno dos elementos bibl presentes em um <div[@type='bibliography']> como citações integrais, e desta forma fará a impressão de uma citação formatada para os outros bibl, toda vez que ocorrerem. A tag designada em Zotero DEVE ser única na biblioteca.

                                            Isto pode ser testado com o uso do parâmetro edn-structure=eagle.

                                            O exemplo a seguir, adaptado do projeto Beta Maṣāḥǝft, mostra a codificação usandobibl e um ptr com target igual à tag do Zotero, em dois contextos diferentes, na bibliografia e em uma citação dentro da edição. A explicação logo depois esclarecerá as configurações e o output.

                                            <div type="edition">
                                             <bibl>
                                              <ptr target="RIE1"/>
                                              <citedRange unit="page">279-280</citedRange>
                                             </bibl>
                                            </div>
                                            <div type="bibliography">
                                             <bibl>
                                              <ptr target="RIE1"/>
                                             </bibl>
                                            </div>

                                            O projeto faz uso de uma biblioteca grupal no Zotero, portanto ZoteroUorG=group permaneceu como valor default, ZoteroKey foi configurado com a chave de grupo 358366 para o grupo EthioStudies.

                                            Esta Biblioteca Grupal é utilizada por diversos projetos, portanto o parâmetro ZoteroNS foi configurado como aquele usado por este projeto, bm:. O projeto também tem seu próprio estilo, e portanto o parâmetro ZoteroStyle foi configurado como hiob-ludolf-centre-for-ethiopian-studies, o short name do estilo salvo no repositório CSL.

                                            As normas completas utilizadas neste projeto para inserção de dados na bibliografia e as utilizadas para especificação de estilo podem ser vistas aqui Zotero HLCES bibliography workflow.

                                            Esta transformação, portanto, buscará cada entrada de API Zotero para gravar com a tag zotero bm:RIE1 e imprimirá para o primeiro bibl Bernard et al. 1991, 279-280, para o segundo "RIE I. Bernard, É., A.J. Drewes, and R. Schneider 1991. Recueil des Inscriptions de l’Éthiopie des périodes pré-axoumite et axoumite, Introduction de Fr. Anfray, I: Les documents (Paris: Diffusion de Boccard, 1991)."

                                            Citações bibliográficas

                                            Cada texto muitas vezes conterá múltiplas citações bibliográficas, como, por exemplo, de trabalhos citados em um comentário, a fonte das traduções ou fotos e, mais importante, de publicações prévias do mesmo texto por outros pesquisadores. Dentro de uma edição EpiDoc, tais citações devem ficar em um <div type="bibliography">, seja num p desestruturado (se a bibliografia for um parágrafo de texto livre com ligação com um texto como "Primeira publicação em ..., de anotações; reimpresos em ...; desta forma ... . Depois reeditado de uma autópsia por..." etc.) ou em um listBibl se as citações forem listas simples ou numeradas.

                                            Alguns projetos preferem criar seções múltiplas de <div type="bibliography"> para cada texto, de modo a agrupar tematicamente citações bibliográficas (por exemplo: edições anteriores, ilustrações disponíveis e assim por diante). O atributo subtype pode ser utilizado para fazer a distinção entre elas e facilitar o processamento. Em particular, listas de imagens publicadas online ou impressas por terceiros às vezes são codificadas dentro de um <div type="bibliography" subtype="illustrations">, e a respeito disto veja mais em Imagens, figuras e facsimile.

                                            Cada citação bibliográfica pode ser codificada de modo relativamente simples em um elemento bibl na forma desejada para a edição online ou impressa, seja ela uma referência bibliográfica completa, autor abreviado + data ou similar. Muitas vezes é util, entretanto, fazer um link para a entrada na autoridade bibliográfica (geralmente a bibliografia master), para que:

                                            1. a edição possa fazer o hiperlink de uma chamada abreviada para uma bibliografia completa ou até comentada;
                                            2. citações bibliográficas (completas ou abreviadas) possam ser geradas automaticamente da bibliografia principal, dando maior consistência e reduzindo a necessidade de entradas múltiplas da mesma informação;
                                            3. uma concordância bibliográfica que pode ser gerada com o uso de idno da edição atual, o xml:id do item bibliográfico e o citedRange da citação bibliográfica na edição.

                                            Presumindo uma bibliografia master em TEI, contendo as entradas do primeiro exemplo acima, a citação bibliográfica abaixo iria (a) apontar para o título Reynolds 1971 dentro dela, e (b) declarar sem ambiguidade que o texto no qual esta citação aparece foi publicado anteriormente como número 3 em sua edição.

                                            <bibl>
                                             <ptr target="biblio.xml#jmr1971a"/>
                                             <citedRange>3</citedRange>
                                            </bibl>

                                            Isto permite, primeiro, que a edição mostre textos como ‘Reynolds 1971, 3’ ou ‘Reynolds, 'Zawiet Msus' (1971), no. 3’ ou similar; segunto, uma concordância bibliográfica seria gerada que listasse todas as incrições em cada publicação anterior, mostrando qual inscrição na coleção atual corresponde a cada publicação. (Veja, por exemplo, a InsAph concordance para um artigo de Reynolds.)

                                            O seguinte exemplo, adaptado de Ancient Inscriptions of the Northern Black Sea (IOSPE), demonstra o uso de um único <div type="bibliography"> com duas listas de edições biliográficas internas, uma para cada um dos dois textos num único suporte. Note o uso de ptr como referência a itens bibliográficos em uma lista bibliográfica externa, como descrito acima.

                                            <div type="bibliography">
                                             <listBibl n="1corresp="#text-1">
                                              <bibl n="L1">
                                            <!-- Сборник -->
                                               <ptr target="bib:b0132"/>, 70, № <citedRange>64</citedRange>
                                              </bibl>
                                              <bibl n="2">
                                            <!-- Латышев 1898a -->
                                               <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                              </bibl>
                                             </listBibl>
                                             <listBibl n="2corresp="#text-2">
                                              <bibl n="L1">
                                            <!-- Латышев 1898a -->
                                               <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                              </bibl>
                                             </listBibl>
                                            </div>

                                            Este exemplo, adaptado do Corpus of the Inscriptions of Campā, demonstra o uso de duas seções subtyped <div type="bibliography">, uma listando as edições anteriores do texto e outra listando outros trabalhos secundários sobre o texto. O exemplo também demonstra o uso de uma descrição bibliográfica em prosa, no lugar de uma simples lista, de modo a fornecer aos usuários informação a respeito da relação entre as edições citadas.

                                            <div type="bibliographysubtype="edition">
                                             <ab>A summary of this inscription was presented in <bibl>
                                               <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                              </bibl>. The present edition and translation after
                                             <bibl>
                                               <ptr target="cic-bibl:ECIC-III"/>: <citedRange unit="item">464</citedRange>
                                              </bibl>.</ab>
                                            </div>
                                            <div type="bibliography"
                                             subtype="secondary">

                                             <listBibl>
                                              <bibl>
                                               <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                              </bibl>
                                              <bibl>
                                               <ptr target="cic-bibl:schweyer-2005a"/>: <citedRange unit="item">106</citedRange>.</bibl>
                                             </listBibl>
                                            </div>

                                            See also:

                                            Other pages describing <listBibl>:

                                              Other pages describing <bibl>:

                                              Other pages describing <biblStruct>:

                                                Other pages describing <citedRange>:

                                                  Responsabilidade por esta seção

                                                  1. Gabriel Bodard, autor
                                                  2. Pietro Liuzzo, autor
                                                  3. Assunção Medeiros, traduzido para o Português por

                                                  EpiDoc version: post-9.5

                                                  Date: 2024-03-05

                                                  \ No newline at end of file diff --git a/gl/dev/supp-bibliography.html b/gl/dev/supp-bibliography.html index ec2947598..cbad5884b 100644 --- a/gl/dev/supp-bibliography.html +++ b/gl/dev/supp-bibliography.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                  Encoding the Bibliography

                                                  2023-04-27

                                                  The bibliographical citations within an epigraphic/papyrological edition (to be distinguished from the master bibliography of a project or publication).

                                                  • TEI definition: listBibl ; EpiDoc-specific +

                                                    Encoding the Bibliography

                                                    2024-03-05

                                                    The bibliographical citations within an epigraphic/papyrological edition (to be distinguished from the master bibliography of a project or publication).

                                                    http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBI

                                                    Master bibliography

                                                    It is generally recommended that a master bibliography, containing all works cited in a publication or project (whether including discussions or only previous publications of texts) be encoded in a separate, single file. This might validate to the EpiDoc schema or to a generic TEI bibliographic schema, or could even be a free-standing database, or an HTML page with an id for each bibliographical entry.

                                                    If encoding in TEI, the bibliography should comprise a structured list either of bibl elements (recommended) or biblStruct elements (probably overkill for most projects, but see second example below). An xml:id on each item will allow referencing or linking from the localized bibliographic citations in individual texts.

                                                    <listBibl>
                                                     <bibl xml:id="applebaum1979">
                                                      <author>Shimon <surname>Applebaum</surname>
                                                      </author>,
                                                     <date>1979</date>, <title level="m">Jews and Greeks in Ancient
                                                         Cyrene</title>, <pubPlace>Leuven</pubPlace>.</bibl>
                                                     <bibl xml:id="jmr1971a">
                                                      <author>Joyce M. <surname>Reynolds</surname>
                                                      </author>,
                                                     <date>1971</date>, <title level="a">Zawiet Msus</title>, <title level="j">Libya Antiqua</title>
                                                      <biblScope unit="issue">8</biblScope>, <biblScope unit="page">39-42</biblScope>
                                                     </bibl>
                                                    </listBibl>
                                                    <listBibl>
                                                     <biblStruct xml:id="b0290">
                                                      <analytic>
                                                       <author>
                                                        <surname>Feissel</surname>
                                                        <forename>D.</forename>
                                                       </author>
                                                       <title level="a">Inscriptions byzantines de Ténos</title>
                                                      </analytic>
                                                      <monogr>
                                                       <title level="j">BCH</title>
                                                       <imprint>
                                                        <date>1980</date>
                                                       </imprint>
                                                       <biblScope unit="issue">104</biblScope>
                                                       <biblScope unit="page">477-518</biblScope>
                                                      </monogr>
                                                     </biblStruct>
                                                    </listBibl>

                                                    Master bibliography in Zotero

                                                    You may want to maintain your bibliography in a Zotero group library or into your personal Zotero library and use that for your EpiDoc project.

                                                    You can export a master bibliography in TEI from Zotero to work following the guidelines above.

                                                    You can also use directly the Zotero API to print your bibliography using the example Stylesheets.

                                                    To do the latter you will need to

                                                    1. Enter data correctly in Zotero
                                                    2. Enter citations in your file (see below)
                                                    3. Compile the bibliography and style the citations with the a CLS Style (it is very wise to use the available ones, but you can still create your own)

                                                    To use this feature of the Example Stylesheets you will have to select a value for the parameter bibliography.

                                                    • none: (default), applies any other locally specified templates and does neither of the following
                                                    • localTEI: the path to the TEI xml bibliography file needs to be given in the parameter localBibl, with a relative path from the xslt (default location, the parent directory of the xslt). This will look up for each bibl the value given in any ptr/@target and print author or editor and date from the TEI bibliography
                                                    • zotero: selecting this will use the example stylesheets to call the Zotero API. There are a series of other parameters which need to be set
                                                      • parameter ZoteroUorG : which selects if the target library in zotero is a group library (default) or a user library
                                                      • parameter ZoteroKey : which gives the key to the library (for the time being it defaults on the EAGLE group bibliography)
                                                      • parameter ZoteroNS : specifies a namespace, if tags in the Zotero library use any (default on nothing)
                                                      • parameter ZoteroStyle : specifies the Zotero Style to be used for the output (defaults on the chicago-author-date, as I think Zotero does anyway)

                                                    The assumptions here are that you have an accessible and open library in Zotero, and that you have assigned a tag to each record you want to use, perhaps with a prefix, in case the same bibliography is used by several projects.

                                                    Given the defaults above, if nothing but bibliography=zotero is specified, the transformation will then look into the EAGLE group library for items with tags equal to the ones given in each ptr with target of each bibl and will return bibl elements present in a <div[@type='bibliography']> as full citations, whereas it will print a formatted citation for the other bibl, wherever they occur. The tag assigned in Zotero MUST be uniquely assigned in the library.

                                                    This is testable using the parameter edn-structure=eagle parameter.

                                                    The following example, adapted from the Beta Maṣāḥǝft project, shows the encoding using bibl and a ptr with target equal to the Zotero tag, in two different contexts, the bibliography and a citation in the edition. The following explanation will clarify the settings and the output.

                                                    <div type="edition">
                                                     <bibl>
                                                      <ptr target="RIE1"/>
                                                      <citedRange unit="page">279-280</citedRange>
                                                     </bibl>
                                                    </div>
                                                    <div type="bibliography">
                                                     <bibl>
                                                      <ptr target="RIE1"/>
                                                     </bibl>
                                                    </div>

                                                    The project uses a Group library in Zotero, so ZoteroUorG=group has been left to the default value, ZoteroKey has been set to the group key 358366 of the EthioStudies group.

                                                    This Group Library is use by several projects, so the ZoteroNS parameter has been set to that used by this project, bm:. One could haveThe project has also its own style, and therefore the ZoteroStyle parameter has been set to hiob-ludolf-centre-for-ethiopian-studies, the short name of the style saved in the CSL repository.

                                                    Full guidelines used by this project for the data entry in the bibliography and for the style specification can be seen here Zotero HLCES bibliography workflow.

                                                    This transformation will thus call for each entry the Zotero API for the record with the zotero tag bm:RIE1 and print for the first bibl Bernard et al. 1991, 279-280, for the second "RIE I. Bernard, É., A.J. Drewes, and R. Schneider 1991. Recueil des Inscriptions de l’Éthiopie des périodes pré-axoumite et axoumite, Introduction de Fr. Anfray, I: Les documents (Paris: Diffusion de Boccard, 1991)."

                                                    Bibliographic citations

                                                    Individual texts will often contain multiple bibliographic citations, for example to works cited in commentary, the source of translations or photographs, and most importantly, to previous publications of the same text by other scholars. Within an EpiDoc edition, such citations should be contained in the <div type="bibliography">, either in an unstructured p (if the bibliography is a paragraph of free text with connecting prose such as, "First published in ..., from notebooks; reprinted in ...; whence ... . Later re-edited from autopsy by..." etc.) or in a listBibl if the citations are a simple (or numbered) list.

                                                    Some projects prefer to create multiple <div type="bibliography"> sections for each text in order to group bibliographic citations thematically (e.g., primary editions, prior editions, derivative editions, translations, available illustrations, and the like. The subtype may be used to distinguish between them and to facilitate processing. In particular, lists of images published on-line or in print by third parties are sometimes encoded within <div type="bibliography" subtype="illustrations">, regarding which see further Images, figures, and facsimile.

                                                    An alternative to creating multiple <div>s as described above, it is also possible to use the type attribute on a <bibl> element to indicate the nature of the source. Suggested values are:

                                                    • principalEdition or editioPrinceps
                                                    • secondary (secondary source)
                                                    • edition (any edition other than princeps)
                                                    • ancientEdition
                                                    • modernEdition
                                                    • citation (text or object is cited in the source)
                                                    • corrections
                                                    • illustrations
                                                    • otherPublications
                                                    • translation

                                                    Each bibliographic citation may be encoded relatively simply in a bibl element in the form that is desired in the online (or print) edition, be that a full bibliographic reference or abbreviated author + date or similar. It is often useful, however, to link back to the entry in a bibliographic authority (generally the master bibliography), for example so that:

                                                    1. edition can hyperlink back from short title to a full or even annotated bibliography;
                                                    2. bibliographic citations (full or short) can be automatically generated from the main bibliography, providing more consistency and reducing the need for multiple entry of identical information;
                                                    3. a bibliographic concordance can be generated (using the idno of the current edition, the xml:id of the bibliographic item, and the citedRange of the bibliographic citation in the edition.

                                                    Assuming a master bibliography in TEI containing the entries from the first example above, the bibliographic citation below would (a) point to the Reynolds 1971 title therein, and (b) state unambiguously that the text in whose edition this citation appears was previously published as number 3 in her edition.

                                                    <bibl>
                                                     <ptr target="biblio.xml#jmr1971a"/>
                                                     <citedRange>3</citedRange>
                                                    </bibl>

                                                    This would allow, firstly, the edition to display text such as ‘Reynolds 1971, 3’ or ‘Reynolds, 'Zawiet Msus' (1971), no. 3’ or similar; and secondly a bibliographic concordance to be generated that lists all of the inscriptions in each previous publication, showing which inscription in the current collection corresponds to each. (See for example the InsAph concordance for a Reynolds article.)

                                                    The following example, adapted from the Ancient Inscriptions of the Northern Black Sea (IOSPE), demonstrates the use of a single <div type="bibliography"> with two internal bibliographic lists of editions, one for each of two texts on the one support. Note the use of ptr to refer to bibliographic items in an external bibliographic list, as described above.

                                                    <div type="bibliography">
                                                     <listBibl n="1corresp="#text-1">
                                                      <bibl n="L1">
                                                    <!-- Сборник -->
                                                       <ptr target="bib:b0132"/>, 70, № <citedRange>64</citedRange>
                                                      </bibl>
                                                      <bibl n="2">
                                                    <!-- Латышев 1898a -->
                                                       <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                                      </bibl>
                                                     </listBibl>
                                                     <listBibl n="2corresp="#text-2">
                                                      <bibl n="L1">
                                                    <!-- Латышев 1898a -->
                                                       <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                                      </bibl>
                                                     </listBibl>
                                                    </div>

                                                    This example, adapted from the Corpus of the Inscriptions of Campā, demonstrates the use of two, subtyped <div type="bibliography"> sections, one listing previous editions of the text and the other listing other secondary work on the text. It also demonstrates the use of a prose bibliographic description, rather than a simple list, in order to provide users with information about the relationship between cited editions.

                                                    <div type="bibliographysubtype="edition">
                                                     <ab>A summary of this inscription was presented in <bibl>
                                                       <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                                      </bibl>. The present edition and translation after
                                                     <bibl>
                                                       <ptr target="cic-bibl:ECIC-III"/>: <citedRange unit="item">464</citedRange>
                                                      </bibl>.</ab>
                                                    </div>
                                                    <div type="bibliography"
                                                     subtype="secondary">

                                                     <listBibl>
                                                      <bibl>
                                                       <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                                      </bibl>
                                                      <bibl>
                                                       <ptr target="cic-bibl:schweyer-2005a"/>: <citedRange unit="item">106</citedRange>.</bibl>
                                                     </listBibl>
                                                    </div>

                                                    Customization of biblScope unit attribute

                                                    The TEI allows bibliographical references in bibl or biblStruct elements to be constrained to one or more subdivisions using the unit attribute. A number of recommended values are provided (e.g., chapter, volume). An additional set of values common to epigraphical publications supplements the TEI list. N.B., this list merely represents an open list of suggested values. While you are not obligated to use these values, or, in fact, any value at all, consistent application of unit attributes should be considered a best practice.

                                                    See also:

                                                    Other pages describing <listBibl>:

                                                      Other pages describing <bibl>:

                                                      Other pages describing <biblStruct>:

                                                        Other pages describing <biblScope>:

                                                          Other pages describing <citedRange>:

                                                            Responsibility for this section

                                                            1. Gabriel Bodard, author
                                                            2. Pietro Liuzzo, Author
                                                            3. Scott Vanderbilt, Author

                                                            EpiDoc version: post-9.5

                                                            Date: 2023-04-27

                                                            \ No newline at end of file + customization: citedRange
                                                          http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COBI

                                                          Master bibliography

                                                          It is generally recommended that a master bibliography, containing all works cited in a publication or project (whether including discussions or only previous publications of texts) be encoded in a separate, single file. This might validate to the EpiDoc schema or to a generic TEI bibliographic schema, or could even be a free-standing database, or an HTML page with an id for each bibliographical entry.

                                                          If encoding in TEI, the bibliography should comprise a structured list either of bibl elements (recommended) or biblStruct elements (probably overkill for most projects, but see second example below). An xml:id on each item will allow referencing or linking from the localized bibliographic citations in individual texts.

                                                          <listBibl>
                                                           <bibl xml:id="applebaum1979">
                                                            <author>Shimon <surname>Applebaum</surname>
                                                            </author>,
                                                           <date>1979</date>, <title level="m">Jews and Greeks in Ancient
                                                               Cyrene</title>, <pubPlace>Leuven</pubPlace>.</bibl>
                                                           <bibl xml:id="jmr1971a">
                                                            <author>Joyce M. <surname>Reynolds</surname>
                                                            </author>,
                                                           <date>1971</date>, <title level="a">Zawiet Msus</title>, <title level="j">Libya Antiqua</title>
                                                            <biblScope unit="issue">8</biblScope>, <biblScope unit="page">39-42</biblScope>
                                                           </bibl>
                                                          </listBibl>
                                                          <listBibl>
                                                           <biblStruct xml:id="b0290">
                                                            <analytic>
                                                             <author>
                                                              <surname>Feissel</surname>
                                                              <forename>D.</forename>
                                                             </author>
                                                             <title level="a">Inscriptions byzantines de Ténos</title>
                                                            </analytic>
                                                            <monogr>
                                                             <title level="j">BCH</title>
                                                             <imprint>
                                                              <date>1980</date>
                                                             </imprint>
                                                             <biblScope unit="issue">104</biblScope>
                                                             <biblScope unit="page">477-518</biblScope>
                                                            </monogr>
                                                           </biblStruct>
                                                          </listBibl>

                                                          Master bibliography in Zotero

                                                          You may want to maintain your bibliography in a Zotero group library or into your personal Zotero library and use that for your EpiDoc project.

                                                          You can export a master bibliography in TEI from Zotero to work following the guidelines above.

                                                          You can also use directly the Zotero API to print your bibliography using the example Stylesheets.

                                                          To do the latter you will need to

                                                          1. Enter data correctly in Zotero
                                                          2. Enter citations in your file (see below)
                                                          3. Compile the bibliography and style the citations with the a CLS Style (it is very wise to use the available ones, but you can still create your own)

                                                          To use this feature of the Example Stylesheets you will have to select a value for the parameter bibliography.

                                                          • none: (default), applies any other locally specified templates and does neither of the following
                                                          • localTEI: the path to the TEI xml bibliography file needs to be given in the parameter localBibl, with a relative path from the xslt (default location, the parent directory of the xslt). This will look up for each bibl the value given in any ptr/@target and print author or editor and date from the TEI bibliography
                                                          • zotero: selecting this will use the example stylesheets to call the Zotero API. There are a series of other parameters which need to be set
                                                            • parameter ZoteroUorG : which selects if the target library in zotero is a group library (default) or a user library
                                                            • parameter ZoteroKey : which gives the key to the library (for the time being it defaults on the EAGLE group bibliography)
                                                            • parameter ZoteroNS : specifies a namespace, if tags in the Zotero library use any (default on nothing)
                                                            • parameter ZoteroStyle : specifies the Zotero Style to be used for the output (defaults on the chicago-author-date, as I think Zotero does anyway)

                                                          The assumptions here are that you have an accessible and open library in Zotero, and that you have assigned a tag to each record you want to use, perhaps with a prefix, in case the same bibliography is used by several projects.

                                                          Given the defaults above, if nothing but bibliography=zotero is specified, the transformation will then look into the EAGLE group library for items with tags equal to the ones given in each ptr with target of each bibl and will return bibl elements present in a <div[@type='bibliography']> as full citations, whereas it will print a formatted citation for the other bibl, wherever they occur. The tag assigned in Zotero MUST be uniquely assigned in the library.

                                                          This is testable using the parameter edn-structure=eagle parameter.

                                                          The following example, adapted from the Beta Maṣāḥǝft project, shows the encoding using bibl and a ptr with target equal to the Zotero tag, in two different contexts, the bibliography and a citation in the edition. The following explanation will clarify the settings and the output.

                                                          <div type="edition">
                                                           <bibl>
                                                            <ptr target="RIE1"/>
                                                            <citedRange unit="page">279-280</citedRange>
                                                           </bibl>
                                                          </div>
                                                          <div type="bibliography">
                                                           <bibl>
                                                            <ptr target="RIE1"/>
                                                           </bibl>
                                                          </div>

                                                          The project uses a Group library in Zotero, so ZoteroUorG=group has been left to the default value, ZoteroKey has been set to the group key 358366 of the EthioStudies group.

                                                          This Group Library is use by several projects, so the ZoteroNS parameter has been set to that used by this project, bm:. One could haveThe project has also its own style, and therefore the ZoteroStyle parameter has been set to hiob-ludolf-centre-for-ethiopian-studies, the short name of the style saved in the CSL repository.

                                                          Full guidelines used by this project for the data entry in the bibliography and for the style specification can be seen here Zotero HLCES bibliography workflow.

                                                          This transformation will thus call for each entry the Zotero API for the record with the zotero tag bm:RIE1 and print for the first bibl Bernard et al. 1991, 279-280, for the second "RIE I. Bernard, É., A.J. Drewes, and R. Schneider 1991. Recueil des Inscriptions de l’Éthiopie des périodes pré-axoumite et axoumite, Introduction de Fr. Anfray, I: Les documents (Paris: Diffusion de Boccard, 1991)."

                                                          Bibliographic citations

                                                          Individual texts will often contain multiple bibliographic citations, for example to works cited in commentary, the source of translations or photographs, and most importantly, to previous publications of the same text by other scholars. Within an EpiDoc edition, such citations should be contained in the <div type="bibliography">, either in an unstructured p (if the bibliography is a paragraph of free text with connecting prose such as, "First published in ..., from notebooks; reprinted in ...; whence ... . Later re-edited from autopsy by..." etc.) or in a listBibl if the citations are a simple (or numbered) list.

                                                          Some projects prefer to create multiple <div type="bibliography"> sections for each text in order to group bibliographic citations thematically (e.g., primary editions, prior editions, derivative editions, translations, available illustrations, and the like. The subtype may be used to distinguish between them and to facilitate processing. In particular, lists of images published on-line or in print by third parties are sometimes encoded within <div type="bibliography" subtype="illustrations">, regarding which see further Images, figures, and facsimile.

                                                          An alternative to creating multiple <div>s as described above, it is also possible to use the type attribute on a <bibl> element to indicate the nature of the source. Suggested values are:

                                                          • principalEdition or editioPrinceps
                                                          • secondary (secondary source)
                                                          • edition (any edition other than princeps)
                                                          • ancientEdition
                                                          • modernEdition
                                                          • citation (text or object is cited in the source)
                                                          • corrections
                                                          • illustrations
                                                          • otherPublications
                                                          • translation

                                                          Each bibliographic citation may be encoded relatively simply in a bibl element in the form that is desired in the online (or print) edition, be that a full bibliographic reference or abbreviated author + date or similar. It is often useful, however, to link back to the entry in a bibliographic authority (generally the master bibliography), for example so that:

                                                          1. edition can hyperlink back from short title to a full or even annotated bibliography;
                                                          2. bibliographic citations (full or short) can be automatically generated from the main bibliography, providing more consistency and reducing the need for multiple entry of identical information;
                                                          3. a bibliographic concordance can be generated (using the idno of the current edition, the xml:id of the bibliographic item, and the citedRange of the bibliographic citation in the edition.

                                                          Assuming a master bibliography in TEI containing the entries from the first example above, the bibliographic citation below would (a) point to the Reynolds 1971 title therein, and (b) state unambiguously that the text in whose edition this citation appears was previously published as number 3 in her edition.

                                                          <bibl>
                                                           <ptr target="biblio.xml#jmr1971a"/>
                                                           <citedRange>3</citedRange>
                                                          </bibl>

                                                          This would allow, firstly, the edition to display text such as ‘Reynolds 1971, 3’ or ‘Reynolds, 'Zawiet Msus' (1971), no. 3’ or similar; and secondly a bibliographic concordance to be generated that lists all of the inscriptions in each previous publication, showing which inscription in the current collection corresponds to each. (See for example the InsAph concordance for a Reynolds article.)

                                                          The following example, adapted from the Ancient Inscriptions of the Northern Black Sea (IOSPE), demonstrates the use of a single <div type="bibliography"> with two internal bibliographic lists of editions, one for each of two texts on the one support. Note the use of ptr to refer to bibliographic items in an external bibliographic list, as described above.

                                                          <div type="bibliography">
                                                           <listBibl n="1corresp="#text-1">
                                                            <bibl n="L1">
                                                          <!-- Сборник -->
                                                             <ptr target="bib:b0132"/>, 70, № <citedRange>64</citedRange>
                                                            </bibl>
                                                            <bibl n="2">
                                                          <!-- Латышев 1898a -->
                                                             <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                                            </bibl>
                                                           </listBibl>
                                                           <listBibl n="2corresp="#text-2">
                                                            <bibl n="L1">
                                                          <!-- Латышев 1898a -->
                                                             <ptr target="bib:b0134"/>, 232, № <citedRange>64</citedRange>
                                                            </bibl>
                                                           </listBibl>
                                                          </div>

                                                          This example, adapted from the Corpus of the Inscriptions of Campā, demonstrates the use of two, subtyped <div type="bibliography"> sections, one listing previous editions of the text and the other listing other secondary work on the text. It also demonstrates the use of a prose bibliographic description, rather than a simple list, in order to provide users with information about the relationship between cited editions.

                                                          <div type="bibliographysubtype="edition">
                                                           <ab>A summary of this inscription was presented in <bibl>
                                                             <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                                            </bibl>. The present edition and translation after
                                                           <bibl>
                                                             <ptr target="cic-bibl:ECIC-III"/>: <citedRange unit="item">464</citedRange>
                                                            </bibl>.</ab>
                                                          </div>
                                                          <div type="bibliography"
                                                           subtype="secondary">

                                                           <listBibl>
                                                            <bibl>
                                                             <ptr target="cic-bibl:chronique-1931"/>: <citedRange unit="item">324</citedRange>
                                                            </bibl>
                                                            <bibl>
                                                             <ptr target="cic-bibl:schweyer-2005a"/>: <citedRange unit="item">106</citedRange>.</bibl>
                                                           </listBibl>
                                                          </div>

                                                          Customization of biblScope unit attribute

                                                          The TEI allows bibliographical references in bibl or biblStruct elements to be constrained to one or more subdivisions using the unit attribute. A number of recommended values are provided (e.g., chapter, volume). An additional set of values common to epigraphical publications supplements the TEI list. N.B., this list merely represents an open list of suggested values. While you are not obligated to use these values, or, in fact, any value at all, consistent application of unit attributes should be considered a best practice.

                                                          See also:

                                                          Other pages describing <listBibl>:

                                                            Other pages describing <bibl>:

                                                            Other pages describing <biblStruct>:

                                                              Other pages describing <biblScope>:

                                                                Other pages describing <citedRange>:

                                                                  Responsibility for this section

                                                                  1. Gabriel Bodard, author
                                                                  2. Pietro Liuzzo, Author
                                                                  3. Scott Vanderbilt, Author

                                                                  EpiDoc version: post-9.5

                                                                  Date: 2024-03-05

                                                                  \ No newline at end of file diff --git a/gl/dev/supp-commentary-pt-br.html b/gl/dev/supp-commentary-pt-br.html index f8d84d58a..cdc81a902 100644 --- a/gl/dev/supp-commentary-pt-br.html +++ b/gl/dev/supp-commentary-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                  Comentário

                                                                  2023-04-27

                                                                  gloss

                                                                  Elemento relevante de documentação:

                                                                  • TEI definition: div ; EpiDoc-specific - customization: div

                                                                  Responsabilidade por esta seção

                                                                  1. xx, autor
                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                  EpiDoc version: post-9.5

                                                                  Date: 2023-04-27

                                                                  \ No newline at end of file +

                                                                  Comentário

                                                                  2024-03-05

                                                                  gloss

                                                                  Elemento relevante de documentação:

                                                                  • TEI definition: div ; EpiDoc-specific + customization: div

                                                                  Responsabilidade por esta seção

                                                                  1. xx, autor
                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                  EpiDoc version: post-9.5

                                                                  Date: 2024-03-05

                                                                  \ No newline at end of file diff --git a/gl/dev/supp-commentary.html b/gl/dev/supp-commentary.html index 652a5d6b1..8c9508394 100644 --- a/gl/dev/supp-commentary.html +++ b/gl/dev/supp-commentary.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                  Commentary

                                                                  2023-04-27

                                                                  gloss

                                                                  Relevant element documentation:

                                                                  • TEI definition: div ; EpiDoc-specific - customization: div

                                                                  Responsibility for this section

                                                                  1. xx, author

                                                                  EpiDoc version: post-9.5

                                                                  Date: 2023-04-27

                                                                  \ No newline at end of file +

                                                                  Commentary

                                                                  2024-03-05

                                                                  gloss

                                                                  Relevant element documentation:

                                                                  • TEI definition: div ; EpiDoc-specific + customization: div

                                                                  Responsibility for this section

                                                                  1. xx, author

                                                                  EpiDoc version: post-9.5

                                                                  Date: 2024-03-05

                                                                  \ No newline at end of file diff --git a/gl/dev/supp-descdecor-pt-br.html b/gl/dev/supp-descdecor-pt-br.html index f021aa506..22d70f1a1 100644 --- a/gl/dev/supp-descdecor-pt-br.html +++ b/gl/dev/supp-descdecor-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                  Descrição de decoração ou iconografia

                                                                  2023-04-27

                                                                  Elemento relevante de documentação:

                                                                  • TEI definition: decoDesc ; EpiDoc-specific +

                                                                    Descrição de decoração ou iconografia

                                                                    2024-03-05

                                                                    Elemento relevante de documentação:

                                                                    • TEI definition: decoDesc ; EpiDoc-specific customization: decoDesc
                                                                    • TEI definition: decoNote ; EpiDoc-specific customization: decoNote
                                                                    • TEI definition: rs ; EpiDoc-specific - customization: rs

                                                                    Iconografia, elementos decorativos ou outras imagens no suporte (ou ao longo do texto), podem ser descritos em prosa como parte da descrição do objeto e/ou do campus de texto, ou podem ser codificados em sua própruia seção usando os elementos decoDesc e decoNote. No primeiro caso, alguns projetos usaram rs com type como "decoração" para marcar palavras chave dentro da descrição, para indexação.

                                                                    <decoDesc>
                                                                     <decoNote>Egg and dart moulding along the top of the block.</decoNote>
                                                                    </decoDesc>
                                                                    <support> White marble sarcophagus with columnar <rs type="decoration">arcade</rs>
                                                                    design. </support>
                                                                    (InsAph: 11.35)

                                                                    You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                    See also:

                                                                    Other pages describing <decoDesc>:

                                                                      Other pages describing <decoNote>:

                                                                        Other pages describing <rs>:

                                                                        Responsabilidade por esta seção

                                                                        1. Gabriel Bodard, autor
                                                                        2. Assunção Medeiros, traduzido para o Português por

                                                                        EpiDoc version: post-9.5

                                                                        Date: 2023-04-27

                                                                        \ No newline at end of file + customization: rs

                                                                      Iconografia, elementos decorativos ou outras imagens no suporte (ou ao longo do texto), podem ser descritos em prosa como parte da descrição do objeto e/ou do campus de texto, ou podem ser codificados em sua própruia seção usando os elementos decoDesc e decoNote. No primeiro caso, alguns projetos usaram rs com type como "decoração" para marcar palavras chave dentro da descrição, para indexação.

                                                                      <decoDesc>
                                                                       <decoNote>Egg and dart moulding along the top of the block.</decoNote>
                                                                      </decoDesc>
                                                                      <support> White marble sarcophagus with columnar <rs type="decoration">arcade</rs>
                                                                      design. </support>
                                                                      (InsAph: 11.35)

                                                                      You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                      See also:

                                                                      Other pages describing <decoDesc>:

                                                                        Other pages describing <decoNote>:

                                                                          Other pages describing <rs>:

                                                                          Responsabilidade por esta seção

                                                                          1. Gabriel Bodard, autor
                                                                          2. Assunção Medeiros, traduzido para o Português por

                                                                          EpiDoc version: post-9.5

                                                                          Date: 2024-03-05

                                                                          \ No newline at end of file diff --git a/gl/dev/supp-descdecor.html b/gl/dev/supp-descdecor.html index d91ebdf93..dd66b1acb 100644 --- a/gl/dev/supp-descdecor.html +++ b/gl/dev/supp-descdecor.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                          Description of decoration or iconography

                                                                          2023-04-27

                                                                          Relevant element documentation:

                                                                          Iconography, decorative features or other imagery on the support or alongside the text may be described in prose as part of the description of object and/or text campus, or may be encoded in its own section using the decoDesc and decoNote elements. In the former case, some projects have used an rs with type of "decoration" to tag keywords within the description for indexing.

                                                                          <decoDesc>
                                                                           <decoNote>Egg and dart moulding along the top of the block.</decoNote>
                                                                          </decoDesc>
                                                                          <support> White marble sarcophagus with columnar <rs type="decoration">arcade</rs>
                                                                          design. </support>
                                                                          (InsAph: 11.35)

                                                                          You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                          Responsibility for this section

                                                                          1. Gabriel Bodard, author

                                                                          EpiDoc version: post-9.5

                                                                          Date: 2024-03-05

                                                                          \ No newline at end of file diff --git a/gl/dev/supp-descdimensions-pt-br.html b/gl/dev/supp-descdimensions-pt-br.html index 8f11e40cd..163556ee9 100644 --- a/gl/dev/supp-descdimensions-pt-br.html +++ b/gl/dev/supp-descdimensions-pt-br.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                          Dimensões do objeto ou campus

                                                                          2023-04-27

                                                                          O elemento dimensions e suas tags internas, geralmente colocados dentro de support ou layout, podem ser usados para registrar as dimensões, em qualquer unidade apropriada, do monumento, do suporte, do fragmento, campo de texto ou objeto sendo descrito.

                                                                          Elemento relevante de documentação:

                                                                          • TEI definition: dimensions ; EpiDoc-specific +

                                                                            Dimensões do objeto ou campus

                                                                            2024-03-05

                                                                            O elemento dimensions e suas tags internas, geralmente colocados dentro de support ou layout, podem ser usados para registrar as dimensões, em qualquer unidade apropriada, do monumento, do suporte, do fragmento, campo de texto ou objeto sendo descrito.

                                                                            Elemento relevante de documentação:

                                                                            • TEI definition: dimensions ; EpiDoc-specific customization: dimensions
                                                                            • TEI definition: height ; EpiDoc-specific customization: height
                                                                            • TEI definition: width ; EpiDoc-specific customization: width
                                                                            • TEI definition: depth ; EpiDoc-specific customization: depth
                                                                            • TEI definition: dim ; EpiDoc-specific - customization: dim

                                                                            O uso mais comum de dimensões em uma edição epigráfica ou papirológica é registrar (a) as dimensões do objeto portador de texto, geralmente dando a altura, largura e profundidade/espessura ou (b) as dimensões do campo de texto, geralmente dando apenas altura e largura. Para esta informação o elemento TEI dimensions deve ser usado; este elemento deve conter apenas os elementos individuais height, width e depth (ou, para dimensões diferentes das três lineares, dim, que pode receber um type com valores como "diameter", "arc", etc.).

                                                                            Se há desejo de normatização, o atributo quantity em cada dimensão pode ser utlizado para conter uma expressão de valor matemático (fração expressa como decimal, ou polegadas expressas no sistema métrico, por exemplo). Dimensões aproximadas (muitas vezes descritas com "circa", "c." ou "ca." quando impressas) devem receber a marcação do atributo precision="low". Dimensões que variam dentro do objeto (como uma coluna que tem maior largura na base que no topo), devem receber os atributos min e max em vez de quantity.

                                                                            Se precision for utilizado em conjunto com os atributos min e max, fica entendido que a baixa precisão se refere aos dois valores. Para expressões mais complicadas, o elemento precision pode ser usado para fazer declarações diferentes de precisão sobre cada um dos atributos.

                                                                            <dimensions unit="cm">
                                                                             <height>196</height>
                                                                             <width>71</width>
                                                                             <depth precision="low">17</depth>
                                                                            </dimensions>
                                                                            <support> Colonnette of marble, spirally fluted and tapering to a point (<dimensions>
                                                                              <dim unit="metremin="0.24max="0.11"
                                                                               type="diameter">
                                                                            0.24-0.11</dim>
                                                                              <height unit="metrequantity="0.55">0.55</height>
                                                                             </dimensions>). </support>
                                                                            <handNote> Letter heights: <height min="0.01max="0.015">0.01 - c. 0.015</height>
                                                                             <precision match="preceding::height/@min"
                                                                              precision="high"/>

                                                                             <precision match="preceding::height/@max"
                                                                              precision="low"/>

                                                                            </handNote>

                                                                            See also:

                                                                            Other pages describing <dimensions>:

                                                                            Other pages describing <height>:

                                                                            Other pages describing <width>:

                                                                              Other pages describing <depth>:

                                                                                Other pages describing <dim>:

                                                                                  Responsabilidade por esta seção

                                                                                  1. Gabriel Bodard, autor
                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                  EpiDoc version: post-9.5

                                                                                  Date: 2023-04-27

                                                                                  \ No newline at end of file + customization: dim

                                                                                O uso mais comum de dimensões em uma edição epigráfica ou papirológica é registrar (a) as dimensões do objeto portador de texto, geralmente dando a altura, largura e profundidade/espessura ou (b) as dimensões do campo de texto, geralmente dando apenas altura e largura. Para esta informação o elemento TEI dimensions deve ser usado; este elemento deve conter apenas os elementos individuais height, width e depth (ou, para dimensões diferentes das três lineares, dim, que pode receber um type com valores como "diameter", "arc", etc.).

                                                                                Se há desejo de normatização, o atributo quantity em cada dimensão pode ser utlizado para conter uma expressão de valor matemático (fração expressa como decimal, ou polegadas expressas no sistema métrico, por exemplo). Dimensões aproximadas (muitas vezes descritas com "circa", "c." ou "ca." quando impressas) devem receber a marcação do atributo precision="low". Dimensões que variam dentro do objeto (como uma coluna que tem maior largura na base que no topo), devem receber os atributos min e max em vez de quantity.

                                                                                Se precision for utilizado em conjunto com os atributos min e max, fica entendido que a baixa precisão se refere aos dois valores. Para expressões mais complicadas, o elemento precision pode ser usado para fazer declarações diferentes de precisão sobre cada um dos atributos.

                                                                                <dimensions unit="cm">
                                                                                 <height>196</height>
                                                                                 <width>71</width>
                                                                                 <depth precision="low">17</depth>
                                                                                </dimensions>
                                                                                <support> Colonnette of marble, spirally fluted and tapering to a point (<dimensions>
                                                                                  <dim unit="metremin="0.24max="0.11"
                                                                                   type="diameter">
                                                                                0.24-0.11</dim>
                                                                                  <height unit="metrequantity="0.55">0.55</height>
                                                                                 </dimensions>). </support>
                                                                                <handNote> Letter heights: <height min="0.01max="0.015">0.01 - c. 0.015</height>
                                                                                 <precision match="preceding::height/@min"
                                                                                  precision="high"/>

                                                                                 <precision match="preceding::height/@max"
                                                                                  precision="low"/>

                                                                                </handNote>

                                                                                See also:

                                                                                Other pages describing <dimensions>:

                                                                                Other pages describing <height>:

                                                                                Other pages describing <width>:

                                                                                  Other pages describing <depth>:

                                                                                    Other pages describing <dim>:

                                                                                      Responsabilidade por esta seção

                                                                                      1. Gabriel Bodard, autor
                                                                                      2. Assunção Medeiros, traduzido para o Português por

                                                                                      EpiDoc version: post-9.5

                                                                                      Date: 2024-03-05

                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-descdimensions.html b/gl/dev/supp-descdimensions.html index 9f3439f72..cbd8c48ec 100644 --- a/gl/dev/supp-descdimensions.html +++ b/gl/dev/supp-descdimensions.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                      Dimensions of object or campus

                                                                                      2023-04-27

                                                                                      The dimensions element, generally placed within the support or layout or their descendents, may be used to record the dimensions, in any appropriate unit, of the monument, support, fragment, text field, or other aspect of the text or object being described.

                                                                                      Relevant element documentation:

                                                                                      • TEI definition: dimensions ; EpiDoc-specific +

                                                                                        Dimensions of object or campus

                                                                                        2024-03-05

                                                                                        The dimensions element, generally placed within the support or layout or their descendents, may be used to record the dimensions, in any appropriate unit, of the monument, support, fragment, text field, or other aspect of the text or object being described.

                                                                                        Relevant element documentation:

                                                                                        • TEI definition: dimensions ; EpiDoc-specific customization: dimensions
                                                                                        • TEI definition: height ; EpiDoc-specific customization: height
                                                                                        • TEI definition: width ; EpiDoc-specific customization: width
                                                                                        • TEI definition: depth ; EpiDoc-specific customization: depth
                                                                                        • TEI definition: dim ; EpiDoc-specific - customization: dim

                                                                                        The most common uses for dimensions in an epigraphic/papyrological edition are to record (a) the dimensions of the text-bearing object, usually giving height, width and depth/thickness, or (b) those of the text field, usually giving only height and width. For these the TEI element dimensions should be used; this element must contain only the individual elements height, width and depth (or, for dimensions other than the three linear ones, dim, which may take an type such as "diameter", "arc", etc.).

                                                                                        If normalization is desired, the quantity attribute on each dimension may be used to contain a mathematically actionable expression of the value (fraction expressed as decimal, or inches expressed as metric, for example). Approximate dimensions (often indicated "circa", "c." or "ca." in print) should be tagged with the attribute precision="low". Dimensions that vary across the object (e.g. a tapering column wider at the base than at the top), should be given min and max attributes, rather than quantity.

                                                                                        If precision is used in combination with min and max, the low precision is understood to refer to both these values. For more complicated expressions, the precision element may be used to make different precision statements about each of these attributes.

                                                                                        <dimensions unit="cm">
                                                                                         <height>196</height>
                                                                                         <width>71</width>
                                                                                         <depth precision="low">17</depth>
                                                                                        </dimensions>
                                                                                        <support> Colonnette of marble, spirally fluted and tapering to a point
                                                                                        (<dimensions>
                                                                                          <dim unit="metremin="0.24max="0.11"
                                                                                           type="diameter">
                                                                                        0.24-0.11</dim>
                                                                                          <height unit="metrequantity="0.55">0.55</height>
                                                                                         </dimensions>).
                                                                                        </support>
                                                                                        <handNote> Letter heights:
                                                                                        <height min="0.01max="0.015">0.01 - c. 0.015</height>
                                                                                         <precision match="preceding::height/@min"
                                                                                          precision="high"/>

                                                                                         <precision match="preceding::height/@max"
                                                                                          precision="low"/>

                                                                                        </handNote>

                                                                                        See also:

                                                                                        Other pages describing <dimensions>:

                                                                                        Other pages describing <height>:

                                                                                        Other pages describing <width>:

                                                                                          Other pages describing <depth>:

                                                                                            Other pages describing <dim>:

                                                                                              Responsibility for this section

                                                                                              1. Gabriel Bodard, author

                                                                                              EpiDoc version: post-9.5

                                                                                              Date: 2023-04-27

                                                                                              \ No newline at end of file + customization: dim

                                                                                            The most common uses for dimensions in an epigraphic/papyrological edition are to record (a) the dimensions of the text-bearing object, usually giving height, width and depth/thickness, or (b) those of the text field, usually giving only height and width. For these the TEI element dimensions should be used; this element must contain only the individual elements height, width and depth (or, for dimensions other than the three linear ones, dim, which may take an type such as "diameter", "arc", etc.).

                                                                                            If normalization is desired, the quantity attribute on each dimension may be used to contain a mathematically actionable expression of the value (fraction expressed as decimal, or inches expressed as metric, for example). Approximate dimensions (often indicated "circa", "c." or "ca." in print) should be tagged with the attribute precision="low". Dimensions that vary across the object (e.g. a tapering column wider at the base than at the top), should be given min and max attributes, rather than quantity.

                                                                                            If precision is used in combination with min and max, the low precision is understood to refer to both these values. For more complicated expressions, the precision element may be used to make different precision statements about each of these attributes.

                                                                                            <dimensions unit="cm">
                                                                                             <height>196</height>
                                                                                             <width>71</width>
                                                                                             <depth precision="low">17</depth>
                                                                                            </dimensions>
                                                                                            <support> Colonnette of marble, spirally fluted and tapering to a point
                                                                                            (<dimensions>
                                                                                              <dim unit="metremin="0.24max="0.11"
                                                                                               type="diameter">
                                                                                            0.24-0.11</dim>
                                                                                              <height unit="metrequantity="0.55">0.55</height>
                                                                                             </dimensions>).
                                                                                            </support>
                                                                                            <handNote> Letter heights:
                                                                                            <height min="0.01max="0.015">0.01 - c. 0.015</height>
                                                                                             <precision match="preceding::height/@min"
                                                                                              precision="high"/>

                                                                                             <precision match="preceding::height/@max"
                                                                                              precision="low"/>

                                                                                            </handNote>

                                                                                            See also:

                                                                                            Other pages describing <dimensions>:

                                                                                            Other pages describing <height>:

                                                                                            Other pages describing <width>:

                                                                                              Other pages describing <depth>:

                                                                                                Other pages describing <dim>:

                                                                                                  Responsibility for this section

                                                                                                  1. Gabriel Bodard, author

                                                                                                  EpiDoc version: post-9.5

                                                                                                  Date: 2024-03-05

                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-descletters-pt-br.html b/gl/dev/supp-descletters-pt-br.html index 00370c431..8fed99ca2 100644 --- a/gl/dev/supp-descletters-pt-br.html +++ b/gl/dev/supp-descletters-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                  Descrição de mãos e de letras

                                                                                                  2023-04-27

                                                                                                  Informações descritivas sobre mãos, paleografia ou estilos de escrita usados no texto devem ser codificadas dentro de uma seção handDesc do header do documento.

                                                                                                  Elemento relevante de documentação:

                                                                                                  A descrição de mão(s) pode incluir informação sobre formas de letra e alturas (ou outras dimensões, como altura de linha), características paleográficas que incluem datação, ligaduras, marcas de abreviatura, caracteres incomuns e outros símbolos ou característica textuais. No todo, só as alturas de letra recebem marcação nesta seção (com height), apesar da datação também, em teoria, poder ser marcada (se for diferente da informação registrada em origDate).

                                                                                                  Ligaduras, apesar de algumas vezes listadas manualmente aqui, podem ser melhor capturadas com a marcação no texto transcrito como hi com rend com valor "ligature", gerando mecanicamente uma lista de instâncias de saída. Veja também Ligaduras.

                                                                                                  Se múltiplas mãos são descritas, cada uma deve receber, separadamente, um handNote, cada um recebendo um n (correspondente a uma seção numerada no texto transcrito), ou um xml:id que pode apontar para um elemento handShift na transcrição. Veja também Mudança de mão ou escriba.

                                                                                                  Veja também Dimensões para maiores informações de marcação de dimensões de objeto, campus ou letra.

                                                                                                  <handDesc>
                                                                                                   <handNote>
                                                                                                    <height unit="metre">0.015</height>; lunate sigma and epsilon; ligatured ΜΝ in
                                                                                                     l. 3. </handNote>
                                                                                                  </handDesc>

                                                                                                  Responsabilidade por esta seção

                                                                                                  1. Gabriel Bodard, autor
                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                  EpiDoc version: post-9.5

                                                                                                  Date: 2024-03-05

                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-descletters.html b/gl/dev/supp-descletters.html index dc07527dd..28ae6fdff 100644 --- a/gl/dev/supp-descletters.html +++ b/gl/dev/supp-descletters.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                  Description of hands and letters

                                                                                                  2023-04-27

                                                                                                  Descriptive information about the hands, palaeography or writing styles used in the text should be encoded within the handDesc section of the document header.

                                                                                                  Relevant element documentation:

                                                                                                  The description of hand(s) may include information on letterforms and heights (or other dimensions, such as line-heights), palaeographic features including dating, ligatures, abbreviation marks, unusual characters and other symbols or textual features. On the whole only letterheights are tagged in this section (with height), although dating may also be marked in principle (if it is different from the information recorded in origDate).

                                                                                                  Ligatures, while sometimes listed here manually, may be better captured by tagging in the transcribed text as hi with rend of "ligature" and mechanically generating a list of instances in the output. See also Ligatures.

                                                                                                  If multiple hands are described, each should be given a separate handNote, each bearing either an n (corresponding to a numbered section in the transcribed text), or an xml:id to which a handShift element in the transcription may point. See also Change of hand or scribe.

                                                                                                  See also Dimensions for more information on tagging object, campus or letter dimensions.

                                                                                                  <handDesc>
                                                                                                   <handNote>
                                                                                                    <height unit="metre">0.015</height>; lunate sigma and epsilon; ligatured ΜΝ in l. 3.
                                                                                                   </handNote>
                                                                                                  </handDesc>

                                                                                                  Responsibility for this section

                                                                                                  1. Gabriel Bodard, author

                                                                                                  EpiDoc version: post-9.5

                                                                                                  Date: 2024-03-05

                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-descobject-pt-br.html b/gl/dev/supp-descobject-pt-br.html index 6adb0bbe5..0bc14268a 100644 --- a/gl/dev/supp-descobject-pt-br.html +++ b/gl/dev/supp-descobject-pt-br.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                  Descrição de objeto ou suporte

                                                                                                  2023-04-27

                                                                                                  A descrição física de um objeto portador de texto (o suporte) é codificada no elemento supportDesc.

                                                                                                  Elemento relevante de documentação:

                                                                                                  • TEI definition: supportDesc ; EpiDoc-specific +

                                                                                                    Descrição de objeto ou suporte

                                                                                                    2024-03-05

                                                                                                    A descrição física de um objeto portador de texto (o suporte) é codificada no elemento supportDesc.

                                                                                                    Elemento relevante de documentação:

                                                                                                    Apesar da TEI apresentar uma variedade de elementos dentro de supportDesc a maioria dos projetos EpiDoc até hoje só sentiu necessidade de fazer uso de um deles: support. Dentro do elemento support existem duas maneiras diferentes de se estruturar informação relevante.

                                                                                                    Na primeira maneira, produz-se um ou mais parágrafos de prosa descritiva (envoltos em elementos p como é apropriado). Dentro desta prosa, certas classes de informação recebem marcação especial, incluindo o material de que é feito, o tipo de objeto e suas dimensões (usando os elementos material, objectType e dimensions). Referência à bibliografia, quando apropriado, pode também ser feita da forma padrão (isto é, bibl).

                                                                                                    Na segunda maneira -- especialmente útil quando dados são importados ou preparados para exportação para um banco de dados ou outro schema -- os elementos especializados material, objectType, e dimensions são produzidos sequencialmente dentro de support sem nenhum texto à volta ou ligado a eles. A estes se segue, então, um ou mais parágrafos de prosa descritiva, como desejado.

                                                                                                    Veja também Dimensões para maiores informações sobre marcação de dimensões de objeto, campus ou letra.

                                                                                                    <support>
                                                                                                     <p>The greater part of a moulded <material>marble</material>
                                                                                                      <objectType>base</objectType>, recomposed from four pieces (together,
                                                                                                     <dimensions unit="metre">
                                                                                                       <width>0.62</width>
                                                                                                       <height>0.33</height>
                                                                                                       <depth precision="low">0.34</depth>
                                                                                                      </dimensions>).</p>
                                                                                                    </support>
                                                                                                    <support>
                                                                                                     <objectType>Quadra</objectType>
                                                                                                     <material>Limestone</material>
                                                                                                     <p>Broken off on the left, chipped along the edges.</p>
                                                                                                     <dimensions unit="cm">
                                                                                                      <height>25,0</height>
                                                                                                      <width>36,0</width>
                                                                                                      <depth>17,0</depth>
                                                                                                     </dimensions>
                                                                                                    </support>

                                                                                                    Você pode alinhar suas definições, ligando-as a um Vocabulário Controlado local ou externo.

                                                                                                    See also:

                                                                                                    Other pages describing <supportDesc>:

                                                                                                      Other pages describing <support>:

                                                                                                        Other pages describing <material>:

                                                                                                          Other pages describing <objectType>:

                                                                                                            Other pages describing <dimensions>:

                                                                                                            Responsabilidade por esta seção

                                                                                                            1. Tom Elliott, autor
                                                                                                            2. Gabriel Bodard, autor
                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                            EpiDoc version: post-9.5

                                                                                                            Date: 2023-04-27

                                                                                                            \ No newline at end of file + customization: dimensions

                                                                                                          Apesar da TEI apresentar uma variedade de elementos dentro de supportDesc a maioria dos projetos EpiDoc até hoje só sentiu necessidade de fazer uso de um deles: support. Dentro do elemento support existem duas maneiras diferentes de se estruturar informação relevante.

                                                                                                          Na primeira maneira, produz-se um ou mais parágrafos de prosa descritiva (envoltos em elementos p como é apropriado). Dentro desta prosa, certas classes de informação recebem marcação especial, incluindo o material de que é feito, o tipo de objeto e suas dimensões (usando os elementos material, objectType e dimensions). Referência à bibliografia, quando apropriado, pode também ser feita da forma padrão (isto é, bibl).

                                                                                                          Na segunda maneira -- especialmente útil quando dados são importados ou preparados para exportação para um banco de dados ou outro schema -- os elementos especializados material, objectType, e dimensions são produzidos sequencialmente dentro de support sem nenhum texto à volta ou ligado a eles. A estes se segue, então, um ou mais parágrafos de prosa descritiva, como desejado.

                                                                                                          Veja também Dimensões para maiores informações sobre marcação de dimensões de objeto, campus ou letra.

                                                                                                          <support>
                                                                                                           <p>The greater part of a moulded <material>marble</material>
                                                                                                            <objectType>base</objectType>, recomposed from four pieces (together,
                                                                                                           <dimensions unit="metre">
                                                                                                             <width>0.62</width>
                                                                                                             <height>0.33</height>
                                                                                                             <depth precision="low">0.34</depth>
                                                                                                            </dimensions>).</p>
                                                                                                          </support>
                                                                                                          <support>
                                                                                                           <objectType>Quadra</objectType>
                                                                                                           <material>Limestone</material>
                                                                                                           <p>Broken off on the left, chipped along the edges.</p>
                                                                                                           <dimensions unit="cm">
                                                                                                            <height>25,0</height>
                                                                                                            <width>36,0</width>
                                                                                                            <depth>17,0</depth>
                                                                                                           </dimensions>
                                                                                                          </support>

                                                                                                          Você pode alinhar suas definições, ligando-as a um Vocabulário Controlado local ou externo.

                                                                                                          See also:

                                                                                                          Other pages describing <supportDesc>:

                                                                                                            Other pages describing <support>:

                                                                                                              Other pages describing <material>:

                                                                                                                Other pages describing <objectType>:

                                                                                                                  Other pages describing <dimensions>:

                                                                                                                  Responsabilidade por esta seção

                                                                                                                  1. Tom Elliott, autor
                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                  EpiDoc version: post-9.5

                                                                                                                  Date: 2024-03-05

                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-descobject.html b/gl/dev/supp-descobject.html index c1702d399..eee1752d2 100644 --- a/gl/dev/supp-descobject.html +++ b/gl/dev/supp-descobject.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                  Description of object or support

                                                                                                                  2023-04-27

                                                                                                                  The physical description of a text-bearing object (i.e., support) is encoded in the supportDesc element.

                                                                                                                  Relevant element documentation:

                                                                                                                  • TEI definition: supportDesc ; EpiDoc-specific +

                                                                                                                    Description of object or support

                                                                                                                    2024-03-05

                                                                                                                    The physical description of a text-bearing object (i.e., support) is encoded in the supportDesc element.

                                                                                                                    Relevant element documentation:

                                                                                                                    Although the TEI supplies a range of elements within supportDesc most EpiDoc projects to date have only found it necessary to make use of one of these: support. Within the support element, there are two different ways in which the relevant information may be structured.

                                                                                                                    In the first approach, one produces one or more paragraphs of descriptive prose (wrapped in p elements as appropriate). Within this prose, certain classes of information are specially tagged, including the material out of which it is made, the type of object it is, and its dimensions (using the material, objectType, and dimensions elements). Reference to bibliography, as appropriate, may also be made in the standard way (i.e., bibl).

                                                                                                                    In the second approach -- useful especially when data is being imported from or prepared for export to a database or other schema -- the specialized material, objectType, and dimensions elements are produced sequentially within support without any surrounding or connecting text. These may then be followed by one or more paragraphs of descriptive prose as desired.

                                                                                                                    See also Dimensions for more information on tagging object, campus or letter dimensions.

                                                                                                                    <support>
                                                                                                                     <p>The greater part of a moulded <material>marble</material>
                                                                                                                      <objectType>base</objectType>, recomposed from four pieces (together,
                                                                                                                     <dimensions unit="metre">
                                                                                                                       <width>0.62</width>
                                                                                                                       <height>0.33</height>
                                                                                                                       <depth precision="low">0.34</depth>
                                                                                                                      </dimensions>).</p>
                                                                                                                    </support>
                                                                                                                    <support>
                                                                                                                     <objectType>Quadra</objectType>
                                                                                                                     <material>Limestone</material>
                                                                                                                     <p>Broken off on the left, chipped along the edges.</p>
                                                                                                                     <dimensions unit="cm">
                                                                                                                      <height>25,0</height>
                                                                                                                      <width>36,0</width>
                                                                                                                      <depth>17,0</depth>
                                                                                                                     </dimensions>
                                                                                                                    </support>

                                                                                                                    You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                    See also:

                                                                                                                    Other pages describing <supportDesc>:

                                                                                                                      Other pages describing <support>:

                                                                                                                        Other pages describing <material>:

                                                                                                                          Other pages describing <objectType>:

                                                                                                                            Other pages describing <dimensions>:

                                                                                                                            Responsibility for this section

                                                                                                                            1. Tom Elliott, author
                                                                                                                            2. Gabriel Bodard, author

                                                                                                                            EpiDoc version: post-9.5

                                                                                                                            Date: 2023-04-27

                                                                                                                            \ No newline at end of file + customization: dimensions

                                                                                                                          Although the TEI supplies a range of elements within supportDesc most EpiDoc projects to date have only found it necessary to make use of one of these: support. Within the support element, there are two different ways in which the relevant information may be structured.

                                                                                                                          In the first approach, one produces one or more paragraphs of descriptive prose (wrapped in p elements as appropriate). Within this prose, certain classes of information are specially tagged, including the material out of which it is made, the type of object it is, and its dimensions (using the material, objectType, and dimensions elements). Reference to bibliography, as appropriate, may also be made in the standard way (i.e., bibl).

                                                                                                                          In the second approach -- useful especially when data is being imported from or prepared for export to a database or other schema -- the specialized material, objectType, and dimensions elements are produced sequentially within support without any surrounding or connecting text. These may then be followed by one or more paragraphs of descriptive prose as desired.

                                                                                                                          See also Dimensions for more information on tagging object, campus or letter dimensions.

                                                                                                                          <support>
                                                                                                                           <p>The greater part of a moulded <material>marble</material>
                                                                                                                            <objectType>base</objectType>, recomposed from four pieces (together,
                                                                                                                           <dimensions unit="metre">
                                                                                                                             <width>0.62</width>
                                                                                                                             <height>0.33</height>
                                                                                                                             <depth precision="low">0.34</depth>
                                                                                                                            </dimensions>).</p>
                                                                                                                          </support>
                                                                                                                          <support>
                                                                                                                           <objectType>Quadra</objectType>
                                                                                                                           <material>Limestone</material>
                                                                                                                           <p>Broken off on the left, chipped along the edges.</p>
                                                                                                                           <dimensions unit="cm">
                                                                                                                            <height>25,0</height>
                                                                                                                            <width>36,0</width>
                                                                                                                            <depth>17,0</depth>
                                                                                                                           </dimensions>
                                                                                                                          </support>

                                                                                                                          You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                          See also:

                                                                                                                          Other pages describing <supportDesc>:

                                                                                                                            Other pages describing <support>:

                                                                                                                              Other pages describing <material>:

                                                                                                                                Other pages describing <objectType>:

                                                                                                                                  Other pages describing <dimensions>:

                                                                                                                                  Responsibility for this section

                                                                                                                                  1. Tom Elliott, author
                                                                                                                                  2. Gabriel Bodard, author

                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                  Date: 2024-03-05

                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-description-pt-br.html b/gl/dev/supp-description-pt-br.html index 59e13c3d1..36ca84f47 100644 --- a/gl/dev/supp-description-pt-br.html +++ b/gl/dev/supp-description-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                  Descrição física

                                                                                                                                  2023-04-27

                                                                                                                                  Elemento relevante de documentação:

                                                                                                                                  A informação que descreve os aspectos físicos de uma inscrição é codificada no elemento physDesc, que é parte do teiHeader.

                                                                                                                                  As seguintes subseções destas normas tratam dos aspectos específicos desta codificação:

                                                                                                                                  Se, em vez de desmembrar a descrição de vários aspectos do suporte, o editor preferir uma passagem única e não estruturada de texto em prosa, descrevendo o objeto, o physDesc pode conter um ou mais elementos p (parágrafo) como alternativa aos (mas não em adição aos) elementos estruturados descritos nas seções linkadas acima.

                                                                                                                                  <physDesc>
                                                                                                                                   <objectDesc>
                                                                                                                                    <supportDesc>
                                                                                                                                     <support>
                                                                                                                                      <p>
                                                                                                                                       <material>Bronze</material> Sextarius</p>
                                                                                                                                     </support>
                                                                                                                                    </supportDesc>
                                                                                                                                    <layoutDesc>
                                                                                                                                     <layout>inscribed on the outside just below the rim</layout>
                                                                                                                                    </layoutDesc>
                                                                                                                                   </objectDesc>
                                                                                                                                   <handDesc>
                                                                                                                                    <handNote>Fourth-century A.D. script; <height>0.02</height>
                                                                                                                                    </handNote>
                                                                                                                                   </handDesc>
                                                                                                                                  </physDesc>

                                                                                                                                  Você pode alinhar suas definições, alinhando-as a um Vocabulário Controlado local ou externo.

                                                                                                                                  See also:

                                                                                                                                  Other pages describing <physDesc>:

                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                    1. Tom Elliott, autor
                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                    3. Simona Stoyanova, autor
                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                    Date: 2023-04-27

                                                                                                                                    \ No newline at end of file +

                                                                                                                                    Descrição física

                                                                                                                                    2024-03-05

                                                                                                                                    Elemento relevante de documentação:

                                                                                                                                    A informação que descreve os aspectos físicos de uma inscrição é codificada no elemento physDesc, que é parte do teiHeader.

                                                                                                                                    As seguintes subseções destas normas tratam dos aspectos específicos desta codificação:

                                                                                                                                    Se, em vez de desmembrar a descrição de vários aspectos do suporte, o editor preferir uma passagem única e não estruturada de texto em prosa, descrevendo o objeto, o physDesc pode conter um ou mais elementos p (parágrafo) como alternativa aos (mas não em adição aos) elementos estruturados descritos nas seções linkadas acima.

                                                                                                                                    <physDesc>
                                                                                                                                     <objectDesc>
                                                                                                                                      <supportDesc>
                                                                                                                                       <support>
                                                                                                                                        <p>
                                                                                                                                         <material>Bronze</material> Sextarius</p>
                                                                                                                                       </support>
                                                                                                                                      </supportDesc>
                                                                                                                                      <layoutDesc>
                                                                                                                                       <layout>inscribed on the outside just below the rim</layout>
                                                                                                                                      </layoutDesc>
                                                                                                                                     </objectDesc>
                                                                                                                                     <handDesc>
                                                                                                                                      <handNote>Fourth-century A.D. script; <height>0.02</height>
                                                                                                                                      </handNote>
                                                                                                                                     </handDesc>
                                                                                                                                    </physDesc>

                                                                                                                                    Você pode alinhar suas definições, alinhando-as a um Vocabulário Controlado local ou externo.

                                                                                                                                    See also:

                                                                                                                                    Other pages describing <physDesc>:

                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                      1. Tom Elliott, autor
                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                      3. Simona Stoyanova, autor
                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                      Date: 2024-03-05

                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-description.html b/gl/dev/supp-description.html index 241ae7d73..93245014e 100644 --- a/gl/dev/supp-description.html +++ b/gl/dev/supp-description.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                      Physical description

                                                                                                                                      2023-04-27

                                                                                                                                      Relevant element documentation:

                                                                                                                                      Information describing the physical aspects of an inscription is encoded in the physDesc element, which is part of the teiHeader.

                                                                                                                                      The following subsections of these guidelines address specific aspects of this encoding:

                                                                                                                                      If, rather than breaking down the description of various aspects of the support, the editor prefers a single unstructured prose passage describing the object, the physDesc may contain one or more p (paragraph) elements as an alternative to (but not in addition to) the structured elements described in the sections linked above.

                                                                                                                                      <physDesc>
                                                                                                                                       <objectDesc>
                                                                                                                                        <supportDesc>
                                                                                                                                         <support>
                                                                                                                                          <p>
                                                                                                                                           <material>Bronze</material> Sextarius</p>
                                                                                                                                         </support>
                                                                                                                                        </supportDesc>
                                                                                                                                        <layoutDesc>
                                                                                                                                         <layout>inscribed on the outside just below the rim</layout>
                                                                                                                                        </layoutDesc>
                                                                                                                                       </objectDesc>
                                                                                                                                       <handDesc>
                                                                                                                                        <handNote>Fourth-century A.D. script; <height>0.02</height>
                                                                                                                                        </handNote>
                                                                                                                                       </handDesc>
                                                                                                                                      </physDesc>

                                                                                                                                      You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                                      See also:

                                                                                                                                      Other pages describing <physDesc>:

                                                                                                                                        Responsibility for this section

                                                                                                                                        1. Tom Elliott, author
                                                                                                                                        2. Gabriel Bodard, author
                                                                                                                                        3. Simona Stoyanova, author

                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                        Date: 2023-04-27

                                                                                                                                        \ No newline at end of file +

                                                                                                                                        Physical description

                                                                                                                                        2024-03-05

                                                                                                                                        Relevant element documentation:

                                                                                                                                        Information describing the physical aspects of an inscription is encoded in the physDesc element, which is part of the teiHeader.

                                                                                                                                        The following subsections of these guidelines address specific aspects of this encoding:

                                                                                                                                        If, rather than breaking down the description of various aspects of the support, the editor prefers a single unstructured prose passage describing the object, the physDesc may contain one or more p (paragraph) elements as an alternative to (but not in addition to) the structured elements described in the sections linked above.

                                                                                                                                        <physDesc>
                                                                                                                                         <objectDesc>
                                                                                                                                          <supportDesc>
                                                                                                                                           <support>
                                                                                                                                            <p>
                                                                                                                                             <material>Bronze</material> Sextarius</p>
                                                                                                                                           </support>
                                                                                                                                          </supportDesc>
                                                                                                                                          <layoutDesc>
                                                                                                                                           <layout>inscribed on the outside just below the rim</layout>
                                                                                                                                          </layoutDesc>
                                                                                                                                         </objectDesc>
                                                                                                                                         <handDesc>
                                                                                                                                          <handNote>Fourth-century A.D. script; <height>0.02</height>
                                                                                                                                          </handNote>
                                                                                                                                         </handDesc>
                                                                                                                                        </physDesc>

                                                                                                                                        You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                                        See also:

                                                                                                                                        Other pages describing <physDesc>:

                                                                                                                                          Responsibility for this section

                                                                                                                                          1. Tom Elliott, author
                                                                                                                                          2. Gabriel Bodard, author
                                                                                                                                          3. Simona Stoyanova, author

                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                          Date: 2024-03-05

                                                                                                                                          \ No newline at end of file diff --git a/gl/dev/supp-desctext-pt-br.html b/gl/dev/supp-desctext-pt-br.html index b241ec145..f5168b351 100644 --- a/gl/dev/supp-desctext-pt-br.html +++ b/gl/dev/supp-desctext-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                          Descrição e layout de campo de texto ou campus

                                                                                                                                          2023-04-27

                                                                                                                                          A informação sobre o layout e posicionamento do texto no objeto é codificada dentro de um elemento layoutDesc na área de descrição do manuscrito.

                                                                                                                                          Elemento relevante de documentação:

                                                                                                                                          • TEI definition: layoutDesc ; EpiDoc-specific +

                                                                                                                                            Descrição e layout de campo de texto ou campus

                                                                                                                                            2024-03-05

                                                                                                                                            A informação sobre o layout e posicionamento do texto no objeto é codificada dentro de um elemento layoutDesc na área de descrição do manuscrito.

                                                                                                                                            Elemento relevante de documentação:

                                                                                                                                            A descrição do(s) campo(s) de texto ou campus de uma inscrição ou texto pode incluir características como forma e dimensões da área de texto, seu posicionamento em uma ou mais faces ou em colunas, direção e orientação do texto (confira Direção de Texto), a presença de margens, modelagem ou linhas-guia, a relação de cada texto com quaisquer decorações ou outras características físicas do objeto (um texto posicionado nos quatro cantos de uma cruz, por exemplo) ou o relacionamento de múltiplos textos entre si.

                                                                                                                                            Para manter a compatibilidade com os bancos de dados EAGLE, alguns projetos marcaram a forma de execução do texto (inscrito, arranhado, cunhado, etc.) com um rs com atributo type com valor "execution". (Veja mais em authority list: Sciptura [Google Spreadsheet] para sugestão de tipologia.)

                                                                                                                                            Veja também Dimensões para maiores informações de marcação de dimensões de objeto, campus ou letra.

                                                                                                                                            <layout>
                                                                                                                                             <rs type="executionkey="scalpro">Inscribed</rs> on the façade above the door
                                                                                                                                            within a panel (<dimensions>
                                                                                                                                              <width unit="metre">0.65</width>
                                                                                                                                              <height unit="metre">0.34</height>
                                                                                                                                             </dimensions>).
                                                                                                                                            </layout>
                                                                                                                                            <layout> i. Between the arms of the cross. ii. Above the cross. iii. Below the cross.
                                                                                                                                            </layout>

                                                                                                                                            Você pode alinhar suas definições, alinhando-as a um Vocabulário Controlado local ou externo.

                                                                                                                                            See also:

                                                                                                                                            Other pages describing <layoutDesc>:

                                                                                                                                              Other pages describing <layout>:

                                                                                                                                                Other pages describing <dimensions>:

                                                                                                                                                Other pages describing <rs>:

                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                1. Gabriel Bodard, autor
                                                                                                                                                2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                Date: 2023-04-27

                                                                                                                                                \ No newline at end of file + customization: rs

                                                                                                                                              A descrição do(s) campo(s) de texto ou campus de uma inscrição ou texto pode incluir características como forma e dimensões da área de texto, seu posicionamento em uma ou mais faces ou em colunas, direção e orientação do texto (confira Direção de Texto), a presença de margens, modelagem ou linhas-guia, a relação de cada texto com quaisquer decorações ou outras características físicas do objeto (um texto posicionado nos quatro cantos de uma cruz, por exemplo) ou o relacionamento de múltiplos textos entre si.

                                                                                                                                              Para manter a compatibilidade com os bancos de dados EAGLE, alguns projetos marcaram a forma de execução do texto (inscrito, arranhado, cunhado, etc.) com um rs com atributo type com valor "execution". (Veja mais em authority list: Sciptura [Google Spreadsheet] para sugestão de tipologia.)

                                                                                                                                              Veja também Dimensões para maiores informações de marcação de dimensões de objeto, campus ou letra.

                                                                                                                                              <layout>
                                                                                                                                               <rs type="executionkey="scalpro">Inscribed</rs> on the façade above the door
                                                                                                                                              within a panel (<dimensions>
                                                                                                                                                <width unit="metre">0.65</width>
                                                                                                                                                <height unit="metre">0.34</height>
                                                                                                                                               </dimensions>).
                                                                                                                                              </layout>
                                                                                                                                              <layout> i. Between the arms of the cross. ii. Above the cross. iii. Below the cross.
                                                                                                                                              </layout>

                                                                                                                                              Você pode alinhar suas definições, alinhando-as a um Vocabulário Controlado local ou externo.

                                                                                                                                              See also:

                                                                                                                                              Other pages describing <layoutDesc>:

                                                                                                                                                Other pages describing <layout>:

                                                                                                                                                  Other pages describing <dimensions>:

                                                                                                                                                  Other pages describing <rs>:

                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-desctext.html b/gl/dev/supp-desctext.html index 93c2cfcab..c4f7422af 100644 --- a/gl/dev/supp-desctext.html +++ b/gl/dev/supp-desctext.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                  Description and layout of text field or campus

                                                                                                                                                  2023-04-27

                                                                                                                                                  Information about the layout and placement of the text on the object is encoded within a layoutDesc element in the manuscript description area.

                                                                                                                                                  Relevant element documentation:

                                                                                                                                                  Description of the text field(s) or campus of an inscription or text may include features such as the shape and dimensions of the text area, its placement on one or more face or in columns, direction and orientation of text (although cf. Direction of Text), the presence of margins, mouldings, or guide-lines, the relationship of each text to any decoration or other physical feature of the object (a text laid out in the four corners of a cross, for example) or the relationship of multiple texts to one another.

                                                                                                                                                  For the sake of compatibility with the EAGLE databases, some projects have tagged the form of execution of the text (incised, scratched, stamped, etc.) with an rs with type of "execution". (See further the authority list: Sciptura [Google Spreadsheet] for suggested typology.)

                                                                                                                                                  See also Dimensions for more information on tagging object, campus or letter dimensions.

                                                                                                                                                  <layout>
                                                                                                                                                   <rs type="executionkey="scalpro">Inscribed</rs> on the façade above the door
                                                                                                                                                  within a panel (<dimensions>
                                                                                                                                                    <width unit="metre">0.65</width>
                                                                                                                                                    <height unit="metre">0.34</height>
                                                                                                                                                   </dimensions>).
                                                                                                                                                  </layout>
                                                                                                                                                  <layout> i. Between the arms of the cross. ii. Above the cross. iii. Below the cross.
                                                                                                                                                  </layout>

                                                                                                                                                  You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                                                  Responsibility for this section

                                                                                                                                                  1. Gabriel Bodard, author

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-desctexttype.html b/gl/dev/supp-desctexttype.html index 266fe7f99..2ed80afd7 100644 --- a/gl/dev/supp-desctexttype.html +++ b/gl/dev/supp-desctexttype.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                  Description of the text type

                                                                                                                                                  2023-04-27

                                                                                                                                                  The description of the type (or function) of the text borne by object is encoded in the textClass/keywords element.

                                                                                                                                                  Relevant element documentation:

                                                                                                                                                  • TEI definition: textClass ; EpiDoc-specific +

                                                                                                                                                    Description of the text type

                                                                                                                                                    2024-03-05

                                                                                                                                                    The description of the type (or function) of the text borne by object is encoded in the textClass/keywords element.

                                                                                                                                                    Relevant element documentation:

                                                                                                                                                    Type of text

                                                                                                                                                    Although there is no specific TEI tag for the category, type, or function of the text, EpiDoc recommends the inclusion of text type information in textClass/keywords:

                                                                                                                                                    <textClass>
                                                                                                                                                     <keywords scheme="hgv">
                                                                                                                                                      <term>Brief (privat)</term>
                                                                                                                                                     </keywords>
                                                                                                                                                    </textClass>

                                                                                                                                                    The use of ref in term for pointing to the related term in an internal authority list or external vocabulary is not required but recommended:

                                                                                                                                                    <textClass>
                                                                                                                                                     <keywords>
                                                                                                                                                      <term ref="#texttype1">Dedication</term>
                                                                                                                                                      <term ref="#texttype2">Decree</term>
                                                                                                                                                     </keywords>
                                                                                                                                                    </textClass>

                                                                                                                                                    The element content is recommended but not required:

                                                                                                                                                    <textClass>
                                                                                                                                                     <keywords>
                                                                                                                                                      <term ref="#texttype1"/>
                                                                                                                                                      <term ref="#texttype2"/>
                                                                                                                                                     </keywords>
                                                                                                                                                    </textClass>

                                                                                                                                                    If different types of text have to be linked to specific text parts, term can have a corresp pointing to the specific text part:

                                                                                                                                                    <textClass>
                                                                                                                                                     <keywords>
                                                                                                                                                      <term corresp="#textpart1">Dedication</term>
                                                                                                                                                      <term corresp="#textpart2">Decree</term>
                                                                                                                                                     </keywords>
                                                                                                                                                    </textClass>

                                                                                                                                                    If the keywords include also other terms used for different purposes (see below), a type can be used to specify what is the term used for:

                                                                                                                                                    <textClass>
                                                                                                                                                     <keywords>
                                                                                                                                                      <term type="textType">Decree</term>
                                                                                                                                                      <term type="keyword">Euergesia</term>
                                                                                                                                                     </keywords>
                                                                                                                                                    </textClass>

                                                                                                                                                    See also:

                                                                                                                                                    Other pages describing <textClass>:

                                                                                                                                                    Other pages describing <keywords>:

                                                                                                                                                    Other pages describing <term>:

                                                                                                                                                    Responsibility for this section

                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                    2. Simona Stoyanova, author
                                                                                                                                                    3. Irene Vagionakis, author
                                                                                                                                                    4. Scott Vanderbilt, author

                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                    \ No newline at end of file + customization: term

                                                                                                                                                  Type of text

                                                                                                                                                  Although there is no specific TEI tag for the category, type, or function of the text, EpiDoc recommends the inclusion of text type information in textClass/keywords:

                                                                                                                                                  <textClass>
                                                                                                                                                   <keywords scheme="hgv">
                                                                                                                                                    <term>Brief (privat)</term>
                                                                                                                                                   </keywords>
                                                                                                                                                  </textClass>

                                                                                                                                                  The use of ref in term for pointing to the related term in an internal authority list or external vocabulary is not required but recommended:

                                                                                                                                                  <textClass>
                                                                                                                                                   <keywords>
                                                                                                                                                    <term ref="#texttype1">Dedication</term>
                                                                                                                                                    <term ref="#texttype2">Decree</term>
                                                                                                                                                   </keywords>
                                                                                                                                                  </textClass>

                                                                                                                                                  The element content is recommended but not required:

                                                                                                                                                  <textClass>
                                                                                                                                                   <keywords>
                                                                                                                                                    <term ref="#texttype1"/>
                                                                                                                                                    <term ref="#texttype2"/>
                                                                                                                                                   </keywords>
                                                                                                                                                  </textClass>

                                                                                                                                                  If different types of text have to be linked to specific text parts, term can have a corresp pointing to the specific text part:

                                                                                                                                                  <textClass>
                                                                                                                                                   <keywords>
                                                                                                                                                    <term corresp="#textpart1">Dedication</term>
                                                                                                                                                    <term corresp="#textpart2">Decree</term>
                                                                                                                                                   </keywords>
                                                                                                                                                  </textClass>

                                                                                                                                                  If the keywords include also other terms used for different purposes (see below), a type can be used to specify what is the term used for:

                                                                                                                                                  <textClass>
                                                                                                                                                   <keywords>
                                                                                                                                                    <term type="textType">Decree</term>
                                                                                                                                                    <term type="keyword">Euergesia</term>
                                                                                                                                                   </keywords>
                                                                                                                                                  </textClass>

                                                                                                                                                  See also:

                                                                                                                                                  Other pages describing <textClass>:

                                                                                                                                                  Other pages describing <keywords>:

                                                                                                                                                  Other pages describing <term>:

                                                                                                                                                  Responsibility for this section

                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                  2. Simona Stoyanova, author
                                                                                                                                                  3. Irene Vagionakis, author
                                                                                                                                                  4. Scott Vanderbilt, author

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histfound-pt-br.html b/gl/dev/supp-histfound-pt-br.html index 4710fd53b..5c8cda137 100644 --- a/gl/dev/supp-histfound-pt-br.html +++ b/gl/dev/supp-histfound-pt-br.html @@ -21,26 +21,26 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                  Contexto de descoberta (Findspot)

                                                                                                                                                  2023-04-27

                                                                                                                                                  Todos os assuntos relativos à proveniência de um documento são codificados na parte de Descrição de Manuscrito (msDesc) do header TEI. Mais exatamente, eles são colocados dentro da subseção history (veja mais em Datas e locais de obsrvações modernas).

                                                                                                                                                  Elemento relevante de documentação (TEI):

                                                                                                                                                  • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                    Contexto de descoberta (Findspot)

                                                                                                                                                    2024-03-05

                                                                                                                                                    Todos os assuntos relativos à proveniência de um documento são codificados na parte de Descrição de Manuscrito (msDesc) do header TEI. Mais exatamente, eles são colocados dentro da subseção history (veja mais em Datas e locais de obsrvações modernas).

                                                                                                                                                    Elemento relevante de documentação (TEI):

                                                                                                                                                    Arquivos padrão EpiDoc incluem toda a informação espacial, temporal e circunstancial sobre a descoberta inicial de um objeto portador de texto numa tag provenance com um atributo type que recebe o valor "found". Geralmente haverá apenas um elemento destes, a não ser que fragmentos separados do documento tenham sido encontrados em locais diferentes. Valores opcionais recomendados para subtype estão disponíveis se houver necessidade de fazer distinções computacionais práticas entre diferentes circunstâncias de descoberta (veja lista em Datas e locais de observações modernas).

                                                                                                                                                    A informação dentro de cada elemento provenance pode ter a forma de um ou mais parágrafos em prosa, ou a de uma lista (com o uso de tags TEI apropriadas quando necessário). Algumas vezes, ciscunstâncias e enfoque editorial farão com que o conteúdo do elemento provenance seja principalmente prosa; em outras ocasiões, um enfoque de codificação mais orientado para dados pode ser indicado. De qualquer forma, a melhor prática é codificar apropriadamente nomes de lugares e qualquer outra informação que valha a pena indexar, linkar ou consultar (por exemplo, com persName, placeName, etc.).

                                                                                                                                                    Examples

                                                                                                                                                    Aqui temos um exemplo adaptado de um marco miliário publicado em The Inscriptions of Roman Tripolitania:

                                                                                                                                                    <provenance type="found"> + customization: teiHeader

                                                                                                                                                  Arquivos padrão EpiDoc incluem toda a informação espacial, temporal e circunstancial sobre a descoberta inicial de um objeto portador de texto numa tag provenance com um atributo type que recebe o valor "found". Geralmente haverá apenas um elemento destes, a não ser que fragmentos separados do documento tenham sido encontrados em locais diferentes. Valores opcionais recomendados para subtype estão disponíveis se houver necessidade de fazer distinções computacionais práticas entre diferentes circunstâncias de descoberta (veja lista em Datas e locais de observações modernas).

                                                                                                                                                  A informação dentro de cada elemento provenance pode ter a forma de um ou mais parágrafos em prosa, ou a de uma lista (com o uso de tags TEI apropriadas quando necessário). Algumas vezes, ciscunstâncias e enfoque editorial farão com que o conteúdo do elemento provenance seja principalmente prosa; em outras ocasiões, um enfoque de codificação mais orientado para dados pode ser indicado. De qualquer forma, a melhor prática é codificar apropriadamente nomes de lugares e qualquer outra informação que valha a pena indexar, linkar ou consultar (por exemplo, com persName, placeName, etc.).

                                                                                                                                                  Examples

                                                                                                                                                  Aqui temos um exemplo adaptado de um marco miliário publicado em The Inscriptions of Roman Tripolitania:

                                                                                                                                                  <provenance type="found">  <placeName key="db648">Coast Road: Oea-Lepcis Magna</placeName>:   <rs type="monuListkey="db669">Gasr Garabulli</rs>: in the Concessione Gherardi, 1 km. West of   the village. </provenance> -

                                                                                                                                                  E um outro adaptado de um óstraco publicado em Papyri.info:

                                                                                                                                                  <provenance type="found"> +

                                                                                                                                                  E um outro adaptado de um óstraco publicado em Papyri.info:

                                                                                                                                                  <provenance type="found">  Roman dump at <placeName ref="http://pleiades.stoa.org/places/785986">Berenike</placeName>. </provenance> -

                                                                                                                                                  E um terceiro do projeto Corpus of the Inscriptions of Cāmpa, demonstrando o uso de atributos padrão de datas TEI, para indicar o tempo da dsescoberta:

                                                                                                                                                  <provenance type="foundnotAfter="1999"> +

                                                                                                                                                  E um terceiro do projeto Corpus of the Inscriptions of Cāmpa, demonstrando o uso de atributos padrão de datas TEI, para indicar o tempo da dsescoberta:

                                                                                                                                                  <provenance type="foundnotAfter="1999">  <ab>It seems that this piece was part of the private collection of Mr. Vũ Kim Lộc in Hồ Chí   Minh City at least until 1999, when Anne-Valérie Schweyer published a study of other objects   in the same collection (<ref target="C0205.xml">C. 205</ref>,   <ref target="C0206.xml">C. 206</ref><ref target="C0207.xml">C. 207</ref>) although without   mentioning the present item and <ref target="C0209.xml">C. 209</ref>.</ab> </provenance> -

                                                                                                                                                  Linkando o local de origem com o local de descoberta

                                                                                                                                                  Muitas vezes é desejável, quando se acredita que objetos foram encontrados in situ, indicar a relação entre o local de descoberta e o local de origem. Ajuda e exemplos são encontrados na seção sobre Local original do objeto portador de texto.

                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                  1. Tom Elliott, autor
                                                                                                                                                  2. Joyce Reynolds, autor
                                                                                                                                                  3. Arlo Griffiths, autor
                                                                                                                                                  4. Gabriel Bodard, autor
                                                                                                                                                  5. James Cowey, autor
                                                                                                                                                  6. Scott Vanderbilt, autor
                                                                                                                                                  7. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                  Linkando o local de origem com o local de descoberta

                                                                                                                                                  Muitas vezes é desejável, quando se acredita que objetos foram encontrados in situ, indicar a relação entre o local de descoberta e o local de origem. Ajuda e exemplos são encontrados na seção sobre Local original do objeto portador de texto.

                                                                                                                                                  See also:

                                                                                                                                                  Other pages describing <history>:

                                                                                                                                                  Other pages describing <msDesc>:

                                                                                                                                                  Other pages describing <persName>:

                                                                                                                                                  Other pages describing <placeName>:

                                                                                                                                                  Other pages describing <provenance>:

                                                                                                                                                  Other pages describing <rs>:

                                                                                                                                                  Other pages describing <teiHeader>:

                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                  1. Tom Elliott, autor
                                                                                                                                                  2. Joyce Reynolds, autor
                                                                                                                                                  3. Arlo Griffiths, autor
                                                                                                                                                  4. Gabriel Bodard, autor
                                                                                                                                                  5. James Cowey, autor
                                                                                                                                                  6. Scott Vanderbilt, autor
                                                                                                                                                  7. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histfound.html b/gl/dev/supp-histfound.html index 24217c9e8..51970a478 100644 --- a/gl/dev/supp-histfound.html +++ b/gl/dev/supp-histfound.html @@ -21,26 +21,26 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                  Findspot and find context

                                                                                                                                                  2023-04-27

                                                                                                                                                  All matters related to the provenance of a document are encoded in the Manuscript Description (msDesc) portion of the TEI header. In particular, they are placed within the history subsection (see further Dates and locations of modern observations).

                                                                                                                                                  Relevant element documentation (TEI):

                                                                                                                                                  • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                    Findspot and find context

                                                                                                                                                    2024-03-05

                                                                                                                                                    All matters related to the provenance of a document are encoded in the Manuscript Description (msDesc) portion of the TEI header. In particular, they are placed within the history subsection (see further Dates and locations of modern observations).

                                                                                                                                                    Relevant element documentation (TEI):

                                                                                                                                                    Standard EpiDoc files include all relevant spatial, temporal, and circumstantial information about the initial discovery of a text-bearing object in a provenance tag with a type attribute bearing the value "found". Generally, there will only be one such element, unless separate fragments of the document were found in different locations. Recommended, optional values for subtype are available if there is a need to make computationally actionable distinctions between different circumstances of finding (see list in Dates and locations of modern observations).

                                                                                                                                                    The information within each provenance element can take the form of one or more paragraphs of prose, or of a list (with appropriate TEI tags used as necessary). Sometimes circumstances and editorial approach will dictate that the contents of provenance element be largely prose; other times a more data-oriented encoding approach may be indicated. In either case, best practice is to tag place names, personal names and other information worthy of indexing, linking or querying appropriately (e.g., with persName, placeName, etc.).

                                                                                                                                                    Examples

                                                                                                                                                    Here is an example adapted from a milestone published in The Inscriptions of Roman Tripolitania:

                                                                                                                                                    <provenance type="found"> + customization: teiHeader

                                                                                                                                                  Standard EpiDoc files include all relevant spatial, temporal, and circumstantial information about the initial discovery of a text-bearing object in a provenance tag with a type attribute bearing the value "found". Generally, there will only be one such element, unless separate fragments of the document were found in different locations. Recommended, optional values for subtype are available if there is a need to make computationally actionable distinctions between different circumstances of finding (see list in Dates and locations of modern observations).

                                                                                                                                                  The information within each provenance element can take the form of one or more paragraphs of prose, or of a list (with appropriate TEI tags used as necessary). Sometimes circumstances and editorial approach will dictate that the contents of provenance element be largely prose; other times a more data-oriented encoding approach may be indicated. In either case, best practice is to tag place names, personal names and other information worthy of indexing, linking or querying appropriately (e.g., with persName, placeName, etc.).

                                                                                                                                                  Examples

                                                                                                                                                  Here is an example adapted from a milestone published in The Inscriptions of Roman Tripolitania:

                                                                                                                                                  <provenance type="found">  <placeName key="db648">Coast Road: Oea-Lepcis Magna</placeName>:   <rs type="monuListkey="db669">Gasr Garabulli</rs>: in the Concessione Gherardi, 1 km. West of   the village. </provenance> -

                                                                                                                                                  And another adapted from an ostracon published in Papyri.info:

                                                                                                                                                  <provenance type="found"> +

                                                                                                                                                  And another adapted from an ostracon published in Papyri.info:

                                                                                                                                                  <provenance type="found">  Roman dump at <placeName ref="http://pleiades.stoa.org/places/785986">Berenike</placeName>. </provenance> -

                                                                                                                                                  And a third from the Corpus of the Inscriptions of Cāmpa project, demonstrating the use of standard TEI date attributes to indicate the timing of the discovery:

                                                                                                                                                  <provenance type="foundnotAfter="1999"> +

                                                                                                                                                  And a third from the Corpus of the Inscriptions of Cāmpa project, demonstrating the use of standard TEI date attributes to indicate the timing of the discovery:

                                                                                                                                                  <provenance type="foundnotAfter="1999">  <ab>It seems that this piece was part of the private collection of Mr. Vũ Kim Lộc in Hồ Chí   Minh City at least until 1999, when Anne-Valérie Schweyer published a study of other objects   in the same collection (<ref target="C0205.xml">C. 205</ref>,   <ref target="C0206.xml">C. 206</ref><ref target="C0207.xml">C. 207</ref>) although without   mentioning the present item and <ref target="C0209.xml">C. 209</ref>.</ab> </provenance> -

                                                                                                                                                  Linking place of origin to place of finding

                                                                                                                                                  It is often desirable, when objects are thought to have been found in situ, to indicate the relationship between place of finding and place of origin. Guidance and examples are provided in the section on Original location of the text-bearing object.

                                                                                                                                                  Responsibility for this section

                                                                                                                                                  1. Tom Elliott, author
                                                                                                                                                  2. Joyce Reynolds, author
                                                                                                                                                  3. Arlo Griffiths, author
                                                                                                                                                  4. Gabriel Bodard, author
                                                                                                                                                  5. James Cowey, author
                                                                                                                                                  6. Scott Vanderbilt, author

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                  Linking place of origin to place of finding

                                                                                                                                                  It is often desirable, when objects are thought to have been found in situ, to indicate the relationship between place of finding and place of origin. Guidance and examples are provided in the section on Original location of the text-bearing object.

                                                                                                                                                  See also:

                                                                                                                                                  Other pages describing <history>:

                                                                                                                                                  Other pages describing <msDesc>:

                                                                                                                                                  Other pages describing <persName>:

                                                                                                                                                  Other pages describing <placeName>:

                                                                                                                                                  Other pages describing <provenance>:

                                                                                                                                                  Other pages describing <rs>:

                                                                                                                                                  Other pages describing <teiHeader>:

                                                                                                                                                  Responsibility for this section

                                                                                                                                                  1. Tom Elliott, author
                                                                                                                                                  2. Joyce Reynolds, author
                                                                                                                                                  3. Arlo Griffiths, author
                                                                                                                                                  4. Gabriel Bodard, author
                                                                                                                                                  5. James Cowey, author
                                                                                                                                                  6. Scott Vanderbilt, author

                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histinvno-pt-br.html b/gl/dev/supp-histinvno-pt-br.html index 34b57bc69..4d698eb95 100644 --- a/gl/dev/supp-histinvno-pt-br.html +++ b/gl/dev/supp-histinvno-pt-br.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                  Números de inventário de depósito

                                                                                                                                                  2023-04-27

                                                                                                                                                  • TEI definition: msIdentifier ; EpiDoc-specific +

                                                                                                                                                    Números de inventário de depósito

                                                                                                                                                    2024-03-05

                                                                                                                                                    Numa edição, registrar os números de inventário e catálogo, passados e presentes, associados a um objeto portador de texto, pode fornecer informação essencial, aos usuários da edição, sobre localização do objeto para sua autópsia e para relacionar referências em publicações e materiais de arquivo. Para isto, TEI/EpiDoc requerem algum tipo de identificação de manuscrito (msIdentifier) para ser codificado como parte da descrição do manuscrito em qualquer edição, como descrito no TEI Guidelines section on the manuscript identifier e ilustrado pelos exemplos abaixo.

                                                                                                                                                    Sempre que possível, o msIdentifier incluirá informação sobre o nome e local da instituição ou depósito que guarda o objeto (com o uso dos elementos settlement e repository), junto com seu número de inventário (idno) e/ou nome convencional (msName). Quando o objeto portador de texto não estiver dentro de uma coleção institucional, civil ou num sítio, como muitas vezes acontece com inscrições, talvez só seja possível fornecer um mínimo de informação. Quando uma instituição de pesquisa compilou e mantém um inventário regional ou temático para materiais que estão espalhados por diversas instituições ou sítios, este número poder ser a melhor escolha, e o número institucional individual, de expedição ou de inventário do sítio pode também ser registrado com o elemento altIdentifier. Observe que, na ausência de um número institucional de inventário (ou para aumentar a informação institucional oferecida) um <altIdentifer> pode ser adicionado, com o <idno type="URI"> apontando para um artigo da Wikipedia ou outro recurso estável da rede sobre o objeto.

                                                                                                                                                    O exemplo seguinte ilustra o uso dos elementos settlement, repository e idno em uma declaração mínima de inventário para um item de uma coleção controlada:

                                                                                                                                                    <msIdentifier>
                                                                                                                                                     <settlement>Sevastopol</settlement>
                                                                                                                                                     <repository>National Preserve of Tauric Chersonesos (НЗХТ)</repository>
                                                                                                                                                     <idno>80/36504</idno>
                                                                                                                                                    </msIdentifier>

                                                                                                                                                    O exemplo a seguir tratada famosa Pedra de Rosetta, expandindo o método utilizado acima, fornecendo o nome convencional da inscrição, bem como um número de inventário usado anteriormente pelo museu:

                                                                                                                                                    <msIdentifier>
                                                                                                                                                     <settlement>London</settlement>
                                                                                                                                                     <repository>The British Museum</repository>
                                                                                                                                                     <idno>E24</idno>
                                                                                                                                                     <msName>The Rosetta Stone</msName>
                                                                                                                                                     <altIdentifier>
                                                                                                                                                      <idno>BS.24</idno>
                                                                                                                                                     </altIdentifier>
                                                                                                                                                    </msIdentifier>

                                                                                                                                                    O próximo exemplo trata de um monumento independente (a Coluna de Trajano) e ilustra uso ideal de uma URI da Wikipedia para aumentar a informação fornecida na parte principal do elemento <msIdentifer>:

                                                                                                                                                    <msIdentifier>
                                                                                                                                                     <settlement>Rome</settlement>
                                                                                                                                                     <msName>The Column of Trajan</msName>
                                                                                                                                                     <altIdentifier>
                                                                                                                                                      <idno type="URI">http://en.wikipedia.org/wiki/Trajan's_Column</idno>
                                                                                                                                                     </altIdentifier>
                                                                                                                                                    </msIdentifier>

                                                                                                                                                    O exemplo a seguir, tirado do Corpus of the Inscriptions of Campā, ilustra diversas possibilidades avançadas e opcionais na codificação de identificadores de objeto. Estas possibilidades incluem:

                                                                                                                                                    • o uso de um número primário de inventário e a "coleta" de um inventário regional/temático compilado por uma instituição (neste caso, o inventário de inscrições Campā é mantido pela École française d'Extrême-Orient ou EFEO)
                                                                                                                                                    • a designação de valores de atributo a xml:id para alguns dos números de inventário, para que estes possam ser linkados (usando, por exemplo, ref), se necessário, a listagens bibliográficas e comentários presentes em outras partes da edição, e para dar suporte a geração de índice
                                                                                                                                                    • uso dos valores do atributo type em altIdentifier para organizá-los e distingui-los
                                                                                                                                                    <msIdentifier>
                                                                                                                                                     <institution>EFEO</institution>
                                                                                                                                                     <idno xml:id="inv-general">C. 152</idno>
                                                                                                                                                     <altIdentifier type="cancelled">
                                                                                                                                                      <institution>EFEO</institution>
                                                                                                                                                      <idno>C. 166</idno>
                                                                                                                                                     </altIdentifier>
                                                                                                                                                     <altIdentifier type="museum-inventory">
                                                                                                                                                      <settlement>Đà Nẵng</settlement>
                                                                                                                                                      <repository>BTC</repository>
                                                                                                                                                      <idno xml:id="inv-btc">BTC 86</idno>
                                                                                                                                                     </altIdentifier>
                                                                                                                                                     <altIdentifier type="museum-inventory-former">
                                                                                                                                                      <settlement>Đà Nẵng</settlement>
                                                                                                                                                      <repository>Musée Parmentier</repository>
                                                                                                                                                      <idno xml:id="inv-musee-parmentier">45,2</idno>
                                                                                                                                                     </altIdentifier>
                                                                                                                                                    </msIdentifier>

                                                                                                                                                    See also:

                                                                                                                                                    Other pages describing <msIdentifier>:

                                                                                                                                                      Other pages describing <msName>:

                                                                                                                                                        Other pages describing <repository>:

                                                                                                                                                          Other pages describing <idno>:

                                                                                                                                                          Other pages describing <altIdentifier>:

                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                            1. Gabriel Bodard, autor
                                                                                                                                                            2. Tom Elliott, autor
                                                                                                                                                            3. Arlo Griffiths, autor
                                                                                                                                                            4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                            \ No newline at end of file + customization: altIdentifier

                                                                                                                                                          Numa edição, registrar os números de inventário e catálogo, passados e presentes, associados a um objeto portador de texto, pode fornecer informação essencial, aos usuários da edição, sobre localização do objeto para sua autópsia e para relacionar referências em publicações e materiais de arquivo. Para isto, TEI/EpiDoc requerem algum tipo de identificação de manuscrito (msIdentifier) para ser codificado como parte da descrição do manuscrito em qualquer edição, como descrito no TEI Guidelines section on the manuscript identifier e ilustrado pelos exemplos abaixo.

                                                                                                                                                          Sempre que possível, o msIdentifier incluirá informação sobre o nome e local da instituição ou depósito que guarda o objeto (com o uso dos elementos settlement e repository), junto com seu número de inventário (idno) e/ou nome convencional (msName). Quando o objeto portador de texto não estiver dentro de uma coleção institucional, civil ou num sítio, como muitas vezes acontece com inscrições, talvez só seja possível fornecer um mínimo de informação. Quando uma instituição de pesquisa compilou e mantém um inventário regional ou temático para materiais que estão espalhados por diversas instituições ou sítios, este número poder ser a melhor escolha, e o número institucional individual, de expedição ou de inventário do sítio pode também ser registrado com o elemento altIdentifier. Observe que, na ausência de um número institucional de inventário (ou para aumentar a informação institucional oferecida) um <altIdentifer> pode ser adicionado, com o <idno type="URI"> apontando para um artigo da Wikipedia ou outro recurso estável da rede sobre o objeto.

                                                                                                                                                          O exemplo seguinte ilustra o uso dos elementos settlement, repository e idno em uma declaração mínima de inventário para um item de uma coleção controlada:

                                                                                                                                                          <msIdentifier>
                                                                                                                                                           <settlement>Sevastopol</settlement>
                                                                                                                                                           <repository>National Preserve of Tauric Chersonesos (НЗХТ)</repository>
                                                                                                                                                           <idno>80/36504</idno>
                                                                                                                                                          </msIdentifier>

                                                                                                                                                          O exemplo a seguir tratada famosa Pedra de Rosetta, expandindo o método utilizado acima, fornecendo o nome convencional da inscrição, bem como um número de inventário usado anteriormente pelo museu:

                                                                                                                                                          <msIdentifier>
                                                                                                                                                           <settlement>London</settlement>
                                                                                                                                                           <repository>The British Museum</repository>
                                                                                                                                                           <idno>E24</idno>
                                                                                                                                                           <msName>The Rosetta Stone</msName>
                                                                                                                                                           <altIdentifier>
                                                                                                                                                            <idno>BS.24</idno>
                                                                                                                                                           </altIdentifier>
                                                                                                                                                          </msIdentifier>

                                                                                                                                                          O próximo exemplo trata de um monumento independente (a Coluna de Trajano) e ilustra uso ideal de uma URI da Wikipedia para aumentar a informação fornecida na parte principal do elemento <msIdentifer>:

                                                                                                                                                          <msIdentifier>
                                                                                                                                                           <settlement>Rome</settlement>
                                                                                                                                                           <msName>The Column of Trajan</msName>
                                                                                                                                                           <altIdentifier>
                                                                                                                                                            <idno type="URI">http://en.wikipedia.org/wiki/Trajan's_Column</idno>
                                                                                                                                                           </altIdentifier>
                                                                                                                                                          </msIdentifier>

                                                                                                                                                          O exemplo a seguir, tirado do Corpus of the Inscriptions of Campā, ilustra diversas possibilidades avançadas e opcionais na codificação de identificadores de objeto. Estas possibilidades incluem:

                                                                                                                                                          • o uso de um número primário de inventário e a "coleta" de um inventário regional/temático compilado por uma instituição (neste caso, o inventário de inscrições Campā é mantido pela École française d'Extrême-Orient ou EFEO)
                                                                                                                                                          • a designação de valores de atributo a xml:id para alguns dos números de inventário, para que estes possam ser linkados (usando, por exemplo, ref), se necessário, a listagens bibliográficas e comentários presentes em outras partes da edição, e para dar suporte a geração de índice
                                                                                                                                                          • uso dos valores do atributo type em altIdentifier para organizá-los e distingui-los
                                                                                                                                                          <msIdentifier>
                                                                                                                                                           <institution>EFEO</institution>
                                                                                                                                                           <idno xml:id="inv-general">C. 152</idno>
                                                                                                                                                           <altIdentifier type="cancelled">
                                                                                                                                                            <institution>EFEO</institution>
                                                                                                                                                            <idno>C. 166</idno>
                                                                                                                                                           </altIdentifier>
                                                                                                                                                           <altIdentifier type="museum-inventory">
                                                                                                                                                            <settlement>Đà Nẵng</settlement>
                                                                                                                                                            <repository>BTC</repository>
                                                                                                                                                            <idno xml:id="inv-btc">BTC 86</idno>
                                                                                                                                                           </altIdentifier>
                                                                                                                                                           <altIdentifier type="museum-inventory-former">
                                                                                                                                                            <settlement>Đà Nẵng</settlement>
                                                                                                                                                            <repository>Musée Parmentier</repository>
                                                                                                                                                            <idno xml:id="inv-musee-parmentier">45,2</idno>
                                                                                                                                                           </altIdentifier>
                                                                                                                                                          </msIdentifier>

                                                                                                                                                          See also:

                                                                                                                                                          Other pages describing <msIdentifier>:

                                                                                                                                                            Other pages describing <msName>:

                                                                                                                                                              Other pages describing <repository>:

                                                                                                                                                                Other pages describing <idno>:

                                                                                                                                                                Other pages describing <altIdentifier>:

                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                  2. Tom Elliott, autor
                                                                                                                                                                  3. Arlo Griffiths, autor
                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histinvno.html b/gl/dev/supp-histinvno.html index c0db2d554..8aea04b8d 100644 --- a/gl/dev/supp-histinvno.html +++ b/gl/dev/supp-histinvno.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                  Inventory numbers and repository

                                                                                                                                                                  2023-04-27

                                                                                                                                                                  • TEI definition: msIdentifier ; EpiDoc-specific +

                                                                                                                                                                    Inventory numbers and repository

                                                                                                                                                                    2024-03-05

                                                                                                                                                                    Recording in an edition the past and present inventory and catalog numbers associated with a text-bearing object can provide users of the edition essential information for locating the object for autopsy and for correlating references in publications and archival materials. Accordingly, TEI/EpiDoc requires some kind of manuscript identifier (msIdentifier) to be encoded as part of the manuscript description in any edition, as described in the TEI Guidelines section on the manuscript identifier and illustrated in the examples below.

                                                                                                                                                                    Whenever possible, the msIdentifier will include information about the name and location of the instition or repository holding the object (using the settlement and repository elements), along with its inventory number (idno) and/or conventional name (msName). When the text-bearing object is not held in an institutional, civic, or site collection, as is often the case with inscriptions, it may only be possible to provide very minimal information. When a research institution has compiled and maintained a regional or thematic inventory for materials that are spread across a range of institutions or sites, this number may be preferred and the individual institutional, expedition, or site inventory numbers recorded also with the altIdentifier element. Note that, in the absence of an institutional inventory number (or to augment the institutional information provided) an <altIdentifer> may be added with <idno type="URI"> pointing to a Wikipedia article or other stable web resource about the object.

                                                                                                                                                                    The following example illustrates the use of the settlement, repository and idno elements in a minimal inventory declaration for an item in a controlled collection:

                                                                                                                                                                    <msIdentifier>
                                                                                                                                                                     <settlement>Sevastopol</settlement>
                                                                                                                                                                     <repository>National Preserve of Tauric Chersonesos (НЗХТ)</repository>
                                                                                                                                                                     <idno>80/36504</idno>
                                                                                                                                                                    </msIdentifier>

                                                                                                                                                                    This next example treats the famous Rosetta Stone, expanding on the approach used above by providing the conventional name for the inscription, as well as a prior inventory number once used by the museum:

                                                                                                                                                                    <msIdentifier>
                                                                                                                                                                     <settlement>London</settlement>
                                                                                                                                                                     <repository>The British Museum</repository>
                                                                                                                                                                     <idno>E24</idno>
                                                                                                                                                                     <msName>The Rosetta Stone</msName>
                                                                                                                                                                     <altIdentifier>
                                                                                                                                                                      <idno>BS.24</idno>
                                                                                                                                                                     </altIdentifier>
                                                                                                                                                                    </msIdentifier>

                                                                                                                                                                    The following example treats a free-standing monument (Trajan's Column) and illustrates the optional use of a Wikipedia URI to augment the information provided in the main portion of the <msIdentifer> element:

                                                                                                                                                                    <msIdentifier>
                                                                                                                                                                     <settlement>Rome</settlement>
                                                                                                                                                                     <msName>The Column of Trajan</msName>
                                                                                                                                                                     <altIdentifier>
                                                                                                                                                                      <idno type="URI">http://en.wikipedia.org/wiki/Trajan's_Column</idno>
                                                                                                                                                                     </altIdentifier>
                                                                                                                                                                    </msIdentifier>

                                                                                                                                                                    The following example, drawn from the Corpus of the Inscriptions of Campā, illustrates several advanced, optional features in the encoding of object identifiers. These include:

                                                                                                                                                                    • the use for primary inventory number and "collection" of a regional/thematic inventory compiled by an institution (in this case the inventory of Campā inscriptions maintained by the École française d'Extrême-Orient or EFEO)
                                                                                                                                                                    • the assignment of xml:id attribute values to some of the inventory numbers so that they can be connected (using e.g., ref) to bibliographic listings and commentary elsewhere in the edition as needed, and to support index generation
                                                                                                                                                                    • use of type values on altIdentifier to organize and distinguish them
                                                                                                                                                                    <msIdentifier>
                                                                                                                                                                     <institution>EFEO</institution>
                                                                                                                                                                     <idno xml:id="inv-general">C. 152</idno>
                                                                                                                                                                     <altIdentifier type="cancelled">
                                                                                                                                                                      <institution>EFEO</institution>
                                                                                                                                                                      <idno>C. 166</idno>
                                                                                                                                                                     </altIdentifier>
                                                                                                                                                                     <altIdentifier type="museum-inventory">
                                                                                                                                                                      <settlement>Đà Nẵng</settlement>
                                                                                                                                                                      <repository>BTC</repository>
                                                                                                                                                                      <idno xml:id="inv-btc">BTC 86</idno>
                                                                                                                                                                     </altIdentifier>
                                                                                                                                                                     <altIdentifier type="museum-inventory-former">
                                                                                                                                                                      <settlement>Đà Nẵng</settlement>
                                                                                                                                                                      <repository>Musée Parmentier</repository>
                                                                                                                                                                      <idno xml:id="inv-musee-parmentier">45,2</idno>
                                                                                                                                                                     </altIdentifier>
                                                                                                                                                                    </msIdentifier>

                                                                                                                                                                    See also:

                                                                                                                                                                    Other pages describing <msIdentifier>:

                                                                                                                                                                      Other pages describing <msName>:

                                                                                                                                                                        Other pages describing <repository>:

                                                                                                                                                                          Other pages describing <idno>:

                                                                                                                                                                          Other pages describing <altIdentifier>:

                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                            1. Gabriel Bodard, author
                                                                                                                                                                            2. Tom Elliott, author
                                                                                                                                                                            3. Arlo Griffiths, author

                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                            \ No newline at end of file + customization: altIdentifier

                                                                                                                                                                          Recording in an edition the past and present inventory and catalog numbers associated with a text-bearing object can provide users of the edition essential information for locating the object for autopsy and for correlating references in publications and archival materials. Accordingly, TEI/EpiDoc requires some kind of manuscript identifier (msIdentifier) to be encoded as part of the manuscript description in any edition, as described in the TEI Guidelines section on the manuscript identifier and illustrated in the examples below.

                                                                                                                                                                          Whenever possible, the msIdentifier will include information about the name and location of the instition or repository holding the object (using the settlement and repository elements), along with its inventory number (idno) and/or conventional name (msName). When the text-bearing object is not held in an institutional, civic, or site collection, as is often the case with inscriptions, it may only be possible to provide very minimal information. When a research institution has compiled and maintained a regional or thematic inventory for materials that are spread across a range of institutions or sites, this number may be preferred and the individual institutional, expedition, or site inventory numbers recorded also with the altIdentifier element. Note that, in the absence of an institutional inventory number (or to augment the institutional information provided) an <altIdentifer> may be added with <idno type="URI"> pointing to a Wikipedia article or other stable web resource about the object.

                                                                                                                                                                          The following example illustrates the use of the settlement, repository and idno elements in a minimal inventory declaration for an item in a controlled collection:

                                                                                                                                                                          <msIdentifier>
                                                                                                                                                                           <settlement>Sevastopol</settlement>
                                                                                                                                                                           <repository>National Preserve of Tauric Chersonesos (НЗХТ)</repository>
                                                                                                                                                                           <idno>80/36504</idno>
                                                                                                                                                                          </msIdentifier>

                                                                                                                                                                          This next example treats the famous Rosetta Stone, expanding on the approach used above by providing the conventional name for the inscription, as well as a prior inventory number once used by the museum:

                                                                                                                                                                          <msIdentifier>
                                                                                                                                                                           <settlement>London</settlement>
                                                                                                                                                                           <repository>The British Museum</repository>
                                                                                                                                                                           <idno>E24</idno>
                                                                                                                                                                           <msName>The Rosetta Stone</msName>
                                                                                                                                                                           <altIdentifier>
                                                                                                                                                                            <idno>BS.24</idno>
                                                                                                                                                                           </altIdentifier>
                                                                                                                                                                          </msIdentifier>

                                                                                                                                                                          The following example treats a free-standing monument (Trajan's Column) and illustrates the optional use of a Wikipedia URI to augment the information provided in the main portion of the <msIdentifer> element:

                                                                                                                                                                          <msIdentifier>
                                                                                                                                                                           <settlement>Rome</settlement>
                                                                                                                                                                           <msName>The Column of Trajan</msName>
                                                                                                                                                                           <altIdentifier>
                                                                                                                                                                            <idno type="URI">http://en.wikipedia.org/wiki/Trajan's_Column</idno>
                                                                                                                                                                           </altIdentifier>
                                                                                                                                                                          </msIdentifier>

                                                                                                                                                                          The following example, drawn from the Corpus of the Inscriptions of Campā, illustrates several advanced, optional features in the encoding of object identifiers. These include:

                                                                                                                                                                          • the use for primary inventory number and "collection" of a regional/thematic inventory compiled by an institution (in this case the inventory of Campā inscriptions maintained by the École française d'Extrême-Orient or EFEO)
                                                                                                                                                                          • the assignment of xml:id attribute values to some of the inventory numbers so that they can be connected (using e.g., ref) to bibliographic listings and commentary elsewhere in the edition as needed, and to support index generation
                                                                                                                                                                          • use of type values on altIdentifier to organize and distinguish them
                                                                                                                                                                          <msIdentifier>
                                                                                                                                                                           <institution>EFEO</institution>
                                                                                                                                                                           <idno xml:id="inv-general">C. 152</idno>
                                                                                                                                                                           <altIdentifier type="cancelled">
                                                                                                                                                                            <institution>EFEO</institution>
                                                                                                                                                                            <idno>C. 166</idno>
                                                                                                                                                                           </altIdentifier>
                                                                                                                                                                           <altIdentifier type="museum-inventory">
                                                                                                                                                                            <settlement>Đà Nẵng</settlement>
                                                                                                                                                                            <repository>BTC</repository>
                                                                                                                                                                            <idno xml:id="inv-btc">BTC 86</idno>
                                                                                                                                                                           </altIdentifier>
                                                                                                                                                                           <altIdentifier type="museum-inventory-former">
                                                                                                                                                                            <settlement>Đà Nẵng</settlement>
                                                                                                                                                                            <repository>Musée Parmentier</repository>
                                                                                                                                                                            <idno xml:id="inv-musee-parmentier">45,2</idno>
                                                                                                                                                                           </altIdentifier>
                                                                                                                                                                          </msIdentifier>

                                                                                                                                                                          See also:

                                                                                                                                                                          Other pages describing <msIdentifier>:

                                                                                                                                                                            Other pages describing <msName>:

                                                                                                                                                                              Other pages describing <repository>:

                                                                                                                                                                                Other pages describing <idno>:

                                                                                                                                                                                Other pages describing <altIdentifier>:

                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                                                  2. Tom Elliott, author
                                                                                                                                                                                  3. Arlo Griffiths, author

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histlocations-pt-br.html b/gl/dev/supp-histlocations-pt-br.html index 7f34ec463..46cb618a7 100644 --- a/gl/dev/supp-histlocations-pt-br.html +++ b/gl/dev/supp-histlocations-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                  Datas e locais de observações modernas

                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                  Nota: orientação para a codificação de informação sobre a disposição original e histórica do objeto portador de texto é oferecida nas seções sobre Local de origem do objeto portador de texto e Data de origem do texto e/ou objeto.

                                                                                                                                                                                  Elemento relevante de documentação (TEI):

                                                                                                                                                                                  • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                                                    Datas e locais de observações modernas

                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                    Nota: orientação para a codificação de informação sobre a disposição original e histórica do objeto portador de texto é oferecida nas seções sobre Local de origem do objeto portador de texto e Data de origem do texto e/ou objeto.

                                                                                                                                                                                    Elemento relevante de documentação (TEI):

                                                                                                                                                                                    É comum, nas edições de manuscritos, de papiros ou de inscrições pré-modernos, enumerar as ocasiões nas quais pessoas da modernidade encontraram com o objeto e relataram informação importante sobre ele, sua condição e disposição, etc., junto com referências bibliográficas, onde for possível. Tal observação inicial é muitas vezes a ocasião da descoberta, algumas vezes in situ, algumas vezes em outras circunstâncias ou reuso, algumas vezes já num contexto de uma coleção moderna. Outras observações seguem, culminando na "última localização observada" ou "localização atual".

                                                                                                                                                                                    Seguindo normas gerais TEI, EpiDoc trata cada uma destas observações como um evento separado no espaço e no tempo, e codifica cada um deles em um elemento provenance separado na seção history do header. O atributo type é utilizado, com os seguintes valores padrão, para fazer a distinção dos principais tipos de evento:

                                                                                                                                                                                    • <provenance type="found"> é usado para codificar informação sobre a primeira aparição, ou reaparição chave, do objeto portador de texto em tempos modernos
                                                                                                                                                                                    • <provenance type="observed"> é usado para codificar informação sobre observações modernas subsequentes
                                                                                                                                                                                    • <provenance type="not-observed"> é usado para codificar informação sobre uma tentativa específica, mal sucedida, de localizar um objeto numa locação presumida ou previamente registrada
                                                                                                                                                                                    • <provenance type="transferred"> é usado para codificar informação sobre relocações modernas documentáveis do objeto portador de texto

                                                                                                                                                                                    Nota: a recomendação antiga de <provenance type="autopsy"> como um caso especial de <provenance type="observed"> foi descontinuada em favor de <provenance type="observed" subtype="autopsied">. Veja mais, abaixo.

                                                                                                                                                                                    Algumas edições impressas, bancos de dados, e projetos em curso são capazes de fornecer um número ainda maior de detalhes sobre a natureza dos eventos de proveniência (por exemplo, se a transferência foi uma mudança simples dentro da área de armazenagem de uma instituição ou se foi o transporte do objeto para uma outra instituição). Quando é desejável codificar distinções tão tênues numa forma compreensível para a máquina (como, por exemplo, a criação de índices para uma busca facetada), o atributo subtype pode ser utilizado. Sugerem-se os seguintes valores padrão para subtype:

                                                                                                                                                                                    Valores padrão do atributo subtype para <provenance type="found">
                                                                                                                                                                                    • "discovered" (descoberto)
                                                                                                                                                                                    • "rediscovered" (redescoberto)
                                                                                                                                                                                    • "first-seen" (primeiramente visto)
                                                                                                                                                                                    • "first-recorded" (primeiramente registrado)
                                                                                                                                                                                    Valores padrão do atributo subtype para <provenance type="observed">
                                                                                                                                                                                    • "seen" (visto)
                                                                                                                                                                                    • "recorded" (registrado)
                                                                                                                                                                                    • "identified" (identificado)
                                                                                                                                                                                    • "photographed" (fotografado)
                                                                                                                                                                                    • "autopsied" (sofreu autópsia) : um evento durante o qual o editor (isto é, a pessoa que está criando a presente edição) examina pessoalmente o objeto
                                                                                                                                                                                    • "squeeze-taken" (squeeze feito)
                                                                                                                                                                                    • "rubbing-taken" (rubbing feito)
                                                                                                                                                                                    • "ink-transfer-taken" (ink-transfer feito)
                                                                                                                                                                                    • "reported" (relatado)
                                                                                                                                                                                    • "built-into" (embutido)
                                                                                                                                                                                    • "reappeared" (reaparecido)
                                                                                                                                                                                    Valores padrão do atributo subtype para <provenance type="not-observed">
                                                                                                                                                                                    • "lost" (perdido)
                                                                                                                                                                                    • "stolen" (roubado)
                                                                                                                                                                                    • "destroyed" (destruído)
                                                                                                                                                                                    • "drawn" (retirado)
                                                                                                                                                                                    • "reported-lost" (relatado como perdido)
                                                                                                                                                                                    • "reported-stolen" (relatado como roubado)
                                                                                                                                                                                    • "reported-destroyed" (relatado como destruído)
                                                                                                                                                                                    Valores padrão do atributo subtype para <provenance type="transferred">
                                                                                                                                                                                    • "moved" (movido)
                                                                                                                                                                                    • "sold" (vendido)
                                                                                                                                                                                    • "given" (doado)
                                                                                                                                                                                    • "loaned" (emprestado)

                                                                                                                                                                                    Um exemplo geral é oferecido na seção principal sobre Proveniência do objeto portador de texto. Orientação específica para cada tipo de evento de proveniência é oferecida em sua própria seção:

                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                    2. Simona Stoyanova, autor
                                                                                                                                                                                    3. Tom Elliott, autor
                                                                                                                                                                                    4. James Cowey, autor
                                                                                                                                                                                    5. Scott Vanderbilt, autor
                                                                                                                                                                                    6. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                    \ No newline at end of file + customization: teiHeader

                                                                                                                                                                                  É comum, nas edições de manuscritos, de papiros ou de inscrições pré-modernos, enumerar as ocasiões nas quais pessoas da modernidade encontraram com o objeto e relataram informação importante sobre ele, sua condição e disposição, etc., junto com referências bibliográficas, onde for possível. Tal observação inicial é muitas vezes a ocasião da descoberta, algumas vezes in situ, algumas vezes em outras circunstâncias ou reuso, algumas vezes já num contexto de uma coleção moderna. Outras observações seguem, culminando na "última localização observada" ou "localização atual".

                                                                                                                                                                                  Seguindo normas gerais TEI, EpiDoc trata cada uma destas observações como um evento separado no espaço e no tempo, e codifica cada um deles em um elemento provenance separado na seção history do header. O atributo type é utilizado, com os seguintes valores padrão, para fazer a distinção dos principais tipos de evento:

                                                                                                                                                                                  • <provenance type="found"> é usado para codificar informação sobre a primeira aparição, ou reaparição chave, do objeto portador de texto em tempos modernos
                                                                                                                                                                                  • <provenance type="observed"> é usado para codificar informação sobre observações modernas subsequentes
                                                                                                                                                                                  • <provenance type="not-observed"> é usado para codificar informação sobre uma tentativa específica, mal sucedida, de localizar um objeto numa locação presumida ou previamente registrada
                                                                                                                                                                                  • <provenance type="transferred"> é usado para codificar informação sobre relocações modernas documentáveis do objeto portador de texto

                                                                                                                                                                                  Nota: a recomendação antiga de <provenance type="autopsy"> como um caso especial de <provenance type="observed"> foi descontinuada em favor de <provenance type="observed" subtype="autopsied">. Veja mais, abaixo.

                                                                                                                                                                                  Algumas edições impressas, bancos de dados, e projetos em curso são capazes de fornecer um número ainda maior de detalhes sobre a natureza dos eventos de proveniência (por exemplo, se a transferência foi uma mudança simples dentro da área de armazenagem de uma instituição ou se foi o transporte do objeto para uma outra instituição). Quando é desejável codificar distinções tão tênues numa forma compreensível para a máquina (como, por exemplo, a criação de índices para uma busca facetada), o atributo subtype pode ser utilizado. Sugerem-se os seguintes valores padrão para subtype:

                                                                                                                                                                                  Valores padrão do atributo subtype para <provenance type="found">
                                                                                                                                                                                  • "discovered" (descoberto)
                                                                                                                                                                                  • "rediscovered" (redescoberto)
                                                                                                                                                                                  • "first-seen" (primeiramente visto)
                                                                                                                                                                                  • "first-recorded" (primeiramente registrado)
                                                                                                                                                                                  Valores padrão do atributo subtype para <provenance type="observed">
                                                                                                                                                                                  • "seen" (visto)
                                                                                                                                                                                  • "recorded" (registrado)
                                                                                                                                                                                  • "identified" (identificado)
                                                                                                                                                                                  • "photographed" (fotografado)
                                                                                                                                                                                  • "autopsied" (sofreu autópsia) : um evento durante o qual o editor (isto é, a pessoa que está criando a presente edição) examina pessoalmente o objeto
                                                                                                                                                                                  • "squeeze-taken" (squeeze feito)
                                                                                                                                                                                  • "rubbing-taken" (rubbing feito)
                                                                                                                                                                                  • "ink-transfer-taken" (ink-transfer feito)
                                                                                                                                                                                  • "reported" (relatado)
                                                                                                                                                                                  • "built-into" (embutido)
                                                                                                                                                                                  • "reappeared" (reaparecido)
                                                                                                                                                                                  Valores padrão do atributo subtype para <provenance type="not-observed">
                                                                                                                                                                                  • "lost" (perdido)
                                                                                                                                                                                  • "stolen" (roubado)
                                                                                                                                                                                  • "destroyed" (destruído)
                                                                                                                                                                                  • "drawn" (retirado)
                                                                                                                                                                                  • "reported-lost" (relatado como perdido)
                                                                                                                                                                                  • "reported-stolen" (relatado como roubado)
                                                                                                                                                                                  • "reported-destroyed" (relatado como destruído)
                                                                                                                                                                                  Valores padrão do atributo subtype para <provenance type="transferred">
                                                                                                                                                                                  • "moved" (movido)
                                                                                                                                                                                  • "sold" (vendido)
                                                                                                                                                                                  • "given" (doado)
                                                                                                                                                                                  • "loaned" (emprestado)

                                                                                                                                                                                  Um exemplo geral é oferecido na seção principal sobre Proveniência do objeto portador de texto. Orientação específica para cada tipo de evento de proveniência é oferecida em sua própria seção:

                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                  2. Simona Stoyanova, autor
                                                                                                                                                                                  3. Tom Elliott, autor
                                                                                                                                                                                  4. James Cowey, autor
                                                                                                                                                                                  5. Scott Vanderbilt, autor
                                                                                                                                                                                  6. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histlocations.html b/gl/dev/supp-histlocations.html index 5327009d6..059960154 100644 --- a/gl/dev/supp-histlocations.html +++ b/gl/dev/supp-histlocations.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                  Dates and locations of modern observations

                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                  NB: Guidance for encoding information about the original and historical disposition of the text-bearing object is provided in the sections on Original location of the text-bearing object and Original date of text and/or object.

                                                                                                                                                                                  Relevant element documentation (TEI):

                                                                                                                                                                                  • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                                                    Dates and locations of modern observations

                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                    NB: Guidance for encoding information about the original and historical disposition of the text-bearing object is provided in the sections on Original location of the text-bearing object and Original date of text and/or object.

                                                                                                                                                                                    Relevant element documentation (TEI):

                                                                                                                                                                                    It is customary in producing an edition of a pre-modern manuscript, papyrus, inscription, or other text-bearing object to enumerate the occasions on which modern persons encountered and reported seminal information about the object, its condition and disposition, etc., together with associated bibliographic references where possible. The initial such observation is often the occasion of finding, sometimes in situ, sometimes in circumstances or reuse, sometimes already in the context of a modern collection. There follow other observations, culminating in the "last observed location" or "current location."

                                                                                                                                                                                    Following general TEI guidance, EpiDoc treats each such observation as a discrete event in space and time, and encodes each in a separate provenance element in the history section of the header. The type attribute is used with the following standard values to distinguish the major types of events:

                                                                                                                                                                                    • <provenance type="found"> is used to encode information about the first appearance, or key re-appearance, of the text-bearing object in modern times
                                                                                                                                                                                    • <provenance type="observed"> is used to encode information about subsequent modern observations
                                                                                                                                                                                    • <provenance type="not-observed"> is used to encode information about a specific, unsuccessful attempt to locate an object in a presumed or previously recorded location
                                                                                                                                                                                    • <provenance type="transferred"> is used to encode information about documentable modern relocations of the text-bearing object

                                                                                                                                                                                    NB: the old recommendation of <provenance type="autopsy"> as a special case of <provenance type="observed"> is now deprecated in favor of <provenance type="observed" subtype="autopsied">. See further, below.

                                                                                                                                                                                    Some print editions, databases, and active projects are able to provide even more detail concerning the nature of provenance events (e.g., whether a transfer was a simple move within an institution's storage areas or the transport of the object to another institution entirely). When it is desireable to encode such fine distinctions in a machine-actionable manner (e.g., for the creation of indices or for faceted search), the subtype attribute can be employed. The following standard values for subtype are suggested:

                                                                                                                                                                                    standard values for subtype on <provenance type="found">
                                                                                                                                                                                    • "discovered"
                                                                                                                                                                                    • "rediscovered"
                                                                                                                                                                                    • "first-seen"
                                                                                                                                                                                    • "first-recorded"
                                                                                                                                                                                    standard values for subtype on <provenance type="observed">
                                                                                                                                                                                    • "seen"
                                                                                                                                                                                    • "recorded"
                                                                                                                                                                                    • "identified"
                                                                                                                                                                                    • "photographed"
                                                                                                                                                                                    • "autopsied": an event during which the editor (i.e., the person creating the present edition) personally examined the object
                                                                                                                                                                                    • "squeeze-taken"
                                                                                                                                                                                    • "rubbing-taken"
                                                                                                                                                                                    • "ink-transfer-taken"
                                                                                                                                                                                    • "reported"
                                                                                                                                                                                    • "built-into"
                                                                                                                                                                                    • "reappeared"
                                                                                                                                                                                    standard values for subtype on <provenance type="not-observed">
                                                                                                                                                                                    • "lost"
                                                                                                                                                                                    • "stolen"
                                                                                                                                                                                    • "destroyed"
                                                                                                                                                                                    • "drawn"
                                                                                                                                                                                    • "reported-lost"
                                                                                                                                                                                    • "reported-stolen"
                                                                                                                                                                                    • "reported-destroyed"
                                                                                                                                                                                    standard values for subtype on <provenance type="transferred">
                                                                                                                                                                                    • "moved"
                                                                                                                                                                                    • "sold"
                                                                                                                                                                                    • "given"
                                                                                                                                                                                    • "loaned"

                                                                                                                                                                                    A general example is provided in the main section on Provenance of the text-bearing object. Specific guidance for each type of provenance event is provided in its own section as follows:

                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                    2. Simona Stoyanova, author
                                                                                                                                                                                    3. Tom Elliott, author
                                                                                                                                                                                    4. James Cowey, author
                                                                                                                                                                                    5. Scott Vanderbilt, author

                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                    \ No newline at end of file + customization: teiHeader

                                                                                                                                                                                  It is customary in producing an edition of a pre-modern manuscript, papyrus, inscription, or other text-bearing object to enumerate the occasions on which modern persons encountered and reported seminal information about the object, its condition and disposition, etc., together with associated bibliographic references where possible. The initial such observation is often the occasion of finding, sometimes in situ, sometimes in circumstances or reuse, sometimes already in the context of a modern collection. There follow other observations, culminating in the "last observed location" or "current location."

                                                                                                                                                                                  Following general TEI guidance, EpiDoc treats each such observation as a discrete event in space and time, and encodes each in a separate provenance element in the history section of the header. The type attribute is used with the following standard values to distinguish the major types of events:

                                                                                                                                                                                  • <provenance type="found"> is used to encode information about the first appearance, or key re-appearance, of the text-bearing object in modern times
                                                                                                                                                                                  • <provenance type="observed"> is used to encode information about subsequent modern observations
                                                                                                                                                                                  • <provenance type="not-observed"> is used to encode information about a specific, unsuccessful attempt to locate an object in a presumed or previously recorded location
                                                                                                                                                                                  • <provenance type="transferred"> is used to encode information about documentable modern relocations of the text-bearing object

                                                                                                                                                                                  NB: the old recommendation of <provenance type="autopsy"> as a special case of <provenance type="observed"> is now deprecated in favor of <provenance type="observed" subtype="autopsied">. See further, below.

                                                                                                                                                                                  Some print editions, databases, and active projects are able to provide even more detail concerning the nature of provenance events (e.g., whether a transfer was a simple move within an institution's storage areas or the transport of the object to another institution entirely). When it is desireable to encode such fine distinctions in a machine-actionable manner (e.g., for the creation of indices or for faceted search), the subtype attribute can be employed. The following standard values for subtype are suggested:

                                                                                                                                                                                  standard values for subtype on <provenance type="found">
                                                                                                                                                                                  • "discovered"
                                                                                                                                                                                  • "rediscovered"
                                                                                                                                                                                  • "first-seen"
                                                                                                                                                                                  • "first-recorded"
                                                                                                                                                                                  standard values for subtype on <provenance type="observed">
                                                                                                                                                                                  • "seen"
                                                                                                                                                                                  • "recorded"
                                                                                                                                                                                  • "identified"
                                                                                                                                                                                  • "photographed"
                                                                                                                                                                                  • "autopsied": an event during which the editor (i.e., the person creating the present edition) personally examined the object
                                                                                                                                                                                  • "squeeze-taken"
                                                                                                                                                                                  • "rubbing-taken"
                                                                                                                                                                                  • "ink-transfer-taken"
                                                                                                                                                                                  • "reported"
                                                                                                                                                                                  • "built-into"
                                                                                                                                                                                  • "reappeared"
                                                                                                                                                                                  standard values for subtype on <provenance type="not-observed">
                                                                                                                                                                                  • "lost"
                                                                                                                                                                                  • "stolen"
                                                                                                                                                                                  • "destroyed"
                                                                                                                                                                                  • "drawn"
                                                                                                                                                                                  • "reported-lost"
                                                                                                                                                                                  • "reported-stolen"
                                                                                                                                                                                  • "reported-destroyed"
                                                                                                                                                                                  standard values for subtype on <provenance type="transferred">
                                                                                                                                                                                  • "moved"
                                                                                                                                                                                  • "sold"
                                                                                                                                                                                  • "given"
                                                                                                                                                                                  • "loaned"

                                                                                                                                                                                  A general example is provided in the main section on Provenance of the text-bearing object. Specific guidance for each type of provenance event is provided in its own section as follows:

                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                                                  2. Simona Stoyanova, author
                                                                                                                                                                                  3. Tom Elliott, author
                                                                                                                                                                                  4. James Cowey, author
                                                                                                                                                                                  5. Scott Vanderbilt, author

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histmodern-pt-br.html b/gl/dev/supp-histmodern-pt-br.html index e06f169c7..7becc1815 100644 --- a/gl/dev/supp-histmodern-pt-br.html +++ b/gl/dev/supp-histmodern-pt-br.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                  Localização moderna ou última conhecida

                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                  Todos os assuntos relacionados à proveniência de um documento são codificados na parte Descrição de Manuscrito (msDesc) do header TEI. Mais especificamente, são colocados na subseção history (veja mais em seção geral sobre proveniência).

                                                                                                                                                                                  Elemento relevante de documentação (TEI):

                                                                                                                                                                                  • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                                                    Localização moderna ou última conhecida

                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                    Todos os assuntos relacionados à proveniência de um documento são codificados na parte Descrição de Manuscrito (msDesc) do header TEI. Mais especificamente, são colocados na subseção history (veja mais em seção geral sobre proveniência).

                                                                                                                                                                                    Elemento relevante de documentação (TEI):

                                                                                                                                                                                    Quando se produz uma edição acadêmica de um texto pré-moderno, muitas vezes é essencial codificar o que é conhecido a respeito do histórico moderno de observação e registro. O ideal seria que este histórico iniciasse com a descoberta do objeto portador de texto (findspot), detalhasse cada instância substantiva subsequente de relato e culminasse com um relato do último local conhecido ou observado. Tal histórico fornece insight importante sobre a possível localização original do objeto. Ele coloca tanto bibliografia publicada quanto materiais não publicados de arquivo (como cadernos de antigos viajantes) em uma sequência cronológica que algumas vezes é crucial para determinar as origens de leituras e adições variantes. O editor pode utilizar este histórico para sinalizar seus próprios momentos de interação com o objeto portador de texto e, juntamente com informação de inventário e depósito codificada em outras partes da edição, pode dar instrumentos ao leitor para que ele possa localizar, verificar e ir além da presente edição.

                                                                                                                                                                                    Exatamente como a descrição da descoberta e do local de descoberta, TEI/EpiDoc usa um elemento provenance separado para registrar cada instância subsequente de observação moderna, incluindo o "último local conhecido". Texto corrido em prosa pode ser utilizado, mas a melhor prática é marcar os componentes espaciais e temporais sempre que possível, de modo a facilitar precessamento futuro, criação de índices de busca e coisas semelhantes.

                                                                                                                                                                                    EpiDoc reconhece os seguintes valores para o atributo type em provenance:

                                                                                                                                                                                    • <provenance type="found"> é usado para codificar informação sobre a primeira aparição, ou reaparição chave, do objeto portador de texto em tempos modernos; veja Contexto de descoberta (Findspot)
                                                                                                                                                                                    • <provenance type="observed"> é usado para codificar informação sobre observações modernas subsequentes
                                                                                                                                                                                    • <provenance type="not-observed"> é utilizado para codificar informação sobre uma tentativa específica e mal sucedida de localizar um objeto em um local presumido ou previamente relatado
                                                                                                                                                                                    • <provenance type="transferred"> é utilizado para codificar informação sobre relocações modernas documentáveis do objeto portador de texto

                                                                                                                                                                                    Valores opcionais recomendados para subtype estão disponíveis, se houver necessidade de tornar computacionalmente práticas distinções entre diferentes circunstâncias de descoberta (veja a lista em Datas e locais de observações modernas). Obs.: a velha recomendação de <provenance type="autopsy"> como caso especial de <provenance type="observed"> foi agora descontinuada em favor de <provenance type="observed" subtype="autopsied">.

                                                                                                                                                                                    Aqui temos um exemplo adaptado de Inscriptions of Aphrodisias:

                                                                                                                                                                                    <history>
                                                                                                                                                                                     <origin>
                                                                                                                                                                                      <origDate evidence="reign titulature lettering"
                                                                                                                                                                                       datingMethod="http://en.wikipedia.org/wiki/Julian_calendarnotBefore-custom="0250-12"
                                                                                                                                                                                       notAfter-custom="0251-01">
                                                                                                                                                                                    December 250 - January
                                                                                                                                                                                         251</origDate>
                                                                                                                                                                                      <origPlace>Theatre of Aphrosidias: north parodos wall</origPlace>
                                                                                                                                                                                     </origin>
                                                                                                                                                                                     <provenance xml:id="copy-picenini"
                                                                                                                                                                                      type="foundnotBefore="1705-08-19"
                                                                                                                                                                                      notAfter="1705-08-23">
                                                                                                                                                                                    The first known copy of the inscription was made by
                                                                                                                                                                                       Picenini in 1705 (10102, 30v), whence Sherard (10101, 41). The stone was
                                                                                                                                                                                       evidently reused in the late antique construction of the city walls, having been
                                                                                                                                                                                       moved from from its original location at the theatre to its present location,
                                                                                                                                                                                       enmured in the western portion of the south wall of the city.</provenance>
                                                                                                                                                                                     <provenance xml:id="copy-wood"
                                                                                                                                                                                      type="observednotBefore="1750-10-01"
                                                                                                                                                                                      notAfter="1750-10-03">
                                                                                                                                                                                    Copied by Wood (14, f45v), but not published.</provenance>
                                                                                                                                                                                     <provenance xml:id="copy-raoul"
                                                                                                                                                                                      type="observednotAfter="1835">
                                                                                                                                                                                    Copied by
                                                                                                                                                                                       Raoul-Rochette.</provenance>
                                                                                                                                                                                     <provenance xml:id="copy-fellows"
                                                                                                                                                                                      type="observedwhen="1840">
                                                                                                                                                                                    Copied by
                                                                                                                                                                                       Fellows.</provenance>
                                                                                                                                                                                     <provenance xml:id="copy-loew"
                                                                                                                                                                                      type="observedwhen="1841">
                                                                                                                                                                                    Copied by
                                                                                                                                                                                       Loew.</provenance>
                                                                                                                                                                                     <provenance xml:id="copy-bailie"
                                                                                                                                                                                      type="observedwhen="1842">
                                                                                                                                                                                    Perhaps copied by
                                                                                                                                                                                       Bailie.</provenance>
                                                                                                                                                                                     <provenance xml:id="copy-waddington"
                                                                                                                                                                                      type="observedwhen="1850">
                                                                                                                                                                                    Copied by
                                                                                                                                                                                       Waddington.</provenance>
                                                                                                                                                                                     <provenance xml:id="record-gaudin"
                                                                                                                                                                                      type="observedwhen="1904">
                                                                                                                                                                                    Recorded by Gaudin
                                                                                                                                                                                       (142).</provenance>
                                                                                                                                                                                     <provenance xml:id="record-mama"
                                                                                                                                                                                      type="observedwhen="1934">
                                                                                                                                                                                    Recorded by the MAMA
                                                                                                                                                                                       Expedition.</provenance>
                                                                                                                                                                                     <provenance xml:id="record-nyu"
                                                                                                                                                                                      type="observedwhen="1965">
                                                                                                                                                                                    Recorded by the NYU
                                                                                                                                                                                       Expedition.</provenance>
                                                                                                                                                                                     <provenance xml:id="autopsy-reynolds"
                                                                                                                                                                                      type="autopsywhen="1982">
                                                                                                                                                                                    Text transcribed at
                                                                                                                                                                                       the findspot by Reynolds.</provenance>
                                                                                                                                                                                    </history>

                                                                                                                                                                                    Aqui um outro exemplo, adaptado de Corpus of the Inscriptions of Campā:

                                                                                                                                                                                    <history>
                                                                                                                                                                                     <origin>
                                                                                                                                                                                      <origPlace type="location">
                                                                                                                                                                                       <placeName type="temple"
                                                                                                                                                                                        ref="cic-geo:chien-dan">
                                                                                                                                                                                    Chiên Đàn</placeName>
                                                                                                                                                                                      </origPlace>
                                                                                                                                                                                      <origDate>
                                                                                                                                                                                       <date datingMethod="http://en.wikipedia.org/wiki/Julian_calendar"
                                                                                                                                                                                        notBefore-custom="1000notAfter-custom="1025">
                                                                                                                                                                                    early 11<hi rend="superscript">th</hi> century</date>
                                                                                                                                                                                       <note xml:space="preserve">We believe that this inscription is to be dated earlier than  + customization: teiHeader

                                                                                                                                                                                  Quando se produz uma edição acadêmica de um texto pré-moderno, muitas vezes é essencial codificar o que é conhecido a respeito do histórico moderno de observação e registro. O ideal seria que este histórico iniciasse com a descoberta do objeto portador de texto (findspot), detalhasse cada instância substantiva subsequente de relato e culminasse com um relato do último local conhecido ou observado. Tal histórico fornece insight importante sobre a possível localização original do objeto. Ele coloca tanto bibliografia publicada quanto materiais não publicados de arquivo (como cadernos de antigos viajantes) em uma sequência cronológica que algumas vezes é crucial para determinar as origens de leituras e adições variantes. O editor pode utilizar este histórico para sinalizar seus próprios momentos de interação com o objeto portador de texto e, juntamente com informação de inventário e depósito codificada em outras partes da edição, pode dar instrumentos ao leitor para que ele possa localizar, verificar e ir além da presente edição.

                                                                                                                                                                                  Exatamente como a descrição da descoberta e do local de descoberta, TEI/EpiDoc usa um elemento provenance separado para registrar cada instância subsequente de observação moderna, incluindo o "último local conhecido". Texto corrido em prosa pode ser utilizado, mas a melhor prática é marcar os componentes espaciais e temporais sempre que possível, de modo a facilitar precessamento futuro, criação de índices de busca e coisas semelhantes.

                                                                                                                                                                                  EpiDoc reconhece os seguintes valores para o atributo type em provenance:

                                                                                                                                                                                  • <provenance type="found"> é usado para codificar informação sobre a primeira aparição, ou reaparição chave, do objeto portador de texto em tempos modernos; veja Contexto de descoberta (Findspot)
                                                                                                                                                                                  • <provenance type="observed"> é usado para codificar informação sobre observações modernas subsequentes
                                                                                                                                                                                  • <provenance type="not-observed"> é utilizado para codificar informação sobre uma tentativa específica e mal sucedida de localizar um objeto em um local presumido ou previamente relatado
                                                                                                                                                                                  • <provenance type="transferred"> é utilizado para codificar informação sobre relocações modernas documentáveis do objeto portador de texto

                                                                                                                                                                                  Valores opcionais recomendados para subtype estão disponíveis, se houver necessidade de tornar computacionalmente práticas distinções entre diferentes circunstâncias de descoberta (veja a lista em Datas e locais de observações modernas). Obs.: a velha recomendação de <provenance type="autopsy"> como caso especial de <provenance type="observed"> foi agora descontinuada em favor de <provenance type="observed" subtype="autopsied">.

                                                                                                                                                                                  Aqui temos um exemplo adaptado de Inscriptions of Aphrodisias:

                                                                                                                                                                                  <history>
                                                                                                                                                                                   <origin>
                                                                                                                                                                                    <origDate evidence="reign titulature lettering"
                                                                                                                                                                                     datingMethod="http://en.wikipedia.org/wiki/Julian_calendarnotBefore-custom="0250-12"
                                                                                                                                                                                     notAfter-custom="0251-01">
                                                                                                                                                                                  December 250 - January
                                                                                                                                                                                       251</origDate>
                                                                                                                                                                                    <origPlace>Theatre of Aphrosidias: north parodos wall</origPlace>
                                                                                                                                                                                   </origin>
                                                                                                                                                                                   <provenance xml:id="copy-picenini"
                                                                                                                                                                                    type="foundnotBefore="1705-08-19"
                                                                                                                                                                                    notAfter="1705-08-23">
                                                                                                                                                                                  The first known copy of the inscription was made by
                                                                                                                                                                                     Picenini in 1705 (10102, 30v), whence Sherard (10101, 41). The stone was
                                                                                                                                                                                     evidently reused in the late antique construction of the city walls, having been
                                                                                                                                                                                     moved from from its original location at the theatre to its present location,
                                                                                                                                                                                     enmured in the western portion of the south wall of the city.</provenance>
                                                                                                                                                                                   <provenance xml:id="copy-wood"
                                                                                                                                                                                    type="observednotBefore="1750-10-01"
                                                                                                                                                                                    notAfter="1750-10-03">
                                                                                                                                                                                  Copied by Wood (14, f45v), but not published.</provenance>
                                                                                                                                                                                   <provenance xml:id="copy-raoul"
                                                                                                                                                                                    type="observednotAfter="1835">
                                                                                                                                                                                  Copied by
                                                                                                                                                                                     Raoul-Rochette.</provenance>
                                                                                                                                                                                   <provenance xml:id="copy-fellows"
                                                                                                                                                                                    type="observedwhen="1840">
                                                                                                                                                                                  Copied by
                                                                                                                                                                                     Fellows.</provenance>
                                                                                                                                                                                   <provenance xml:id="copy-loew"
                                                                                                                                                                                    type="observedwhen="1841">
                                                                                                                                                                                  Copied by
                                                                                                                                                                                     Loew.</provenance>
                                                                                                                                                                                   <provenance xml:id="copy-bailie"
                                                                                                                                                                                    type="observedwhen="1842">
                                                                                                                                                                                  Perhaps copied by
                                                                                                                                                                                     Bailie.</provenance>
                                                                                                                                                                                   <provenance xml:id="copy-waddington"
                                                                                                                                                                                    type="observedwhen="1850">
                                                                                                                                                                                  Copied by
                                                                                                                                                                                     Waddington.</provenance>
                                                                                                                                                                                   <provenance xml:id="record-gaudin"
                                                                                                                                                                                    type="observedwhen="1904">
                                                                                                                                                                                  Recorded by Gaudin
                                                                                                                                                                                     (142).</provenance>
                                                                                                                                                                                   <provenance xml:id="record-mama"
                                                                                                                                                                                    type="observedwhen="1934">
                                                                                                                                                                                  Recorded by the MAMA
                                                                                                                                                                                     Expedition.</provenance>
                                                                                                                                                                                   <provenance xml:id="record-nyu"
                                                                                                                                                                                    type="observedwhen="1965">
                                                                                                                                                                                  Recorded by the NYU
                                                                                                                                                                                     Expedition.</provenance>
                                                                                                                                                                                   <provenance xml:id="autopsy-reynolds"
                                                                                                                                                                                    type="autopsywhen="1982">
                                                                                                                                                                                  Text transcribed at
                                                                                                                                                                                     the findspot by Reynolds.</provenance>
                                                                                                                                                                                  </history>

                                                                                                                                                                                  Aqui um outro exemplo, adaptado de Corpus of the Inscriptions of Campā:

                                                                                                                                                                                  <history>
                                                                                                                                                                                   <origin>
                                                                                                                                                                                    <origPlace type="location">
                                                                                                                                                                                     <placeName type="temple"
                                                                                                                                                                                      ref="cic-geo:chien-dan">
                                                                                                                                                                                  Chiên Đàn</placeName>
                                                                                                                                                                                    </origPlace>
                                                                                                                                                                                    <origDate>
                                                                                                                                                                                     <date datingMethod="http://en.wikipedia.org/wiki/Julian_calendar"
                                                                                                                                                                                      notBefore-custom="1000notAfter-custom="1025">
                                                                                                                                                                                  early 11<hi rend="superscript">th</hi> century</date>
                                                                                                                                                                                     <note xml:space="preserve">We believe that this inscription is to be dated earlier than       previous scholars have assumed. See Cf. <bibl><ptr target="cic-bibl:ECIC-III"/>:       <biblScope>454 n. 36</biblScope></bibl>.</note>
                                                                                                                                                                                    </origDate>
                                                                                                                                                                                   </origin>
                                                                                                                                                                                   <provenance type="observed"
                                                                                                                                                                                    notAfter="1892">

                                                                                                                                                                                    <p xml:space="preserve">This boulder was found before 1892, when it was first mentioned       in the literature (<bibl><ptr target="cic-bibl:paris-1892"/>:  @@ -54,4 +54,4 @@      because Camille Paris himself, in the first ever report of the inscription, clearly states       that the stone was already broken in three pieces when he found it. For reasons unknown to       us, this report is not cited in any of the publications of Parmentier and Cœdès, and could  -     thus come to be forgotten by subsequent generations of scholars.</note>
                                                                                                                                                                                    </p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                  </history>

                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                  1. autor, Tom Elliott
                                                                                                                                                                                  2. autor, Gabriel Bodard
                                                                                                                                                                                  3. autor, Charlotte Roueché
                                                                                                                                                                                  4. autor, Arlo Griffiths
                                                                                                                                                                                  5. James Cowey, autor
                                                                                                                                                                                  6. Scott Vanderbilt, autor
                                                                                                                                                                                  7. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                  \ No newline at end of file +     thus come to be forgotten by subsequent generations of scholars.</note>
                                                                                                                                                                                    </p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                  </history>

                                                                                                                                                                                  See also:

                                                                                                                                                                                  Other pages describing <history>:

                                                                                                                                                                                  Other pages describing <msDesc>:

                                                                                                                                                                                  Other pages describing <provenance>:

                                                                                                                                                                                  Other pages describing <teiHeader>:

                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                  1. autor, Tom Elliott
                                                                                                                                                                                  2. autor, Gabriel Bodard
                                                                                                                                                                                  3. autor, Charlotte Roueché
                                                                                                                                                                                  4. autor, Arlo Griffiths
                                                                                                                                                                                  5. James Cowey, autor
                                                                                                                                                                                  6. Scott Vanderbilt, autor
                                                                                                                                                                                  7. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-histmodern.html b/gl/dev/supp-histmodern.html index f56309a83..339f361c1 100644 --- a/gl/dev/supp-histmodern.html +++ b/gl/dev/supp-histmodern.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                  Modern or last known locations

                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                  All matters related to the provenance of a document are encoded in the Manuscript Description (msDesc) portion of the TEI header. In particular, they are placed within the history subsection (see further the general section on provenance).

                                                                                                                                                                                  Relevant element documentation (TEI):

                                                                                                                                                                                  • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                                                    Modern or last known locations

                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                    All matters related to the provenance of a document are encoded in the Manuscript Description (msDesc) portion of the TEI header. In particular, they are placed within the history subsection (see further the general section on provenance).

                                                                                                                                                                                    Relevant element documentation (TEI):

                                                                                                                                                                                    When producing a scholarly edition of a pre-modern text, it is often essential to encode what is known about the modern history of observation and recording, as well as transactions involving the object. Ideally, this account begins with the discovery of the text-bearing object (findspot), details each substantive subsequent instance of reporting, and culminates in a report of the last-known or last-observed location. Such a history can provide important insight into the likely original location of the object. It places both published bibliography and unpublished archival materials (such as early travelers' notebooks) into a chronological sequence that is sometimes crucial to determining the origins of variant readings and supplements. The editor can use this history to signal her own moments of interaction with the text-bearing object and, in conjunction with inventory and repository information encoded elsewhere in the edition, can equip the reader with the ability to locate, verify, and build upon the present edition.

                                                                                                                                                                                    Just like the description of discovery and place of finding, TEI/EpiDoc uses a separate provenance element to record each subsequent instance of modern observation, including the final "last known location". Extended prose can be used, but it is best practice to markup the spatial and temporal components wherever possible in order to facilitate subsequent processing, search index creation, and the like.

                                                                                                                                                                                    EpiDoc recognizes the following values for the type attribute on provenance:

                                                                                                                                                                                    • <provenance type="found"> is used to encode information about the first appearance, or key re-appearance, of the text-bearing object in modern times; see Findspot and find context
                                                                                                                                                                                    • <provenance type="observed"> is used to encode information about subsequent modern observations
                                                                                                                                                                                    • <provenance type="not-observed"> is used to encode information about a specific, unsuccessful attempt to locate an object in a presumed or previously recorded location
                                                                                                                                                                                    • <provenance type="transferred"> is used to encode information about documentable modern relocations of the text-bearing object

                                                                                                                                                                                    Recommended, optional values for subtype are available if there is a need to make computationally actionable distinctions between different circumstances of finding (see list in Dates and locations of modern observations). NB: the old recommendation of <provenance type="autopsy"> as a special case of <provenance type="observed"> is now deprecated in favor of <provenance type="observed" subtype="autopsied">.

                                                                                                                                                                                    The following values are recommended for subtype when using <provenance type="transferred">.

                                                                                                                                                                                    • "moved"
                                                                                                                                                                                    • "sold"
                                                                                                                                                                                    • "given"
                                                                                                                                                                                    • "loaned"
                                                                                                                                                                                    • "purchased"
                                                                                                                                                                                    • "acquired"
                                                                                                                                                                                    • "donated"

                                                                                                                                                                                    Here is an example adapted from the Inscriptions of Aphrodisias:

                                                                                                                                                                                    <history> + customization: provenance

                                                                                                                                                                                  When producing a scholarly edition of a pre-modern text, it is often essential to encode what is known about the modern history of observation and recording, as well as transactions involving the object. Ideally, this account begins with the discovery of the text-bearing object (findspot), details each substantive subsequent instance of reporting, and culminates in a report of the last-known or last-observed location. Such a history can provide important insight into the likely original location of the object. It places both published bibliography and unpublished archival materials (such as early travelers' notebooks) into a chronological sequence that is sometimes crucial to determining the origins of variant readings and supplements. The editor can use this history to signal her own moments of interaction with the text-bearing object and, in conjunction with inventory and repository information encoded elsewhere in the edition, can equip the reader with the ability to locate, verify, and build upon the present edition.

                                                                                                                                                                                  Just like the description of discovery and place of finding, TEI/EpiDoc uses a separate provenance element to record each subsequent instance of modern observation, including the final "last known location". Extended prose can be used, but it is best practice to markup the spatial and temporal components wherever possible in order to facilitate subsequent processing, search index creation, and the like.

                                                                                                                                                                                  EpiDoc recognizes the following values for the type attribute on provenance:

                                                                                                                                                                                  • <provenance type="found"> is used to encode information about the first appearance, or key re-appearance, of the text-bearing object in modern times; see Findspot and find context
                                                                                                                                                                                  • <provenance type="observed"> is used to encode information about subsequent modern observations
                                                                                                                                                                                  • <provenance type="not-observed"> is used to encode information about a specific, unsuccessful attempt to locate an object in a presumed or previously recorded location
                                                                                                                                                                                  • <provenance type="transferred"> is used to encode information about documentable modern relocations of the text-bearing object

                                                                                                                                                                                  Recommended, optional values for subtype are available if there is a need to make computationally actionable distinctions between different circumstances of finding (see list in Dates and locations of modern observations). NB: the old recommendation of <provenance type="autopsy"> as a special case of <provenance type="observed"> is now deprecated in favor of <provenance type="observed" subtype="autopsied">.

                                                                                                                                                                                  The following values are recommended for subtype when using <provenance type="transferred">.

                                                                                                                                                                                  • "moved"
                                                                                                                                                                                  • "sold"
                                                                                                                                                                                  • "given"
                                                                                                                                                                                  • "loaned"
                                                                                                                                                                                  • "purchased"
                                                                                                                                                                                  • "acquired"
                                                                                                                                                                                  • "donated"

                                                                                                                                                                                  Here is an example adapted from the Inscriptions of Aphrodisias:

                                                                                                                                                                                  <history>    <origin>   <origDate evidence="reign titulature lettering"
                                                                                                                                                                                   datingMethod="http://en.wikipedia.org/wiki/Julian_calendarnotBefore-custom="0250-12"
                                                                                                                                                                                   notAfter-custom="0251-01">
                                                                                                                                                                                  December 250 - January 251</origDate> @@ -58,7 +58,7 @@  <provenance xml:id="autopsy-reynolds"
                                                                                                                                                                                   type="autopsywhen="1982">
                                                                                                                                                                                  Text transcribed at the findspot by Reynolds.</provenance>    </history> -

                                                                                                                                                                                  Here is another example, adapted from the Corpus of the Inscriptions of Campā:

                                                                                                                                                                                  <history> +

                                                                                                                                                                                  Here is another example, adapted from the Corpus of the Inscriptions of Campā:

                                                                                                                                                                                  <history>  <origin>   <origPlace type="location"> @@ -123,4 +123,4 @@      thus come to be forgotten by subsequent generations of scholars.</note></p>  </provenance> </history> -

                                                                                                                                                                                  Here is an example from the US Epigraphy Project showing a series of transfers of ownership and marking transaction details such as names and roles of responsible parties.

                                                                                                                                                                                  <history>
                                                                                                                                                                                   <origin>
                                                                                                                                                                                    <date evidence="#formulae #palaeography"
                                                                                                                                                                                     notBefore="0075notAfter="0125">
                                                                                                                                                                                  late
                                                                                                                                                                                       first-early second century CE</date>
                                                                                                                                                                                    <placeName ref="europe.italy.rome">Italy, Rome, Porta Salaria</placeName>
                                                                                                                                                                                   </origin>
                                                                                                                                                                                   <provenance type="found"
                                                                                                                                                                                    subtype="discovered">

                                                                                                                                                                                    <p>Reportedly found in <date when="1886">1886</date> in a graveyard outside the Porta Salaria between the Via Salaria and the Via Pinciana</p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                   <provenance type="transferred"
                                                                                                                                                                                    subtype="purchased">

                                                                                                                                                                                    <p>purchased in <placeName>Rome</placeName> by <persName role="purchaser">
                                                                                                                                                                                      <name key="Clifford Moore">Clifford Moore</name>
                                                                                                                                                                                     </persName> for the <orgName>Harvard Department of Classics</orgName>, <date notBefore="1905notAfter="1906">1905-1906</date>
                                                                                                                                                                                    </p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                   <provenance type="transferred"
                                                                                                                                                                                    subtype="moved">

                                                                                                                                                                                    <p>internally transferred from the <orgName>Harvard Department of Classics</orgName> to the <orgName>Sackler Museum</orgName>, <date when="1977">1977</date>
                                                                                                                                                                                    </p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                  </history>

                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                  1. Tom Elliott, author
                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                  3. Charlotte Roueché, author
                                                                                                                                                                                  4. Arlo Griffiths, author
                                                                                                                                                                                  5. James Cowey, author
                                                                                                                                                                                  6. Scott Vanderbilt, author
                                                                                                                                                                                  7. Scott DiGiulio, author
                                                                                                                                                                                  8. Elli Mylonas, author

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                  Here is an example from the US Epigraphy Project showing a series of transfers of ownership and marking transaction details such as names and roles of responsible parties.

                                                                                                                                                                                  <history>
                                                                                                                                                                                   <origin>
                                                                                                                                                                                    <date evidence="#formulae #palaeography"
                                                                                                                                                                                     notBefore="0075notAfter="0125">
                                                                                                                                                                                  late
                                                                                                                                                                                       first-early second century CE</date>
                                                                                                                                                                                    <placeName ref="europe.italy.rome">Italy, Rome, Porta Salaria</placeName>
                                                                                                                                                                                   </origin>
                                                                                                                                                                                   <provenance type="found"
                                                                                                                                                                                    subtype="discovered">

                                                                                                                                                                                    <p>Reportedly found in <date when="1886">1886</date> in a graveyard outside the Porta Salaria between the Via Salaria and the Via Pinciana</p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                   <provenance type="transferred"
                                                                                                                                                                                    subtype="purchased">

                                                                                                                                                                                    <p>purchased in <placeName>Rome</placeName> by <persName role="purchaser">
                                                                                                                                                                                      <name key="Clifford Moore">Clifford Moore</name>
                                                                                                                                                                                     </persName> for the <orgName>Harvard Department of Classics</orgName>, <date notBefore="1905notAfter="1906">1905-1906</date>
                                                                                                                                                                                    </p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                   <provenance type="transferred"
                                                                                                                                                                                    subtype="moved">

                                                                                                                                                                                    <p>internally transferred from the <orgName>Harvard Department of Classics</orgName> to the <orgName>Sackler Museum</orgName>, <date when="1977">1977</date>
                                                                                                                                                                                    </p>
                                                                                                                                                                                   </provenance>
                                                                                                                                                                                  </history>

                                                                                                                                                                                  See also:

                                                                                                                                                                                  Other pages describing <history>:

                                                                                                                                                                                  Other pages describing <origin>:

                                                                                                                                                                                  Other pages describing <provenance>:

                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                  1. Tom Elliott, author
                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                  3. Charlotte Roueché, author
                                                                                                                                                                                  4. Arlo Griffiths, author
                                                                                                                                                                                  5. James Cowey, author
                                                                                                                                                                                  6. Scott Vanderbilt, author
                                                                                                                                                                                  7. Scott DiGiulio, author
                                                                                                                                                                                  8. Elli Mylonas, author

                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-historigdate-pt-br.html b/gl/dev/supp-historigdate-pt-br.html index 7136a4728..9a38e2df8 100644 --- a/gl/dev/supp-historigdate-pt-br.html +++ b/gl/dev/supp-historigdate-pt-br.html @@ -21,13 +21,13 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                  Data original do texto e/ou objeto

                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                  Esta seção das Normas EpiDoc fornece orientação sobre a codificação da data de origem do texto (ou, em alguns casos, do objeto ou alguma outra característica, decoração ou reuso deste), seja ela resultado da análise do editor ou uma data interna explícita. Também se fornece orientação sobre o registro de possíveis intervalos de datas, períodos históricos citados, graus de precisão e critérios de datação.

                                                                                                                                                                                  Elemento relevante de documentação (TEI):

                                                                                                                                                                                  • TEI definition: origDate ; EpiDoc-specific +

                                                                                                                                                                                    Data original do texto e/ou objeto

                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                    Esta seção das Normas EpiDoc fornece orientação sobre a codificação da data de origem do texto (ou, em alguns casos, do objeto ou alguma outra característica, decoração ou reuso deste), seja ela resultado da análise do editor ou uma data interna explícita. Também se fornece orientação sobre o registro de possíveis intervalos de datas, períodos históricos citados, graus de precisão e critérios de datação.

                                                                                                                                                                                    Elemento relevante de documentação (TEI):

                                                                                                                                                                                    A data de origem do texto (ou do objeto, se diferentes) deve ser registrada em um elemento origDate na seção origin da área de descrição do manuscrito (veja a seção geral sobre proveniência para contextualização). Se for preciso registrar datas diferentes para o texto e o objeto, ou para textos diferentes no mesmo suporte, ou diferentes intervenções no mesmo texto, o elemento origDate pode ser repetido, ou todo o history pode ser embutido em múltiplos msPart.

                                                                                                                                                                                    Geralmente se recomenda que a informação sobre data seja embutida em forma numérica, seguindo o antigo calendário juliano, usando os atributos att.datable.custom no elemento origDate. Estes atributros de data "customizados" são necessários porque o sistema default de datação presumido pelos atributos de datação básicos TEI (att.datable) é o calendário gregoriano. Portanto, além disto, o elemento de datação deve sempre conter um atributo datingMethod que aponte para um elemento calendar no header-- ou para uma autoridade externa para o calendário juliano, como http://en.wikipedia.org/wiki/Julian_calendar.

                                                                                                                                                                                    Uma data específica, seja ela um único dia, um mês ou um ano no calendario juliano, pode ser expressa com o uso do atributo when-custom, que deve ser organizado no mesmo formato de uma data ISO 8601/W3C (apesar de ser no calendário juliano, não gregoriano). Em outras palavras:

                                                                                                                                                                                    1. Um ano deve ser codificado em quatro dígitos, adicionando zeros à esquerda, se necessário (por exemplo, 14 C.E. deve ser "0014")
                                                                                                                                                                                    2. Datas B.C.E./B.C. devem ser registradas como números negativos (isto é, precedidos do sinal "-"); Nota: não existe ano "0"
                                                                                                                                                                                    3. Mês e dia devem ser codificados em dois dígitos, com um zero à esquerda se necessário (isto é, sete de janeiro deve ser "--01-07")
                                                                                                                                                                                    4. Um ano pode aparecer sem meses ou dia; um ano+mês pode aparecer sem dia

                                                                                                                                                                                    Intervalo de datas

                                                                                                                                                                                    Uma data que ocorre dentro de um intervalo (um evento que ocorre dentro do reino de um imperador, como por exemplo o levantamento de um marco miliário; ou um século para, por exemplo, texto datado paleograficamente) deve ser codificada com o uso dos atributos notBefore-custom e notAfter-custom, que marcam o início e o fim de um possível intervalo de datas. Os formatos de data destes atributos são os mesmos que para when-custom.

                                                                                                                                                                                    Este exemplo codifica uma data juliana simples:

                                                                                                                                                                                    <origDate when-custom="0139"
                                                                                                                                                                                     datingMethod="#julian">
                                                                                                                                                                                    139 C.E.</origDate>

                                                                                                                                                                                    Este exemplo codifica uma data que ocorre dentro de um intervalo, novamente no calendário juliano:

                                                                                                                                                                                    <origDate notBefore-custom="-0020-12-11"
                                                                                                                                                                                     notAfter-custom="-0019-12-10datingMethod="#julian">
                                                                                                                                                                                    December 11th, 20 to December 10th, 19 B.C.E.</origDate>

                                                                                                                                                                                    Este exemplo utiliza atributos de datação no elemento origDate para expressar uma data no calendário juliano que deriva de uma data registrada em uma inscrição na era Śaka. (O atributo calendar registra o sistema de calendário da data registrada por este elemento, enquanto que datingMethod registra o sistema pelo qual esta data é normatizada nos atributos xx-custom. Sem isto, a normatização presumida seria a do calendário gregoriano.)

                                                                                                                                                                                    <origDate notBefore-custom="1409"
                                                                                                                                                                                     notAfter-custom="1410"
                                                                                                                                                                                     datingMethod="http://en.wikipedia.org/wiki/Julian_calendar">
                                                                                                                                                                                    The text records a composition  + customization: precision

                                                                                                                                                                                  A data de origem do texto (ou do objeto, se diferentes) deve ser registrada em um elemento origDate na seção origin da área de descrição do manuscrito (veja a seção geral sobre proveniência para contextualização). Se for preciso registrar datas diferentes para o texto e o objeto, ou para textos diferentes no mesmo suporte, ou diferentes intervenções no mesmo texto, o elemento origDate pode ser repetido, ou todo o history pode ser embutido em múltiplos msPart.

                                                                                                                                                                                  Geralmente se recomenda que a informação sobre data seja embutida em forma numérica, seguindo o antigo calendário juliano, usando os atributos att.datable.custom no elemento origDate. Estes atributros de data "customizados" são necessários porque o sistema default de datação presumido pelos atributos de datação básicos TEI (att.datable) é o calendário gregoriano. Portanto, além disto, o elemento de datação deve sempre conter um atributo datingMethod que aponte para um elemento calendar no header-- ou para uma autoridade externa para o calendário juliano, como http://en.wikipedia.org/wiki/Julian_calendar.

                                                                                                                                                                                  Uma data específica, seja ela um único dia, um mês ou um ano no calendario juliano, pode ser expressa com o uso do atributo when-custom, que deve ser organizado no mesmo formato de uma data ISO 8601/W3C (apesar de ser no calendário juliano, não gregoriano). Em outras palavras:

                                                                                                                                                                                  1. Um ano deve ser codificado em quatro dígitos, adicionando zeros à esquerda, se necessário (por exemplo, 14 C.E. deve ser "0014")
                                                                                                                                                                                  2. Datas B.C.E./B.C. devem ser registradas como números negativos (isto é, precedidos do sinal "-"); Nota: não existe ano "0"
                                                                                                                                                                                  3. Mês e dia devem ser codificados em dois dígitos, com um zero à esquerda se necessário (isto é, sete de janeiro deve ser "--01-07")
                                                                                                                                                                                  4. Um ano pode aparecer sem meses ou dia; um ano+mês pode aparecer sem dia

                                                                                                                                                                                  Intervalo de datas

                                                                                                                                                                                  Uma data que ocorre dentro de um intervalo (um evento que ocorre dentro do reino de um imperador, como por exemplo o levantamento de um marco miliário; ou um século para, por exemplo, texto datado paleograficamente) deve ser codificada com o uso dos atributos notBefore-custom e notAfter-custom, que marcam o início e o fim de um possível intervalo de datas. Os formatos de data destes atributos são os mesmos que para when-custom.

                                                                                                                                                                                  Este exemplo codifica uma data juliana simples:

                                                                                                                                                                                  <origDate when-custom="0139"
                                                                                                                                                                                   datingMethod="#julian">
                                                                                                                                                                                  139 C.E.</origDate>

                                                                                                                                                                                  Este exemplo codifica uma data que ocorre dentro de um intervalo, novamente no calendário juliano:

                                                                                                                                                                                  <origDate notBefore-custom="-0020-12-11"
                                                                                                                                                                                   notAfter-custom="-0019-12-10datingMethod="#julian">
                                                                                                                                                                                  December 11th, 20 to December 10th, 19 B.C.E.</origDate>

                                                                                                                                                                                  Este exemplo utiliza atributos de datação no elemento origDate para expressar uma data no calendário juliano que deriva de uma data registrada em uma inscrição na era Śaka. (O atributo calendar registra o sistema de calendário da data registrada por este elemento, enquanto que datingMethod registra o sistema pelo qual esta data é normatizada nos atributos xx-custom. Sem isto, a normatização presumida seria a do calendário gregoriano.)

                                                                                                                                                                                  <origDate notBefore-custom="1409"
                                                                                                                                                                                   notAfter-custom="1410"
                                                                                                                                                                                   datingMethod="http://en.wikipedia.org/wiki/Julian_calendar">
                                                                                                                                                                                  The text records a composition                     date of <date calendar="http://en.wikipedia.org/wiki/Shalivahana_era">1331</date>(Śaka)</origDate> -            

                                                                                                                                                                                  Certeza e precisão

                                                                                                                                                                                  Nem todos os textos são datados com segurança em um ano específico ou num firme intervalo de anos. Se uma data dada for explicitamente marcada como menos certa que o habitual (por exemplo, uma "?" ou uma formulação como "possivelmente") o origDate pode receber um atributo cert com um valor "low". Se uma data é aproximada (que é algo diferente de incerta, muitas vezes escrita com um "cerca", "ca." or "c.") origDate deve receber um atributo precision com o valor "low". Se um intervalo de data for especificado (com notBefore-custom e notAfter-custom) com datas de início e fim que são essencialmente arbritárias, como um século ou meio século para uma data paleológica, então deve-se dar um valor "medium" para precision, para indicar que os pontos de início e fim são apenas teóricos.

                                                                                                                                                                                  Em alguns casos, um texto pode ser datado dentro de um intervalo de datas com um fim teórico mas com um firme terminus post quem. Para registrar isto em XML, um elemento precision pode ser colocado dentro de origDate para apontar quais dos atributos representa o ponto final menos concreto. (Veja o terceiro exemplo abaixo)

                                                                                                                                                                                  <origDate notBefore-custom="-0100"
                                                                                                                                                                                   notAfter-custom="0100precision="mediumdatingMethod="#julian">
                                                                                                                                                                                  First century B.C. to first century A.D. </origDate>
                                                                                                                                                                                  <origDate when-custom="-0355"
                                                                                                                                                                                   precision="lowdatingMethod="#julian">
                                                                                                                                                                                  Circa 355
                                                                                                                                                                                  B.C.E. </origDate>
                                                                                                                                                                                  <origDate notBefore-custom="0015"
                                                                                                                                                                                   notAfter-custom="0050datingMethod="#julian">
                                                                                                                                                                                  First half first century C.E., but certainly after the death of Augustus.  +            

                                                                                                                                                                                  Certeza e precisão

                                                                                                                                                                                  Nem todos os textos são datados com segurança em um ano específico ou num firme intervalo de anos. Se uma data dada for explicitamente marcada como menos certa que o habitual (por exemplo, uma "?" ou uma formulação como "possivelmente") o origDate pode receber um atributo cert com um valor "low". Se uma data é aproximada (que é algo diferente de incerta, muitas vezes escrita com um "cerca", "ca." or "c.") origDate deve receber um atributo precision com o valor "low". Se um intervalo de data for especificado (com notBefore-custom e notAfter-custom) com datas de início e fim que são essencialmente arbritárias, como um século ou meio século para uma data paleológica, então deve-se dar um valor "medium" para precision, para indicar que os pontos de início e fim são apenas teóricos.

                                                                                                                                                                                  Em alguns casos, um texto pode ser datado dentro de um intervalo de datas com um fim teórico mas com um firme terminus post quem. Para registrar isto em XML, um elemento precision pode ser colocado dentro de origDate para apontar quais dos atributos representa o ponto final menos concreto. (Veja o terceiro exemplo abaixo)

                                                                                                                                                                                  <origDate notBefore-custom="-0100"
                                                                                                                                                                                   notAfter-custom="0100precision="mediumdatingMethod="#julian">
                                                                                                                                                                                  First century B.C. to first century A.D. </origDate>
                                                                                                                                                                                  <origDate when-custom="-0355"
                                                                                                                                                                                   precision="lowdatingMethod="#julian">
                                                                                                                                                                                  Circa 355
                                                                                                                                                                                  B.C.E. </origDate>
                                                                                                                                                                                  <origDate notBefore-custom="0015"
                                                                                                                                                                                   notAfter-custom="0050datingMethod="#julian">
                                                                                                                                                                                  First half first century C.E., but certainly after the death of Augustus.    <precision match="../@notBefore-custom"
                                                                                                                                                                                   precision="high"/>
                                                                                                                                                                                    <precision match="../@notAfter-custom"
                                                                                                                                                                                   precision="medium"/>
                                                                                                                                                                                  </origDate> -

                                                                                                                                                                                  Você pode alinhar suas definições, alinhando-as a um Vocabulário controlado local ou externo.

                                                                                                                                                                                  Períodos históricos com nomes

                                                                                                                                                                                  Em alguns casos, em vez de (ou além de) um intervalo numérico de datas, específico ou aproximado, pesquisadores vão datar uma inscrição por um período histórico com nome, como "helenístico", "imperial," "bizantino" ou "período arcaico". Se desejado, o período histórico pode ser codificado no elemento origDate com o uso do atributo period, apontando para o URI de um vocabulário para períodos históricos como o PeriodO ou uma página da Wikidata. (Este período não precisa corresponder exatamente ao intervalo numérico fornecido, se se existe um).

                                                                                                                                                                                  <origDate notBefore="-0332"
                                                                                                                                                                                   notAfter="-0200precision="medium"
                                                                                                                                                                                   period="http://n2t.net/ark:/99152/p0m63njc4hdevidence="lettering">
                                                                                                                                                                                  Early
                                                                                                                                                                                  Hellenistic (lettering)</origDate>
                                                                                                                                                                                  <origDate when="-3000precision="low"
                                                                                                                                                                                   period="https://www.wikidata.org/wiki/Q187979evidence="context">
                                                                                                                                                                                  Early
                                                                                                                                                                                  Dynastic Period (context)</origDate>

                                                                                                                                                                                  Critérios de datação

                                                                                                                                                                                  Os critérios de datação dados no elemento origDate podem ser expressos através do atributo evidence. Os conteúdos deste atributo devem ser considerados como uma série de tokens com espaços delimitados em vez de uma frase de texto em prosa. Isto significa, por exemplo, que se a datação de uma inscrição depende do estilo de letra, da nomenclatura e parcialmente do contexto arqueológico, em vez de codificar isto como <origDate evidence="lettering, nomenclature and partly archaeological context"> é mais apropriado escrever: <origDate evidence="lettering nomenclature archaeological_context">. Note que, por serem valores com espaços delimitados nesta lista, quaisquer valores que sejam frases de mais de uma palavra devem ter algum símbolo, muito provavelmente o subscrito '_' no lugar do espaço. A maioria dos projetos vai achar útil ter uma tipologia de critérios com um vocabulário controlado de valores para os termos neste atributo.

                                                                                                                                                                                  O schema EpiDoc sugere uma pequena lista de valores para o atributro evidence, para encorajar a consistência. Estes valores são: lettering; nomenclature; prosopography; reign; titulature; internal-date; context.

                                                                                                                                                                                  Como estas são apenas sugestões, não existe proibição contra qualquer projeto que use, por exemplo, "palaeography" no lugar de lettering, ou "onomastics" em vez de nomenclature; o mais eficaz, entretanto, seria manter uma tabela interna de termos de critérios de datação, com os termos mapeados para linguagem humana (que pode, por exemplo, não ser inglês). A maioria dos projetos vai desejar adicionar valores a esta lista; muitos podem, por exemplo, subdividir o termo "context" em subcategorias como "archaeological context", "architectural context", "epigraphic context", "historical context".

                                                                                                                                                                                  Cf.

                                                                                                                                                                                  <origDate notBefore-custom="0367"
                                                                                                                                                                                   notAfter-custom="0400precision="medium"
                                                                                                                                                                                   evidence="lettering nomenclaturedatingMethod="#julian">
                                                                                                                                                                                  Late fourth century
                                                                                                                                                                                  (lettering and nomenclature).</origDate>

                                                                                                                                                                                  This example encodes a certain date within a particular consular year:

                                                                                                                                                                                  <origDate when-custom="0152-08-23"
                                                                                                                                                                                   precision="highevidence="consulship"
                                                                                                                                                                                   datingMethod="#julian">
                                                                                                                                                                                  23 August 152 C.E.</origDate>
                                                                                                                                                                                  <!-- ... Glabrione et H[om]ulo co(n)s(ulibus) (a(nte) d(iem)) X K(alendas) Sept(embres) - (RIB 309) -->

                                                                                                                                                                                  See also:

                                                                                                                                                                                  Other pages describing <origDate>:

                                                                                                                                                                                  Other pages describing <precision>:

                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                    2. Scott Vanderbilt, autor
                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                    Você pode alinhar suas definições, alinhando-as a um Vocabulário controlado local ou externo.

                                                                                                                                                                                    Períodos históricos com nomes

                                                                                                                                                                                    Em alguns casos, em vez de (ou além de) um intervalo numérico de datas, específico ou aproximado, pesquisadores vão datar uma inscrição por um período histórico com nome, como "helenístico", "imperial," "bizantino" ou "período arcaico". Se desejado, o período histórico pode ser codificado no elemento origDate com o uso do atributo period, apontando para o URI de um vocabulário para períodos históricos como o PeriodO ou uma página da Wikidata. (Este período não precisa corresponder exatamente ao intervalo numérico fornecido, se se existe um).

                                                                                                                                                                                    <origDate notBefore="-0332"
                                                                                                                                                                                     notAfter="-0200precision="medium"
                                                                                                                                                                                     period="http://n2t.net/ark:/99152/p0m63njc4hdevidence="lettering">
                                                                                                                                                                                    Early
                                                                                                                                                                                    Hellenistic (lettering)</origDate>
                                                                                                                                                                                    <origDate when="-3000precision="low"
                                                                                                                                                                                     period="https://www.wikidata.org/wiki/Q187979evidence="context">
                                                                                                                                                                                    Early
                                                                                                                                                                                    Dynastic Period (context)</origDate>

                                                                                                                                                                                    Critérios de datação

                                                                                                                                                                                    Os critérios de datação dados no elemento origDate podem ser expressos através do atributo evidence. Os conteúdos deste atributo devem ser considerados como uma série de tokens com espaços delimitados em vez de uma frase de texto em prosa. Isto significa, por exemplo, que se a datação de uma inscrição depende do estilo de letra, da nomenclatura e parcialmente do contexto arqueológico, em vez de codificar isto como <origDate evidence="lettering, nomenclature and partly archaeological context"> é mais apropriado escrever: <origDate evidence="lettering nomenclature archaeological_context">. Note que, por serem valores com espaços delimitados nesta lista, quaisquer valores que sejam frases de mais de uma palavra devem ter algum símbolo, muito provavelmente o subscrito '_' no lugar do espaço. A maioria dos projetos vai achar útil ter uma tipologia de critérios com um vocabulário controlado de valores para os termos neste atributo.

                                                                                                                                                                                    O schema EpiDoc sugere uma pequena lista de valores para o atributro evidence, para encorajar a consistência. Estes valores são: lettering; nomenclature; prosopography; reign; titulature; internal-date; context.

                                                                                                                                                                                    Como estas são apenas sugestões, não existe proibição contra qualquer projeto que use, por exemplo, "palaeography" no lugar de lettering, ou "onomastics" em vez de nomenclature; o mais eficaz, entretanto, seria manter uma tabela interna de termos de critérios de datação, com os termos mapeados para linguagem humana (que pode, por exemplo, não ser inglês). A maioria dos projetos vai desejar adicionar valores a esta lista; muitos podem, por exemplo, subdividir o termo "context" em subcategorias como "archaeological context", "architectural context", "epigraphic context", "historical context".

                                                                                                                                                                                    Cf.

                                                                                                                                                                                    <origDate notBefore-custom="0367"
                                                                                                                                                                                     notAfter-custom="0400precision="medium"
                                                                                                                                                                                     evidence="lettering nomenclaturedatingMethod="#julian">
                                                                                                                                                                                    Late fourth century
                                                                                                                                                                                    (lettering and nomenclature).</origDate>

                                                                                                                                                                                    This example encodes a certain date within a particular consular year:

                                                                                                                                                                                    <origDate when-custom="0152-08-23"
                                                                                                                                                                                     precision="highevidence="consulship"
                                                                                                                                                                                     datingMethod="#julian">
                                                                                                                                                                                    23 August 152 C.E.</origDate>
                                                                                                                                                                                    <!-- ... Glabrione et H[om]ulo co(n)s(ulibus) (a(nte) d(iem)) X K(alendas) Sept(embres) + (RIB 309) -->

                                                                                                                                                                                    See also:

                                                                                                                                                                                    Other pages describing <origDate>:

                                                                                                                                                                                    Other pages describing <precision>:

                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                    2. Scott Vanderbilt, autor
                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/supp-historigdate.html b/gl/dev/supp-historigdate.html index 1b1ba91f5..c71f7e35c 100644 --- a/gl/dev/supp-historigdate.html +++ b/gl/dev/supp-historigdate.html @@ -21,13 +21,13 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                    Original date of text and/or object

                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                    This section of the EpiDoc Guidelines provides direction for encoding the date of origin of the text (or in some cases, of the object or some other feature, decoration, or reuse of it), whether the result of the editor's analysis or an explicit, internal date. Guidance is also provided on recording possible ranges of dates, named historical periods, degrees of precision and dating criteria.

                                                                                                                                                                                    Relevant element documentation (TEI):

                                                                                                                                                                                    • TEI definition: origDate ; EpiDoc-specific +

                                                                                                                                                                                      Original date of text and/or object

                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                      This section of the EpiDoc Guidelines provides direction for encoding the date of origin of the text (or in some cases, of the object or some other feature, decoration, or reuse of it), whether the result of the editor's analysis or an explicit, internal date. Guidance is also provided on recording possible ranges of dates, named historical periods, degrees of precision and dating criteria.

                                                                                                                                                                                      Relevant element documentation (TEI):

                                                                                                                                                                                      The date of orgin of the text (or object, if different) should be recorded in an origDate element in the origin section of the manuscript description area (see the general section on provenance for context). If different dates need to be recorded for text and object, different texts on the same support, or different interventions in the same text, the origDate may be repeated, or the entire history may be embedded in multiple msParts.

                                                                                                                                                                                      It is generally recommended to encode the dating information in numerical form, following the proleptic Julian calendar, using the att.datable.custom attributes on the origDate element. These "custom" date attributes are required because the default dating system assumed by the basic TEI date attributes (att.datable) is the Gregorian calendar. Moreover, therefore, the dating element should always carry a datingMethod attribute pointing to a calendar element in the header--or to an external authority for the Julian calendar, such as http://en.wikipedia.org/wiki/Julian_calendar.

                                                                                                                                                                                      A specific date, whether a single day, month, or year in the Julian calendar, can be expressed using the when-custom attribute, which should be laid out in the same form as an ISO 8601/W3C date (albeit in the Julian, not Gregorian calendar). In other words:

                                                                                                                                                                                      1. A year should be encoded in four digits, with leading zeroes as necessary (i.e. 14 C.E. should be "0014")
                                                                                                                                                                                      2. B.C.E./B.C. dates should be recorded as negative numbers (i.e. preceded by "-"); NB there is no year "0"
                                                                                                                                                                                      3. Month and day should be encoded in two digits, with leading zero as necessary (i.e. January 7th should be "--01-07")
                                                                                                                                                                                      4. A year may appear without months or day; a year+month may appear without day

                                                                                                                                                                                      Date range

                                                                                                                                                                                      A date within a range (such as an event occurring within the reign of an emperor, e.g., the raising of a milestone, or a century for, e.g., palaeographically dated text) should be encoded using the notBefore-custom and notAfter-custom attributes, marking the beginning and end of the possible span of dates. The date formats of these attributes are the same as for when-custom.

                                                                                                                                                                                      This example encodes a simple Julian date:

                                                                                                                                                                                      <origDate when-custom="0139"
                                                                                                                                                                                       datingMethod="#julian">
                                                                                                                                                                                      139 C.E.</origDate>

                                                                                                                                                                                      This example encodes a date occurring within a range, again in Julian calendar:

                                                                                                                                                                                      <origDate notBefore-custom="-0020-12-11"
                                                                                                                                                                                       notAfter-custom="-0019-12-10datingMethod="#julian">
                                                                                                                                                                                      December 11th, 20 to December 10th, 19 B.C.E.</origDate>

                                                                                                                                                                                      This example uses the custom dating attributes on the origDate element to express a date in the Julian calendar that is derived from a date recorded on an inscription in the Śaka era. (The calendar attribute records the calendrical system of the date recorded by this element, wheras datingMethod records the system to which the date is normalized in the xx-custom attributes. Normalization would otherwise be assumed to be to the Gregorian calendar.)

                                                                                                                                                                                      <origDate notBefore-custom="1409"
                                                                                                                                                                                       notAfter-custom="1410"
                                                                                                                                                                                       datingMethod="http://en.wikipedia.org/wiki/Julian_calendar">
                                                                                                                                                                                      The text records a composition  + customization: precision

                                                                                                                                                                                    The date of orgin of the text (or object, if different) should be recorded in an origDate element in the origin section of the manuscript description area (see the general section on provenance for context). If different dates need to be recorded for text and object, different texts on the same support, or different interventions in the same text, the origDate may be repeated, or the entire history may be embedded in multiple msParts.

                                                                                                                                                                                    It is generally recommended to encode the dating information in numerical form, following the proleptic Julian calendar, using the att.datable.custom attributes on the origDate element. These "custom" date attributes are required because the default dating system assumed by the basic TEI date attributes (att.datable) is the Gregorian calendar. Moreover, therefore, the dating element should always carry a datingMethod attribute pointing to a calendar element in the header--or to an external authority for the Julian calendar, such as http://en.wikipedia.org/wiki/Julian_calendar.

                                                                                                                                                                                    A specific date, whether a single day, month, or year in the Julian calendar, can be expressed using the when-custom attribute, which should be laid out in the same form as an ISO 8601/W3C date (albeit in the Julian, not Gregorian calendar). In other words:

                                                                                                                                                                                    1. A year should be encoded in four digits, with leading zeroes as necessary (i.e. 14 C.E. should be "0014")
                                                                                                                                                                                    2. B.C.E./B.C. dates should be recorded as negative numbers (i.e. preceded by "-"); NB there is no year "0"
                                                                                                                                                                                    3. Month and day should be encoded in two digits, with leading zero as necessary (i.e. January 7th should be "--01-07")
                                                                                                                                                                                    4. A year may appear without months or day; a year+month may appear without day

                                                                                                                                                                                    Date range

                                                                                                                                                                                    A date within a range (such as an event occurring within the reign of an emperor, e.g., the raising of a milestone, or a century for, e.g., palaeographically dated text) should be encoded using the notBefore-custom and notAfter-custom attributes, marking the beginning and end of the possible span of dates. The date formats of these attributes are the same as for when-custom.

                                                                                                                                                                                    This example encodes a simple Julian date:

                                                                                                                                                                                    <origDate when-custom="0139"
                                                                                                                                                                                     datingMethod="#julian">
                                                                                                                                                                                    139 C.E.</origDate>

                                                                                                                                                                                    This example encodes a date occurring within a range, again in Julian calendar:

                                                                                                                                                                                    <origDate notBefore-custom="-0020-12-11"
                                                                                                                                                                                     notAfter-custom="-0019-12-10datingMethod="#julian">
                                                                                                                                                                                    December 11th, 20 to December 10th, 19 B.C.E.</origDate>

                                                                                                                                                                                    This example uses the custom dating attributes on the origDate element to express a date in the Julian calendar that is derived from a date recorded on an inscription in the Śaka era. (The calendar attribute records the calendrical system of the date recorded by this element, wheras datingMethod records the system to which the date is normalized in the xx-custom attributes. Normalization would otherwise be assumed to be to the Gregorian calendar.)

                                                                                                                                                                                    <origDate notBefore-custom="1409"
                                                                                                                                                                                     notAfter-custom="1410"
                                                                                                                                                                                     datingMethod="http://en.wikipedia.org/wiki/Julian_calendar">
                                                                                                                                                                                    The text records a composition                     date of <date calendar="http://en.wikipedia.org/wiki/Shalivahana_era">1331</date>(Śaka)</origDate> -            

                                                                                                                                                                                    Certainty and precision

                                                                                                                                                                                    Not all texts are dated confidently to a specific year or firm span of years. If a date given is flagged explicitly as less certain than usual (for example, either with a "?" or a formulation such as "just possibly") the origDate may be given a cert attribute with a value of "low". If a date is flagged as approximate (which is different from being uncertain; often written "circa", "ca." or "c.") origDate should be given an precision with a value of low. If a date range is specified (with notBefore-custom and notAfter-custom) whose start and end points are essentially arbitrary, such as a century or half-century for a palaeographical date, then a precision of "medium" should be given, to indicate that the start and end-points are both notional.

                                                                                                                                                                                    In a few cases, a text may be dated within a span of dates with a notional end-point but a firm terminus post quem. To record this in XML, a precision element may be placed inside the origDate to point to whichever of the attributes represents the less concrete end-point. (See third example below.)

                                                                                                                                                                                    <origDate notBefore-custom="-0100"
                                                                                                                                                                                     notAfter-custom="0100precision="mediumdatingMethod="#julian">
                                                                                                                                                                                    First century B.C. to first century A.D. </origDate>
                                                                                                                                                                                    <origDate when-custom="-0355"
                                                                                                                                                                                     precision="lowdatingMethod="#julian">
                                                                                                                                                                                    Circa 355
                                                                                                                                                                                    B.C.E. </origDate>
                                                                                                                                                                                    <origDate notBefore-custom="0015"
                                                                                                                                                                                     notAfter-custom="0050datingMethod="#julian">
                                                                                                                                                                                    First half first century C.E., but certainly after the death of Augustus.  +            

                                                                                                                                                                                    Certainty and precision

                                                                                                                                                                                    Not all texts are dated confidently to a specific year or firm span of years. If a date given is flagged explicitly as less certain than usual (for example, either with a "?" or a formulation such as "just possibly") the origDate may be given a cert attribute with a value of "low". If a date is flagged as approximate (which is different from being uncertain; often written "circa", "ca." or "c.") origDate should be given an precision with a value of low. If a date range is specified (with notBefore-custom and notAfter-custom) whose start and end points are essentially arbitrary, such as a century or half-century for a palaeographical date, then a precision of "medium" should be given, to indicate that the start and end-points are both notional.

                                                                                                                                                                                    In a few cases, a text may be dated within a span of dates with a notional end-point but a firm terminus post quem. To record this in XML, a precision element may be placed inside the origDate to point to whichever of the attributes represents the less concrete end-point. (See third example below.)

                                                                                                                                                                                    <origDate notBefore-custom="-0100"
                                                                                                                                                                                     notAfter-custom="0100precision="mediumdatingMethod="#julian">
                                                                                                                                                                                    First century B.C. to first century A.D. </origDate>
                                                                                                                                                                                    <origDate when-custom="-0355"
                                                                                                                                                                                     precision="lowdatingMethod="#julian">
                                                                                                                                                                                    Circa 355
                                                                                                                                                                                    B.C.E. </origDate>
                                                                                                                                                                                    <origDate notBefore-custom="0015"
                                                                                                                                                                                     notAfter-custom="0050datingMethod="#julian">
                                                                                                                                                                                    First half first century C.E., but certainly after the death of Augustus.    <precision match="../@notBefore-custom"
                                                                                                                                                                                     precision="high"/>
                                                                                                                                                                                      <precision match="../@notAfter-custom"
                                                                                                                                                                                     precision="medium"/>
                                                                                                                                                                                    </origDate> -

                                                                                                                                                                                    You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                                                                                    Named historical periods

                                                                                                                                                                                    In some cases, rather than (or as well as) a specific or approximate numerical date range, scholars will date an inscription by a named historical period, such as "Hellenistic," "Imperial," "Byzantine" or "Early Dynastic." If desired, the historical period may be encoded in the origDate element using the period attribute, pointing to the URI of a vocabulary for historical periods such as PeriodO or a Wikidata page. (This period need not correspond precisely to the numerical date range offered, if any.)

                                                                                                                                                                                    <origDate notBefore="-0332"
                                                                                                                                                                                     notAfter="-0200precision="medium"
                                                                                                                                                                                     period="http://n2t.net/ark:/99152/p0m63njc4hdevidence="lettering">
                                                                                                                                                                                    Early Hellenistic (lettering)</origDate>
                                                                                                                                                                                    <origDate when="-3000precision="low"
                                                                                                                                                                                     period="https://www.wikidata.org/wiki/Q187979evidence="context">
                                                                                                                                                                                    Early Dynastic Period (context)</origDate>

                                                                                                                                                                                    Dating criteria

                                                                                                                                                                                    The criteria for the date given in the origDate element may be expressed in the evidence attribute. The contents of this attribute should be thought of as a series of space-delimited tokens rather than a sentence of prose. That is to say, for example, if the dating of an inscription depends on lettering, nomenclature and partly archaeological context, rather than encoding this as <origDate evidence="lettering, nomenclature and partly archaeological context"> it would be more appropriate to enter: <origDate evidence="lettering nomenclature archaeological_context">. Note that because values in this list are space-delimited, any values that are multi-word phrases should have some symbol, most likely underscore '_' in place of spaces. Most projects will find it useful to have a typology of criteria with a controlled vocabulary of values for the terms in this attribute.

                                                                                                                                                                                    The EpiDoc schema suggests a short list of values for evidence to encourage consistency. These values are: lettering; nomenclature; prosopography; reign; titulature; internal-date; context.

                                                                                                                                                                                    As these are only suggestions, there is no prohibition against any project using, e.g., "palaeography" instead of lettering, or "onomastics" instead of nomenclature, although it might be more effective to maintain an internal table of dating criteria terms, with the terms mapped to the human-readable language (which might, for example, not be in English). Most projects will want to add values to this list; many may for example want to sub-divide the term "context" into subcategories such as "archaeological context", "architectural context", "epigraphic context", "historical context".

                                                                                                                                                                                    Cf.

                                                                                                                                                                                    <origDate notBefore-custom="0367"
                                                                                                                                                                                     notAfter-custom="0400precision="medium"
                                                                                                                                                                                     evidence="lettering nomenclaturedatingMethod="#julian">
                                                                                                                                                                                    Late fourth century
                                                                                                                                                                                    (lettering and nomenclature).</origDate>

                                                                                                                                                                                    This example encodes a certain date within a particular consular year:

                                                                                                                                                                                    <origDate when-custom="0152-08-23"
                                                                                                                                                                                     precision="highevidence="consulship"
                                                                                                                                                                                     datingMethod="#julian">
                                                                                                                                                                                    23 August 152 C.E.</origDate>
                                                                                                                                                                                    <!-- ... Glabrione et H[om]ulo co(n)s(ulibus) (a(nte) d(iem)) X K(alendas) Sept(embres) - (RIB 309) -->

                                                                                                                                                                                    See also:

                                                                                                                                                                                    Other pages describing <origDate>:

                                                                                                                                                                                    Other pages describing <precision>:

                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                      2. Scott Vanderbilt, author

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                      You can align your definitions by aligning to a local or to an external Controlled Vocabulary.

                                                                                                                                                                                      Named historical periods

                                                                                                                                                                                      In some cases, rather than (or as well as) a specific or approximate numerical date range, scholars will date an inscription by a named historical period, such as "Hellenistic," "Imperial," "Byzantine" or "Early Dynastic." If desired, the historical period may be encoded in the origDate element using the period attribute, pointing to the URI of a vocabulary for historical periods such as PeriodO or a Wikidata page. (This period need not correspond precisely to the numerical date range offered, if any.)

                                                                                                                                                                                      <origDate notBefore="-0332"
                                                                                                                                                                                       notAfter="-0200precision="medium"
                                                                                                                                                                                       period="http://n2t.net/ark:/99152/p0m63njc4hdevidence="lettering">
                                                                                                                                                                                      Early Hellenistic (lettering)</origDate>
                                                                                                                                                                                      <origDate when="-3000precision="low"
                                                                                                                                                                                       period="https://www.wikidata.org/wiki/Q187979evidence="context">
                                                                                                                                                                                      Early Dynastic Period (context)</origDate>

                                                                                                                                                                                      Dating criteria

                                                                                                                                                                                      The criteria for the date given in the origDate element may be expressed in the evidence attribute. The contents of this attribute should be thought of as a series of space-delimited tokens rather than a sentence of prose. That is to say, for example, if the dating of an inscription depends on lettering, nomenclature and partly archaeological context, rather than encoding this as <origDate evidence="lettering, nomenclature and partly archaeological context"> it would be more appropriate to enter: <origDate evidence="lettering nomenclature archaeological_context">. Note that because values in this list are space-delimited, any values that are multi-word phrases should have some symbol, most likely underscore '_' in place of spaces. Most projects will find it useful to have a typology of criteria with a controlled vocabulary of values for the terms in this attribute.

                                                                                                                                                                                      The EpiDoc schema suggests a short list of values for evidence to encourage consistency. These values are: lettering; nomenclature; prosopography; reign; titulature; internal-date; context.

                                                                                                                                                                                      As these are only suggestions, there is no prohibition against any project using, e.g., "palaeography" instead of lettering, or "onomastics" instead of nomenclature, although it might be more effective to maintain an internal table of dating criteria terms, with the terms mapped to the human-readable language (which might, for example, not be in English). Most projects will want to add values to this list; many may for example want to sub-divide the term "context" into subcategories such as "archaeological context", "architectural context", "epigraphic context", "historical context".

                                                                                                                                                                                      Cf.

                                                                                                                                                                                      <origDate notBefore-custom="0367"
                                                                                                                                                                                       notAfter-custom="0400precision="medium"
                                                                                                                                                                                       evidence="lettering nomenclaturedatingMethod="#julian">
                                                                                                                                                                                      Late fourth century
                                                                                                                                                                                      (lettering and nomenclature).</origDate>

                                                                                                                                                                                      This example encodes a certain date within a particular consular year:

                                                                                                                                                                                      <origDate when-custom="0152-08-23"
                                                                                                                                                                                       precision="highevidence="consulship"
                                                                                                                                                                                       datingMethod="#julian">
                                                                                                                                                                                      23 August 152 C.E.</origDate>
                                                                                                                                                                                      <!-- ... Glabrione et H[om]ulo co(n)s(ulibus) (a(nte) d(iem)) X K(alendas) Sept(embres) + (RIB 309) -->

                                                                                                                                                                                      See also:

                                                                                                                                                                                      Other pages describing <origDate>:

                                                                                                                                                                                      Other pages describing <precision>:

                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                      2. Scott Vanderbilt, author

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-historigin-pt-br.html b/gl/dev/supp-historigin-pt-br.html index 78ed9eb59..685ec0bab 100644 --- a/gl/dev/supp-historigin-pt-br.html +++ b/gl/dev/supp-historigin-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                      Local original do objeto portador de texto

                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                      Como discutido na seção geral de proveniência, a informação sobre a origem e o subsequente histórico de um objeto portador de texto é coletada em um elemento history que é parte do msDesc no teiHeader. Um elemento origin dentro de history, e de seu elemento filho origPlace é utilizado para declarações geográficas e topográficas associadas com a origem do objeto. origPlace normalmente é acompanhado por um elemento origDate (q.v.), que é utilizado para codificar informação a respeito da data de origem.

                                                                                                                                                                                      Elemento relevante de documentação (TEI):

                                                                                                                                                                                      • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                                                        Local original do objeto portador de texto

                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                        Como discutido na seção geral de proveniência, a informação sobre a origem e o subsequente histórico de um objeto portador de texto é coletada em um elemento history que é parte do msDesc no teiHeader. Um elemento origin dentro de history, e de seu elemento filho origPlace é utilizado para declarações geográficas e topográficas associadas com a origem do objeto. origPlace normalmente é acompanhado por um elemento origDate (q.v.), que é utilizado para codificar informação a respeito da data de origem.

                                                                                                                                                                                        Elemento relevante de documentação (TEI):

                                                                                                                                                                                        • TEI definition: history ; EpiDoc-specific customization: history
                                                                                                                                                                                        • TEI definition: msDesc ; EpiDoc-specific customization: msDesc
                                                                                                                                                                                        • TEI definition: origin ; EpiDoc-specific customization: origin
                                                                                                                                                                                        • TEI definition: origDate ; EpiDoc-specific @@ -32,7 +32,7 @@ customization: provenance
                                                                                                                                                                                        • TEI definition: rs ; EpiDoc-specific customization: rs
                                                                                                                                                                                        • TEI definition: seg ; EpiDoc-specific customization: seg
                                                                                                                                                                                        • TEI definition: teiHeader ; EpiDoc-specific - customization: teiHeader

                                                                                                                                                                                        origPlace tem o mesmo modelo de conteúdo básico em TEI que a tag p (parágrafo), portanto seu conteúdo pode ir do texto simples até dados altamente estruturados com links cruzados (ou uma combinação de ambos).

                                                                                                                                                                                        origPlace pode conter os atributos type e subtype. EpiDoc não requer o uso destes atributos, nem restringe seus valores através do schema; entrretanto, são recomendados os seguintes valores para o atributo type, se forem úteis para um dado projeto:

                                                                                                                                                                                        typeanotações
                                                                                                                                                                                        composedlocal da composição original (na antiguidade) do texto
                                                                                                                                                                                        executedlocal da execução original (na antiguidade) do texto, isto é, onde estava o suporte físico quando o texto que temos foi colocado nele
                                                                                                                                                                                        sentpara uma carta ou outro documento transmitido: quando foi despachado na antiguidade
                                                                                                                                                                                        receivedpara uma carta ou outro documento transmitido: quando foi entregue na antiguidade
                                                                                                                                                                                        storedpara um documento portátil, como um codex ou rolo de papiro, onde era habitualmente armazenado na antiguidade

                                                                                                                                                                                        Os exemplos a seguir ilustram algumas destas opções.

                                                                                                                                                                                        Exemplos de texto simples

                                                                                                                                                                                        Um exemplo de texto simples que presume um contexto topográfico específico inferido pela pela publicação ou corpus enquadrado:

                                                                                                                                                                                        <origPlace>Probably from the cella wall.</origPlace>

                                                                                                                                                                                        Um exemplo mais extenso, que fornece contexto geográfico pode ser escrito assim:

                                                                                                                                                                                        <origPlace>Probably from the cella wall of the temple of Aphrodite at
                                                                                                                                                                                        Aphrodisias.</origPlace>

                                                                                                                                                                                        Uma declaração, em texto simples, onde o local de origem é coincidente com o local de descoberta (que, presume-se, foi descrito de forma apropriada em um elemento provenance em outro local do history):

                                                                                                                                                                                        <origPlace>Findspot.</origPlace>

                                                                                                                                                                                        Marcação em TEI pode ser adicionada para lidar com uma grande variedade de detalhes, como neste exemplo, onde múltiplos idiomas e sistemas de escrita são utilizados:

                                                                                                                                                                                        <origPlace ref="origPlace.xml#p003n="1">
                                                                                                                                                                                         <seg xml:lang="ru">Херсон</seg>
                                                                                                                                                                                         <seg xml:lang="en">Chersonesos</seg>
                                                                                                                                                                                        </origPlace>

                                                                                                                                                                                        Dados estruturados e links para gazetteers e outros vocabulários controlados

                                                                                                                                                                                        A melhor prática é marcar os nomes de local como tais, usando o elemento TEI placeName apropriado:

                                                                                                                                                                                        <origPlace>All commentators agree that the altar must originally have been placed
                                                                                                                                                                                        somewhere on the site of ancient <placeName type="ancient">Veii</placeName>.</origPlace>

                                                                                                                                                                                        A informação no origPlace pode ser linkada a uma lista interna de locais/monumentos com um key

                                                                                                                                                                                        <origPlace>Perhaps <rs type="monuListkey="db1047">Shrine of the
                                                                                                                                                                                           Dioscuri</rs>
                                                                                                                                                                                        </origPlace>

                                                                                                                                                                                        O atributo ref pode ser usado para linkar a uma lista específica de projeto ou um gazetteer que faz uso de HTTP Uniform Resource Identifiers (URIs) para identificar locais ou estruturas individuais:

                                                                                                                                                                                        <origPlace>Perhaps from the <rs type="monuListkey="db1047">Shrine of the
                                                                                                                                                                                           Dioscuri</rs> at <placeName ref="http://pleiades.stoa.org/places/423025">Rome</placeName>.</origPlace>

                                                                                                                                                                                        Linkar o local de origem ao lugar de descoberta

                                                                                                                                                                                        Em um dos exemplos simples acima, a palavra "Findspot" foi colocada dentro de origPlace para declarar que o objeto portador de texto foi encontrado in situ. Alguns projetos desejam poder usar software para identificar programaticamente e fazer uso destas situações em um output mais completo, criação de mapas, de índices e semelhantes. É possível escrever um script ou transform que, ao encontrar tal construção, tente encontrar um elemento provenance com o valor de atributo padrão type="found" no mesmo arquivo; entretanto, não é difícil tornar esta referência cruzada mais prática para a máquina no XML. Ao utilizar o atributo corresp para linkar origPlace ao elemento provenance que carrega um atributo xml:id com valor correspondente, estas conexões se tornam mais consistentes e confiáveis. Note que qualquer valor de ID correspondente poderia ter sido utilizado; "findspot" foi escolhido para este exemplo porque tem significado imediato para o leitor humano.

                                                                                                                                                                                        <history>
                                                                                                                                                                                         <origin>
                                                                                                                                                                                          <origPlace corresp="#fs">Findspot.</origPlace>
                                                                                                                                                                                         </origin>
                                                                                                                                                                                         <provenance xml:id="fstype="found">Found in the Carrer de Llibreteria,
                                                                                                                                                                                           Barcelona</provenance>
                                                                                                                                                                                        </history>

                                                                                                                                                                                        A mesma técnica é usada neste exemplo estendido:

                                                                                                                                                                                        + customization: teiHeader

                                                                                                                                                                                      origPlace tem o mesmo modelo de conteúdo básico em TEI que a tag p (parágrafo), portanto seu conteúdo pode ir do texto simples até dados altamente estruturados com links cruzados (ou uma combinação de ambos).

                                                                                                                                                                                      origPlace pode conter os atributos type e subtype. EpiDoc não requer o uso destes atributos, nem restringe seus valores através do schema; entrretanto, são recomendados os seguintes valores para o atributo type, se forem úteis para um dado projeto:

                                                                                                                                                                                      typeanotações
                                                                                                                                                                                      composedlocal da composição original (na antiguidade) do texto
                                                                                                                                                                                      executedlocal da execução original (na antiguidade) do texto, isto é, onde estava o suporte físico quando o texto que temos foi colocado nele
                                                                                                                                                                                      sentpara uma carta ou outro documento transmitido: quando foi despachado na antiguidade
                                                                                                                                                                                      receivedpara uma carta ou outro documento transmitido: quando foi entregue na antiguidade
                                                                                                                                                                                      storedpara um documento portátil, como um codex ou rolo de papiro, onde era habitualmente armazenado na antiguidade

                                                                                                                                                                                      Os exemplos a seguir ilustram algumas destas opções.

                                                                                                                                                                                      Exemplos de texto simples

                                                                                                                                                                                      Um exemplo de texto simples que presume um contexto topográfico específico inferido pela pela publicação ou corpus enquadrado:

                                                                                                                                                                                      <origPlace>Probably from the cella wall.</origPlace>

                                                                                                                                                                                      Um exemplo mais extenso, que fornece contexto geográfico pode ser escrito assim:

                                                                                                                                                                                      <origPlace>Probably from the cella wall of the temple of Aphrodite at
                                                                                                                                                                                      Aphrodisias.</origPlace>

                                                                                                                                                                                      Uma declaração, em texto simples, onde o local de origem é coincidente com o local de descoberta (que, presume-se, foi descrito de forma apropriada em um elemento provenance em outro local do history):

                                                                                                                                                                                      <origPlace>Findspot.</origPlace>

                                                                                                                                                                                      Marcação em TEI pode ser adicionada para lidar com uma grande variedade de detalhes, como neste exemplo, onde múltiplos idiomas e sistemas de escrita são utilizados:

                                                                                                                                                                                      <origPlace ref="origPlace.xml#p003n="1">
                                                                                                                                                                                       <seg xml:lang="ru">Херсон</seg>
                                                                                                                                                                                       <seg xml:lang="en">Chersonesos</seg>
                                                                                                                                                                                      </origPlace>

                                                                                                                                                                                      Dados estruturados e links para gazetteers e outros vocabulários controlados

                                                                                                                                                                                      A melhor prática é marcar os nomes de local como tais, usando o elemento TEI placeName apropriado:

                                                                                                                                                                                      <origPlace>All commentators agree that the altar must originally have been placed
                                                                                                                                                                                      somewhere on the site of ancient <placeName type="ancient">Veii</placeName>.</origPlace>

                                                                                                                                                                                      A informação no origPlace pode ser linkada a uma lista interna de locais/monumentos com um key

                                                                                                                                                                                      <origPlace>Perhaps <rs type="monuListkey="db1047">Shrine of the
                                                                                                                                                                                         Dioscuri</rs>
                                                                                                                                                                                      </origPlace>

                                                                                                                                                                                      O atributo ref pode ser usado para linkar a uma lista específica de projeto ou um gazetteer que faz uso de HTTP Uniform Resource Identifiers (URIs) para identificar locais ou estruturas individuais:

                                                                                                                                                                                      <origPlace>Perhaps from the <rs type="monuListkey="db1047">Shrine of the
                                                                                                                                                                                         Dioscuri</rs> at <placeName ref="http://pleiades.stoa.org/places/423025">Rome</placeName>.</origPlace>

                                                                                                                                                                                      Linkar o local de origem ao lugar de descoberta

                                                                                                                                                                                      Em um dos exemplos simples acima, a palavra "Findspot" foi colocada dentro de origPlace para declarar que o objeto portador de texto foi encontrado in situ. Alguns projetos desejam poder usar software para identificar programaticamente e fazer uso destas situações em um output mais completo, criação de mapas, de índices e semelhantes. É possível escrever um script ou transform que, ao encontrar tal construção, tente encontrar um elemento provenance com o valor de atributo padrão type="found" no mesmo arquivo; entretanto, não é difícil tornar esta referência cruzada mais prática para a máquina no XML. Ao utilizar o atributo corresp para linkar origPlace ao elemento provenance que carrega um atributo xml:id com valor correspondente, estas conexões se tornam mais consistentes e confiáveis. Note que qualquer valor de ID correspondente poderia ter sido utilizado; "findspot" foi escolhido para este exemplo porque tem significado imediato para o leitor humano.

                                                                                                                                                                                      <history>
                                                                                                                                                                                       <origin>
                                                                                                                                                                                        <origPlace corresp="#fs">Findspot.</origPlace>
                                                                                                                                                                                       </origin>
                                                                                                                                                                                       <provenance xml:id="fstype="found">Found in the Carrer de Llibreteria,
                                                                                                                                                                                         Barcelona</provenance>
                                                                                                                                                                                      </history>

                                                                                                                                                                                      A mesma técnica é usada neste exemplo estendido:

                                                                                                                                                                                      <history>    <origin> @@ -81,4 +81,4 @@  </provenance>   </history> -

                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                      1. Simona Stoyanova, autor
                                                                                                                                                                                      2. Tom Elliott, autor
                                                                                                                                                                                      3. Arlo Griffiths, autor
                                                                                                                                                                                      4. James Cowey, autor
                                                                                                                                                                                      5. Scott Vanderbilt, autor
                                                                                                                                                                                      6. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                      See also:

                                                                                                                                                                                      Other pages describing <history>:

                                                                                                                                                                                      Other pages describing <msDesc>:

                                                                                                                                                                                      Other pages describing <origin>:

                                                                                                                                                                                      Other pages describing <origDate>:

                                                                                                                                                                                      Other pages describing <origPlace>:

                                                                                                                                                                                      Other pages describing <p>:

                                                                                                                                                                                      Other pages describing <placeName>:

                                                                                                                                                                                      Other pages describing <provenance>:

                                                                                                                                                                                      Other pages describing <rs>:

                                                                                                                                                                                      Other pages describing <seg>:

                                                                                                                                                                                      Other pages describing <teiHeader>:

                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                      1. Simona Stoyanova, autor
                                                                                                                                                                                      2. Tom Elliott, autor
                                                                                                                                                                                      3. Arlo Griffiths, autor
                                                                                                                                                                                      4. James Cowey, autor
                                                                                                                                                                                      5. Scott Vanderbilt, autor
                                                                                                                                                                                      6. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-historigin.html b/gl/dev/supp-historigin.html index 48d485895..faacacf2d 100644 --- a/gl/dev/supp-historigin.html +++ b/gl/dev/supp-historigin.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                      Original location of the text-bearing object

                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                      As discussed in the general section on provenance, information about the origin and subsequent history of a text-bearing object is collected in a history element that is part of the msDesc in the teiHeader. An origin element is used within history, and its child element origPlace is used for topographic and geographic assertions associated with the object's origin. origPlace is normally accompanied by an origDate element (q.v.), which is used to encode information about the date of origin.

                                                                                                                                                                                      Relevant element documentation (TEI):

                                                                                                                                                                                      • TEI definition: history ; EpiDoc-specific +

                                                                                                                                                                                        Original location of the text-bearing object

                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                        As discussed in the general section on provenance, information about the origin and subsequent history of a text-bearing object is collected in a history element that is part of the msDesc in the teiHeader. An origin element is used within history, and its child element origPlace is used for topographic and geographic assertions associated with the object's origin. origPlace is normally accompanied by an origDate element (q.v.), which is used to encode information about the date of origin.

                                                                                                                                                                                        Relevant element documentation (TEI):

                                                                                                                                                                                        • TEI definition: history ; EpiDoc-specific customization: history
                                                                                                                                                                                        • TEI definition: msDesc ; EpiDoc-specific customization: msDesc
                                                                                                                                                                                        • TEI definition: origin ; EpiDoc-specific customization: origin
                                                                                                                                                                                        • TEI definition: origDate ; EpiDoc-specific @@ -32,7 +32,7 @@ customization: provenance
                                                                                                                                                                                        • TEI definition: rs ; EpiDoc-specific customization: rs
                                                                                                                                                                                        • TEI definition: seg ; EpiDoc-specific customization: seg
                                                                                                                                                                                        • TEI definition: teiHeader ; EpiDoc-specific - customization: teiHeader

                                                                                                                                                                                        origPlace has the same basic content model in the TEI as a p (paragraph) tag, so its contents can range from plain text to highly structured and cross-linked data (or a combination of both).

                                                                                                                                                                                        origPlace can carry both the type and subtype attributes. EpiDoc does not require the use of these attributes, nor does it constrain their values via the schema; however, the following values for the type attribute are recommended if useful for a given project:

                                                                                                                                                                                        typenotes
                                                                                                                                                                                        composedplace of original (ancient) composition of the text
                                                                                                                                                                                        executedplace of original (ancient) execution of the text; i.e., where the physical support was when the text we have was placed upon it
                                                                                                                                                                                        sentfor a letter or other transmitted document: whence it was dispatched in antiquity
                                                                                                                                                                                        receivedfor a letter or other transmitted document: where it was delivered in antiquity
                                                                                                                                                                                        storedfor a portable document, such as a codex or papyrus roll, where it was habitually stored in antiquity

                                                                                                                                                                                        The following examples illustrate some of the options.

                                                                                                                                                                                        Plain-text examples

                                                                                                                                                                                        A simple, plain-text example that assumes a narrow topographic context implied by the framing publication or corpus:

                                                                                                                                                                                        <origPlace>Probably from the cella wall.</origPlace>

                                                                                                                                                                                        A more expanded example providing geographic context might be written thus:

                                                                                                                                                                                        <origPlace>Probably from the cella wall of the temple of Aphrodite at Aphrodisias.</origPlace>

                                                                                                                                                                                        A plain-text assertion that the place of origin is coincident with the place of finding (which is presumably described appropriately in a provenance element elsewhere in the history):

                                                                                                                                                                                        <origPlace>Findspot.</origPlace>

                                                                                                                                                                                        TEI markup can be added to deal with a wide variety of details, as in this example where multiple languages and writing systems are used:

                                                                                                                                                                                        <origPlace ref="origPlace.xml#p003n="1">
                                                                                                                                                                                         <seg xml:lang="ru">Херсон</seg>
                                                                                                                                                                                         <seg xml:lang="en">Chersonesos</seg>
                                                                                                                                                                                        </origPlace>

                                                                                                                                                                                        Structured data and links to gazetteers and other controlled vocabularies

                                                                                                                                                                                        Best practice is to mark placenames as such, using the appropriate TEI placeName element:

                                                                                                                                                                                        <origPlace>All commentators agree that the altar must originally have been placed somewhere on the
                                                                                                                                                                                        site of ancient <placeName type="ancient">Veii</placeName>.</origPlace>

                                                                                                                                                                                        The information in the origPlace could be linked to an internal list of places/monuments with a key

                                                                                                                                                                                        <origPlace>Perhaps <rs type="monuListkey="db1047">Shrine of the
                                                                                                                                                                                           Dioscuri</rs>
                                                                                                                                                                                        </origPlace>

                                                                                                                                                                                        The ref attribute can be used to link to a project-specific or external list or gazetteer that makes use of HTTP Uniform Resource Identifiers (URIs) to identify individual structures or places:

                                                                                                                                                                                        <origPlace>Perhaps from the <rs type="monuListkey="db1047">Shrine of the Dioscuri</rs>
                                                                                                                                                                                        at <placeName ref="http://pleiades.stoa.org/places/423025">Rome</placeName>.</origPlace>

                                                                                                                                                                                        Linking place of origin to place of finding

                                                                                                                                                                                        In one of the simple examples above, the word "Findspot" was put inside origPlace to assert that the text-bearing object was found in situ. Some projects may want to be able to use software to identify programmatically and exploit such situations for fuller output, map-making, index creation, and the like. It is possible to write a script or transform that, upon encountering such a construct, attempts to look up a provenance element with the standard type="found" attribute value in the same file; however, it is not difficult to make such a cross reference more readily machine actionable in the XML. By using the corresp attribute to link origPlace to a provenance element that carries an xml:id attribute with a matching value, such connections are rendered more consistent and reliable. Note that any corresponding ID value could be used; "findspot" was chosen for this example because it is readily meaningful to the human reader.

                                                                                                                                                                                        <history>
                                                                                                                                                                                         <origin>
                                                                                                                                                                                          <origPlace corresp="#findspot">Findspot.</origPlace>
                                                                                                                                                                                         </origin>
                                                                                                                                                                                         <provenance xml:id="findspottype="found">Found in the Carrer de Llibreteria,
                                                                                                                                                                                           Barcelona</provenance>
                                                                                                                                                                                        </history>

                                                                                                                                                                                        The same technique is used in this extended example:

                                                                                                                                                                                        + customization: teiHeader

                                                                                                                                                                                      origPlace has the same basic content model in the TEI as a p (paragraph) tag, so its contents can range from plain text to highly structured and cross-linked data (or a combination of both).

                                                                                                                                                                                      origPlace can carry both the type and subtype attributes. EpiDoc does not require the use of these attributes, nor does it constrain their values via the schema; however, the following values for the type attribute are recommended if useful for a given project:

                                                                                                                                                                                      typenotes
                                                                                                                                                                                      composedplace of original (ancient) composition of the text
                                                                                                                                                                                      executedplace of original (ancient) execution of the text; i.e., where the physical support was when the text we have was placed upon it
                                                                                                                                                                                      sentfor a letter or other transmitted document: whence it was dispatched in antiquity
                                                                                                                                                                                      receivedfor a letter or other transmitted document: where it was delivered in antiquity
                                                                                                                                                                                      storedfor a portable document, such as a codex or papyrus roll, where it was habitually stored in antiquity

                                                                                                                                                                                      The following examples illustrate some of the options.

                                                                                                                                                                                      Plain-text examples

                                                                                                                                                                                      A simple, plain-text example that assumes a narrow topographic context implied by the framing publication or corpus:

                                                                                                                                                                                      <origPlace>Probably from the cella wall.</origPlace>

                                                                                                                                                                                      A more expanded example providing geographic context might be written thus:

                                                                                                                                                                                      <origPlace>Probably from the cella wall of the temple of Aphrodite at Aphrodisias.</origPlace>

                                                                                                                                                                                      A plain-text assertion that the place of origin is coincident with the place of finding (which is presumably described appropriately in a provenance element elsewhere in the history):

                                                                                                                                                                                      <origPlace>Findspot.</origPlace>

                                                                                                                                                                                      TEI markup can be added to deal with a wide variety of details, as in this example where multiple languages and writing systems are used:

                                                                                                                                                                                      <origPlace ref="origPlace.xml#p003n="1">
                                                                                                                                                                                       <seg xml:lang="ru">Херсон</seg>
                                                                                                                                                                                       <seg xml:lang="en">Chersonesos</seg>
                                                                                                                                                                                      </origPlace>

                                                                                                                                                                                      Structured data and links to gazetteers and other controlled vocabularies

                                                                                                                                                                                      Best practice is to mark placenames as such, using the appropriate TEI placeName element:

                                                                                                                                                                                      <origPlace>All commentators agree that the altar must originally have been placed somewhere on the
                                                                                                                                                                                      site of ancient <placeName type="ancient">Veii</placeName>.</origPlace>

                                                                                                                                                                                      The information in the origPlace could be linked to an internal list of places/monuments with a key

                                                                                                                                                                                      <origPlace>Perhaps <rs type="monuListkey="db1047">Shrine of the
                                                                                                                                                                                         Dioscuri</rs>
                                                                                                                                                                                      </origPlace>

                                                                                                                                                                                      The ref attribute can be used to link to a project-specific or external list or gazetteer that makes use of HTTP Uniform Resource Identifiers (URIs) to identify individual structures or places:

                                                                                                                                                                                      <origPlace>Perhaps from the <rs type="monuListkey="db1047">Shrine of the Dioscuri</rs>
                                                                                                                                                                                      at <placeName ref="http://pleiades.stoa.org/places/423025">Rome</placeName>.</origPlace>

                                                                                                                                                                                      Linking place of origin to place of finding

                                                                                                                                                                                      In one of the simple examples above, the word "Findspot" was put inside origPlace to assert that the text-bearing object was found in situ. Some projects may want to be able to use software to identify programmatically and exploit such situations for fuller output, map-making, index creation, and the like. It is possible to write a script or transform that, upon encountering such a construct, attempts to look up a provenance element with the standard type="found" attribute value in the same file; however, it is not difficult to make such a cross reference more readily machine actionable in the XML. By using the corresp attribute to link origPlace to a provenance element that carries an xml:id attribute with a matching value, such connections are rendered more consistent and reliable. Note that any corresponding ID value could be used; "findspot" was chosen for this example because it is readily meaningful to the human reader.

                                                                                                                                                                                      <history>
                                                                                                                                                                                       <origin>
                                                                                                                                                                                        <origPlace corresp="#findspot">Findspot.</origPlace>
                                                                                                                                                                                       </origin>
                                                                                                                                                                                       <provenance xml:id="findspottype="found">Found in the Carrer de Llibreteria,
                                                                                                                                                                                         Barcelona</provenance>
                                                                                                                                                                                      </history>

                                                                                                                                                                                      The same technique is used in this extended example:

                                                                                                                                                                                      <history>    <origin> @@ -81,4 +81,4 @@  </provenance>   </history> -

                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                      1. Simona Stoyanova, author
                                                                                                                                                                                      2. Tom Elliott, author
                                                                                                                                                                                      3. Arlo Griffiths, author
                                                                                                                                                                                      4. James Cowey, author
                                                                                                                                                                                      5. Scott Vanderbilt, author

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                      See also:

                                                                                                                                                                                      Other pages describing <history>:

                                                                                                                                                                                      Other pages describing <msDesc>:

                                                                                                                                                                                      Other pages describing <origin>:

                                                                                                                                                                                      Other pages describing <origDate>:

                                                                                                                                                                                      Other pages describing <origPlace>:

                                                                                                                                                                                      Other pages describing <p>:

                                                                                                                                                                                      Other pages describing <placeName>:

                                                                                                                                                                                      Other pages describing <provenance>:

                                                                                                                                                                                      Other pages describing <rs>:

                                                                                                                                                                                      Other pages describing <seg>:

                                                                                                                                                                                      Other pages describing <teiHeader>:

                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                      1. Simona Stoyanova, author
                                                                                                                                                                                      2. Tom Elliott, author
                                                                                                                                                                                      3. Arlo Griffiths, author
                                                                                                                                                                                      4. James Cowey, author
                                                                                                                                                                                      5. Scott Vanderbilt, author

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-history-pt-br.html b/gl/dev/supp-history-pt-br.html index deb7a4138..795319ce7 100644 --- a/gl/dev/supp-history-pt-br.html +++ b/gl/dev/supp-history-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                      Proveniência do objeto portador de texto

                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                      EpiDoc oferece tanto detalhe quanto flexibilidade na descrição do que se sabe ou está registrado sobre a origem e o histórico subsequente de um objeto portador de texto. Como está descrito na History Section of the TEI Guidelines, esta informaçãop é reunida em um elemento history que é parte do msDesc no teiHeader. Dentro de history, primeiramente se codifica um elemento origin, que é usado para narrar o que se sabe sobre as datas e locais associadas com a criação e publicação originais (históricas) do objeto (os elementos origDate e origPlace são oferecidos para cada um destes objetivos). Após codificar o elemento origin, o editor pode criar um ou mais elementos provenance, cada um deles descrevendo um evento particular na história do objeto, capturando o que se sabe de relevante dentro da informação espacial e temporal. Exemplos de eventos de proveniência incluem: local e data (modernos) de descoberta ou observação e registro subsequentes.

                                                                                                                                                                                      Este é um exemplo adaptado do projeto Inscriptions of Aphrodisias:

                                                                                                                                                                                      <history>
                                                                                                                                                                                       <origin>
                                                                                                                                                                                        <origDate>Second to third centuries C.E.</origDate>
                                                                                                                                                                                        <origPlace>
                                                                                                                                                                                         <placeName type="ancient">Aphrodisias</placeName>: probably in the
                                                                                                                                                                                           grounds of the Temple of Aphrodite.</origPlace>
                                                                                                                                                                                       </origin>
                                                                                                                                                                                       <provenance type="foundwhen="1968">
                                                                                                                                                                                        <p>Re-used in the City Walls of <placeName type="ancient">Aphrodisias</placeName>.</p>
                                                                                                                                                                                       </provenance>
                                                                                                                                                                                       <provenance type="observedwhen="2012">
                                                                                                                                                                                        <p>Aphrodisias Museum.</p>
                                                                                                                                                                                       </provenance>
                                                                                                                                                                                      </history>

                                                                                                                                                                                      Se informação histórica detalhada sobre datas e proveniência não for conhecida (como no caso de um objeto ou manuscrito que esteja há muito tempo em um depósito ou coleção particular), uma descrição geral da história do objeto pode ser descrita em um ou mais elementos p (como mostrado abaixo) no lugar dos elementos estruturtados descritos acima.

                                                                                                                                                                                      <history>
                                                                                                                                                                                       <p>The stone may have been in the private collection of Pr Cresson, who invited Louis
                                                                                                                                                                                         Robert to read and translate the inscription. Robert recorded no information on its
                                                                                                                                                                                         provenance and its later whereabouts are unknown. It has never emerged on the
                                                                                                                                                                                         antiquities market.</p>
                                                                                                                                                                                      </history>

                                                                                                                                                                                      Uma discussão mais detalhada, com exemplos específicos (para, por exemplo, tratar de uma série de lugares de origem possíveis ou objetos fragmentados cujas partes foram separadas em tempos modernos), veja as seguintes seções das normas:

                                                                                                                                                                                      Observe que números de inventário, informação de depósito e outros dados deste tipo são tratados em uma parte separada do msDesc (um elemento irmão de history, chamado de msIdentifier). A codificação desta informação é descrita na seção Números de inventário e depósitos.

                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                      1. Simona Stoyanova, autor
                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                      3. Tom Elliott, autor
                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-history.html b/gl/dev/supp-history.html index f391af60c..551b4d043 100644 --- a/gl/dev/supp-history.html +++ b/gl/dev/supp-history.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                      Provenance of the text-bearing object

                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                      EpiDoc provides for both detail and flexibility in describing what is known or recorded about the origin and subsequent history of a text-bearing object. As described in the History Section of the TEI Guidelines, this information is collected in a history element that is part of the msDesc in the teiHeader. Within history, one first encodes an origin element, which is used to lay out what is known about the date(s) and location(s) associated with the original (historic) creation and publication of the object (the origDate and origPlace elements are provided for each of these purposes). After the origin element, the editor may create one or more provenance elements, each of which describes a discrete event in the history of the object, capturing whatever is known and relevant in the way of temporal and spatial information. Examples of provenance events include: (modern) place and date of finding, subsequent observation and recording, or transfers, gifts and sales.

                                                                                                                                                                                      Here is an example adapted from the Inscriptions of Aphrodisias project:

                                                                                                                                                                                      <history>
                                                                                                                                                                                       <origin>
                                                                                                                                                                                        <origDate>Second to third centuries C.E.</origDate>
                                                                                                                                                                                        <origPlace>
                                                                                                                                                                                         <placeName type="ancient">Aphrodisias</placeName>: probably in the grounds of the
                                                                                                                                                                                           Temple of Aphrodite.</origPlace>
                                                                                                                                                                                       </origin>
                                                                                                                                                                                       <provenance type="foundwhen="1968">
                                                                                                                                                                                        <p>Re-used in the City Walls of <placeName type="ancient">Aphrodisias</placeName>.</p>
                                                                                                                                                                                       </provenance>
                                                                                                                                                                                       <provenance type="observedwhen="2012">
                                                                                                                                                                                        <p>Aphrodisias Museum.</p>
                                                                                                                                                                                       </provenance>
                                                                                                                                                                                      </history>

                                                                                                                                                                                      If detailed historical, dating and provenance information is not known (e.g. for an object or manuscript long held in a repository or private collection), a general description of the history of the object may be given in one or more p element (as shown below) rather than using the structured elements described above.

                                                                                                                                                                                      <history>
                                                                                                                                                                                       <p>The stone may have been in the private collection of Pr Cresson, who invited Louis Robert to read and
                                                                                                                                                                                         translate the inscription. Robert recorded no information on its provenance and its later whereabouts
                                                                                                                                                                                         are unknown. It has never emerged on the antiquities market.</p>
                                                                                                                                                                                      </history>

                                                                                                                                                                                      More detailed discussion and specific examples (e.g., for dealing with a range of possible places of origin or fragmentary objects whose component parts have been separated in modern times) see the following sections of the guidelines:

                                                                                                                                                                                      Note that inventory numbers, repository information and related indicia are treated in a separate part of msDesc (a sibling element of history called msIdentifier). The encoding of this information is described in the Inventory numbers and repositories section.

                                                                                                                                                                                      The TEI offers a separate set of elements <custodialHist> and <custEvent> to record information about custodial actions such as photography, conservation and loans, also encoded in a separate part of msDesc (a sibling element of history called additional). See: Availability and Custodial History.

                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                      1. Simona Stoyanova, author
                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                      3. Tom Elliott, author
                                                                                                                                                                                      4. Scott DiGiulio, author
                                                                                                                                                                                      5. Elli Mylonas, author

                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/supp-images-pt-br.html b/gl/dev/supp-images-pt-br.html index c91acde32..e171fa6ba 100644 --- a/gl/dev/supp-images-pt-br.html +++ b/gl/dev/supp-images-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                      Imagens, figuras e fac-símile

                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                      Muitos projetos EpiDoc vão mencionar imagens do objeto portador de texto tratadas por eles, e de outros conteúdos imagéticos relevantes, que forneçam contexto ou comparação. Tais imagens podem ser fotografias ou desenhos ("cópias") dos objetos em si ou de derivados intermediários como squeezes, rubbings, e ink-transfers (estampages), bem como outros tipos de mapas, planos e ilustrações. O TEI fornece uma variedade de mecanismos que ajudam na referência destes materiais visuais, sejam estes publicados junto com o material textual produzido pelo projeto ou publicado por terceiros, online ou em impressos.

                                                                                                                                                                                      • TEI definition: facsimile ; EpiDoc-specific +

                                                                                                                                                                                        Imagens, figuras e fac-símile

                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                        Muitos projetos EpiDoc vão mencionar imagens do objeto portador de texto tratadas por eles, e de outros conteúdos imagéticos relevantes, que forneçam contexto ou comparação. Tais imagens podem ser fotografias ou desenhos ("cópias") dos objetos em si ou de derivados intermediários como squeezes, rubbings, e ink-transfers (estampages), bem como outros tipos de mapas, planos e ilustrações. O TEI fornece uma variedade de mecanismos que ajudam na referência destes materiais visuais, sejam estes publicados junto com o material textual produzido pelo projeto ou publicado por terceiros, online ou em impressos.

                                                                                                                                                                                        • TEI definition: facsimile ; EpiDoc-specific customization: facsimile
                                                                                                                                                                                        • TEI definition: surface ; EpiDoc-specific customization: surface
                                                                                                                                                                                        • TEI definition: graphic ; EpiDoc-specific customization: graphic
                                                                                                                                                                                        • TEI definition: div ; EpiDoc-specific @@ -30,4 +30,4 @@ customization: bibl
                                                                                                                                                                                        • TEI definition: ptr ; EpiDoc-specific customization: ptr
                                                                                                                                                                                        • TEI definition: ref ; EpiDoc-specific customization: ref
                                                                                                                                                                                        • TEI definition: date ; EpiDoc-specific - customization: date

                                                                                                                                                                                        Codificando imagens digitais

                                                                                                                                                                                        Quando um projeto EpiDoc publica imagens digitais de um objeto com inscrição junto com material de texto, o elemento facsimile deve ser usado para listar, linkar e descrever as imagens, e para conectá-las ao material textual e analítico codificado em outra parte do XML. O método de codificação delineado nas seções iniciais das TEI Guidelines, chapter 11 "Representation of Primary Sources" deve ser seguido por projetos EpiDoc nas partes apropriadas. Esta parte das Normas TEI também descreve o uso do elemento sourceDoc, que deve ser utiliazado em vez de facsimile, quando um projeto tem extensa documentação fotográfica de um objeto portador de texto, e quando os objetivos do projeto e o caráter do texto pedem uma fac-símile digital que contenha uma transcrição em documento ligada ao layout visível nas fotos.

                                                                                                                                                                                        Usando o elemento <facsimile>

                                                                                                                                                                                        Os seguintes exemplos, adaptados dos projetos Inscriptions of Aphrodisias e Corpus of the Inscriptions of Campā, ilustram as aplicações do elemento facsimile (e de alguns de seus elementos subordinados opcionais) em um contexto. Outros exemplos tirados das Normas TEI podem também fornecer padrões úteis de codificação.

                                                                                                                                                                                        <facsimile>
                                                                                                                                                                                         <surface n="i">
                                                                                                                                                                                          <desc>Face of inscribed base</desc>
                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/72_L_27A.jpg">
                                                                                                                                                                                           <desc>Photograph (1972)</desc>
                                                                                                                                                                                          </graphic>
                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_pr_046.jpg">
                                                                                                                                                                                           <desc>Squeeze</desc>
                                                                                                                                                                                          </graphic>
                                                                                                                                                                                         </surface>
                                                                                                                                                                                         <surface>
                                                                                                                                                                                          <desc>Top of base</desc>
                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_94_55_03.jpg">
                                                                                                                                                                                           <desc>Photograph (1994)</desc>
                                                                                                                                                                                          </graphic>
                                                                                                                                                                                         </surface>
                                                                                                                                                                                         <surface>
                                                                                                                                                                                          <desc>Inscription on head of statue</desc>
                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/smith-ala254.jpg">
                                                                                                                                                                                           <desc>Drawing (2001)</desc>
                                                                                                                                                                                          </graphic>
                                                                                                                                                                                         </surface>
                                                                                                                                                                                        </facsimile>
                                                                                                                                                                                        <facsimile>
                                                                                                                                                                                         <graphic xml:id="fac1"
                                                                                                                                                                                          url="../images/inscriptions/C0215_1_AG_2011.jpg">

                                                                                                                                                                                          <desc>Photograph of the front of the sculptural stela whose back bears
                                                                                                                                                                                             inscription <ptr target="#inv-general"/>. Taken in the exhibition room
                                                                                                                                                                                             at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                         </graphic>
                                                                                                                                                                                         <graphic xml:id="fac2"
                                                                                                                                                                                          url="../images/inscriptions/C0215_2_AG_2011.jpg">

                                                                                                                                                                                          <desc>Photograph of inscription <ptr target="#inv-general"/>. Taken in the
                                                                                                                                                                                             exhibition room at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                         </graphic>
                                                                                                                                                                                         <graphic xml:id="fac3"
                                                                                                                                                                                          url="../images/inscriptions/EFEOB-est.n2129.jpg">

                                                                                                                                                                                          <desc>Photograph of EFEO estampage n. 2129.</desc>
                                                                                                                                                                                         </graphic>
                                                                                                                                                                                        </facsimile>

                                                                                                                                                                                        Usando o elemento <zone>

                                                                                                                                                                                        Dentro de facsimile, EpiDoc segue a orientação default de TEI, permitindo que surface contenha o elemento zone, que define qualquer área bidimensional dentro de surface. Isto permite que o editor identifique uma seção do suporte e a associe com a área dentro da fac-símile onde está representada. Uma zona pode ter qualquer forma: uma zona retangular pode ser definida com o uso de ulx, uly, lrx, e lry, enquanto uma zona poligonal pode ser definida com o uso de points. Estes mesmos atributos podem também ser usados no próprio elemento surface. Exemplos mais complexos podem ser encontrados nas Normas TEI.

                                                                                                                                                                                        <facsimile>
                                                                                                                                                                                         <surface>
                                                                                                                                                                                          <desc>Face of the inscribed altar.</desc>
                                                                                                                                                                                          <graphic url="../images/a0001.jpg">
                                                                                                                                                                                           <desc>Photograph (2014)</desc>
                                                                                                                                                                                          </graphic>
                                                                                                                                                                                          <zone ulx="240uly="25lrx="400"
                                                                                                                                                                                           lry="280">
                                                                                                                                                                                        Column B of the inscribed
                                                                                                                                                                                             text.</zone>
                                                                                                                                                                                         </surface>
                                                                                                                                                                                        </facsimile>

                                                                                                                                                                                        Citação de imagens do objeto portador de texto, publicadas externamente

                                                                                                                                                                                        Quando se sinaliza a disponibilidade de imagens publicadas fora do projeto EpiDoc (estejam elas disponíveis online ou em forma impressa), os editores podem preferir tratar as referências a estas imagens como citações bibliográficas. O seguinte exemplo adapta as convenções utilizadas pelo projeto Digital Corpus of Literary Papyrology para isto, dando ao elemento padrão do EpiDoc div o atributo type = "bibliography".

                                                                                                                                                                                        <div type="bibliography"
                                                                                                                                                                                         subtype="illustrations">

                                                                                                                                                                                         <listBibl>
                                                                                                                                                                                          <bibl type="printed">G. Cavallo - H.Maehler, Greek Bookhands, pl.10b</bibl>
                                                                                                                                                                                          <bibl type="online">
                                                                                                                                                                                           <title level="m">Berliner Papyrusdatenbank</title>: "<title level="a">P.
                                                                                                                                                                                               11629 a+b: Fragmente aus Kallimachos, Aitia I und III.</title>," <ptr target="http://berlpap.smb.museum/03174/"/>
                                                                                                                                                                                          </bibl>
                                                                                                                                                                                         </listBibl>
                                                                                                                                                                                        </div>

                                                                                                                                                                                        See also:

                                                                                                                                                                                        Other pages describing <facsimile>:

                                                                                                                                                                                          Other pages describing <surface>:

                                                                                                                                                                                            Other pages describing <graphic>:

                                                                                                                                                                                              Other pages describing <div>:

                                                                                                                                                                                              Other pages describing <desc>:

                                                                                                                                                                                              Other pages describing <bibl>:

                                                                                                                                                                                              Other pages describing <ptr>:

                                                                                                                                                                                                Other pages describing <ref>:

                                                                                                                                                                                                  Other pages describing <date>:

                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                    2. Tom Elliott, autor
                                                                                                                                                                                                    3. Arlo Griffiths, autor
                                                                                                                                                                                                    4. Charlotte Tupman, autor
                                                                                                                                                                                                    5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                    \ No newline at end of file + customization: date

                                                                                                                                                                                                  Codificando imagens digitais

                                                                                                                                                                                                  Quando um projeto EpiDoc publica imagens digitais de um objeto com inscrição junto com material de texto, o elemento facsimile deve ser usado para listar, linkar e descrever as imagens, e para conectá-las ao material textual e analítico codificado em outra parte do XML. O método de codificação delineado nas seções iniciais das TEI Guidelines, chapter 11 "Representation of Primary Sources" deve ser seguido por projetos EpiDoc nas partes apropriadas. Esta parte das Normas TEI também descreve o uso do elemento sourceDoc, que deve ser utiliazado em vez de facsimile, quando um projeto tem extensa documentação fotográfica de um objeto portador de texto, e quando os objetivos do projeto e o caráter do texto pedem uma fac-símile digital que contenha uma transcrição em documento ligada ao layout visível nas fotos.

                                                                                                                                                                                                  Usando o elemento <facsimile>

                                                                                                                                                                                                  Os seguintes exemplos, adaptados dos projetos Inscriptions of Aphrodisias e Corpus of the Inscriptions of Campā, ilustram as aplicações do elemento facsimile (e de alguns de seus elementos subordinados opcionais) em um contexto. Outros exemplos tirados das Normas TEI podem também fornecer padrões úteis de codificação.

                                                                                                                                                                                                  <facsimile>
                                                                                                                                                                                                   <surface n="i">
                                                                                                                                                                                                    <desc>Face of inscribed base</desc>
                                                                                                                                                                                                    <graphic url="http://insaph.kcl.ac.uk/images/photo/full/72_L_27A.jpg">
                                                                                                                                                                                                     <desc>Photograph (1972)</desc>
                                                                                                                                                                                                    </graphic>
                                                                                                                                                                                                    <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_pr_046.jpg">
                                                                                                                                                                                                     <desc>Squeeze</desc>
                                                                                                                                                                                                    </graphic>
                                                                                                                                                                                                   </surface>
                                                                                                                                                                                                   <surface>
                                                                                                                                                                                                    <desc>Top of base</desc>
                                                                                                                                                                                                    <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_94_55_03.jpg">
                                                                                                                                                                                                     <desc>Photograph (1994)</desc>
                                                                                                                                                                                                    </graphic>
                                                                                                                                                                                                   </surface>
                                                                                                                                                                                                   <surface>
                                                                                                                                                                                                    <desc>Inscription on head of statue</desc>
                                                                                                                                                                                                    <graphic url="http://insaph.kcl.ac.uk/images/photo/full/smith-ala254.jpg">
                                                                                                                                                                                                     <desc>Drawing (2001)</desc>
                                                                                                                                                                                                    </graphic>
                                                                                                                                                                                                   </surface>
                                                                                                                                                                                                  </facsimile>
                                                                                                                                                                                                  <facsimile>
                                                                                                                                                                                                   <graphic xml:id="fac1"
                                                                                                                                                                                                    url="../images/inscriptions/C0215_1_AG_2011.jpg">

                                                                                                                                                                                                    <desc>Photograph of the front of the sculptural stela whose back bears
                                                                                                                                                                                                       inscription <ptr target="#inv-general"/>. Taken in the exhibition room
                                                                                                                                                                                                       at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                                   </graphic>
                                                                                                                                                                                                   <graphic xml:id="fac2"
                                                                                                                                                                                                    url="../images/inscriptions/C0215_2_AG_2011.jpg">

                                                                                                                                                                                                    <desc>Photograph of inscription <ptr target="#inv-general"/>. Taken in the
                                                                                                                                                                                                       exhibition room at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                                   </graphic>
                                                                                                                                                                                                   <graphic xml:id="fac3"
                                                                                                                                                                                                    url="../images/inscriptions/EFEOB-est.n2129.jpg">

                                                                                                                                                                                                    <desc>Photograph of EFEO estampage n. 2129.</desc>
                                                                                                                                                                                                   </graphic>
                                                                                                                                                                                                  </facsimile>

                                                                                                                                                                                                  Usando o elemento <zone>

                                                                                                                                                                                                  Dentro de facsimile, EpiDoc segue a orientação default de TEI, permitindo que surface contenha o elemento zone, que define qualquer área bidimensional dentro de surface. Isto permite que o editor identifique uma seção do suporte e a associe com a área dentro da fac-símile onde está representada. Uma zona pode ter qualquer forma: uma zona retangular pode ser definida com o uso de ulx, uly, lrx, e lry, enquanto uma zona poligonal pode ser definida com o uso de points. Estes mesmos atributos podem também ser usados no próprio elemento surface. Exemplos mais complexos podem ser encontrados nas Normas TEI.

                                                                                                                                                                                                  <facsimile>
                                                                                                                                                                                                   <surface>
                                                                                                                                                                                                    <desc>Face of the inscribed altar.</desc>
                                                                                                                                                                                                    <graphic url="../images/a0001.jpg">
                                                                                                                                                                                                     <desc>Photograph (2014)</desc>
                                                                                                                                                                                                    </graphic>
                                                                                                                                                                                                    <zone ulx="240uly="25lrx="400"
                                                                                                                                                                                                     lry="280">
                                                                                                                                                                                                  Column B of the inscribed
                                                                                                                                                                                                       text.</zone>
                                                                                                                                                                                                   </surface>
                                                                                                                                                                                                  </facsimile>

                                                                                                                                                                                                  Citação de imagens do objeto portador de texto, publicadas externamente

                                                                                                                                                                                                  Quando se sinaliza a disponibilidade de imagens publicadas fora do projeto EpiDoc (estejam elas disponíveis online ou em forma impressa), os editores podem preferir tratar as referências a estas imagens como citações bibliográficas. O seguinte exemplo adapta as convenções utilizadas pelo projeto Digital Corpus of Literary Papyrology para isto, dando ao elemento padrão do EpiDoc div o atributo type = "bibliography".

                                                                                                                                                                                                  <div type="bibliography"
                                                                                                                                                                                                   subtype="illustrations">

                                                                                                                                                                                                   <listBibl>
                                                                                                                                                                                                    <bibl type="printed">G. Cavallo - H.Maehler, Greek Bookhands, pl.10b</bibl>
                                                                                                                                                                                                    <bibl type="online">
                                                                                                                                                                                                     <title level="m">Berliner Papyrusdatenbank</title>: "<title level="a">P.
                                                                                                                                                                                                         11629 a+b: Fragmente aus Kallimachos, Aitia I und III.</title>," <ptr target="http://berlpap.smb.museum/03174/"/>
                                                                                                                                                                                                    </bibl>
                                                                                                                                                                                                   </listBibl>
                                                                                                                                                                                                  </div>

                                                                                                                                                                                                  See also:

                                                                                                                                                                                                  Other pages describing <facsimile>:

                                                                                                                                                                                                    Other pages describing <surface>:

                                                                                                                                                                                                      Other pages describing <graphic>:

                                                                                                                                                                                                        Other pages describing <div>:

                                                                                                                                                                                                        Other pages describing <desc>:

                                                                                                                                                                                                        Other pages describing <bibl>:

                                                                                                                                                                                                        Other pages describing <ptr>:

                                                                                                                                                                                                          Other pages describing <ref>:

                                                                                                                                                                                                            Other pages describing <date>:

                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                              1. Gabriel Bodard, autor
                                                                                                                                                                                                              2. Tom Elliott, autor
                                                                                                                                                                                                              3. Arlo Griffiths, autor
                                                                                                                                                                                                              4. Charlotte Tupman, autor
                                                                                                                                                                                                              5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/supp-images.html b/gl/dev/supp-images.html index 45970668c..9a060f0bf 100644 --- a/gl/dev/supp-images.html +++ b/gl/dev/supp-images.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                              Images, figures and facsimile

                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                              Many EpiDoc projects will need to refer users to images of the text-bearing objects treated by the projects, and to other relevant imagery that provides context or comparison. Such images may be photographs or drawings ("copies") of the objects themselves or of intermediary derivatives like squeezes, rubbings, and ink-transfers (estampages), as well as other kinds of maps, plans, and illustrations. The TEI provides a variety of mechanisms for making reference to such visual materials, whether published alongside the textual material produced by the project or published by third parties online or in print.

                                                                                                                                                                                                              • TEI definition: facsimile ; EpiDoc-specific +

                                                                                                                                                                                                                Images, figures and facsimile

                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                Many EpiDoc projects will need to refer users to images of the text-bearing objects treated by the projects, and to other relevant imagery that provides context or comparison. Such images may be photographs or drawings ("copies") of the objects themselves or of intermediary derivatives like squeezes, rubbings, and ink-transfers (estampages), as well as other kinds of maps, plans, and illustrations. The TEI provides a variety of mechanisms for making reference to such visual materials, whether published alongside the textual material produced by the project or published by third parties online or in print.

                                                                                                                                                                                                                • TEI definition: facsimile ; EpiDoc-specific customization: facsimile
                                                                                                                                                                                                                • TEI definition: surface ; EpiDoc-specific customization: surface
                                                                                                                                                                                                                • TEI definition: graphic ; EpiDoc-specific customization: graphic
                                                                                                                                                                                                                • TEI definition: div ; EpiDoc-specific @@ -30,4 +30,4 @@ customization: bibl
                                                                                                                                                                                                                • TEI definition: ptr ; EpiDoc-specific customization: ptr
                                                                                                                                                                                                                • TEI definition: ref ; EpiDoc-specific customization: ref
                                                                                                                                                                                                                • TEI definition: date ; EpiDoc-specific - customization: date

                                                                                                                                                                                                                Encoding Digital Images

                                                                                                                                                                                                                When an EpiDoc project publishes digital images of an inscribed object alongside textual material, the facsimile element should be used to list, link to, and describe the images, and to connect them to the textual and analytic material marked up elsewhere in the XML. The encoding approach outlined in the initial sections of the TEI Guidelines, chapter 11 "Representation of Primary Sources" should be followed by EpiDoc projects where appropriate. This portion of the TEI Guidelines also describes the use of the sourceDoc element, which should be used instead of facsimile when a project has comprehensive photographic documentation for a text-bearing object, and when the goals of the project and the character of the text call for a digital facsimile that contains a documentary transcription tied to the visible layout in the photographs.

                                                                                                                                                                                                                Using the <facsimile> element

                                                                                                                                                                                                                The following examples, adapted from the Inscriptions of Aphrodisias and from the Corpus of the Inscriptions of Campā, illustrate the application of the facsimile element (and some of its optional subordinate elements) in an EpiDoc context. Additional examples drawn from the TEI Guidelines may also provide helpful encoding patterns.

                                                                                                                                                                                                                <facsimile>
                                                                                                                                                                                                                 <surface n="i">
                                                                                                                                                                                                                  <desc>Face of inscribed base</desc>
                                                                                                                                                                                                                  <graphic url="http://insaph.kcl.ac.uk/images/photo/full/72_L_27A.jpg">
                                                                                                                                                                                                                   <desc>Photograph (1972)</desc>
                                                                                                                                                                                                                  </graphic>
                                                                                                                                                                                                                  <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_pr_046.jpg">
                                                                                                                                                                                                                   <desc>Squeeze</desc>
                                                                                                                                                                                                                  </graphic>
                                                                                                                                                                                                                 </surface>
                                                                                                                                                                                                                 <surface>
                                                                                                                                                                                                                  <desc>Top of base</desc>
                                                                                                                                                                                                                  <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_94_55_03.jpg">
                                                                                                                                                                                                                   <desc>Photograph (1994)</desc>
                                                                                                                                                                                                                  </graphic>
                                                                                                                                                                                                                 </surface>
                                                                                                                                                                                                                 <surface>
                                                                                                                                                                                                                  <desc>Inscription on head of statue</desc>
                                                                                                                                                                                                                  <graphic url="http://insaph.kcl.ac.uk/images/photo/full/smith-ala254.jpg">
                                                                                                                                                                                                                   <desc>Drawing (2001)</desc>
                                                                                                                                                                                                                  </graphic>
                                                                                                                                                                                                                 </surface>
                                                                                                                                                                                                                </facsimile>
                                                                                                                                                                                                                <facsimile>
                                                                                                                                                                                                                 <graphic xml:id="fac1"
                                                                                                                                                                                                                  url="../images/inscriptions/C0215_1_AG_2011.jpg">

                                                                                                                                                                                                                  <desc>Photograph of the front of the sculptural stela whose back bears
                                                                                                                                                                                                                     inscription <ptr target="#inv-general"/>. Taken in the exhibition room
                                                                                                                                                                                                                     at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                                                 </graphic>
                                                                                                                                                                                                                 <graphic xml:id="fac2"
                                                                                                                                                                                                                  url="../images/inscriptions/C0215_2_AG_2011.jpg">

                                                                                                                                                                                                                  <desc>Photograph of inscription <ptr target="#inv-general"/>. Taken in the
                                                                                                                                                                                                                     exhibition room at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                                                 </graphic>
                                                                                                                                                                                                                 <graphic xml:id="fac3"
                                                                                                                                                                                                                  url="../images/inscriptions/EFEOB-est.n2129.jpg">

                                                                                                                                                                                                                  <desc>Photograph of EFEO estampage n. 2129.</desc>
                                                                                                                                                                                                                 </graphic>
                                                                                                                                                                                                                </facsimile>

                                                                                                                                                                                                                Using the <zone> element

                                                                                                                                                                                                                Within facsimile, EpiDoc follows default TEI in allowing surface to contain the zone element, which defines any two-dimensional area within surface. This permits the editor to identify a section of the support and to associate it with an area within the facsimile in which it is represented. A zone may be of any shape: a rectangular zone can be defined using ulx, uly, lrx, and lry, while a polygonal zone can be defined using points. These same attributes can also be used on the surface element itself. More complex examples can be found in the TEI Guidelines.

                                                                                                                                                                                                                <facsimile>
                                                                                                                                                                                                                 <surface>
                                                                                                                                                                                                                  <desc>Face of the inscribed altar.</desc>
                                                                                                                                                                                                                  <graphic url="../images/a0001.jpg">
                                                                                                                                                                                                                   <desc>Photograph (2014)</desc>
                                                                                                                                                                                                                  </graphic>
                                                                                                                                                                                                                  <zone ulx="240uly="25lrx="400"
                                                                                                                                                                                                                   lry="280">
                                                                                                                                                                                                                Column B of the inscribed
                                                                                                                                                                                                                     text.</zone>
                                                                                                                                                                                                                 </surface>
                                                                                                                                                                                                                </facsimile>

                                                                                                                                                                                                                Citing Externally Published Images of the Text-bearing Object

                                                                                                                                                                                                                When signalling the availability of images published externally to the EpiDoc project (whether available on-line or only in print), editors may prefer to treat references to these images as bibliographic citations. The following example adapts conventions used by the Digital Corpus of Literary Papyrology project for this purpose, subtyping the standard EpiDoc div with type = "bibliography".

                                                                                                                                                                                                                <div type="bibliography"
                                                                                                                                                                                                                 subtype="illustrations">

                                                                                                                                                                                                                 <listBibl>
                                                                                                                                                                                                                  <bibl type="printed">G. Cavallo - H.Maehler, Greek Bookhands, pl.10b</bibl>
                                                                                                                                                                                                                  <bibl type="online">
                                                                                                                                                                                                                   <title level="m">Berliner Papyrusdatenbank</title>: "<title level="a">P.
                                                                                                                                                                                                                       11629 a+b: Fragmente aus Kallimachos, Aitia I und III.</title>," <ptr target="http://berlpap.smb.museum/03174/"/>
                                                                                                                                                                                                                  </bibl>
                                                                                                                                                                                                                 </listBibl>
                                                                                                                                                                                                                </div>

                                                                                                                                                                                                                See also:

                                                                                                                                                                                                                Other pages describing <facsimile>:

                                                                                                                                                                                                                  Other pages describing <surface>:

                                                                                                                                                                                                                    Other pages describing <graphic>:

                                                                                                                                                                                                                      Other pages describing <div>:

                                                                                                                                                                                                                      Other pages describing <desc>:

                                                                                                                                                                                                                      Other pages describing <bibl>:

                                                                                                                                                                                                                      Other pages describing <ptr>:

                                                                                                                                                                                                                        Other pages describing <ref>:

                                                                                                                                                                                                                          Other pages describing <date>:

                                                                                                                                                                                                                          Responsibility for this section

                                                                                                                                                                                                                          1. Gabriel Bodard, author
                                                                                                                                                                                                                          2. Tom Elliott, author
                                                                                                                                                                                                                          3. Arlo Griffiths, author
                                                                                                                                                                                                                          4. Charlotte Tupman, author

                                                                                                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                                                                                                          Date: 2023-04-27

                                                                                                                                                                                                                          \ No newline at end of file + customization: date

                                                                                                                                                                                                                        Encoding Digital Images

                                                                                                                                                                                                                        When an EpiDoc project publishes digital images of an inscribed object alongside textual material, the facsimile element should be used to list, link to, and describe the images, and to connect them to the textual and analytic material marked up elsewhere in the XML. The encoding approach outlined in the initial sections of the TEI Guidelines, chapter 11 "Representation of Primary Sources" should be followed by EpiDoc projects where appropriate. This portion of the TEI Guidelines also describes the use of the sourceDoc element, which should be used instead of facsimile when a project has comprehensive photographic documentation for a text-bearing object, and when the goals of the project and the character of the text call for a digital facsimile that contains a documentary transcription tied to the visible layout in the photographs.

                                                                                                                                                                                                                        Using the <facsimile> element

                                                                                                                                                                                                                        The following examples, adapted from the Inscriptions of Aphrodisias and from the Corpus of the Inscriptions of Campā, illustrate the application of the facsimile element (and some of its optional subordinate elements) in an EpiDoc context. Additional examples drawn from the TEI Guidelines may also provide helpful encoding patterns.

                                                                                                                                                                                                                        <facsimile>
                                                                                                                                                                                                                         <surface n="i">
                                                                                                                                                                                                                          <desc>Face of inscribed base</desc>
                                                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/72_L_27A.jpg">
                                                                                                                                                                                                                           <desc>Photograph (1972)</desc>
                                                                                                                                                                                                                          </graphic>
                                                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_pr_046.jpg">
                                                                                                                                                                                                                           <desc>Squeeze</desc>
                                                                                                                                                                                                                          </graphic>
                                                                                                                                                                                                                         </surface>
                                                                                                                                                                                                                         <surface>
                                                                                                                                                                                                                          <desc>Top of base</desc>
                                                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/NY_94_55_03.jpg">
                                                                                                                                                                                                                           <desc>Photograph (1994)</desc>
                                                                                                                                                                                                                          </graphic>
                                                                                                                                                                                                                         </surface>
                                                                                                                                                                                                                         <surface>
                                                                                                                                                                                                                          <desc>Inscription on head of statue</desc>
                                                                                                                                                                                                                          <graphic url="http://insaph.kcl.ac.uk/images/photo/full/smith-ala254.jpg">
                                                                                                                                                                                                                           <desc>Drawing (2001)</desc>
                                                                                                                                                                                                                          </graphic>
                                                                                                                                                                                                                         </surface>
                                                                                                                                                                                                                        </facsimile>
                                                                                                                                                                                                                        <facsimile>
                                                                                                                                                                                                                         <graphic xml:id="fac1"
                                                                                                                                                                                                                          url="../images/inscriptions/C0215_1_AG_2011.jpg">

                                                                                                                                                                                                                          <desc>Photograph of the front of the sculptural stela whose back bears
                                                                                                                                                                                                                             inscription <ptr target="#inv-general"/>. Taken in the exhibition room
                                                                                                                                                                                                                             at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                                                         </graphic>
                                                                                                                                                                                                                         <graphic xml:id="fac2"
                                                                                                                                                                                                                          url="../images/inscriptions/C0215_2_AG_2011.jpg">

                                                                                                                                                                                                                          <desc>Photograph of inscription <ptr target="#inv-general"/>. Taken in the
                                                                                                                                                                                                                             exhibition room at the Trà Kiệu church by Arlo Griffiths on <date when="20111123"/>.</desc>
                                                                                                                                                                                                                         </graphic>
                                                                                                                                                                                                                         <graphic xml:id="fac3"
                                                                                                                                                                                                                          url="../images/inscriptions/EFEOB-est.n2129.jpg">

                                                                                                                                                                                                                          <desc>Photograph of EFEO estampage n. 2129.</desc>
                                                                                                                                                                                                                         </graphic>
                                                                                                                                                                                                                        </facsimile>

                                                                                                                                                                                                                        Using the <zone> element

                                                                                                                                                                                                                        Within facsimile, EpiDoc follows default TEI in allowing surface to contain the zone element, which defines any two-dimensional area within surface. This permits the editor to identify a section of the support and to associate it with an area within the facsimile in which it is represented. A zone may be of any shape: a rectangular zone can be defined using ulx, uly, lrx, and lry, while a polygonal zone can be defined using points. These same attributes can also be used on the surface element itself. More complex examples can be found in the TEI Guidelines.

                                                                                                                                                                                                                        <facsimile>
                                                                                                                                                                                                                         <surface>
                                                                                                                                                                                                                          <desc>Face of the inscribed altar.</desc>
                                                                                                                                                                                                                          <graphic url="../images/a0001.jpg">
                                                                                                                                                                                                                           <desc>Photograph (2014)</desc>
                                                                                                                                                                                                                          </graphic>
                                                                                                                                                                                                                          <zone ulx="240uly="25lrx="400"
                                                                                                                                                                                                                           lry="280">
                                                                                                                                                                                                                        Column B of the inscribed
                                                                                                                                                                                                                             text.</zone>
                                                                                                                                                                                                                         </surface>
                                                                                                                                                                                                                        </facsimile>

                                                                                                                                                                                                                        Citing Externally Published Images of the Text-bearing Object

                                                                                                                                                                                                                        When signalling the availability of images published externally to the EpiDoc project (whether available on-line or only in print), editors may prefer to treat references to these images as bibliographic citations. The following example adapts conventions used by the Digital Corpus of Literary Papyrology project for this purpose, subtyping the standard EpiDoc div with type = "bibliography".

                                                                                                                                                                                                                        <div type="bibliography"
                                                                                                                                                                                                                         subtype="illustrations">

                                                                                                                                                                                                                         <listBibl>
                                                                                                                                                                                                                          <bibl type="printed">G. Cavallo - H.Maehler, Greek Bookhands, pl.10b</bibl>
                                                                                                                                                                                                                          <bibl type="online">
                                                                                                                                                                                                                           <title level="m">Berliner Papyrusdatenbank</title>: "<title level="a">P.
                                                                                                                                                                                                                               11629 a+b: Fragmente aus Kallimachos, Aitia I und III.</title>," <ptr target="http://berlpap.smb.museum/03174/"/>
                                                                                                                                                                                                                          </bibl>
                                                                                                                                                                                                                         </listBibl>
                                                                                                                                                                                                                        </div>

                                                                                                                                                                                                                        See also:

                                                                                                                                                                                                                        Other pages describing <facsimile>:

                                                                                                                                                                                                                          Other pages describing <surface>:

                                                                                                                                                                                                                            Other pages describing <graphic>:

                                                                                                                                                                                                                              Other pages describing <div>:

                                                                                                                                                                                                                              Other pages describing <desc>:

                                                                                                                                                                                                                              Other pages describing <bibl>:

                                                                                                                                                                                                                              Other pages describing <ptr>:

                                                                                                                                                                                                                                Other pages describing <ref>:

                                                                                                                                                                                                                                  Other pages describing <date>:

                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                                                                                                  2. Tom Elliott, author
                                                                                                                                                                                                                                  3. Arlo Griffiths, author
                                                                                                                                                                                                                                  4. Charlotte Tupman, author

                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-indexing-pt-br.html b/gl/dev/supp-indexing-pt-br.html index 0e1327ff4..69708470e 100644 --- a/gl/dev/supp-indexing-pt-br.html +++ b/gl/dev/supp-indexing-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                  Marcação de palavras, nomes, locais, palavras chave e outros itens de indexação no texto

                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                  gloss

                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                  1. xx, autor
                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                  Marcação de palavras, nomes, locais, palavras chave e outros itens de indexação no texto

                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                  gloss

                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                  1. xx, autor
                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-indexing.html b/gl/dev/supp-indexing.html index 4bc03e3ae..457214812 100644 --- a/gl/dev/supp-indexing.html +++ b/gl/dev/supp-indexing.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                  Tagging words, names, places, keywords and other items for indexing in the text

                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                  gloss

                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                  1. xx, author

                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                  Tagging words, names, places, keywords and other items for indexing in the text

                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                  gloss

                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                  1. xx, author

                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/supp-language-pt-br.html b/gl/dev/supp-language-pt-br.html index 1ff06960a..6330ed6a1 100644 --- a/gl/dev/supp-language-pt-br.html +++ b/gl/dev/supp-language-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                  Línguas e escritas

                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                  TEI/EpiDoc fornecem mecanismos para a codificação de linguagens e sistemas de escrita, da relação destes com o conteúdo de um arquivo EpiDoc e com o texto descrito e transcrito dentro do arquivo. Ao fazer isto, utilizamos os padrões de Internet para a identificação destas linguagens e escritas. Esta parte das Normas trata de todos os aspectos relevantes.

                                                                                                                                                                                                                                  Elemento relevante de documentação (TEI):

                                                                                                                                                                                                                                  • TEI definition: langUsage ; EpiDoc-specific +

                                                                                                                                                                                                                                    Línguas e escritas

                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                    TEI/EpiDoc fornecem mecanismos para a codificação de linguagens e sistemas de escrita, da relação destes com o conteúdo de um arquivo EpiDoc e com o texto descrito e transcrito dentro do arquivo. Ao fazer isto, utilizamos os padrões de Internet para a identificação destas linguagens e escritas. Esta parte das Normas trata de todos os aspectos relevantes.

                                                                                                                                                                                                                                    Elemento relevante de documentação (TEI):

                                                                                                                                                                                                                                    Forma de indicar as línguas e escritas utilizadas em um arquivo EpiDoc

                                                                                                                                                                                                                                    TEI e EpiDoc seguem as melhores práticas em uso, delineadas no Network Working Group's RFC 5646: Tags for Identifying Languages, que estabelece as normas para isto em toda a Internet. O RFC e seus documentos de suporte definem uma sintaxe para a criação de cadeias curtas de caracteres (‘language tags’) que funcionam como identificadores únicos para qualquer combinação desejada de lingua e escrita. Estas tags são compostas de ‘subtags’ para línguas enquanto língua, sistema de escrita e variações regionais e de dialeto. O RFC também estabelece um processo de registro e manutenção destas subtags através da Internet Assigned Numbers Authority.

                                                                                                                                                                                                                                    Um arquivo EpiDoc válido deve utilizar as subtags registradas no IANA Language Subtag Registry. Muitos criadores de EpiDoc já dever estar familiarizados com alguns destes códigos, vistos em outros projetos digitais, como por exemplo:

                                                                                                                                                                                                                                    • Grek = escrita grega
                                                                                                                                                                                                                                    • Latn = escrita latina
                                                                                                                                                                                                                                    • en = língua inglesa (presumida como apresentada em sua escrita padrão: Latn)
                                                                                                                                                                                                                                    • fr = língua francesa (presumida como apresentada em sua escrita padrão: Latn)
                                                                                                                                                                                                                                    • el = língua grega moderna (1453-; presumida como apresentada em sua escrita padrão: Grek)
                                                                                                                                                                                                                                    • grc = língua grega antiga (to 1453; presumida como apresentada em sua escrita padrão: Grek)
                                                                                                                                                                                                                                    • grc-Latn = língua grega antiga (to 1453), escrita em caracteres latinos

                                                                                                                                                                                                                                    Quando o registro do IANA não fornece códigos apropriados, um projeto EpiDoc pode criar "subtags de uso privado", desde que elas sejam definidas internacionalmente no arquivo EpiDoc como descrito no parágrafo a seguir e desde que elas estejam em conformação sintática com as especificações descritas no RFC 5646, seções 2.1: Syntax e 4.6: Considerations for Private Use Subtags. Por exemplo, a equipe das Inscrições Campā verificou que as duas subtags de língua cham (cja = cham ocidental e cjm = cham oriental) e a subtag de escrita associada a elas (Cham) eram bastante diferentes da língua cham antiga e da escrita representada nas inscrições. Portanto, o uso privado da subtag "x-oldcam-latn-ci" foi inventado e recebeu um significado específico para o projeto "língua cam antiga em escrita cam antiga, transcrita em caracteres latinos". Sempre que possível os projetos e adeptos do EpiDoc devem assumir a tarefa de registrar novas subtags no IANA, para benefício de outros. O procedimento para fazer isto está descrito no RFC 5646 Section 3.5.

                                                                                                                                                                                                                                    Describe langUsage here.

                                                                                                                                                                                                                                    <langUsage>
                                                                                                                                                                                                                                     <language ident="ar">Arabic</language>
                                                                                                                                                                                                                                     <language ident="cop">Coptic</language>
                                                                                                                                                                                                                                     <language ident="egy-Egyd">Egyptian in Demotic script</language>
                                                                                                                                                                                                                                     <language ident="egy-Egyh">Egyptian in Hieratic script</language>
                                                                                                                                                                                                                                     <language ident="egy-Egyp">Egyptian Hieroglyphic</language>
                                                                                                                                                                                                                                     <language ident="etr">Etruscan</language>
                                                                                                                                                                                                                                     <language ident="el">Modern Greek</language>
                                                                                                                                                                                                                                     <language ident="grc">Ancient Greek</language>
                                                                                                                                                                                                                                     <language ident="grc-Latn">Ancient Greek written in latin script</language>
                                                                                                                                                                                                                                     <language ident="he">Hebrew</language>
                                                                                                                                                                                                                                     <language ident="la">Latin</language>
                                                                                                                                                                                                                                     <language ident="la-Grek">Latin written in Greek script</language>
                                                                                                                                                                                                                                    </langUsage>

                                                                                                                                                                                                                                    Codificação de caracteres e fontes

                                                                                                                                                                                                                                    Indicação da língua e escrita moderna utilizada em todo o arquivo EpiDoc

                                                                                                                                                                                                                                    Sinalização de línguas e escritas usadas em textos e nas traduções apresentadas

                                                                                                                                                                                                                                    <textLang mainLang="grc"
                                                                                                                                                                                                                                     otherLangs="grc-Latn la">
                                                                                                                                                                                                                                    Inscription in ancient Greek with
                                                                                                                                                                                                                                    some words transcribed in Latin characters, and later annotation in Latin.
                                                                                                                                                                                                                                    </textLang>

                                                                                                                                                                                                                                    Marcação de transições de língua ou escrita no texto

                                                                                                                                                                                                                                    tba

                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                    Other pages describing <langUsage>:

                                                                                                                                                                                                                                      Other pages describing <language>:

                                                                                                                                                                                                                                        Other pages describing <textLang>:

                                                                                                                                                                                                                                          Other pages describing <foreign>:

                                                                                                                                                                                                                                          Responsabilidade por esta seção

                                                                                                                                                                                                                                          1. Gabriel Bodard, autor
                                                                                                                                                                                                                                          2. Tom Elliott, autor
                                                                                                                                                                                                                                          3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                                                                                                                          Date: 2023-04-27

                                                                                                                                                                                                                                          \ No newline at end of file + customization: foreign

                                                                                                                                                                                                                                        Forma de indicar as línguas e escritas utilizadas em um arquivo EpiDoc

                                                                                                                                                                                                                                        TEI e EpiDoc seguem as melhores práticas em uso, delineadas no Network Working Group's RFC 5646: Tags for Identifying Languages, que estabelece as normas para isto em toda a Internet. O RFC e seus documentos de suporte definem uma sintaxe para a criação de cadeias curtas de caracteres (‘language tags’) que funcionam como identificadores únicos para qualquer combinação desejada de lingua e escrita. Estas tags são compostas de ‘subtags’ para línguas enquanto língua, sistema de escrita e variações regionais e de dialeto. O RFC também estabelece um processo de registro e manutenção destas subtags através da Internet Assigned Numbers Authority.

                                                                                                                                                                                                                                        Um arquivo EpiDoc válido deve utilizar as subtags registradas no IANA Language Subtag Registry. Muitos criadores de EpiDoc já dever estar familiarizados com alguns destes códigos, vistos em outros projetos digitais, como por exemplo:

                                                                                                                                                                                                                                        • Grek = escrita grega
                                                                                                                                                                                                                                        • Latn = escrita latina
                                                                                                                                                                                                                                        • en = língua inglesa (presumida como apresentada em sua escrita padrão: Latn)
                                                                                                                                                                                                                                        • fr = língua francesa (presumida como apresentada em sua escrita padrão: Latn)
                                                                                                                                                                                                                                        • el = língua grega moderna (1453-; presumida como apresentada em sua escrita padrão: Grek)
                                                                                                                                                                                                                                        • grc = língua grega antiga (to 1453; presumida como apresentada em sua escrita padrão: Grek)
                                                                                                                                                                                                                                        • grc-Latn = língua grega antiga (to 1453), escrita em caracteres latinos

                                                                                                                                                                                                                                        Quando o registro do IANA não fornece códigos apropriados, um projeto EpiDoc pode criar "subtags de uso privado", desde que elas sejam definidas internacionalmente no arquivo EpiDoc como descrito no parágrafo a seguir e desde que elas estejam em conformação sintática com as especificações descritas no RFC 5646, seções 2.1: Syntax e 4.6: Considerations for Private Use Subtags. Por exemplo, a equipe das Inscrições Campā verificou que as duas subtags de língua cham (cja = cham ocidental e cjm = cham oriental) e a subtag de escrita associada a elas (Cham) eram bastante diferentes da língua cham antiga e da escrita representada nas inscrições. Portanto, o uso privado da subtag "x-oldcam-latn-ci" foi inventado e recebeu um significado específico para o projeto "língua cam antiga em escrita cam antiga, transcrita em caracteres latinos". Sempre que possível os projetos e adeptos do EpiDoc devem assumir a tarefa de registrar novas subtags no IANA, para benefício de outros. O procedimento para fazer isto está descrito no RFC 5646 Section 3.5.

                                                                                                                                                                                                                                        Describe langUsage here.

                                                                                                                                                                                                                                        <langUsage>
                                                                                                                                                                                                                                         <language ident="ar">Arabic</language>
                                                                                                                                                                                                                                         <language ident="cop">Coptic</language>
                                                                                                                                                                                                                                         <language ident="egy-Egyd">Egyptian in Demotic script</language>
                                                                                                                                                                                                                                         <language ident="egy-Egyh">Egyptian in Hieratic script</language>
                                                                                                                                                                                                                                         <language ident="egy-Egyp">Egyptian Hieroglyphic</language>
                                                                                                                                                                                                                                         <language ident="etr">Etruscan</language>
                                                                                                                                                                                                                                         <language ident="el">Modern Greek</language>
                                                                                                                                                                                                                                         <language ident="grc">Ancient Greek</language>
                                                                                                                                                                                                                                         <language ident="grc-Latn">Ancient Greek written in latin script</language>
                                                                                                                                                                                                                                         <language ident="he">Hebrew</language>
                                                                                                                                                                                                                                         <language ident="la">Latin</language>
                                                                                                                                                                                                                                         <language ident="la-Grek">Latin written in Greek script</language>
                                                                                                                                                                                                                                        </langUsage>

                                                                                                                                                                                                                                        Codificação de caracteres e fontes

                                                                                                                                                                                                                                        Indicação da língua e escrita moderna utilizada em todo o arquivo EpiDoc

                                                                                                                                                                                                                                        Sinalização de línguas e escritas usadas em textos e nas traduções apresentadas

                                                                                                                                                                                                                                        <textLang mainLang="grc"
                                                                                                                                                                                                                                         otherLangs="grc-Latn la">
                                                                                                                                                                                                                                        Inscription in ancient Greek with
                                                                                                                                                                                                                                        some words transcribed in Latin characters, and later annotation in Latin.
                                                                                                                                                                                                                                        </textLang>

                                                                                                                                                                                                                                        Marcação de transições de língua ou escrita no texto

                                                                                                                                                                                                                                        tba

                                                                                                                                                                                                                                        See also:

                                                                                                                                                                                                                                        Other pages describing <langUsage>:

                                                                                                                                                                                                                                          Other pages describing <language>:

                                                                                                                                                                                                                                            Other pages describing <textLang>:

                                                                                                                                                                                                                                              Other pages describing <foreign>:

                                                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                                                              1. Gabriel Bodard, autor
                                                                                                                                                                                                                                              2. Tom Elliott, autor
                                                                                                                                                                                                                                              3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/supp-language.html b/gl/dev/supp-language.html index a730c162f..5e053fe4a 100644 --- a/gl/dev/supp-language.html +++ b/gl/dev/supp-language.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                              Languages and scripts

                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                              TEI/EpiDoc provides mechanisms for encoding languages and scripts (writing systems) as they relate to the contents of an EpiDoc file and to the text(s) described and transcribed therein. In doing so, we make use of Internet standards for the identification of these languages and scripts. This portion of the Guidelines addresses all relevant aspects.

                                                                                                                                                                                                                                              Relevant element documentation (TEI):

                                                                                                                                                                                                                                              • TEI definition: langUsage ; EpiDoc-specific +

                                                                                                                                                                                                                                                Languages and scripts

                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                TEI/EpiDoc provides mechanisms for encoding languages and scripts (writing systems) as they relate to the contents of an EpiDoc file and to the text(s) described and transcribed therein. In doing so, we make use of Internet standards for the identification of these languages and scripts. This portion of the Guidelines addresses all relevant aspects.

                                                                                                                                                                                                                                                Relevant element documentation (TEI):

                                                                                                                                                                                                                                                Indicating languages and scripts used in an EpiDoc file

                                                                                                                                                                                                                                                TEI and EpiDoc follow the best current practice outlined in the Network Working Group's RFC 5646: Tags for Identifying Languages, which establishes the norms for same on an Internet-wide basis. The RFC and supporting documents define a syntax for creating short strings of characters (‘language tags’) that function as unique identifiers for any desired combination of language and script. These tags are composed of ‘subtags’ for language qua language, writing sysem (script), and regional and dialectical variation. The RFC also establishes a process for registration and maintenance of these subtags by the Internet Assigned Numbers Authority.

                                                                                                                                                                                                                                                A valid EpiDoc file must make use of subtags recorded in the IANA Language Subtag Registry. Many EpiDoc creators will already be familiar with some of these codes from other digital projects, for example:

                                                                                                                                                                                                                                                • Grek = Greek script
                                                                                                                                                                                                                                                • Latn = Latin script
                                                                                                                                                                                                                                                • en = English language (assumed to be in its standard script: Latn)
                                                                                                                                                                                                                                                • fr = French language (assumed to be in its standard script: Latn)
                                                                                                                                                                                                                                                • el = Modern Greek language (1453-; assumed to be in its standard script: Grek)
                                                                                                                                                                                                                                                • grc = Ancient Greek language (to 1453; assumed to be in its standard script: Grek)
                                                                                                                                                                                                                                                • grc-Latn = Ancient Greek Language (to 1453), rendered in Latin script

                                                                                                                                                                                                                                                When the IANA registry does not provide appropriate codes, then an EpiDoc project may devise "private use subtags", so long as they are internally defined in the EpiDoc file as outlined in the following paragraph and so long as they conform syntactically to the specifications laid out in RFC 5646, sections 2.1: Syntax and 4.6: Considerations for Private Use Subtags. For example, the Campā Inscriptions team determined that the two Cham language subtags (cja = Western Cham and cjm = Eastern Cham) and the associated script subtag (Cham) were substantively different from the ancient Cham language and script represented in the inscriptions. Therefore the private use subtag "x-oldcam-latn-ci" was invented and given the project-specific meaning "Old Cam language in Old Cam script transliterated in Latin characters." Whenever possible, EpiDoc projects and practitioners should undertake to register new subtags with the IANA for the benefit of others. A procedure for same is set out in RFC 5646 Section 3.5.

                                                                                                                                                                                                                                                <langUsage>
                                                                                                                                                                                                                                                 <language ident="ar">Arabic</language>
                                                                                                                                                                                                                                                 <language ident="cop">Coptic</language>
                                                                                                                                                                                                                                                 <language ident="egy-Egyd">Egyptian in Demotic script</language>
                                                                                                                                                                                                                                                 <language ident="egy-Egyh">Egyptian in Hieratic script</language>
                                                                                                                                                                                                                                                 <language ident="egy-Egyp">Egyptian Hieroglyphic</language>
                                                                                                                                                                                                                                                 <language ident="etr">Etruscan</language>
                                                                                                                                                                                                                                                 <language ident="el">Modern Greek</language>
                                                                                                                                                                                                                                                 <language ident="grc">Ancient Greek</language>
                                                                                                                                                                                                                                                 <language ident="grc-Latn">Ancient Greek written in Latin script</language>
                                                                                                                                                                                                                                                 <language ident="he">Hebrew</language>
                                                                                                                                                                                                                                                 <language ident="la">Latin</language>
                                                                                                                                                                                                                                                 <language ident="la-Grek">Latin written in Greek script</language>
                                                                                                                                                                                                                                                </langUsage>

                                                                                                                                                                                                                                                Character Encodings and Fonts

                                                                                                                                                                                                                                                tba

                                                                                                                                                                                                                                                Indicating the modern language and script used throughout the EpiDoc file

                                                                                                                                                                                                                                                tba

                                                                                                                                                                                                                                                Signaling the languages and scripts used in the texts and translations being presented

                                                                                                                                                                                                                                                The primary and secondary language(s) of an inscription should be declared in the textLang element contained in the TEI header; the primary language should be contained within the mainLang attribute and any other languages should be listed in the otherLangs attribute. Note that the languages included here should only refer to the languages or writing systems contained within the text itself, rather than those throughout the edition. If the script differs from the default script of the language (e.g., Greek transliterated into Latin), this should also be indicated using the appropriate language codes, where available.

                                                                                                                                                                                                                                                <textLang mainLang="grc"
                                                                                                                                                                                                                                                 otherLangs="grc-Latn la">
                                                                                                                                                                                                                                                Inscription in ancient Greek with some words transcribed in Latin characters, and
                                                                                                                                                                                                                                                later annotation in Latin.
                                                                                                                                                                                                                                                </textLang>

                                                                                                                                                                                                                                                The language·s for a given translation of a text should not be included in the textLang element; instead, they should be included as an xml:lang attribute on <div type="translation"> or nested <div type="textpart">s within it.

                                                                                                                                                                                                                                                <div type="translationxml:lang="en">
                                                                                                                                                                                                                                                 <p>To the Divine Spirits. Quintus Rutilius Faustio lived for twenty-one years
                                                                                                                                                                                                                                                   (and) twenty-six days. (His) parents (made this) for (their) most beloved son.</p>
                                                                                                                                                                                                                                                </div>

                                                                                                                                                                                                                                                Marking transitions in language and/or script in the text

                                                                                                                                                                                                                                                A single language should be indicated as the default for a text by including it in the mainLang attribute on the textLang element. The default script for a given language is assumed unless otherwise indicated (i.e. Greek will be written in the Greek alphabet, etc.). When transitions can between languages and/or script are limited in scope (i.e. a single word, a short phrase, etc. in a language differing from that declare in the mainLang attribute in the header), the word or words should be contained within a foreign element (see Multi-Language Texts). Language and/or script may be identified by including the attribute xml:lang. In the following brief example from the US Epigraphy Project, the inscription begins in Latin but transitions to Greek which is written in the Latin script:

                                                                                                                                                                                                                                                <div type="edition">
                                                                                                                                                                                                                                                 <ab>
                                                                                                                                                                                                                                                  <lb n="1"/>Cum tu<unclear>i</unclear>s <foreign xml:lang="grc-Latn">pie zeses</foreign>.
                                                                                                                                                                                                                                                 </ab>
                                                                                                                                                                                                                                                </div>

                                                                                                                                                                                                                                                If longer passages of the text are in different languages and/or scripts, the default language may be further specified with an xml:lang attribute on the <div type="edition"> and if other sections are in different languages/scripts, these should be declared by adding a xml:lang attribute to the block-level containers of that text (e.g. ab, lg, seg, or <div type="textpart">. (Compare the examples given at Multi-Language Texts under point 2.) One may also indicate shifts in script in the same fashion; that is, a hypothetical inscription that is entirely in Greek but also includes Greek transliterated into the Roman alphabet would declare its default language ("grc") in the xml:lang attribute and transliterated passages would be marked with the xml:lang attribute with a value of "grc-Latn". It may also be desirable to indicate a change in hand when the script and/or language changes using the handShift element, if such a shift is discernible; further details about the script can be included in the handNote elements of the manuscript description. Compare the following example from the US Epigraphy Project, which begins in Latin and then contains a translation of the text in Greek:

                                                                                                                                                                                                                                                <div type="editionxml:lang="lat">
                                                                                                                                                                                                                                                 <ab>
                                                                                                                                                                                                                                                  <lb n="1"/>Divi <persName>
                                                                                                                                                                                                                                                   <name type="cognomenkey="Augustus">
                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                     <abbr>Aug</abbr>
                                                                                                                                                                                                                                                     <ex>usti</ex>
                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                   </name>
                                                                                                                                                                                                                                                  </persName> liberti
                                                                                                                                                                                                                                                 <lb n="2"/>
                                                                                                                                                                                                                                                  <persName>
                                                                                                                                                                                                                                                   <name type="cognomenkey="Calyx">Calycis</name>
                                                                                                                                                                                                                                                  </persName>
                                                                                                                                                                                                                                                  <persName>
                                                                                                                                                                                                                                                   <name type="cognomenkey="Hygeia">Hygeiae</name>
                                                                                                                                                                                                                                                  </persName>.
                                                                                                                                                                                                                                                 </ab>
                                                                                                                                                                                                                                                 <ab xml:lang="grc">
                                                                                                                                                                                                                                                  <lb n="3"/>
                                                                                                                                                                                                                                                  <handShift n="2"/> Θεοῦ Σεβαστοῦ
                                                                                                                                                                                                                                                 <lb n="4"/>ἀπελευθέρου
                                                                                                                                                                                                                                                 <lb n="5"/>
                                                                                                                                                                                                                                                  <persName>
                                                                                                                                                                                                                                                   <name type="cognomenkey="Calyx">Καλύκος</name>
                                                                                                                                                                                                                                                  </persName> ἀπελευ
                                                                                                                                                                                                                                                 <lb n="6break="no"/>θέρα <persName>
                                                                                                                                                                                                                                                   <name type="cognomenkey="Hygeia">Ὑγεῖα</name>
                                                                                                                                                                                                                                                  </persName>.
                                                                                                                                                                                                                                                 </ab>
                                                                                                                                                                                                                                                </div>
                                                                                                                                                                                                                                                <div xml:lang="artype="edition"
                                                                                                                                                                                                                                                 xml:space="preserve">
                                                                                                                                                                                                                                                + customization: foreign

                                                                                                                                                                                                                                              Indicating languages and scripts used in an EpiDoc file

                                                                                                                                                                                                                                              TEI and EpiDoc follow the best current practice outlined in the Network Working Group's RFC 5646: Tags for Identifying Languages, which establishes the norms for same on an Internet-wide basis. The RFC and supporting documents define a syntax for creating short strings of characters (‘language tags’) that function as unique identifiers for any desired combination of language and script. These tags are composed of ‘subtags’ for language qua language, writing sysem (script), and regional and dialectical variation. The RFC also establishes a process for registration and maintenance of these subtags by the Internet Assigned Numbers Authority.

                                                                                                                                                                                                                                              A valid EpiDoc file must make use of subtags recorded in the IANA Language Subtag Registry. Many EpiDoc creators will already be familiar with some of these codes from other digital projects, for example:

                                                                                                                                                                                                                                              • Grek = Greek script
                                                                                                                                                                                                                                              • Latn = Latin script
                                                                                                                                                                                                                                              • en = English language (assumed to be in its standard script: Latn)
                                                                                                                                                                                                                                              • fr = French language (assumed to be in its standard script: Latn)
                                                                                                                                                                                                                                              • el = Modern Greek language (1453-; assumed to be in its standard script: Grek)
                                                                                                                                                                                                                                              • grc = Ancient Greek language (to 1453; assumed to be in its standard script: Grek)
                                                                                                                                                                                                                                              • grc-Latn = Ancient Greek Language (to 1453), rendered in Latin script

                                                                                                                                                                                                                                              When the IANA registry does not provide appropriate codes, then an EpiDoc project may devise "private use subtags", so long as they are internally defined in the EpiDoc file as outlined in the following paragraph and so long as they conform syntactically to the specifications laid out in RFC 5646, sections 2.1: Syntax and 4.6: Considerations for Private Use Subtags. For example, the Campā Inscriptions team determined that the two Cham language subtags (cja = Western Cham and cjm = Eastern Cham) and the associated script subtag (Cham) were substantively different from the ancient Cham language and script represented in the inscriptions. Therefore the private use subtag "x-oldcam-latn-ci" was invented and given the project-specific meaning "Old Cam language in Old Cam script transliterated in Latin characters." Whenever possible, EpiDoc projects and practitioners should undertake to register new subtags with the IANA for the benefit of others. A procedure for same is set out in RFC 5646 Section 3.5.

                                                                                                                                                                                                                                              <langUsage>
                                                                                                                                                                                                                                               <language ident="ar">Arabic</language>
                                                                                                                                                                                                                                               <language ident="cop">Coptic</language>
                                                                                                                                                                                                                                               <language ident="egy-Egyd">Egyptian in Demotic script</language>
                                                                                                                                                                                                                                               <language ident="egy-Egyh">Egyptian in Hieratic script</language>
                                                                                                                                                                                                                                               <language ident="egy-Egyp">Egyptian Hieroglyphic</language>
                                                                                                                                                                                                                                               <language ident="etr">Etruscan</language>
                                                                                                                                                                                                                                               <language ident="el">Modern Greek</language>
                                                                                                                                                                                                                                               <language ident="grc">Ancient Greek</language>
                                                                                                                                                                                                                                               <language ident="grc-Latn">Ancient Greek written in Latin script</language>
                                                                                                                                                                                                                                               <language ident="he">Hebrew</language>
                                                                                                                                                                                                                                               <language ident="la">Latin</language>
                                                                                                                                                                                                                                               <language ident="la-Grek">Latin written in Greek script</language>
                                                                                                                                                                                                                                              </langUsage>

                                                                                                                                                                                                                                              Character Encodings and Fonts

                                                                                                                                                                                                                                              tba

                                                                                                                                                                                                                                              Indicating the modern language and script used throughout the EpiDoc file

                                                                                                                                                                                                                                              tba

                                                                                                                                                                                                                                              Signaling the languages and scripts used in the texts and translations being presented

                                                                                                                                                                                                                                              The primary and secondary language(s) of an inscription should be declared in the textLang element contained in the TEI header; the primary language should be contained within the mainLang attribute and any other languages should be listed in the otherLangs attribute. Note that the languages included here should only refer to the languages or writing systems contained within the text itself, rather than those throughout the edition. If the script differs from the default script of the language (e.g., Greek transliterated into Latin), this should also be indicated using the appropriate language codes, where available.

                                                                                                                                                                                                                                              <textLang mainLang="grc"
                                                                                                                                                                                                                                               otherLangs="grc-Latn la">
                                                                                                                                                                                                                                              Inscription in ancient Greek with some words transcribed in Latin characters, and
                                                                                                                                                                                                                                              later annotation in Latin.
                                                                                                                                                                                                                                              </textLang>

                                                                                                                                                                                                                                              The language·s for a given translation of a text should not be included in the textLang element; instead, they should be included as an xml:lang attribute on <div type="translation"> or nested <div type="textpart">s within it.

                                                                                                                                                                                                                                              <div type="translationxml:lang="en">
                                                                                                                                                                                                                                               <p>To the Divine Spirits. Quintus Rutilius Faustio lived for twenty-one years
                                                                                                                                                                                                                                                 (and) twenty-six days. (His) parents (made this) for (their) most beloved son.</p>
                                                                                                                                                                                                                                              </div>

                                                                                                                                                                                                                                              Marking transitions in language and/or script in the text

                                                                                                                                                                                                                                              A single language should be indicated as the default for a text by including it in the mainLang attribute on the textLang element. The default script for a given language is assumed unless otherwise indicated (i.e. Greek will be written in the Greek alphabet, etc.). When transitions can between languages and/or script are limited in scope (i.e. a single word, a short phrase, etc. in a language differing from that declare in the mainLang attribute in the header), the word or words should be contained within a foreign element (see Multi-Language Texts). Language and/or script may be identified by including the attribute xml:lang. In the following brief example from the US Epigraphy Project, the inscription begins in Latin but transitions to Greek which is written in the Latin script:

                                                                                                                                                                                                                                              <div type="edition">
                                                                                                                                                                                                                                               <ab>
                                                                                                                                                                                                                                                <lb n="1"/>Cum tu<unclear>i</unclear>s <foreign xml:lang="grc-Latn">pie zeses</foreign>.
                                                                                                                                                                                                                                               </ab>
                                                                                                                                                                                                                                              </div>

                                                                                                                                                                                                                                              If longer passages of the text are in different languages and/or scripts, the default language may be further specified with an xml:lang attribute on the <div type="edition"> and if other sections are in different languages/scripts, these should be declared by adding a xml:lang attribute to the block-level containers of that text (e.g. ab, lg, seg, or <div type="textpart">. (Compare the examples given at Multi-Language Texts under point 2.) One may also indicate shifts in script in the same fashion; that is, a hypothetical inscription that is entirely in Greek but also includes Greek transliterated into the Roman alphabet would declare its default language ("grc") in the xml:lang attribute and transliterated passages would be marked with the xml:lang attribute with a value of "grc-Latn". It may also be desirable to indicate a change in hand when the script and/or language changes using the handShift element, if such a shift is discernible; further details about the script can be included in the handNote elements of the manuscript description. Compare the following example from the US Epigraphy Project, which begins in Latin and then contains a translation of the text in Greek:

                                                                                                                                                                                                                                              <div type="editionxml:lang="lat">
                                                                                                                                                                                                                                               <ab>
                                                                                                                                                                                                                                                <lb n="1"/>Divi <persName>
                                                                                                                                                                                                                                                 <name type="cognomenkey="Augustus">
                                                                                                                                                                                                                                                  <expan>
                                                                                                                                                                                                                                                   <abbr>Aug</abbr>
                                                                                                                                                                                                                                                   <ex>usti</ex>
                                                                                                                                                                                                                                                  </expan>
                                                                                                                                                                                                                                                 </name>
                                                                                                                                                                                                                                                </persName> liberti
                                                                                                                                                                                                                                               <lb n="2"/>
                                                                                                                                                                                                                                                <persName>
                                                                                                                                                                                                                                                 <name type="cognomenkey="Calyx">Calycis</name>
                                                                                                                                                                                                                                                </persName>
                                                                                                                                                                                                                                                <persName>
                                                                                                                                                                                                                                                 <name type="cognomenkey="Hygeia">Hygeiae</name>
                                                                                                                                                                                                                                                </persName>.
                                                                                                                                                                                                                                               </ab>
                                                                                                                                                                                                                                               <ab xml:lang="grc">
                                                                                                                                                                                                                                                <lb n="3"/>
                                                                                                                                                                                                                                                <handShift n="2"/> Θεοῦ Σεβαστοῦ
                                                                                                                                                                                                                                               <lb n="4"/>ἀπελευθέρου
                                                                                                                                                                                                                                               <lb n="5"/>
                                                                                                                                                                                                                                                <persName>
                                                                                                                                                                                                                                                 <name type="cognomenkey="Calyx">Καλύκος</name>
                                                                                                                                                                                                                                                </persName> ἀπελευ
                                                                                                                                                                                                                                               <lb n="6break="no"/>θέρα <persName>
                                                                                                                                                                                                                                                 <name type="cognomenkey="Hygeia">Ὑγεῖα</name>
                                                                                                                                                                                                                                                </persName>.
                                                                                                                                                                                                                                               </ab>
                                                                                                                                                                                                                                              </div>
                                                                                                                                                                                                                                              <div xml:lang="artype="edition"
                                                                                                                                                                                                                                               xml:space="preserve">
                                                                                                                                                                                                                                                              <ab>                     <lb n="1"/><supplied reason="lost">بـ</supplied>ـسم الـ<supplied reason="lost">ـلّه</supplied> <supplied reason="lost">الرّحمن</supplied> <supplied reason="lost">الرّحيم</supplied>                     <lb n="2"/><seg xml:lang="grc"><supplied reason="lost">ἐν ὀνόματι τοῦ <expan>θ<ex>εο</ex></expan> τοῦ ἐλεήμον</supplied><unclear>ος</unclear> <expan><ex>καὶ</ex></expan> <expan>φιλανθρ<supplied reason="lost">ώ</supplied><unclear>π</unclear><ex>ου</ex></expan> @@ -41,4 +41,4 @@                     <lb n="12"/> هذ<supplied reason="omitted">ا</supplied> ممّا أمر به الأمير <supplied reason="lost">عبد</supplied> <supplied reason="lost">اللّه</supplied> <supplied reason="lost">بن</supplied> <supplied reason="lost">عبد</supplied> <supplied reason="lost">الملك</supplied>                     <lb n="13"/>  في سنة <supplied reason="lost">تسع</supplied> <supplied reason="lost">وثمنين</supplied>                 </ab> -            
                                                                                                                                                                                                                                              </div>

                                                                                                                                                                                                                                              See also:

                                                                                                                                                                                                                                              Other pages describing <langUsage>:

                                                                                                                                                                                                                                                Other pages describing <language>:

                                                                                                                                                                                                                                                  Other pages describing <textLang>:

                                                                                                                                                                                                                                                    Other pages describing <foreign>:

                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                                                                                    2. Tom Elliott, author
                                                                                                                                                                                                                                                    3. Scott DiGiulio, author

                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                    \ No newline at end of file +            
                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                    (Source)

                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                    Other pages describing <langUsage>:

                                                                                                                                                                                                                                                    Other pages describing <language>:

                                                                                                                                                                                                                                                    Other pages describing <textLang>:

                                                                                                                                                                                                                                                    Other pages describing <foreign>:

                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                                                                                    2. Tom Elliott, author
                                                                                                                                                                                                                                                    3. Scott DiGiulio, author

                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/supp-publication-pt-br.html b/gl/dev/supp-publication-pt-br.html index c2e53e1c2..6bdaf4e6c 100644 --- a/gl/dev/supp-publication-pt-br.html +++ b/gl/dev/supp-publication-pt-br.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                    Informação sobre publicação

                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                    Informação a respeito do status atual de publicação e licenciamento para edição da inscrição/papiro deve estar registrada nos elementos titleStmt e publicationStmt no header.

                                                                                                                                                                                                                                                    • TEI definition: titleStmt ; EpiDoc-specific +

                                                                                                                                                                                                                                                      Informação sobre publicação

                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                      Informação a respeito do status atual de publicação e licenciamento para edição da inscrição/papiro deve estar registrada nos elementos titleStmt e publicationStmt no header.

                                                                                                                                                                                                                                                      <titleStmt>
                                                                                                                                                                                                                                                       <title>Verse honours for Oikoumenios</title>
                                                                                                                                                                                                                                                       <editor>Joyce M. Reynolds</editor>
                                                                                                                                                                                                                                                       <editor>Charlotte M. Roueché</editor>
                                                                                                                                                                                                                                                      </titleStmt>
                                                                                                                                                                                                                                                      <publicationStmt>
                                                                                                                                                                                                                                                       <authority>IOSPE Project</authority>
                                                                                                                                                                                                                                                       <idno type="filename">Byz212</idno>
                                                                                                                                                                                                                                                       <availability>
                                                                                                                                                                                                                                                        <licence target="http://creativecommons.org/licenses/by/3.0/"> Licensed under a
                                                                                                                                                                                                                                                           Creative Commons-Attribution 3.0 licence. </licence>
                                                                                                                                                                                                                                                       </availability>
                                                                                                                                                                                                                                                      </publicationStmt>

                                                                                                                                                                                                                                                      Informação adicional pode ser incluída para declarar status específicos para fotos, por exemplo.

                                                                                                                                                                                                                                                      <graphic n="UTS_5"
                                                                                                                                                                                                                                                       url="https://commons.wikimedia.org/wiki/File:UTS_5.png">

                                                                                                                                                                                                                                                       <desc> Frgament from Ulpia Traiana Sarmizegetusa. Face and Drawing. <ref type="license"
                                                                                                                                                                                                                                                         target="creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                      Licensed under the Creative
                                                                                                                                                                                                                                                           Commons Attribution-ShareAlike 3.0 Unported license. </ref>
                                                                                                                                                                                                                                                       </desc>
                                                                                                                                                                                                                                                      </graphic>
                                                                                                                                                                                                                                                      (EDH: HD058118)

                                                                                                                                                                                                                                                      Os status de licenciamento associado a traduções pode ser expresso da mesma forma, se necessário.

                                                                                                                                                                                                                                                      <div type="translation">
                                                                                                                                                                                                                                                       <p> To the emperor Caesar Nerva Traianus, son of the divine Nerva, Augustus, Germanicus,
                                                                                                                                                                                                                                                         Dacicus </p>
                                                                                                                                                                                                                                                       <desc>
                                                                                                                                                                                                                                                        <ref type="license"
                                                                                                                                                                                                                                                         target="http://creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                      Licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported licence.
                                                                                                                                                                                                                                                        </ref>
                                                                                                                                                                                                                                                       </desc>
                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                      Other pages describing <titleStmt>:

                                                                                                                                                                                                                                                        Other pages describing <title>:

                                                                                                                                                                                                                                                          Other pages describing <editor>:

                                                                                                                                                                                                                                                            Other pages describing <publicationStmt>:

                                                                                                                                                                                                                                                              Other pages describing <idno>:

                                                                                                                                                                                                                                                              Other pages describing <availability>:

                                                                                                                                                                                                                                                                Other pages describing <licence>:

                                                                                                                                                                                                                                                                  Responsabilitdade por esta seção

                                                                                                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                  2. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                  \ No newline at end of file + customization: licence

                                                                                                                                                                                                                                                                <titleStmt>
                                                                                                                                                                                                                                                                 <title>Verse honours for Oikoumenios</title>
                                                                                                                                                                                                                                                                 <editor>Joyce M. Reynolds</editor>
                                                                                                                                                                                                                                                                 <editor>Charlotte M. Roueché</editor>
                                                                                                                                                                                                                                                                </titleStmt>
                                                                                                                                                                                                                                                                <publicationStmt>
                                                                                                                                                                                                                                                                 <authority>IOSPE Project</authority>
                                                                                                                                                                                                                                                                 <idno type="filename">Byz212</idno>
                                                                                                                                                                                                                                                                 <availability>
                                                                                                                                                                                                                                                                  <licence target="http://creativecommons.org/licenses/by/3.0/"> Licensed under a
                                                                                                                                                                                                                                                                     Creative Commons-Attribution 3.0 licence. </licence>
                                                                                                                                                                                                                                                                 </availability>
                                                                                                                                                                                                                                                                </publicationStmt>

                                                                                                                                                                                                                                                                Informação adicional pode ser incluída para declarar status específicos para fotos, por exemplo.

                                                                                                                                                                                                                                                                <graphic n="UTS_5"
                                                                                                                                                                                                                                                                 url="https://commons.wikimedia.org/wiki/File:UTS_5.png">

                                                                                                                                                                                                                                                                 <desc> Frgament from Ulpia Traiana Sarmizegetusa. Face and Drawing. <ref type="license"
                                                                                                                                                                                                                                                                   target="creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                                Licensed under the Creative
                                                                                                                                                                                                                                                                     Commons Attribution-ShareAlike 3.0 Unported license. </ref>
                                                                                                                                                                                                                                                                 </desc>
                                                                                                                                                                                                                                                                </graphic>
                                                                                                                                                                                                                                                                (EDH: HD058118)

                                                                                                                                                                                                                                                                Os status de licenciamento associado a traduções pode ser expresso da mesma forma, se necessário.

                                                                                                                                                                                                                                                                <div type="translation">
                                                                                                                                                                                                                                                                 <p> To the emperor Caesar Nerva Traianus, son of the divine Nerva, Augustus, Germanicus,
                                                                                                                                                                                                                                                                   Dacicus </p>
                                                                                                                                                                                                                                                                 <desc>
                                                                                                                                                                                                                                                                  <ref type="license"
                                                                                                                                                                                                                                                                   target="http://creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                                Licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported licence.
                                                                                                                                                                                                                                                                  </ref>
                                                                                                                                                                                                                                                                 </desc>
                                                                                                                                                                                                                                                                </div>

                                                                                                                                                                                                                                                                See also:

                                                                                                                                                                                                                                                                Other pages describing <titleStmt>:

                                                                                                                                                                                                                                                                  Other pages describing <title>:

                                                                                                                                                                                                                                                                    Other pages describing <editor>:

                                                                                                                                                                                                                                                                      Other pages describing <publicationStmt>:

                                                                                                                                                                                                                                                                        Other pages describing <idno>:

                                                                                                                                                                                                                                                                        Other pages describing <availability>:

                                                                                                                                                                                                                                                                          Other pages describing <licence>:

                                                                                                                                                                                                                                                                            Responsabilitdade por esta seção

                                                                                                                                                                                                                                                                            1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                            2. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/supp-publication.html b/gl/dev/supp-publication.html index 66cb75892..66e73ba2e 100644 --- a/gl/dev/supp-publication.html +++ b/gl/dev/supp-publication.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                            Publication information

                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                            Information about the current publication and licensing status of the inscription/papyrus edition should be recorded in the titleStmt and publicationStmt elements in the header.

                                                                                                                                                                                                                                                                            • TEI definition: titleStmt ; EpiDoc-specific +

                                                                                                                                                                                                                                                                              Publication information

                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                              Information about the current publication and licensing status of the inscription/papyrus edition should be recorded in the titleStmt and publicationStmt elements in the header.

                                                                                                                                                                                                                                                                              <titleStmt>
                                                                                                                                                                                                                                                                               <title>Verse honours for Oikoumenios</title>
                                                                                                                                                                                                                                                                               <editor>Joyce M. Reynolds</editor>
                                                                                                                                                                                                                                                                               <editor>Charlotte M. Roueché</editor>
                                                                                                                                                                                                                                                                              </titleStmt>
                                                                                                                                                                                                                                                                              <publicationStmt>
                                                                                                                                                                                                                                                                               <authority>IOSPE Project</authority>
                                                                                                                                                                                                                                                                               <idno type="filename">Byz212</idno>
                                                                                                                                                                                                                                                                               <availability>
                                                                                                                                                                                                                                                                                <licence target="http://creativecommons.org/licenses/by/3.0/"> Licensed under a
                                                                                                                                                                                                                                                                                   Creative Commons-Attribution 3.0 licence. </licence>
                                                                                                                                                                                                                                                                               </availability>
                                                                                                                                                                                                                                                                              </publicationStmt>

                                                                                                                                                                                                                                                                              Additional information can be added to state particular licencing status of photos for example.

                                                                                                                                                                                                                                                                              <graphic n="UTS_5"
                                                                                                                                                                                                                                                                               url="https://commons.wikimedia.org/wiki/File:UTS_5.png">

                                                                                                                                                                                                                                                                               <desc> Frgament from Ulpia Traiana Sarmizegetusa. Face and Drawing. <ref type="license"
                                                                                                                                                                                                                                                                                 target="creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                                              Licensed under the Creative
                                                                                                                                                                                                                                                                                   Commons Attribution-ShareAlike 3.0 Unported license. </ref>
                                                                                                                                                                                                                                                                               </desc>
                                                                                                                                                                                                                                                                              </graphic>
                                                                                                                                                                                                                                                                              (EDH: HD058118)

                                                                                                                                                                                                                                                                              Also more specific licencing status associated with the translation might be expressed in the same way if needed.

                                                                                                                                                                                                                                                                              <div type="translation">
                                                                                                                                                                                                                                                                               <p> To the emperor Caesar Nerva Traianus, son of the divine Nerva, Augustus, Germanicus,
                                                                                                                                                                                                                                                                                 Dacicus </p>
                                                                                                                                                                                                                                                                               <desc>
                                                                                                                                                                                                                                                                                <ref type="license"
                                                                                                                                                                                                                                                                                 target="http://creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                                              Licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported licence.
                                                                                                                                                                                                                                                                                </ref>
                                                                                                                                                                                                                                                                               </desc>
                                                                                                                                                                                                                                                                              </div>

                                                                                                                                                                                                                                                                              See also:

                                                                                                                                                                                                                                                                              Other pages describing <titleStmt>:

                                                                                                                                                                                                                                                                                Other pages describing <title>:

                                                                                                                                                                                                                                                                                  Other pages describing <editor>:

                                                                                                                                                                                                                                                                                    Other pages describing <publicationStmt>:

                                                                                                                                                                                                                                                                                      Other pages describing <idno>:

                                                                                                                                                                                                                                                                                      Other pages describing <availability>:

                                                                                                                                                                                                                                                                                        Other pages describing <licence>:

                                                                                                                                                                                                                                                                                          Responsibility for this section

                                                                                                                                                                                                                                                                                          1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                          2. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                          Date: 2023-04-27

                                                                                                                                                                                                                                                                                          \ No newline at end of file + customization: licence

                                                                                                                                                                                                                                                                                        <titleStmt>
                                                                                                                                                                                                                                                                                         <title>Verse honours for Oikoumenios</title>
                                                                                                                                                                                                                                                                                         <editor>Joyce M. Reynolds</editor>
                                                                                                                                                                                                                                                                                         <editor>Charlotte M. Roueché</editor>
                                                                                                                                                                                                                                                                                        </titleStmt>
                                                                                                                                                                                                                                                                                        <publicationStmt>
                                                                                                                                                                                                                                                                                         <authority>IOSPE Project</authority>
                                                                                                                                                                                                                                                                                         <idno type="filename">Byz212</idno>
                                                                                                                                                                                                                                                                                         <availability>
                                                                                                                                                                                                                                                                                          <licence target="http://creativecommons.org/licenses/by/3.0/"> Licensed under a
                                                                                                                                                                                                                                                                                             Creative Commons-Attribution 3.0 licence. </licence>
                                                                                                                                                                                                                                                                                         </availability>
                                                                                                                                                                                                                                                                                        </publicationStmt>

                                                                                                                                                                                                                                                                                        Additional information can be added to state particular licencing status of photos for example.

                                                                                                                                                                                                                                                                                        <graphic n="UTS_5"
                                                                                                                                                                                                                                                                                         url="https://commons.wikimedia.org/wiki/File:UTS_5.png">

                                                                                                                                                                                                                                                                                         <desc> Frgament from Ulpia Traiana Sarmizegetusa. Face and Drawing. <ref type="license"
                                                                                                                                                                                                                                                                                           target="creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                                                        Licensed under the Creative
                                                                                                                                                                                                                                                                                             Commons Attribution-ShareAlike 3.0 Unported license. </ref>
                                                                                                                                                                                                                                                                                         </desc>
                                                                                                                                                                                                                                                                                        </graphic>
                                                                                                                                                                                                                                                                                        (EDH: HD058118)

                                                                                                                                                                                                                                                                                        Also more specific licencing status associated with the translation might be expressed in the same way if needed.

                                                                                                                                                                                                                                                                                        <div type="translation">
                                                                                                                                                                                                                                                                                         <p> To the emperor Caesar Nerva Traianus, son of the divine Nerva, Augustus, Germanicus,
                                                                                                                                                                                                                                                                                           Dacicus </p>
                                                                                                                                                                                                                                                                                         <desc>
                                                                                                                                                                                                                                                                                          <ref type="license"
                                                                                                                                                                                                                                                                                           target="http://creativecommons.org/licenses/by-sa/3.0/">
                                                                                                                                                                                                                                                                                        Licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported licence.
                                                                                                                                                                                                                                                                                          </ref>
                                                                                                                                                                                                                                                                                         </desc>
                                                                                                                                                                                                                                                                                        </div>

                                                                                                                                                                                                                                                                                        See also:

                                                                                                                                                                                                                                                                                        Other pages describing <titleStmt>:

                                                                                                                                                                                                                                                                                          Other pages describing <title>:

                                                                                                                                                                                                                                                                                            Other pages describing <editor>:

                                                                                                                                                                                                                                                                                              Other pages describing <publicationStmt>:

                                                                                                                                                                                                                                                                                                Other pages describing <idno>:

                                                                                                                                                                                                                                                                                                Other pages describing <availability>:

                                                                                                                                                                                                                                                                                                  Other pages describing <licence>:

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                    2. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/supp-structure-pt-br.html b/gl/dev/supp-structure-pt-br.html index a8f2a9b08..ab5f8592b 100644 --- a/gl/dev/supp-structure-pt-br.html +++ b/gl/dev/supp-structure-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Estrutura de uma edição EpiDoc

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Esta seção apresenta a forma e estrutura de uma edição EpiDoc, apresentando o enfoque TEI P5 para descrição e histórico de manuscritos, as divisões no corpo, etc.

                                                                                                                                                                                                                                                                                                    • TEI definition: msDesc ; EpiDoc-specific - customization: msDesc

                                                                                                                                                                                                                                                                                                    A maior parte das características que comumente aparecem numa edição epigráfica/papirológica são tratadas em locais específicos num arquivo EpiDoc. Este documento pretende dar uma visão geral destes locais. Páginas individuais na seção Dados de Suporte das Normas darão informação mais detalhada sobre cada um destes elementos e características.

                                                                                                                                                                                                                                                                                                    Um arquivo EpiDoc relativamente simples, contendo informação descritiva e histórica sobre uma inscrição, pode parecer com o exemplo a seguir. Uma versão deste exemplo, ligado à versão mais atualizada do schema EpiDoc e apropriado ao uso como template de projeto, pode ser baixada do site EpiDoc:ex-epidoctemplate.xml.

                                                                                                                                                                                                                                                                                                    <TEI xml:space="preservexml:lang="en" xmlns="http://www.tei-c.org/ns/1.0"> +

                                                                                                                                                                                                                                                                                                    Estrutura de uma edição EpiDoc

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Esta seção apresenta a forma e estrutura de uma edição EpiDoc, apresentando o enfoque TEI P5 para descrição e histórico de manuscritos, as divisões no corpo, etc.

                                                                                                                                                                                                                                                                                                    • TEI definition: msDesc ; EpiDoc-specific + customization: msDesc

                                                                                                                                                                                                                                                                                                    A maior parte das características que comumente aparecem numa edição epigráfica/papirológica são tratadas em locais específicos num arquivo EpiDoc. Este documento pretende dar uma visão geral destes locais. Páginas individuais na seção Dados de Suporte das Normas darão informação mais detalhada sobre cada um destes elementos e características.

                                                                                                                                                                                                                                                                                                    Um arquivo EpiDoc relativamente simples, contendo informação descritiva e histórica sobre uma inscrição, pode parecer com o exemplo a seguir. Uma versão deste exemplo, ligado à versão mais atualizada do schema EpiDoc e apropriado ao uso como template de projeto, pode ser baixada do site EpiDoc:ex-epidoctemplate.xml.

                                                                                                                                                                                                                                                                                                    <TEI xml:space="preservexml:lang="en" xmlns="http://www.tei-c.org/ns/1.0">     <teiHeader>         <fileDesc>             <titleStmt> @@ -91,4 +91,4 @@             </div>         </body>     </text> -
                                                                                                                                                                                                                                                                                                    </TEI>

                                                                                                                                                                                                                                                                                                    Edição

                                                                                                                                                                                                                                                                                                    div com type de "edição". A divisão de edição contém o texto epigráfico, papirológico, etc. em si, bem como intervenções editoriais (por exemplo, representações em EpiDoc da sigla Leiden) que devem ser aplicadas ao texto. Equivalência ao Leiden é o mínimo necessário; maiores detalhes sobre intervenções editoriais podem ser incluídos, se preciso. xml:lang é um atributo necessário, a não ser que textparts tenham línguas diferentes (veja imediatamente abaixo).

                                                                                                                                                                                                                                                                                                    A divisão de edição pode ser separada usando elementos div com um type de "textpart", que é um valor restrito. Se textparts têm línguas diferentes, xml:lang deve ser adicionado a cada textpart. Uma edição pode ter qualquer número de textparts, que podem ser subdivididos utilizando subtype com valores não restritos (como "fragmento", "coluna" ou qualquer descrição que seja relevante para aquele texto em particular). Para uma discussão detalhada e exemplos, veja a Lista de Todas as Normas de Transcrição.

                                                                                                                                                                                                                                                                                                    Tradução

                                                                                                                                                                                                                                                                                                    div com type de "tradução". A divisão de tradução segue as mesmas regras que a de edição, mas geralmente vai conter uma quantidade menor de marcação, e provavelmente terá uma estrutura mais simples. A linguagem da divisão tradução pode ser codificada utilizando lang (com códigos de idiomas de duas ou três letras, como "pt", "fr", "en").A fonte ou responsabilidade pela tradução pode ser codificada utilizandosource ou resp. A divisão de tradução pode receber um subtype (irrestrito) para descrevê-la melhor, como "literal", "literária", "pedagógica", etc. Para uma discussão detalhada e exemplos, vejaTradução

                                                                                                                                                                                                                                                                                                    Aparato

                                                                                                                                                                                                                                                                                                    div com type de "aparato". O módulo de aparato TEI é feito para o apparatus criticus lachmanniano, que permite múltiplos testemunhos para um texto.O apparatus criticus epigráfico provavelmente incluirá comentários sobre formas de letras; suplementos; interpretações; e as leituras de editores anteriores. Para uma discussão detalhada e exemplos, veja Apparatus Criticus.

                                                                                                                                                                                                                                                                                                    Comentário

                                                                                                                                                                                                                                                                                                    div com type de "comentário". A divisão comentário será geralmente escrita em prosa e pode conter uma discussão geral do contexto do texto ou do suporte, maiores informaçãoes sobre critério de datação, referências externas, comentários sobre seções específicas do texto, etc.

                                                                                                                                                                                                                                                                                                    Bibliografia

                                                                                                                                                                                                                                                                                                    div com type de "bibliografia". A divisão bibliografia pode ter tanto conteúdo independente quanto links para a bibliografia principal, utilizando listBibl com qualquer número de elementos bibl.Esta divisão pode ser subdividida utilizando subtype com valores irrestritos que podem incluir "principal", "derivado", "discussão", etc. Para uma discussão detalhada e exemplos, veja Codificando a Bibliografia.

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, Autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, Autor
                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +
                                                                                                                                                                                                                                                                                                    </TEI>

                                                                                                                                                                                                                                                                                                    Edição

                                                                                                                                                                                                                                                                                                    div com type de "edição". A divisão de edição contém o texto epigráfico, papirológico, etc. em si, bem como intervenções editoriais (por exemplo, representações em EpiDoc da sigla Leiden) que devem ser aplicadas ao texto. Equivalência ao Leiden é o mínimo necessário; maiores detalhes sobre intervenções editoriais podem ser incluídos, se preciso. xml:lang é um atributo necessário, a não ser que textparts tenham línguas diferentes (veja imediatamente abaixo).

                                                                                                                                                                                                                                                                                                    A divisão de edição pode ser separada usando elementos div com um type de "textpart", que é um valor restrito. Se textparts têm línguas diferentes, xml:lang deve ser adicionado a cada textpart. Uma edição pode ter qualquer número de textparts, que podem ser subdivididos utilizando subtype com valores não restritos (como "fragmento", "coluna" ou qualquer descrição que seja relevante para aquele texto em particular). Para uma discussão detalhada e exemplos, veja a Lista de Todas as Normas de Transcrição.

                                                                                                                                                                                                                                                                                                    Tradução

                                                                                                                                                                                                                                                                                                    div com type de "tradução". A divisão de tradução segue as mesmas regras que a de edição, mas geralmente vai conter uma quantidade menor de marcação, e provavelmente terá uma estrutura mais simples. A linguagem da divisão tradução pode ser codificada utilizando lang (com códigos de idiomas de duas ou três letras, como "pt", "fr", "en").A fonte ou responsabilidade pela tradução pode ser codificada utilizandosource ou resp. A divisão de tradução pode receber um subtype (irrestrito) para descrevê-la melhor, como "literal", "literária", "pedagógica", etc. Para uma discussão detalhada e exemplos, vejaTradução

                                                                                                                                                                                                                                                                                                    Aparato

                                                                                                                                                                                                                                                                                                    div com type de "aparato". O módulo de aparato TEI é feito para o apparatus criticus lachmanniano, que permite múltiplos testemunhos para um texto.O apparatus criticus epigráfico provavelmente incluirá comentários sobre formas de letras; suplementos; interpretações; e as leituras de editores anteriores. Para uma discussão detalhada e exemplos, veja Apparatus Criticus.

                                                                                                                                                                                                                                                                                                    Comentário

                                                                                                                                                                                                                                                                                                    div com type de "comentário". A divisão comentário será geralmente escrita em prosa e pode conter uma discussão geral do contexto do texto ou do suporte, maiores informaçãoes sobre critério de datação, referências externas, comentários sobre seções específicas do texto, etc.

                                                                                                                                                                                                                                                                                                    Bibliografia

                                                                                                                                                                                                                                                                                                    div com type de "bibliografia". A divisão bibliografia pode ter tanto conteúdo independente quanto links para a bibliografia principal, utilizando listBibl com qualquer número de elementos bibl.Esta divisão pode ser subdividida utilizando subtype com valores irrestritos que podem incluir "principal", "derivado", "discussão", etc. Para uma discussão detalhada e exemplos, veja Codificando a Bibliografia.

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, Autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, Autor
                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/supp-structure.html b/gl/dev/supp-structure.html index 9d42b1c25..a018fb4d5 100644 --- a/gl/dev/supp-structure.html +++ b/gl/dev/supp-structure.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Structure of an EpiDoc edition

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    This section introduces the structure and shape of an EpiDoc edition, introducing the TEI P5 approach to manuscript description and history, the divisions in the body, etc.

                                                                                                                                                                                                                                                                                                    • TEI definition: msDesc ; EpiDoc-specific - customization: msDesc

                                                                                                                                                                                                                                                                                                    Most of the features that most commonly occur in an epigraphic/papyrological edition are catered for by specific locations in an EpiDoc file. This document aims to give an overview of those locations. Individual pages in the Supporting Data section of the Guidelines will give more detailed information on each of these elements and features.

                                                                                                                                                                                                                                                                                                    A relatively simple EpiDoc file containing descriptive and historical information about an inscription might look something like the following example. A version of this example, keyed to the latest version of the EpiDoc schema and suitable for use as a project template, may be downloaded from the EpiDoc website: ex-epidoctemplate.xml.

                                                                                                                                                                                                                                                                                                    <TEI xml:space="preservexml:lang="en" xmlns="http://www.tei-c.org/ns/1.0"> +

                                                                                                                                                                                                                                                                                                    Structure of an EpiDoc edition

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    This section introduces the structure and shape of an EpiDoc edition, introducing the TEI P5 approach to manuscript description and history, the divisions in the body, etc.

                                                                                                                                                                                                                                                                                                    • TEI definition: msDesc ; EpiDoc-specific + customization: msDesc

                                                                                                                                                                                                                                                                                                    Most of the features that most commonly occur in an epigraphic/papyrological edition are catered for by specific locations in an EpiDoc file. This document aims to give an overview of those locations. Individual pages in the Supporting Data section of the Guidelines will give more detailed information on each of these elements and features.

                                                                                                                                                                                                                                                                                                    A relatively simple EpiDoc file containing descriptive and historical information about an inscription might look something like the following example. A version of this example, keyed to the latest version of the EpiDoc schema and suitable for use as a project template, may be downloaded from the EpiDoc website: ex-epidoctemplate.xml.

                                                                                                                                                                                                                                                                                                    <TEI xml:space="preservexml:lang="en" xmlns="http://www.tei-c.org/ns/1.0">     <teiHeader>         <fileDesc>             <titleStmt> @@ -91,4 +91,4 @@             </div>         </body>     </text> -
                                                                                                                                                                                                                                                                                                    </TEI>

                                                                                                                                                                                                                                                                                                    Edition

                                                                                                                                                                                                                                                                                                    div with type of "edition". The edition division contains the epigraphic, papyrological (etc.) text itself as well as editorial interventions (i.e. representations in EpiDoc of the Leiden sigla) that are to be applied to the text. Leiden equivalence is a minimum requirement; further detail on editorial interventions can be included as required. xml:lang is a required attribute, unless textparts have individual languages (see immediately below).

                                                                                                                                                                                                                                                                                                    The edition division can be divided using div elements with an type of "textpart", which is a constrained value. If textparts have individual languages, xml:lang should be added to each textpart. An edition may have any number of textparts, which can be further subdivided using subtype with unconstrained values (e.g. "fragment", "column" or whatever description is relevant to that particular text). For detailed discussion and examples see List Of All Transcription Guidelines.

                                                                                                                                                                                                                                                                                                    Translation

                                                                                                                                                                                                                                                                                                    div with type of "translation". The translation division follows the same rules as for the edition, but will usually contains much less markup, and is likely to have a simpler structure. The language of the translation division can be encoded using lang (with two- or three- letter language codes e.g. "de", "fr", "en"). The source or responsibility for the translation can be encoded using source or resp. The translation division can be given a subtype (unconstrained) to describe it further, e.g. "literal", "literary", "pedagogical" etc. For detailed discussion and examples see Translation

                                                                                                                                                                                                                                                                                                    Apparatus

                                                                                                                                                                                                                                                                                                    div with type of "apparatus". The TEI apparatus module is designed for Lachmannian apparatus criticus, which allows for multiple witnesses to a text. The epigraphic apparatus criticus is likely to include comments on letterforms; supplements; interpretations; and the readings of previous editors. For detailed discussion and examples see Apparatus Criticus.

                                                                                                                                                                                                                                                                                                    Commentary

                                                                                                                                                                                                                                                                                                    div with type of "commentary". The commentary division will usually be written in prose, and might contain general discussion of the context of the text or the support, further information about dating criteria, external references, comments on specific sections of the text etc.

                                                                                                                                                                                                                                                                                                    Bibliography

                                                                                                                                                                                                                                                                                                    div with type of "bibliography". The bibliography division can contain both free-standing content and links to the master bibliography, using listBibl with any number of bibl elements. This division can be subdivided further using subtype with unconstrained values that might include e.g. "principal", "derived", "discussion" etc. For detailed discussion and examples see Encoding the Bibliography.

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, Author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, Author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +
                                                                                                                                                                                                                                                                                                    </TEI>

                                                                                                                                                                                                                                                                                                    Edition

                                                                                                                                                                                                                                                                                                    div with type of "edition". The edition division contains the epigraphic, papyrological (etc.) text itself as well as editorial interventions (i.e. representations in EpiDoc of the Leiden sigla) that are to be applied to the text. Leiden equivalence is a minimum requirement; further detail on editorial interventions can be included as required. xml:lang is a required attribute, unless textparts have individual languages (see immediately below).

                                                                                                                                                                                                                                                                                                    The edition division can be divided using div elements with an type of "textpart", which is a constrained value. If textparts have individual languages, xml:lang should be added to each textpart. An edition may have any number of textparts, which can be further subdivided using subtype with unconstrained values (e.g. "fragment", "column" or whatever description is relevant to that particular text). For detailed discussion and examples see List Of All Transcription Guidelines.

                                                                                                                                                                                                                                                                                                    Translation

                                                                                                                                                                                                                                                                                                    div with type of "translation". The translation division follows the same rules as for the edition, but will usually contains much less markup, and is likely to have a simpler structure. The language of the translation division can be encoded using lang (with two- or three- letter language codes e.g. "de", "fr", "en"). The source or responsibility for the translation can be encoded using source or resp. The translation division can be given a subtype (unconstrained) to describe it further, e.g. "literal", "literary", "pedagogical" etc. For detailed discussion and examples see Translation

                                                                                                                                                                                                                                                                                                    Apparatus

                                                                                                                                                                                                                                                                                                    div with type of "apparatus". The TEI apparatus module is designed for Lachmannian apparatus criticus, which allows for multiple witnesses to a text. The epigraphic apparatus criticus is likely to include comments on letterforms; supplements; interpretations; and the readings of previous editors. For detailed discussion and examples see Apparatus Criticus.

                                                                                                                                                                                                                                                                                                    Commentary

                                                                                                                                                                                                                                                                                                    div with type of "commentary". The commentary division will usually be written in prose, and might contain general discussion of the context of the text or the support, further information about dating criteria, external references, comments on specific sections of the text etc.

                                                                                                                                                                                                                                                                                                    Bibliography

                                                                                                                                                                                                                                                                                                    div with type of "bibliography". The bibliography division can contain both free-standing content and links to the master bibliography, using listBibl with any number of bibl elements. This division can be subdivided further using subtype with unconstrained values that might include e.g. "principal", "derived", "discussion" etc. For detailed discussion and examples see Encoding the Bibliography.

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, Author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, Author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/supp-translation-pt-br.html b/gl/dev/supp-translation-pt-br.html index 99b16276a..d1e090b83 100644 --- a/gl/dev/supp-translation-pt-br.html +++ b/gl/dev/supp-translation-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Tradução

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Marcação da tradução do texto para o inglês ou outra língua (geralmente moderna).

                                                                                                                                                                                                                                                                                                    Em um nível mais geral, vale a pena dizer que quase tudo que pode receber marcação, numa divisão de transcrição de texto de uma edição epigráfica ou papirológica, pode, em princípio, também receber marcação na divisão de tradução. Na prática, entretanto, muito menos marcação vai aparecer na maioria das traduções, em alguns casos quase nenhuma.

                                                                                                                                                                                                                                                                                                    Características da divisão

                                                                                                                                                                                                                                                                                                    A tradução ou traduções devem estar contidas em uma divisão do body do arquivo TEI, com um atributo type que a identifique como uma divisão de tradução.

                                                                                                                                                                                                                                                                                                    <div type="translation">
                                                                                                                                                                                                                                                                                                     <p>...</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    No caso de uma edição com múltiplas traduções, cada tradução deve estar contida dentro de um elemento div separado, e pode receber alguns tipos de subcategorias. Por exemplo, uma edição pode conter mais de uma tradução para uma única língua, de acordo com uma tipologia particular; os div de tradução devem então receber atributos subtype com valores como "literal", "poética", "livre" e assim por diante. Talvez o mais comum seja uma edição codificar traduções em mais de uma linguagem moderna, o que seria então diferenciado através de atributos xml:lang. A pessoa responsável pela tradução pode ser indicada pelo atributo resp. Se a tradução for de uma fonte externa, publicada, isto pode ser indicado com o uso do atributo source.

                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="en"
                                                                                                                                                                                                                                                                                                     resp="IPolinskaya ">

                                                                                                                                                                                                                                                                                                     <p>In the year 6960, in the 13th (or 10th) indiction. With the Lord's help, the wall
                                                                                                                                                                                                                                                                                                       was completed. Christ, come as a Helper, to ... Kosta. In the year 6960.</p>
                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="ru"
                                                                                                                                                                                                                                                                                                     resp="AVinogradov">

                                                                                                                                                                                                                                                                                                     <p>6960, в 13-й (или: 10-й) индикт (?). С [Божьей] помощью окончена стена. Приди
                                                                                                                                                                                                                                                                                                       Помощником, Христе, к ... Косте. В 6960 году.</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    Traduções paralelas de um texto completo podem ser codificadas como divisões irmãs no nível principal, com os atributos resp, subtype e xml:lang para indicar qual o tipo de tradução. Quando, em uma edição, existem traduções separadas para partes diferentes do texto, é mais apropriado que sejam codificadas com o uso de <div type="textpart"> como elemento filho da divisão de tradução, em vez de divisões separadas no mesmo nível. Cada tradução pode ter também um apparatus. A correspondência entre partes de uma transcrição e de uma tradução pode ser registrada em um atributo como n (dando o número ou letra da seção correspondente) ou, mais formalmente, através do atributo corresp, linkando a tradução diretamente ao xml:id da divisão que contém o texto correspondente.

                                                                                                                                                                                                                                                                                                    Pode-se imaginar outras maneiras de diferenciar traduções múltiplas, usando diversos atributos TEI em um elemento div.

                                                                                                                                                                                                                                                                                                    Características do texto traduzido

                                                                                                                                                                                                                                                                                                    Como observado acima, uma tradução provavelmente vai precisar de um número bem menor de elementos de marcação que o texto transcrito em si. Os elementos de uma tradução que mais comumente recebem marcação incluem:

                                                                                                                                                                                                                                                                                                    • Restored text: (<supplied reason="lost">) para marcar texto restaurado (muitas vezes palavras ou frases inteiras, já que a tradução raramente vai ser mais próxima que isto do texto original);
                                                                                                                                                                                                                                                                                                    • Editor makes "subaudible" word manifest: (<supplied reason="subaudible">) para marcar palavras ou frases que não estavam presentes na transcrição, incluídas para esclarecimento da tradução;
                                                                                                                                                                                                                                                                                                    • Editor's note: (note) para marcar as palavras do editor que não são parte da tradução em si, como "isto é, 212 CE", ou "não está claro".
                                                                                                                                                                                                                                                                                                    • Abbreviation fully expanded: (expan, ex) na maior parte das vezes utilizado, se for utilizado, para indicar nomes abreviados no original;
                                                                                                                                                                                                                                                                                                    • Lost characters (gap) para indicar trechos significativos de espaço ou lacuna no texto original.

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Tradução

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Marcação da tradução do texto para o inglês ou outra língua (geralmente moderna).

                                                                                                                                                                                                                                                                                                    Em um nível mais geral, vale a pena dizer que quase tudo que pode receber marcação, numa divisão de transcrição de texto de uma edição epigráfica ou papirológica, pode, em princípio, também receber marcação na divisão de tradução. Na prática, entretanto, muito menos marcação vai aparecer na maioria das traduções, em alguns casos quase nenhuma.

                                                                                                                                                                                                                                                                                                    Características da divisão

                                                                                                                                                                                                                                                                                                    A tradução ou traduções devem estar contidas em uma divisão do body do arquivo TEI, com um atributo type que a identifique como uma divisão de tradução.

                                                                                                                                                                                                                                                                                                    <div type="translation">
                                                                                                                                                                                                                                                                                                     <p>...</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    No caso de uma edição com múltiplas traduções, cada tradução deve estar contida dentro de um elemento div separado, e pode receber alguns tipos de subcategorias. Por exemplo, uma edição pode conter mais de uma tradução para uma única língua, de acordo com uma tipologia particular; os div de tradução devem então receber atributos subtype com valores como "literal", "poética", "livre" e assim por diante. Talvez o mais comum seja uma edição codificar traduções em mais de uma linguagem moderna, o que seria então diferenciado através de atributos xml:lang. A pessoa responsável pela tradução pode ser indicada pelo atributo resp. Se a tradução for de uma fonte externa, publicada, isto pode ser indicado com o uso do atributo source.

                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="en"
                                                                                                                                                                                                                                                                                                     resp="IPolinskaya ">

                                                                                                                                                                                                                                                                                                     <p>In the year 6960, in the 13th (or 10th) indiction. With the Lord's help, the wall
                                                                                                                                                                                                                                                                                                       was completed. Christ, come as a Helper, to ... Kosta. In the year 6960.</p>
                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="ru"
                                                                                                                                                                                                                                                                                                     resp="AVinogradov">

                                                                                                                                                                                                                                                                                                     <p>6960, в 13-й (или: 10-й) индикт (?). С [Божьей] помощью окончена стена. Приди
                                                                                                                                                                                                                                                                                                       Помощником, Христе, к ... Косте. В 6960 году.</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    Traduções paralelas de um texto completo podem ser codificadas como divisões irmãs no nível principal, com os atributos resp, subtype e xml:lang para indicar qual o tipo de tradução. Quando, em uma edição, existem traduções separadas para partes diferentes do texto, é mais apropriado que sejam codificadas com o uso de <div type="textpart"> como elemento filho da divisão de tradução, em vez de divisões separadas no mesmo nível. Cada tradução pode ter também um apparatus. A correspondência entre partes de uma transcrição e de uma tradução pode ser registrada em um atributo como n (dando o número ou letra da seção correspondente) ou, mais formalmente, através do atributo corresp, linkando a tradução diretamente ao xml:id da divisão que contém o texto correspondente.

                                                                                                                                                                                                                                                                                                    Pode-se imaginar outras maneiras de diferenciar traduções múltiplas, usando diversos atributos TEI em um elemento div.

                                                                                                                                                                                                                                                                                                    Características do texto traduzido

                                                                                                                                                                                                                                                                                                    Como observado acima, uma tradução provavelmente vai precisar de um número bem menor de elementos de marcação que o texto transcrito em si. Os elementos de uma tradução que mais comumente recebem marcação incluem:

                                                                                                                                                                                                                                                                                                    • Restored text: (<supplied reason="lost">) para marcar texto restaurado (muitas vezes palavras ou frases inteiras, já que a tradução raramente vai ser mais próxima que isto do texto original);
                                                                                                                                                                                                                                                                                                    • Editor makes "subaudible" word manifest: (<supplied reason="subaudible">) para marcar palavras ou frases que não estavam presentes na transcrição, incluídas para esclarecimento da tradução;
                                                                                                                                                                                                                                                                                                    • Editor's note: (note) para marcar as palavras do editor que não são parte da tradução em si, como "isto é, 212 CE", ou "não está claro".
                                                                                                                                                                                                                                                                                                    • Abbreviation fully expanded: (expan, ex) na maior parte das vezes utilizado, se for utilizado, para indicar nomes abreviados no original;
                                                                                                                                                                                                                                                                                                    • Lost characters (gap) para indicar trechos significativos de espaço ou lacuna no texto original.

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/supp-translation.html b/gl/dev/supp-translation.html index c33c4ba6d..ddaee33b4 100644 --- a/gl/dev/supp-translation.html +++ b/gl/dev/supp-translation.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Translation

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Tagging the translation of the text into English or another (usually modern) language.

                                                                                                                                                                                                                                                                                                    At the most general level, it is worth saying that almost anything that can be tagged in the transcribed text division of an epigraphic or papyrological edition can in principle also be tagged in the translation division. In practice, however, far less markup will appear in most translations, in some cases almost none at all.

                                                                                                                                                                                                                                                                                                    Features of the division

                                                                                                                                                                                                                                                                                                    The translation or translations should be contained in a division of the body of the TEI file, with a type attribute identifying it as a translation division.

                                                                                                                                                                                                                                                                                                    <div type="translation">
                                                                                                                                                                                                                                                                                                     <p>...</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    In the case of an edtion with multiple translations, each translation should be encoded in a separate div and might be subcategorized in some way. For instance, an edition might contain more than one translation into a single language, according to a particular typology; the translation divs could therefore bear subtype attributes with values such as "literal", "poetic", "free" and so forth. Perhaps more commonly, an edition might encode translations in more than one modern language, which would then be differentiated by means of xml:lang attributes. The person responsible for the translation can be indicated by the resp attribute. If the translation is ascribed to an external, published source, this can be indicated using the source attribute.

                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="en"
                                                                                                                                                                                                                                                                                                     resp="IPolinskaya ">

                                                                                                                                                                                                                                                                                                     <p>In the year 6960, in the 13th (or 10th) indiction. With the Lord's help, the wall was completed.
                                                                                                                                                                                                                                                                                                       Christ, come as a Helper, to ... Kosta. In the year 6960.</p>
                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="ru"
                                                                                                                                                                                                                                                                                                     resp="AVinogradov">

                                                                                                                                                                                                                                                                                                     <p>6960, в 13-й (или: 10-й) индикт (?). С [Божьей] помощью окончена стена.
                                                                                                                                                                                                                                                                                                       Приди Помощником, Христе, к ... Косте. В 6960 году.</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    Parallel translations of a full text should be encoded as sibling, top-level divisions, with resp, subtype and xml:lang attributes to indicate the kind of translation. When there are separate translations for different parts of the text in an edition, theyt are most appropriately encoded using <div type="textpart"> as children of the translation division, rather than as separate top-level divisions. Each translation may have an apparatus as well. The correspondence between parts of the transcription and of the translation might be recorded in an attribute such as n (giving the number or letter of the corresponding section), or more formally, corresp, linking directly to the xml:id of a division containing the corresponding text.

                                                                                                                                                                                                                                                                                                    Other means of differentiating multiple translations, using the various TEI attributes on div are imaginable.

                                                                                                                                                                                                                                                                                                    Features of the translated text

                                                                                                                                                                                                                                                                                                    As noted above, the translation is likely to require far fewer features of markup than the transcribed text itself. The features most commonly tagged in translations include:

                                                                                                                                                                                                                                                                                                    • Restored text: (<supplied reason="lost">) to tag restored text (most often entire words or phrases, since the translation will seldom align with the original text more finely than this);
                                                                                                                                                                                                                                                                                                    • Editor makes "subaudible" word manifest: (<supplied reason="subaudible">) to tag words or phrases added by way of clarification in the translation that were not present in the transcription;
                                                                                                                                                                                                                                                                                                    • Editor's note: (note) to tag the editor's words that are not part of the translation per se, such as "i.e. 212 CE", or "unclear".
                                                                                                                                                                                                                                                                                                    • Abbreviation fully expanded: (expan, ex) most often used to indicate names, if at all, abbreviated in the original;
                                                                                                                                                                                                                                                                                                    • Lost characters (gap) to indicate significant spans of lacuna in the original text.

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Translation

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Tagging the translation of the text into English or another (usually modern) language.

                                                                                                                                                                                                                                                                                                    At the most general level, it is worth saying that almost anything that can be tagged in the transcribed text division of an epigraphic or papyrological edition can in principle also be tagged in the translation division. In practice, however, far less markup will appear in most translations, in some cases almost none at all.

                                                                                                                                                                                                                                                                                                    Features of the division

                                                                                                                                                                                                                                                                                                    The translation or translations should be contained in a division of the body of the TEI file, with a type attribute identifying it as a translation division.

                                                                                                                                                                                                                                                                                                    <div type="translation">
                                                                                                                                                                                                                                                                                                     <p>...</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    In the case of an edtion with multiple translations, each translation should be encoded in a separate div and might be subcategorized in some way. For instance, an edition might contain more than one translation into a single language, according to a particular typology; the translation divs could therefore bear subtype attributes with values such as "literal", "poetic", "free" and so forth. Perhaps more commonly, an edition might encode translations in more than one modern language, which would then be differentiated by means of xml:lang attributes. The person responsible for the translation can be indicated by the resp attribute. If the translation is ascribed to an external, published source, this can be indicated using the source attribute.

                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="en"
                                                                                                                                                                                                                                                                                                     resp="IPolinskaya ">

                                                                                                                                                                                                                                                                                                     <p>In the year 6960, in the 13th (or 10th) indiction. With the Lord's help, the wall was completed.
                                                                                                                                                                                                                                                                                                       Christ, come as a Helper, to ... Kosta. In the year 6960.</p>
                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                    <div type="translationxml:lang="ru"
                                                                                                                                                                                                                                                                                                     resp="AVinogradov">

                                                                                                                                                                                                                                                                                                     <p>6960, в 13-й (или: 10-й) индикт (?). С [Божьей] помощью окончена стена.
                                                                                                                                                                                                                                                                                                       Приди Помощником, Христе, к ... Косте. В 6960 году.</p>
                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                    Parallel translations of a full text should be encoded as sibling, top-level divisions, with resp, subtype and xml:lang attributes to indicate the kind of translation. When there are separate translations for different parts of the text in an edition, theyt are most appropriately encoded using <div type="textpart"> as children of the translation division, rather than as separate top-level divisions. Each translation may have an apparatus as well. The correspondence between parts of the transcription and of the translation might be recorded in an attribute such as n (giving the number or letter of the corresponding section), or more formally, corresp, linking directly to the xml:id of a division containing the corresponding text.

                                                                                                                                                                                                                                                                                                    Other means of differentiating multiple translations, using the various TEI attributes on div are imaginable.

                                                                                                                                                                                                                                                                                                    Features of the translated text

                                                                                                                                                                                                                                                                                                    As noted above, the translation is likely to require far fewer features of markup than the transcribed text itself. The features most commonly tagged in translations include:

                                                                                                                                                                                                                                                                                                    • Restored text: (<supplied reason="lost">) to tag restored text (most often entire words or phrases, since the translation will seldom align with the original text more finely than this);
                                                                                                                                                                                                                                                                                                    • Editor makes "subaudible" word manifest: (<supplied reason="subaudible">) to tag words or phrases added by way of clarification in the translation that were not present in the transcription;
                                                                                                                                                                                                                                                                                                    • Editor's note: (note) to tag the editor's words that are not part of the translation per se, such as "i.e. 212 CE", or "unclear".
                                                                                                                                                                                                                                                                                                    • Abbreviation fully expanded: (expan, ex) most often used to indicate names, if at all, abbreviated in the original;
                                                                                                                                                                                                                                                                                                    • Lost characters (gap) to indicate significant spans of lacuna in the original text.

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/toc-bg.html b/gl/dev/toc-bg.html index 44f383297..1048c68c4 100644 --- a/gl/dev/toc-bg.html +++ b/gl/dev/toc-bg.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    EpiDoc Насоки: Антични документи в TEI XML формат

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    EpiDoc е международен проект, основаващ се на взаимно сътрудничество, който предлага насоки и инструменти за кодиране на научни и образователни издания на антични документи. Настоящият текст представлява Насоки, които са продукт от усилията на екипа от сътрудници. В допълнение,сайтът на EpiDoc осигурява достъп до всички инструменти и среди на сътрудничество, поддържани от екипа.

                                                                                                                                                                                                                                                                                                    EpiDoc се позовава на стандарта на Text Encoding Initiative за пресъздаване на текстове в дигитален формат, използвайки Extensible Markup Language (XML), технически стандарт, разпространен от World-Wide Web Consortium. Той е насочен не само към транскрибирането и редакторската подготовка на самите текстове, но също така и към историята и материала на обектите, върху които се намира текстът.

                                                                                                                                                                                                                                                                                                    Настоящите Насоки съдържат описания на текстовите, описателните и други особености, които често се изразяват чрез EpiDoc, а също така и чрез елементи на TEI и атрибути, използвани за тяхното кодиране. Връзките по-долу предлагат няколко отправни точки към целия документ, които трябва да се смятат по-скоро за поредица от тематични индекси към съдържанието на Насоките, отколкото за „съдържание“ само по себе си, отразяващо подредена и йерархична структура на документа.

                                                                                                                                                                                                                                                                                                    Търсене в Насоките

                                                                                                                                                                                                                                                                                                    Насоки, поддържани от външни източници за специализирани общности:

                                                                                                                                                                                                                                                                                                    Също така може да свалите и архивирано копие на последния вариант на Насоките от нашия раздел „Файлове“, ако желаете да ги използвате офлайн.

                                                                                                                                                                                                                                                                                                    Можете да се консултирате с предишните версии на Насоките в Архивите в секция Files.

                                                                                                                                                                                                                                                                                                    При цитиране на Насоките за EpiDoc, моля, използвайте следната информация:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), EpiDoc Guidelines: Ancient documents in TEI XML (Version 9). Достъпни на: https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Отговорни лица за този раздел:

                                                                                                                                                                                                                                                                                                    1. Габриел Бодар, автор
                                                                                                                                                                                                                                                                                                    2. Ели Милонас, автор
                                                                                                                                                                                                                                                                                                    3. Том Елиът, автор
                                                                                                                                                                                                                                                                                                    4. Симона Стоянова, автор
                                                                                                                                                                                                                                                                                                    5. Мария Дончева, преведе на български език
                                                                                                                                                                                                                                                                                                    6. Полина Йорданова, редактор на превода

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    EpiDoc Насоки: Антични документи в TEI XML формат

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    EpiDoc е международен проект, основаващ се на взаимно сътрудничество, който предлага насоки и инструменти за кодиране на научни и образователни издания на антични документи. Настоящият текст представлява Насоки, които са продукт от усилията на екипа от сътрудници. В допълнение,сайтът на EpiDoc осигурява достъп до всички инструменти и среди на сътрудничество, поддържани от екипа.

                                                                                                                                                                                                                                                                                                    EpiDoc се позовава на стандарта на Text Encoding Initiative за пресъздаване на текстове в дигитален формат, използвайки Extensible Markup Language (XML), технически стандарт, разпространен от World-Wide Web Consortium. Той е насочен не само към транскрибирането и редакторската подготовка на самите текстове, но също така и към историята и материала на обектите, върху които се намира текстът.

                                                                                                                                                                                                                                                                                                    Настоящите Насоки съдържат описания на текстовите, описателните и други особености, които често се изразяват чрез EpiDoc, а също така и чрез елементи на TEI и атрибути, използвани за тяхното кодиране. Връзките по-долу предлагат няколко отправни точки към целия документ, които трябва да се смятат по-скоро за поредица от тематични индекси към съдържанието на Насоките, отколкото за „съдържание“ само по себе си, отразяващо подредена и йерархична структура на документа.

                                                                                                                                                                                                                                                                                                    Търсене в Насоките

                                                                                                                                                                                                                                                                                                    Насоки, поддържани от външни източници за специализирани общности:

                                                                                                                                                                                                                                                                                                    Също така може да свалите и архивирано копие на последния вариант на Насоките от нашия раздел „Файлове“, ако желаете да ги използвате офлайн.

                                                                                                                                                                                                                                                                                                    Можете да се консултирате с предишните версии на Насоките в Архивите в секция Files.

                                                                                                                                                                                                                                                                                                    При цитиране на Насоките за EpiDoc, моля, използвайте следната информация:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), EpiDoc Guidelines: Ancient documents in TEI XML (Version 9). Достъпни на: https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Отговорни лица за този раздел:

                                                                                                                                                                                                                                                                                                    1. Габриел Бодар, автор
                                                                                                                                                                                                                                                                                                    2. Ели Милонас, автор
                                                                                                                                                                                                                                                                                                    3. Том Елиът, автор
                                                                                                                                                                                                                                                                                                    4. Симона Стоянова, автор
                                                                                                                                                                                                                                                                                                    5. Мария Дончева, преведе на български език
                                                                                                                                                                                                                                                                                                    6. Полина Йорданова, редактор на превода

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/toc-es.html b/gl/dev/toc-es.html index 083ea999f..49511db49 100644 --- a/gl/dev/toc-es.html +++ b/gl/dev/toc-es.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Guía de Uso de EpiDoc: Documentos antiguos en TEI XML

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    EpiDoc es un esfuerzo internacional y colaborativo que proporciona pautas y herramientas para codificar ediciones académicas y didácticas de documentos antiguos. El presente texto es su Guía de Uso, producida por sus colaboradores. Además, el sitio Web EpiDoc proporciona acceso a todas las herramientas y a los entornos necesarios.

                                                                                                                                                                                                                                                                                                    EpiDoc emplea un subconjunto de Text Encoding Initiative para la representación de textos de forma digital usando el Extensible Markup Language (XML), un estándar técnico promulgado por el World-Wide Web Consortium. No sólo está dirigido a la transcripción y a la preparación editorial de textos, sino también a la historia y a la materialidad de los objetos en los que los textos aparecen.

                                                                                                                                                                                                                                                                                                    La presente Guía de Uso contiene descripciones de las características textuales y descriptivas, entre otras, que suelen expresarse con EpiDoc, así como los elementos y atributos TEI que se emplean para codificarlos. Los vínculos de la parte inferior proporcionan numerosas entradas al documento completo y deben entenderse como una serie de índices temáticos al contenido de la Guía de Uso más que como una simple tabla de contenidos que refleje una estructura ordenada y jerárquica del documento.

                                                                                                                                                                                                                                                                                                    También se puede descargar una copia en zip de la versión más reciente de la Guía desde nuestra sección "Archivos" (Files) si se necesita trabajar sin conexión.

                                                                                                                                                                                                                                                                                                    Puede consultar versiones anteriores de la Guía en el Archivo (Archive) en la sección Ficheros (Files).

                                                                                                                                                                                                                                                                                                    Para citar la Guía de EpiDoc, por favor use la siguiente información:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), EpiDoc Guidelines: Ancient documents in TEI XML (Versión 9). Disponible en: https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Responsables de esta sección

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Elli Mylonas, autora
                                                                                                                                                                                                                                                                                                    3. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                    4. Simona Stoyanova, autora
                                                                                                                                                                                                                                                                                                    5. María José Estarán Tolosa, traducido al español
                                                                                                                                                                                                                                                                                                    6. Núria Garcia Casacuberta, traducido al español

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Guía de Uso de EpiDoc: Documentos antiguos en TEI XML

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    EpiDoc es un esfuerzo internacional y colaborativo que proporciona pautas y herramientas para codificar ediciones académicas y didácticas de documentos antiguos. El presente texto es su Guía de Uso, producida por sus colaboradores. Además, el sitio Web EpiDoc proporciona acceso a todas las herramientas y a los entornos necesarios.

                                                                                                                                                                                                                                                                                                    EpiDoc emplea un subconjunto de Text Encoding Initiative para la representación de textos de forma digital usando el Extensible Markup Language (XML), un estándar técnico promulgado por el World-Wide Web Consortium. No sólo está dirigido a la transcripción y a la preparación editorial de textos, sino también a la historia y a la materialidad de los objetos en los que los textos aparecen.

                                                                                                                                                                                                                                                                                                    La presente Guía de Uso contiene descripciones de las características textuales y descriptivas, entre otras, que suelen expresarse con EpiDoc, así como los elementos y atributos TEI que se emplean para codificarlos. Los vínculos de la parte inferior proporcionan numerosas entradas al documento completo y deben entenderse como una serie de índices temáticos al contenido de la Guía de Uso más que como una simple tabla de contenidos que refleje una estructura ordenada y jerárquica del documento.

                                                                                                                                                                                                                                                                                                    También se puede descargar una copia en zip de la versión más reciente de la Guía desde nuestra sección "Archivos" (Files) si se necesita trabajar sin conexión.

                                                                                                                                                                                                                                                                                                    Puede consultar versiones anteriores de la Guía en el Archivo (Archive) en la sección Ficheros (Files).

                                                                                                                                                                                                                                                                                                    Para citar la Guía de EpiDoc, por favor use la siguiente información:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), EpiDoc Guidelines: Ancient documents in TEI XML (Versión 9). Disponible en: https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Responsables de esta sección

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Elli Mylonas, autora
                                                                                                                                                                                                                                                                                                    3. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                    4. Simona Stoyanova, autora
                                                                                                                                                                                                                                                                                                    5. María José Estarán Tolosa, traducido al español
                                                                                                                                                                                                                                                                                                    6. Núria Garcia Casacuberta, traducido al español

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/toc-it.html b/gl/dev/toc-it.html index d8c4a5fc4..b3bd9f727 100644 --- a/gl/dev/toc-it.html +++ b/gl/dev/toc-it.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Linee Guida EpiDoc: documenti antichi in XML TEI

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    EpiDoc è il risultato di un lavoro internazionale e collaborativo che fornisca linee guida e strumenti per la codifica di edizioni erudite e scolastiche di testi antichi. Queste sono le Linee Guida prodotte da questa collaborazione. Inoltre, il sito EpiDoc fornisce accesso a tutti gli strumenti e gli ambienti di collaborazione mantenuti dal collaborativo.

                                                                                                                                                                                                                                                                                                    EpiDoc usa un sottoinsieme dello standard Text Encoding Initiative per la rappresentazione di testi in forma digitale, usando il linguaggio di marcatura estensibile XML, uno standard tecnico promulgato dal World-Wide Web Consortium. Esso si occupa non solo della trascrizione e della preparazione ecdotica dei testi stessi, ma anche della storia e della materialità dell'oggetto in cui il testo appare.

                                                                                                                                                                                                                                                                                                    Queste Linee Guida contengono descrizioni delle caratteristiche testuali, descrittive e altro, che si possono esprimere e codificare con elementi e attributi EpiDoc e TEI. I link qui sotto forniscono una serie di punti di entrata nel documento completo e devono essere intesi più come una serie di indici tematici dei contenuti delle Linee Guida, che come una "tavola dei contenuti" singola che rifletta la struttura di un documento in modo ordinato e gerarchico.

                                                                                                                                                                                                                                                                                                    È inoltre possibile scaricare una copia compressa delle Linee Guida più recenti dalla nostra sezione Files, in caso debbano essere usate offline.

                                                                                                                                                                                                                                                                                                    Versioni precedenti delle Linee Guida possono essere consultate nell'area Archivio della sezione Files.

                                                                                                                                                                                                                                                                                                    Per citare le Linee Guida EpiDoc, è necessario usare la seguente formula:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), EpiDoc Guidelines: Ancient documents in TEI XML (Version 9). Available: https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Responsabilità per questa sezione:

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autore
                                                                                                                                                                                                                                                                                                    2. Elli Mylonas, autore
                                                                                                                                                                                                                                                                                                    3. Tom Elliott, autore
                                                                                                                                                                                                                                                                                                    4. Simona Stoyanova, autore
                                                                                                                                                                                                                                                                                                    5. Eleonora Litta, traduzione italiana
                                                                                                                                                                                                                                                                                                    6. Greta Franzini, traduzione italiana
                                                                                                                                                                                                                                                                                                    7. Irene Vagionakis, traduzione italiana

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Linee Guida EpiDoc: documenti antichi in XML TEI

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    EpiDoc è il risultato di un lavoro internazionale e collaborativo che fornisca linee guida e strumenti per la codifica di edizioni erudite e scolastiche di testi antichi. Queste sono le Linee Guida prodotte da questa collaborazione. Inoltre, il sito EpiDoc fornisce accesso a tutti gli strumenti e gli ambienti di collaborazione mantenuti dal collaborativo.

                                                                                                                                                                                                                                                                                                    EpiDoc usa un sottoinsieme dello standard Text Encoding Initiative per la rappresentazione di testi in forma digitale, usando il linguaggio di marcatura estensibile XML, uno standard tecnico promulgato dal World-Wide Web Consortium. Esso si occupa non solo della trascrizione e della preparazione ecdotica dei testi stessi, ma anche della storia e della materialità dell'oggetto in cui il testo appare.

                                                                                                                                                                                                                                                                                                    Queste Linee Guida contengono descrizioni delle caratteristiche testuali, descrittive e altro, che si possono esprimere e codificare con elementi e attributi EpiDoc e TEI. I link qui sotto forniscono una serie di punti di entrata nel documento completo e devono essere intesi più come una serie di indici tematici dei contenuti delle Linee Guida, che come una "tavola dei contenuti" singola che rifletta la struttura di un documento in modo ordinato e gerarchico.

                                                                                                                                                                                                                                                                                                    È inoltre possibile scaricare una copia compressa delle Linee Guida più recenti dalla nostra sezione Files, in caso debbano essere usate offline.

                                                                                                                                                                                                                                                                                                    Versioni precedenti delle Linee Guida possono essere consultate nell'area Archivio della sezione Files.

                                                                                                                                                                                                                                                                                                    Per citare le Linee Guida EpiDoc, è necessario usare la seguente formula:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), EpiDoc Guidelines: Ancient documents in TEI XML (Version 9). Available: https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Responsabilità per questa sezione:

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autore
                                                                                                                                                                                                                                                                                                    2. Elli Mylonas, autore
                                                                                                                                                                                                                                                                                                    3. Tom Elliott, autore
                                                                                                                                                                                                                                                                                                    4. Simona Stoyanova, autore
                                                                                                                                                                                                                                                                                                    5. Eleonora Litta, traduzione italiana
                                                                                                                                                                                                                                                                                                    6. Greta Franzini, traduzione italiana
                                                                                                                                                                                                                                                                                                    7. Irene Vagionakis, traduzione italiana

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/toc-pt-br.html b/gl/dev/toc-pt-br.html index 4cdf6d44c..f72a7d221 100644 --- a/gl/dev/toc-pt-br.html +++ b/gl/dev/toc-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Normas EpiDoc: Documentos antigos em TEI XML

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    EpiDoc é um esforço colaborativo internacional que fornece normas e ferramentas para a codificação de edições de pesquisa ou educacionais de documentos antigos. Estas páginas são as Normas EpiDoc produzidas pelo colaborativo. Além delas, o EpiDoc Website fornece o acesso a outras ferramentas e ambientes de colaboração que recebem suporte do colaborativo.

                                                                                                                                                                                                                                                                                                    EpiDoc especifica um subconjunto do padrão Text Encoding Initiative(Iniciativa de Codificação de Texto) para a representação de textos em forma digital, fazendo uso de Extensible Markup Language (XML), um padrão técnico promulgado pelo World-Wide Web Consortium(Consórcio da Rede Mundial), endereçado não apenas à transcrição ou à preparação editorial dos textos em si, mas também à história, materialidade e metadata dos objetos onde aparecem os textos.

                                                                                                                                                                                                                                                                                                    Estas Normas contém descrições das características textuais, descritivas e outras que são expressas com o EpiDoc, bem como os elementos e atributos TEI utilizados para codificá-los. As páginas abaixo fornecem uma série de pontos de entrada para a documentação completa, através de uma quantidade de índices temáticos do conteúdo das Normas, em vez de um único índice refletindo uma estrutura de documentos ordenada e hierárquica (e inexistente).

                                                                                                                                                                                                                                                                                                    Apêndices

                                                                                                                                                                                                                                                                                                    Normas mantidas externamente para comunidades especializadas:

                                                                                                                                                                                                                                                                                                    Você também pode fazer o download de uma cópia zipada das Normas atualizadas para sua seção Arquivos, se precisar utilizá-las offline.

                                                                                                                                                                                                                                                                                                    Você pode consultar versões antigas das Normas na áreaAcervo da seção Arquivos.

                                                                                                                                                                                                                                                                                                    Para citar as Normas EpiDoc, por favor utilize as seguintes informações:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), Normas EpiDoc: Documentos antigos em TEI XML (Versão 9). Disponível em:https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Elli Mylonas, autor
                                                                                                                                                                                                                                                                                                    3. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                    4. Simona Stoyanova, autor
                                                                                                                                                                                                                                                                                                    5. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    6. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Normas EpiDoc: Documentos antigos em TEI XML

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    EpiDoc é um esforço colaborativo internacional que fornece normas e ferramentas para a codificação de edições de pesquisa ou educacionais de documentos antigos. Estas páginas são as Normas EpiDoc produzidas pelo colaborativo. Além delas, o EpiDoc Website fornece o acesso a outras ferramentas e ambientes de colaboração que recebem suporte do colaborativo.

                                                                                                                                                                                                                                                                                                    EpiDoc especifica um subconjunto do padrão Text Encoding Initiative(Iniciativa de Codificação de Texto) para a representação de textos em forma digital, fazendo uso de Extensible Markup Language (XML), um padrão técnico promulgado pelo World-Wide Web Consortium(Consórcio da Rede Mundial), endereçado não apenas à transcrição ou à preparação editorial dos textos em si, mas também à história, materialidade e metadata dos objetos onde aparecem os textos.

                                                                                                                                                                                                                                                                                                    Estas Normas contém descrições das características textuais, descritivas e outras que são expressas com o EpiDoc, bem como os elementos e atributos TEI utilizados para codificá-los. As páginas abaixo fornecem uma série de pontos de entrada para a documentação completa, através de uma quantidade de índices temáticos do conteúdo das Normas, em vez de um único índice refletindo uma estrutura de documentos ordenada e hierárquica (e inexistente).

                                                                                                                                                                                                                                                                                                    Apêndices

                                                                                                                                                                                                                                                                                                    Normas mantidas externamente para comunidades especializadas:

                                                                                                                                                                                                                                                                                                    Você também pode fazer o download de uma cópia zipada das Normas atualizadas para sua seção Arquivos, se precisar utilizá-las offline.

                                                                                                                                                                                                                                                                                                    Você pode consultar versões antigas das Normas na áreaAcervo da seção Arquivos.

                                                                                                                                                                                                                                                                                                    Para citar as Normas EpiDoc, por favor utilize as seguintes informações:

                                                                                                                                                                                                                                                                                                    Tom Elliott, Gabriel Bodard, Elli Mylonas, Simona Stoyanova, Charlotte Tupman, Scott Vanderbilt, et al. (2007-2020), Normas EpiDoc: Documentos antigos em TEI XML (Versão 9). Disponível em:https://epidoc.stoa.org/gl/latest/.

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Elli Mylonas, autor
                                                                                                                                                                                                                                                                                                    3. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                    4. Simona Stoyanova, autor
                                                                                                                                                                                                                                                                                                    5. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    6. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevfully-pt-br.html b/gl/dev/trans-abbrevfully-pt-br.html index cc0260d26..697b1a6f2 100644 --- a/gl/dev/trans-abbrevfully-pt-br.html +++ b/gl/dev/trans-abbrevfully-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abreviação completamente expandida

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    abbr (abreviação) contém a parte abreviada, ou seja, as letras realmente presentes na pedra/página.

                                                                                                                                                                                                                                                                                                    expan (palavra expandida) contém a expansão completa de uma palavra ou termo abreviado.

                                                                                                                                                                                                                                                                                                    ex (expansão editorial) contém as letras adicionadas pelo editor quando se expande uma abreviação.

                                                                                                                                                                                                                                                                                                    No caso mais simples de abreviação, quando algumas letras se encontram na pedra/suporte e o editor expande esta palavra através da adição de letras depois da abreviação— entre parênteses no Leiden, como em "Aug(ustus)"—a marcação TEI recomenda que o EpiDoc identifique três componentes desta palavra:

                                                                                                                                                                                                                                                                                                    1. a palavra completamente expandida: a palavra completa, com a abreviação e a expansão, como aparece na versão editorial (no nosso exemplo, "Augustus"). A tag utilizada neste caso é o elemento expan .
                                                                                                                                                                                                                                                                                                    2. a abreviação: os caracteres que estão realmente na pedra, ou que apareceriam na transcrição diplomática (no nosso exemplo, "Aug" ou "AVG"). A tag utilizada neste caso é abbr.
                                                                                                                                                                                                                                                                                                    3. a expansão editorial: os caracteres adicionados pelo editor para expandir a abreviação (no nosso exemplo, "ustus"). A tag utilizada neste caso é ex.

                                                                                                                                                                                                                                                                                                    Nosso elemento, ao final, estaria completamente marcado para que todos os três elementos contenham as letras correspondentes ao componente em questão, sem que letras precisem ser repetidas:

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>Aug</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ustus</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Abreviações resolvidas e não resolvidas são tratadas de modo ligeirametne diferente, pois neste caso não há a palavra expandida ou a expansão editorial, portanto apenas a tag abbr (cuja semântica não foi, portanto, alterada) precisa ser utilizada. Veja Abreviação não expandida para maiores detalhes na marcação de abreviações cuja a expansão não é conhecida.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.1; SEG; Sosin 2011; : a(bc)

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>a</abbr>
                                                                                                                                                                                                                                                                                                     <ex>bc</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: a(bc)
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <expan>Καρ<ex>ανίδι</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Καρ(ανίδι)
                                                                                                                                                                                                                                                                                                    Note: Note que, por razões históricas, o Duke Databank não usa o elemento abbr para abreviações expandidas.
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>Iul</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ius</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Iul(ius)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>trib</abbr>
                                                                                                                                                                                                                                                                                                     <ex>unicia</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: trib(unicia)
                                                                                                                                                                                                                                                                                                    (IRT: 24)

                                                                                                                                                                                                                                                                                                    Uma palavra que esteja suspensa em vez de abreviada recebe o mesmo tipo de tag, desde que se entenda (tanto semanticamente quanto no processamento, como na renderização XSLT e nas ferramentas de indexação) que múltiplos elementos abbr dentro e um único expan compõe uma única abreviação. Por exemplo, no caso de "QQ", que se expande para "q(uin)q(uennalis)", usamos a seguinte codificação:

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>q</abbr>
                                                                                                                                                                                                                                                                                                     <ex>uin</ex>
                                                                                                                                                                                                                                                                                                     <abbr>q</abbr>
                                                                                                                                                                                                                                                                                                     <ex>uennalis</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Se o texto abreviado implica tacitamente uma palavra ou palavras suplementares que são compreendidas mas omitidas do suporte original (como tribu, filius, etc.), a abreviação pode ser codificada de dois modos diferentes, dependendo da renderização desejada. No primeiro, todo o texto omitido fica dentro da tag ex. No segundo, apenas os caracters que formam uma parte da palavra que foi abreviada ficam dentro de ex, enquanto a(s) palavra(s) omitida(s) fica(m) dentro de um elemento supplied, cujo atributo reason deve receber um valor "subaudible". Veja os exemplos abaixo.


                                                                                                                                                                                                                                                                                                    <!-- RIB 293 --><expan>
                                                                                                                                                                                                                                                                                                     <abbr>Poll</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ia</ex>
                                                                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                                                                    <supplied reason="subaudible">tribu</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Poll(ia) (scil. tribu)
                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                    <!-- RIB 293 --><expan>
                                                                                                                                                                                                                                                                                                     <abbr>Poll</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ia tribu</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Poll(ia tribu)
                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevfully.html b/gl/dev/trans-abbrevfully.html index 2c42cf9b2..c86babb6f 100644 --- a/gl/dev/trans-abbrevfully.html +++ b/gl/dev/trans-abbrevfully.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abbreviation fully expanded

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    abbr (abbreviation) contains the abbreviated part, i.e. the letters actually on the stone/page.

                                                                                                                                                                                                                                                                                                    expan (expanded word) contains the full expansion of an abbreviated word or term.

                                                                                                                                                                                                                                                                                                    ex (editorial expansion) contains the letters added by the editor when expanding an abbreviation.

                                                                                                                                                                                                                                                                                                    In the simplest case of an abbreviation where a few letters are on the stone/support, and the editor expands this word by the addition of letters after the abbreviation—with parentheses in Leiden, for example "Aug(ustus)"—the TEI markup recommended by EpiDoc identifies three components of this word:

                                                                                                                                                                                                                                                                                                    1. the fully expanded word: the whole word, including both abbreviation and expansion, that appears in an editorial edition (in our example "Augustus"). This is tagged using the expan element.
                                                                                                                                                                                                                                                                                                    2. the abbreviation: the characters that are actually on the stone, or would appear in a diplomatic transcription (in our example "Aug" or "AVG"). These are tagged using the abbr element.
                                                                                                                                                                                                                                                                                                    3. the editorial expansion: the characters added by the editor in expanding the abbreviation (in our example, "ustus"). These are tagged with ex.

                                                                                                                                                                                                                                                                                                    In full, our example would therefore be tagged so that each of the three elements contains the letters corresponding to the component in question, with no letters needing to be repeated:

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>Aug</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ustus</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Resolved and unresolved abbreviations are treated slightly differently, in that there is no expanded word nor editorial expansion, so only the abbr (whose semantics is therefore unchanged) need be tagged. See Abbreviation not expanded at all for more detail on marking up abbreviations for which the expansion is unknown.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.1; SEG; Sosin 2011; : a(bc)

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>a</abbr>
                                                                                                                                                                                                                                                                                                     <ex>bc</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: a(bc)
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <expan>Καρ<ex>ανίδι</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Καρ(ανίδι)
                                                                                                                                                                                                                                                                                                    Note: Note that for historical reasons the Duke Databank does not use the abbr element for expanded abbreviations.
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>Iul</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ius</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Iul(ius)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>trib</abbr>
                                                                                                                                                                                                                                                                                                     <ex>unicia</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: trib(unicia)
                                                                                                                                                                                                                                                                                                    (IRT: 24)

                                                                                                                                                                                                                                                                                                    A suspended rather than abbreviated word is tagged in precisely the same way, with the undertstanding (both semantically and by processing such as rendering XSLT and indexing tools) that multiple abbr elements within a single expan are considered to compose a single abbreviation between them. For example, in the case of "QQ" expanding to "q(uin)q(uennalis)", we might encode as follows:

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>q</abbr>
                                                                                                                                                                                                                                                                                                     <ex>uin</ex>
                                                                                                                                                                                                                                                                                                     <abbr>q</abbr>
                                                                                                                                                                                                                                                                                                     <ex>uennalis</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    If the abbreviated text tacitly implies a supplementary word or words which are understood but omitted from the original support (e.g., tribu, filius, etc.), the abbreviation may be encoded in two different ways depending on the rendering desired. In the first, all omitted text is enclosed within ex. In the second, only the characters which form part of the word actually abbreviated are enclosed within ex, while the word(s) omitted but understood are enclosed within a supplied element, whose reason attribute should be given a value of "subaudible". See examples below.


                                                                                                                                                                                                                                                                                                    <!-- RIB 293 --><expan>
                                                                                                                                                                                                                                                                                                     <abbr>Poll</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ia</ex>
                                                                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                                                                    <supplied reason="subaudible">tribu</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Poll(ia) (scil. tribu)
                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                    <!-- RIB 293 --><expan>
                                                                                                                                                                                                                                                                                                     <abbr>Poll</abbr>
                                                                                                                                                                                                                                                                                                     <ex>ia tribu</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Poll(ia tribu)
                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    2. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevmark-pt-br.html b/gl/dev/trans-abbrevmark-pt-br.html index 055b2eaf4..b8c97fd85 100644 --- a/gl/dev/trans-abbrevmark-pt-br.html +++ b/gl/dev/trans-abbrevmark-pt-br.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Expansão de abreviação com inclusão de símbolo/caracteres

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Uma abreviação que inclua uma marca de algum tipo, como uma letra ou marca de pontuação adicional, que não aparecerá na forma expandida. Isto é muitas vezes omitido em edições convencionais, mas pode ser útil de se incluir em uma transcrição digital, por exemplo para a inclusão em uma renderização diplomática.

                                                                                                                                                                                                                                                                                                    Quaisquer caracteres ou símbolos que apareçam na versão abreviada presente no suporte (abbr), mas que não seja parte da palavra completamente expandida (expan), devem ser incluídos dentro do elemento abbr, e deve ainda receber a marcação do elemento am (marca de abreviação). Na tansformação XSLT padrão, por exemplo, isto faria com que o conteúdo da tag am fosse omitido da transcrição interpretativa, mas incluído na edição diplomática. (O primeiro exemplo abaixo, portanto, apareceria como "Aug(usti duo)" na forma interpretativa e como "AVGG" na diplomática.)

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>Aug<am>g</am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex>usti duo</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Aug(usti duo)
                                                                                                                                                                                                                                                                                                    (EDH: HD000067)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                       <g type="sestertius"/>
                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex>sestertios</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: (sestertios)
                                                                                                                                                                                                                                                                                                    (IRT: 788)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                       <g type="dot"/>
                                                                                                                                                                                                                                                                                                       <g type="reverse-slanting-stroke"/>
                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex cert="low">ὡς ἐτῶν</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: (ὡς ἐτῶν(?))
                                                                                                                                                                                                                                                                                                    (DDbDP: sb.14.11692#1)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    4. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                    5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevmark.html b/gl/dev/trans-abbrevmark.html index c0004effa..11b389132 100644 --- a/gl/dev/trans-abbrevmark.html +++ b/gl/dev/trans-abbrevmark.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Expansion of abbreviation including symbol/characters

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    An abbreviation that includes a mark of some kind, such as an additional letter or mark of punctuation, that will not appear in the expanded form. This is often omitted in conventional editions, but may be useful to include in a digital transcription, for example for inclusion in a diplomatic rendering.

                                                                                                                                                                                                                                                                                                    Any characters or symbols that appear in the abbreviated form on the support (abbr), but do not form part of the fully expended word (expan), should be included within the abbr element, and should additionally be enclosed in an am (abbreviation mark) element. In the default XSLT transformation, for example, this will result in the content of the am being omitted from the interpretive transcription, but included in the diplomatic edition. (The first example below, therefore, would appear as "Aug(usti duo)" in interpretive, as "AVGG" in diplomatic.)

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>Aug<am>g</am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex>usti duo</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Aug(usti duo)
                                                                                                                                                                                                                                                                                                    (EDH: HD000067)

                                                                                                                                                                                                                                                                                                    The following examples use type in g, as this has been in use in past project providing these examples. Please see Symbol (Non Meaning-Bearing) for the recommended use of <g[@ref]>.

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                       <g type="sestertius"/>
                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex>sestertios</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: (sestertios)
                                                                                                                                                                                                                                                                                                    (IRT: 788)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                       <g type="dot"/>
                                                                                                                                                                                                                                                                                                       <g type="reverse-slanting-stroke"/>
                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex cert="low">ὡς ἐτῶν</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: (ὡς ἐτῶν(?))
                                                                                                                                                                                                                                                                                                    (DDbDP: sb.14.11692#1)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                    4. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevnotex-pt-br.html b/gl/dev/trans-abbrevnotex-pt-br.html index 58f65441f..ead42540b 100644 --- a/gl/dev/trans-abbrevnotex-pt-br.html +++ b/gl/dev/trans-abbrevnotex-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abreviação não expandida

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: abbr ; EpiDoc-specific - customization: abbr

                                                                                                                                                                                                                                                                                                    abbr (abreviação) contém uma abreviação de qualquer tipo.

                                                                                                                                                                                                                                                                                                    Quando a expansão de uma abreviação é desconhecida, os caracteres presentes originalmente no suporte são marcados com o elemento abbr, sem expan, para indicar que existe uma abreviação mesmo que o editor não consiga expandi-la.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.2; Sosin 2011: ab(---)

                                                                                                                                                                                                                                                                                                    <abbr>ab</abbr>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <abbr>pl</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: pl(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>στρατηγ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: στρατηγ(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>S</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: S(- - -)
                                                                                                                                                                                                                                                                                                    (IRT: 11)
                                                                                                                                                                                                                                                                                                    <abbr>δειλ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: δειλ(  )
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.14#5)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Abreviação não expandida

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: abbr ; EpiDoc-specific + customization: abbr

                                                                                                                                                                                                                                                                                                    abbr (abreviação) contém uma abreviação de qualquer tipo.

                                                                                                                                                                                                                                                                                                    Quando a expansão de uma abreviação é desconhecida, os caracteres presentes originalmente no suporte são marcados com o elemento abbr, sem expan, para indicar que existe uma abreviação mesmo que o editor não consiga expandi-la.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.2; Sosin 2011: ab(---)

                                                                                                                                                                                                                                                                                                    <abbr>ab</abbr>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <abbr>pl</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: pl(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>στρατηγ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: στρατηγ(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>S</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: S(- - -)
                                                                                                                                                                                                                                                                                                    (IRT: 11)
                                                                                                                                                                                                                                                                                                    <abbr>δειλ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: δειλ(  )
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.14#5)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevnotex.html b/gl/dev/trans-abbrevnotex.html index 3723c9949..da8f280c3 100644 --- a/gl/dev/trans-abbrevnotex.html +++ b/gl/dev/trans-abbrevnotex.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abbreviation not expanded at all

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: abbr ; EpiDoc-specific - customization: abbr

                                                                                                                                                                                                                                                                                                    abbr (abbreviation) contains an abbreviation of any sort.

                                                                                                                                                                                                                                                                                                    Where the expansion of the abbreviation is unknown, the characters present on the original support are marked up with the abbr element, with no expan, to indicate that there is an abbreviation even though the editor cannot expand it.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.2; Sosin 2011: ab(---)

                                                                                                                                                                                                                                                                                                    <abbr>ab</abbr>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <abbr>pl</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: pl(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>στρατηγ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: στρατηγ(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>S</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: S(- - -)
                                                                                                                                                                                                                                                                                                    (IRT: 11)
                                                                                                                                                                                                                                                                                                    <abbr>δειλ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: δειλ(  )
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.14#5)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Abbreviation not expanded at all

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: abbr ; EpiDoc-specific + customization: abbr

                                                                                                                                                                                                                                                                                                    abbr (abbreviation) contains an abbreviation of any sort.

                                                                                                                                                                                                                                                                                                    Where the expansion of the abbreviation is unknown, the characters present on the original support are marked up with the abbr element, with no expan, to indicate that there is an abbreviation even though the editor cannot expand it.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.2; Sosin 2011: ab(---)

                                                                                                                                                                                                                                                                                                    <abbr>ab</abbr>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <abbr>pl</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: pl(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>στρατηγ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: στρατηγ(- - -)
                                                                                                                                                                                                                                                                                                    <abbr>S</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: S(- - -)
                                                                                                                                                                                                                                                                                                    (IRT: 11)
                                                                                                                                                                                                                                                                                                    <abbr>δειλ</abbr>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: δειλ(  )
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.14#5)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevpartial-pt-br.html b/gl/dev/trans-abbrevpartial-pt-br.html index 69c4bfec9..457838714 100644 --- a/gl/dev/trans-abbrevpartial-pt-br.html +++ b/gl/dev/trans-abbrevpartial-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abreviação parcialmente expandida

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    expan (expansão) contém a expansão de uma abreviação.

                                                                                                                                                                                                                                                                                                    ex (expansão editorial) contém uma sequência de letras adicionadas por um editor ou trascritor quando este expande uma abreviação.

                                                                                                                                                                                                                                                                                                    Os caracteres que formam toda a extensão de uma abreviação (incluindo tanto os caracters que estavam presentes no suporte original quanto aqueles adicionados pelo editor) recebem a marcação expan.

                                                                                                                                                                                                                                                                                                    Além disto, os caracteres adicionados pelo editor (ou seja, os caracteres que não aparecem no suporte original) são indicados pela marcação ex.

                                                                                                                                                                                                                                                                                                    Abreviações solucionadas e não solucionadas recebem tratamento diferenciado; veja Abreviação não expandida para ter a explicação de como se faz a marcação de abreviações cuja a expansão é desconhecida.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.1: a(bc-)

                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>Iul<ex cert="low">ius</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Iul(ius?)
                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>patr</abbr>
                                                                                                                                                                                                                                                                                                      <ex cert="low"/>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: patr(?-)-
                                                                                                                                                                                                                                                                                                    (IRT: 571)

                                                                                                                                                                                                                                                                                                    Sosin 2011: a(bc  )

                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: a(bc(?))
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>Καρ<ex cert="low">ανίδι</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Καρ(ανίδι(?))
                                                                                                                                                                                                                                                                                                    (Sosin)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevpartial.html b/gl/dev/trans-abbrevpartial.html index 819096f5c..d6ecbc313 100644 --- a/gl/dev/trans-abbrevpartial.html +++ b/gl/dev/trans-abbrevpartial.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abbreviation partially expanded

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    expan (expansion) contains the expansion of an abbreviation.

                                                                                                                                                                                                                                                                                                    ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation.

                                                                                                                                                                                                                                                                                                    The characters that form the entire expansion of an abbreviation (including both the charaters that are present on the original support and those added by the editor) are marked up using expan.

                                                                                                                                                                                                                                                                                                    In addition, the characters added by the editor (i.e. those characters that do not appear on the original support) are indicated with ex.

                                                                                                                                                                                                                                                                                                    Resolved and unresolved abbreviations are treated differently; see Abbreviation not expanded at all for an explanation of how to mark up abbreviations for which the expansion is unknown.

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.1: a(bc-)

                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>Iul<ex cert="low">ius</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Iul(ius?)
                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>patr</abbr>
                                                                                                                                                                                                                                                                                                      <ex cert="low"/>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: patr(?-)-
                                                                                                                                                                                                                                                                                                    (IRT: 571)

                                                                                                                                                                                                                                                                                                    Sosin 2011: a(bc  )

                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: a(bc(?))
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <w part="I">
                                                                                                                                                                                                                                                                                                     <expan>Καρ<ex cert="low">ανίδι</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Καρ(ανίδι(?))
                                                                                                                                                                                                                                                                                                    (Sosin)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevsymbo-pt-br.html b/gl/dev/trans-abbrevsymbo-pt-br.html index 5db867bfc..72e33d3ed 100644 --- a/gl/dev/trans-abbrevsymbo-pt-br.html +++ b/gl/dev/trans-abbrevsymbo-pt-br.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Expansão de símbolo para palavra

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Uma palavra que seja expandida, não de uma abreviação ou suspensão de letras do texto, mas de um símbolo ou glifo na pedra/página. O símbolo pode ou não estar registado na marcação.

                                                                                                                                                                                                                                                                                                    Quando toda uma palavra é solucionada pelo editor, não com base em uma abreviação, mas de uma marca simbólica ou um ideograma, como o símbolo de denarius, o glifo para um ano e meio, o solidus como sinônimo de patronímico ou liberto, o 'et' tirolês e outros símbolos; uma edição tradicional geralmente não representa o símbolo em si, mostrando apenas a palavra expandida entre parênteses. No caso mais simples, EpiDoc pode simplesmente replicar esta prática, usando expan e ex para codificar a palavra expandida sem nenhum registro de abbr.

                                                                                                                                                                                                                                                                                                    É preferível, no entanto, quando possível, codificar completamente os caracteres na pedra, bem como a interpretação destes pelo editor. Neste caso o elemento abbr será utilizado, com a adição de um am (marca de abreviação), para indicar que o símbolo, sendo parte de uma abreviação, não é parte da palavra solucionada.

                                                                                                                                                                                                                                                                                                    POxy: (ἀρτάβης)

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <ex>ἀρτάβης</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: (ἀρτάβης)
                                                                                                                                                                                                                                                                                                    • Duke Databank style: (ἀρτάβης)
                                                                                                                                                                                                                                                                                                    ()
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                       <g type="year">𐅹</g>
                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex>ἔτους</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: (ἔτους)
                                                                                                                                                                                                                                                                                                    • London style: (ἔτους)
                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevsymbol.html b/gl/dev/trans-abbrevsymbol.html index bf7b06460..9229abef8 100644 --- a/gl/dev/trans-abbrevsymbol.html +++ b/gl/dev/trans-abbrevsymbol.html @@ -21,9 +21,9 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Expansion of symbol

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    A word expanded, not from an abbreviation or suspension of letters in the text, but from a symbol or glyph on the stone/page. The symbol may or may not be recorded in the markup.

                                                                                                                                                                                                                                                                                                    When an entire word is resolved by the editor on the basis not of an abbreviation per se, but of a symbolic mark or ideogram, such as the denarius symbol, the glyph for year or half, the solidus for a synonymous patronymic or freedman, Tyrolean 'et', and such symbols, a traditional edition generally does not represent the symbol itself, only showing the expanded word in parentheses. In the simplest case, EpiDoc can simply replicate this practice, using expan and ex to encode the expanded word without any abbr recorded.

                                                                                                                                                                                                                                                                                                    It is preferable however, where possible, to encode fully the characters on the stone as well as the editor's interpretation of them. In this case the abbr element will be used, with the addition of an am (abbreviation mark), to indicate that the symbol, while part of the abbreviation, is not part of the resolved word.

                                                                                                                                                                                                                                                                                                    POxy: (ἀρτάβης)

                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <ex>ἀρτάβης</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: (ἀρτάβης)
                                                                                                                                                                                                                                                                                                    • Duke Databank style: (ἀρτάβης)
                                                                                                                                                                                                                                                                                                    ()
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                       <g type="year">𐅹</g>
                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                     <ex>ἔτους</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: (ἔτους)
                                                                                                                                                                                                                                                                                                    • London style: (ἔτους)
                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevuncert-pt-br.html b/gl/dev/trans-abbrevuncert-pt-br.html index d129e1cb6..4706638d1 100644 --- a/gl/dev/trans-abbrevuncert-pt-br.html +++ b/gl/dev/trans-abbrevuncert-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abreviação expandida de modo incerto

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: abbr ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                      Abreviação expandida de modo incerto

                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                      • TEI definition: abbr ; EpiDoc-specific customization: abbr
                                                                                                                                                                                                                                                                                                      • TEI definition: ex ; EpiDoc-specific customization: ex
                                                                                                                                                                                                                                                                                                      • TEI definition: expan ; EpiDoc-specific - customization: expan

                                                                                                                                                                                                                                                                                                      expan (expansão) contém a expansão de uma abreviação. Os caracteres que formam a expansão completa de uma abreviação (incluindo tanto os caracteres que estão presentes no suporte original quanto aqueles adicionados pelo editor) devem ficar contidos dentro do expan. Os caracteres que aparecem no suporte geralmente ficam contidos em abbr (apesar disto não ser obrigatório).

                                                                                                                                                                                                                                                                                                      ex (expansão editorial) contém uma sequência de letras adicionadas por um editor ou transcritor quando este expande uma abreviação. Os caracteres expandidos ou fornecidos pelo editor (isto é, aqueles caracteres que não aparecem no suporte original) são incluídos no ex. No caso de incerteza a respeito da expansão das abreviações, geralmente são estes caracteres expandidos a origem da incerteza, portanto o elemento ex leva consigo um cert com o valor "low".

                                                                                                                                                                                                                                                                                                      Quando o expan contém mais de uma cadeia de caracteres fornecidos ou expandidos, ou quando a abreviação em si contém caracteres que se perderam e foram restaurados, então a incerteza pode vir de algumas ou todas estas restaurações. Um editor pode indicar esta complexidade, anexando cert="low" a um ou mais destes elementos, ou pode simplesmente registrar esta incerteza a respeito de toda a palavra anexando cert ao expan (veja exemplo abaixo).

                                                                                                                                                                                                                                                                                                      Abreviações sem solução são tratadas de forma diferente; veja a seção Abreviação não expandida fpara ter uma explicação sobre como fazer a marcação de abreviações cujas expansões são completamente desconhecidas (ou quando o editor está inseguro demais para oferecer uma proposta de expansão).

                                                                                                                                                                                                                                                                                                      Panciera 1991 X.1: a(bc?)

                                                                                                                                                                                                                                                                                                      <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                      <expan>Iul<ex cert="low">ius</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: Iul(ius?)
                                                                                                                                                                                                                                                                                                      <seg part="I">
                                                                                                                                                                                                                                                                                                       <expan>
                                                                                                                                                                                                                                                                                                        <abbr>Aug</abbr>
                                                                                                                                                                                                                                                                                                        <ex cert="low">ust</ex>
                                                                                                                                                                                                                                                                                                       </expan>
                                                                                                                                                                                                                                                                                                      </seg>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • London style: Aug(ust?-)-
                                                                                                                                                                                                                                                                                                      (IRT: 732)

                                                                                                                                                                                                                                                                                                      Sosin 2011: a(bc(?))

                                                                                                                                                                                                                                                                                                      <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Duke Databank style: a(bc(?))
                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                      <expan>Καρ<ex cert="low">ανίδι</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Duke Databank style: Καρ(ανίδι(?))
                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                       <ex cert="low">ἔτους</ex>
                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                      <num value="29">
                                                                                                                                                                                                                                                                                                       <unclear>κ</unclear>θ
                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • London style: (ἔτους?) κ̣θ
                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.116#15)

                                                                                                                                                                                                                                                                                                      : [F]el(icitati)(?)

                                                                                                                                                                                                                                                                                                      <expan cert="low">
                                                                                                                                                                                                                                                                                                       <abbr>
                                                                                                                                                                                                                                                                                                        <supplied reason="lost">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                       <ex>icitati</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                      • Duke Databank style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                      • London style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                       <abbr>
                                                                                                                                                                                                                                                                                                        <supplied reason="lostcert="low">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                       <ex cert="low">icitati</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: [F?]el(icitati?)
                                                                                                                                                                                                                                                                                                      • Duke Databank style: [F(?)]el(icitati(?))
                                                                                                                                                                                                                                                                                                      • London style: [F?]el(icitati?)

                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                      1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                      \ No newline at end of file + customization: expan

                                                                                                                                                                                                                                                                                                    expan (expansão) contém a expansão de uma abreviação. Os caracteres que formam a expansão completa de uma abreviação (incluindo tanto os caracteres que estão presentes no suporte original quanto aqueles adicionados pelo editor) devem ficar contidos dentro do expan. Os caracteres que aparecem no suporte geralmente ficam contidos em abbr (apesar disto não ser obrigatório).

                                                                                                                                                                                                                                                                                                    ex (expansão editorial) contém uma sequência de letras adicionadas por um editor ou transcritor quando este expande uma abreviação. Os caracteres expandidos ou fornecidos pelo editor (isto é, aqueles caracteres que não aparecem no suporte original) são incluídos no ex. No caso de incerteza a respeito da expansão das abreviações, geralmente são estes caracteres expandidos a origem da incerteza, portanto o elemento ex leva consigo um cert com o valor "low".

                                                                                                                                                                                                                                                                                                    Quando o expan contém mais de uma cadeia de caracteres fornecidos ou expandidos, ou quando a abreviação em si contém caracteres que se perderam e foram restaurados, então a incerteza pode vir de algumas ou todas estas restaurações. Um editor pode indicar esta complexidade, anexando cert="low" a um ou mais destes elementos, ou pode simplesmente registrar esta incerteza a respeito de toda a palavra anexando cert ao expan (veja exemplo abaixo).

                                                                                                                                                                                                                                                                                                    Abreviações sem solução são tratadas de forma diferente; veja a seção Abreviação não expandida fpara ter uma explicação sobre como fazer a marcação de abreviações cujas expansões são completamente desconhecidas (ou quando o editor está inseguro demais para oferecer uma proposta de expansão).

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.1: a(bc?)

                                                                                                                                                                                                                                                                                                    <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <expan>Iul<ex cert="low">ius</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Iul(ius?)
                                                                                                                                                                                                                                                                                                    <seg part="I">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>Aug</abbr>
                                                                                                                                                                                                                                                                                                      <ex cert="low">ust</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </seg>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Aug(ust?-)-
                                                                                                                                                                                                                                                                                                    (IRT: 732)

                                                                                                                                                                                                                                                                                                    Sosin 2011: a(bc(?))

                                                                                                                                                                                                                                                                                                    <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: a(bc(?))
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <expan>Καρ<ex cert="low">ανίδι</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Καρ(ανίδι(?))
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <ex cert="low">ἔτους</ex>
                                                                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                                                                    <num value="29">
                                                                                                                                                                                                                                                                                                     <unclear>κ</unclear>θ
                                                                                                                                                                                                                                                                                                    </num>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: (ἔτους?) κ̣θ
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.116#15)

                                                                                                                                                                                                                                                                                                    : [F]el(icitati)(?)

                                                                                                                                                                                                                                                                                                    <expan cert="low">
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <supplied reason="lost">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                     <ex>icitati</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                    • Duke Databank style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                    • London style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <supplied reason="lostcert="low">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                     <ex cert="low">icitati</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: [F?]el(icitati?)
                                                                                                                                                                                                                                                                                                    • Duke Databank style: [F(?)]el(icitati(?))
                                                                                                                                                                                                                                                                                                    • London style: [F?]el(icitati?)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-abbrevuncert.html b/gl/dev/trans-abbrevuncert.html index 653dac9b8..9b3a91145 100644 --- a/gl/dev/trans-abbrevuncert.html +++ b/gl/dev/trans-abbrevuncert.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Abbreviation uncertainly expanded

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: abbr ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                      Abbreviation uncertainly expanded

                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                      • TEI definition: abbr ; EpiDoc-specific customization: abbr
                                                                                                                                                                                                                                                                                                      • TEI definition: ex ; EpiDoc-specific customization: ex
                                                                                                                                                                                                                                                                                                      • TEI definition: expan ; EpiDoc-specific - customization: expan

                                                                                                                                                                                                                                                                                                      expan (expansion) contains the expansion of an abbreviation. The characters that form the entire expansion of an abbreviation (including both the charaters that are present on the original support and those added by the editor) should be encompassed within the expan. The characters that appear on the support are usually contained in abbr (although this is not obligatory).

                                                                                                                                                                                                                                                                                                      ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. The characters expanded or supplied by the editor (i.e. those characters that do not appear on the original support) are included in the ex. In the case of uncertainly expanded abbreviations, it is generally these expanded characters that are the source of the uncertainty, so the ex element carries a cert with a value of "low".

                                                                                                                                                                                                                                                                                                      Where the expan contains more than one string of supplied or expanded characters, or the abbreviation itself contains characters that are lost but restored, then the uncertainty of the expansion may stem from some or all of these restorations. An editor may indicate this complexity by attaching cert="low" on one or more of these elements, or may simply record the uncertainty of the entire word by attaching cert to the expan (see example below).

                                                                                                                                                                                                                                                                                                      Completely unresolved abbreviations are treated differently; see section Abbreviation not expanded at all for an explanation of how to mark up abbreviations for which the expansion is completely unknown (or where the editor is too uncertain even to offer an expansion).

                                                                                                                                                                                                                                                                                                      Panciera 1991 X.1: a(bc?)

                                                                                                                                                                                                                                                                                                      <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                      <expan>Iul<ex cert="low">ius</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: Iul(ius?)
                                                                                                                                                                                                                                                                                                      <seg part="I">
                                                                                                                                                                                                                                                                                                       <expan>
                                                                                                                                                                                                                                                                                                        <abbr>Aug</abbr>
                                                                                                                                                                                                                                                                                                        <ex cert="low">ust</ex>
                                                                                                                                                                                                                                                                                                       </expan>
                                                                                                                                                                                                                                                                                                      </seg>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • London style: Aug(ust?-)-
                                                                                                                                                                                                                                                                                                      (IRT: 732)

                                                                                                                                                                                                                                                                                                      Sosin 2011: a(bc(?))

                                                                                                                                                                                                                                                                                                      <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Duke Databank style: a(bc(?))
                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                      <expan>Καρ<ex cert="low">ανίδι</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Duke Databank style: Καρ(ανίδι(?))
                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                       <ex cert="low">ἔτους</ex>
                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                      <num value="29">
                                                                                                                                                                                                                                                                                                       <unclear>κ</unclear>θ
                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • London style: (ἔτους?) κ̣θ
                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.116#15)

                                                                                                                                                                                                                                                                                                      : [F]el(icitati)(?)

                                                                                                                                                                                                                                                                                                      <expan cert="low">
                                                                                                                                                                                                                                                                                                       <abbr>
                                                                                                                                                                                                                                                                                                        <supplied reason="lost">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                       <ex>icitati</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                      • Duke Databank style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                      • London style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                       <abbr>
                                                                                                                                                                                                                                                                                                        <supplied reason="lostcert="low">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                       <ex cert="low">icitati</ex>
                                                                                                                                                                                                                                                                                                      </expan>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: [F?]el(icitati?)
                                                                                                                                                                                                                                                                                                      • Duke Databank style: [F(?)]el(icitati(?))
                                                                                                                                                                                                                                                                                                      • London style: [F?]el(icitati?)

                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                      1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                      \ No newline at end of file + customization: expan

                                                                                                                                                                                                                                                                                                    expan (expansion) contains the expansion of an abbreviation. The characters that form the entire expansion of an abbreviation (including both the charaters that are present on the original support and those added by the editor) should be encompassed within the expan. The characters that appear on the support are usually contained in abbr (although this is not obligatory).

                                                                                                                                                                                                                                                                                                    ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. The characters expanded or supplied by the editor (i.e. those characters that do not appear on the original support) are included in the ex. In the case of uncertainly expanded abbreviations, it is generally these expanded characters that are the source of the uncertainty, so the ex element carries a cert with a value of "low".

                                                                                                                                                                                                                                                                                                    Where the expan contains more than one string of supplied or expanded characters, or the abbreviation itself contains characters that are lost but restored, then the uncertainty of the expansion may stem from some or all of these restorations. An editor may indicate this complexity by attaching cert="low" on one or more of these elements, or may simply record the uncertainty of the entire word by attaching cert to the expan (see example below).

                                                                                                                                                                                                                                                                                                    Completely unresolved abbreviations are treated differently; see section Abbreviation not expanded at all for an explanation of how to mark up abbreviations for which the expansion is completely unknown (or where the editor is too uncertain even to offer an expansion).

                                                                                                                                                                                                                                                                                                    Panciera 1991 X.1: a(bc?)

                                                                                                                                                                                                                                                                                                    <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <expan>Iul<ex cert="low">ius</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Iul(ius?)
                                                                                                                                                                                                                                                                                                    <seg part="I">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>Aug</abbr>
                                                                                                                                                                                                                                                                                                      <ex cert="low">ust</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </seg>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Aug(ust?-)-
                                                                                                                                                                                                                                                                                                    (IRT: 732)

                                                                                                                                                                                                                                                                                                    Sosin 2011: a(bc(?))

                                                                                                                                                                                                                                                                                                    <expan>a<ex cert="low">bc</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: a(bc(?))
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <expan>Καρ<ex cert="low">ανίδι</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Καρ(ανίδι(?))
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <ex cert="low">ἔτους</ex>
                                                                                                                                                                                                                                                                                                    </expan>
                                                                                                                                                                                                                                                                                                    <num value="29">
                                                                                                                                                                                                                                                                                                     <unclear>κ</unclear>θ
                                                                                                                                                                                                                                                                                                    </num>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: (ἔτους?) κ̣θ
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.116#15)

                                                                                                                                                                                                                                                                                                    : [F]el(icitati)(?)

                                                                                                                                                                                                                                                                                                    <expan cert="low">
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <supplied reason="lost">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                     <ex>icitati</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                    • Duke Databank style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                    • London style: [F]el(icitati)(?)
                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                      <supplied reason="lostcert="low">F</supplied>el</abbr>
                                                                                                                                                                                                                                                                                                     <ex cert="low">icitati</ex>
                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: [F?]el(icitati?)
                                                                                                                                                                                                                                                                                                    • Duke Databank style: [F(?)]el(icitati(?))
                                                                                                                                                                                                                                                                                                    • London style: [F?]el(icitati?)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-addition-pt-br.html b/gl/dev/trans-addition-pt-br.html index d1394ccea..19b03e51b 100644 --- a/gl/dev/trans-addition-pt-br.html +++ b/gl/dev/trans-addition-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Texto adicionado por mão na antiguidade

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                    Text adicionado por mão na antiguidade (acima, abaixo, à esquerda, etc.)

                                                                                                                                                                                                                                                                                                    Em Leiden tradicional o lugar do texto adicionado não é especificado na transcrição, mas anotado no comentário ou apparatus. Esta informação adicional, gravada aqui pelo uso de um atributo de lugar, é, portanto, adicional e pode ser omitida sem dano. Se for incluída na transcrição, deve-se utilizar add, com um place cujo valor deve refletir a posição do texto adicional ("above", "below", "left" etc.).

                                                                                                                                                                                                                                                                                                    Panciera 1991 VII.1: `abc´

                                                                                                                                                                                                                                                                                                    Sosin 2011: \abc/ (above), /abc\ (below)

                                                                                                                                                                                                                                                                                                    <add place="above">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: \αβ/
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add place="below">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: /αβ\
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <add place="above">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>Imp</abbr>
                                                                                                                                                                                                                                                                                                      <ex>erator</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: `Imp(erator)´
                                                                                                                                                                                                                                                                                                    (IRT: 29)
                                                                                                                                                                                                                                                                                                    καὶ <add place="above">ὅτι</add>
                                                                                                                                                                                                                                                                                                    ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: καὶ \ὅτι/ ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Responsabilidade po esta seção

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Texto adicionado por mão na antiguidade

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific + customization: add

                                                                                                                                                                                                                                                                                                    Text adicionado por mão na antiguidade (acima, abaixo, à esquerda, etc.)

                                                                                                                                                                                                                                                                                                    Em Leiden tradicional o lugar do texto adicionado não é especificado na transcrição, mas anotado no comentário ou apparatus. Esta informação adicional, gravada aqui pelo uso de um atributo de lugar, é, portanto, adicional e pode ser omitida sem dano. Se for incluída na transcrição, deve-se utilizar add, com um place cujo valor deve refletir a posição do texto adicional ("above", "below", "left" etc.).

                                                                                                                                                                                                                                                                                                    Panciera 1991 VII.1: `abc´

                                                                                                                                                                                                                                                                                                    Sosin 2011: \abc/ (above), /abc\ (below)

                                                                                                                                                                                                                                                                                                    <add place="above">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: \αβ/
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add place="below">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: /αβ\
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <add place="above">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>Imp</abbr>
                                                                                                                                                                                                                                                                                                      <ex>erator</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: `Imp(erator)´
                                                                                                                                                                                                                                                                                                    (IRT: 29)
                                                                                                                                                                                                                                                                                                    καὶ <add place="above">ὅτι</add>
                                                                                                                                                                                                                                                                                                    ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: καὶ \ὅτι/ ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Responsabilidade po esta seção

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-addition.html b/gl/dev/trans-addition.html index 8a5272af2..fdae5ad06 100644 --- a/gl/dev/trans-addition.html +++ b/gl/dev/trans-addition.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Text Addition by Ancient Hand

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                    Text added by ancient hand (above, below, left etc.)

                                                                                                                                                                                                                                                                                                    In traditional Leiden the place of added text is not specified in the transcription, but noted in the apparatus or commentary. This added information, recorded here by use of the place attribute, is therefore optional and may be omitted without harm. If it is to be included in the transcription, add should be used, with a place whose value should reflect the position of the added text ("above", "below", "left" etc.).

                                                                                                                                                                                                                                                                                                    Panciera 1991 VII.1: `abc´

                                                                                                                                                                                                                                                                                                    Sosin 2011: \abc/ (above), /abc\ (below)

                                                                                                                                                                                                                                                                                                    <add place="above">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: \αβ/
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add place="below">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: /αβ\
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <add place="above">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>Imp</abbr>
                                                                                                                                                                                                                                                                                                      <ex>erator</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: `Imp(erator)´
                                                                                                                                                                                                                                                                                                    (IRT: 29)

                                                                                                                                                                                                                                                                                                    καὶ <add place="above">ὅτι</add> ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: καὶ \ὅτι/ ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Text Addition by Ancient Hand

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific + customization: add

                                                                                                                                                                                                                                                                                                    Text added by ancient hand (above, below, left etc.)

                                                                                                                                                                                                                                                                                                    In traditional Leiden the place of added text is not specified in the transcription, but noted in the apparatus or commentary. This added information, recorded here by use of the place attribute, is therefore optional and may be omitted without harm. If it is to be included in the transcription, add should be used, with a place whose value should reflect the position of the added text ("above", "below", "left" etc.).

                                                                                                                                                                                                                                                                                                    Panciera 1991 VII.1: `abc´

                                                                                                                                                                                                                                                                                                    Sosin 2011: \abc/ (above), /abc\ (below)

                                                                                                                                                                                                                                                                                                    <add place="above">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: \αβ/
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add place="below">αβ</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: `αβ´
                                                                                                                                                                                                                                                                                                    • Duke Databank style: /αβ\
                                                                                                                                                                                                                                                                                                    • London style: `αβ´
                                                                                                                                                                                                                                                                                                    • Petrae style: \αβ/
                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                    <add place="above">
                                                                                                                                                                                                                                                                                                     <expan>
                                                                                                                                                                                                                                                                                                      <abbr>Imp</abbr>
                                                                                                                                                                                                                                                                                                      <ex>erator</ex>
                                                                                                                                                                                                                                                                                                     </expan>
                                                                                                                                                                                                                                                                                                    </add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: `Imp(erator)´
                                                                                                                                                                                                                                                                                                    (IRT: 29)

                                                                                                                                                                                                                                                                                                    καὶ <add place="above">ὅτι</add> ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: καὶ \ὅτι/ ὑγιαίνετε

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-additionwithmark-pt-br.html b/gl/dev/trans-additionwithmark-pt-br.html index c87c27a7f..c52b7227d 100644 --- a/gl/dev/trans-additionwithmark-pt-br.html +++ b/gl/dev/trans-additionwithmark-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Aditção com Marca

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                    Use rend com valores como "sling", "underline", etc.

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add rend="sling"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underline"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underlineplace="margin">οὕτως ἔχει</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: οὕτως ἔχει
                                                                                                                                                                                                                                                                                                    (DDbDP: p.prag.2.137)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Aditção com Marca

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific + customization: add

                                                                                                                                                                                                                                                                                                    Use rend com valores como "sling", "underline", etc.

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add rend="sling"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underline"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underlineplace="margin">οὕτως ἔχει</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: οὕτως ἔχει
                                                                                                                                                                                                                                                                                                    (DDbDP: p.prag.2.137)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-additionwithmark.html b/gl/dev/trans-additionwithmark.html index b8e03e082..bc424e43e 100644 --- a/gl/dev/trans-additionwithmark.html +++ b/gl/dev/trans-additionwithmark.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Addition With Mark

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                    Use rend with values such as "sling" or "underline" etc.

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add rend="sling"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underline"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underlineplace="margin">οὕτως ἔχει</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: οὕτως ἔχει
                                                                                                                                                                                                                                                                                                    (DDbDP: p.prag.2.137)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Addition With Mark

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific + customization: add

                                                                                                                                                                                                                                                                                                    Use rend with values such as "sling" or "underline" etc.

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add rend="sling"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underline"/>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <add rend="underlineplace="margin">οὕτως ἔχει</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: οὕτως ἔχει
                                                                                                                                                                                                                                                                                                    (DDbDP: p.prag.2.137)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-alt-inline.html b/gl/dev/trans-alt-inline.html index d59b33ae9..aaadf48a5 100644 --- a/gl/dev/trans-alt-inline.html +++ b/gl/dev/trans-alt-inline.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Alternative readings: inline encoding and display

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Where there are two or more possible readings or interpretations of a string of text, an editor may choose to present all options to the reader for full transparency. In EpiDoc, these readings are encoded using the app with type attribute with value "alternative", containing lem (the preferred reading; optional) and one or more rdgs (all other readings). On a project level, editor·s might decide to display this variety of readings in a separate apparatus criticus or in the body of the text.

                                                                                                                                                                                                                                                                                                    <app type="alternative">
                                                                                                                                                                                                                                                                                                     <lem>
                                                                                                                                                                                                                                                                                                      <num value="13">ιγ</num>
                                                                                                                                                                                                                                                                                                     </lem>
                                                                                                                                                                                                                                                                                                     <rdg>
                                                                                                                                                                                                                                                                                                      <num value="13">ι<surplus>γ</surplus>
                                                                                                                                                                                                                                                                                                      </num>
                                                                                                                                                                                                                                                                                                     </rdg>
                                                                                                                                                                                                                                                                                                    </app>
                                                                                                                                                                                                                                                                                                    Note: displayed in the edition as: ιγ´ resp. ι{γ}´.

                                                                                                                                                                                                                                                                                                    A second example, with two expansions of abbreviation:

                                                                                                                                                                                                                                                                                                    <app type="alternative">
                                                                                                                                                                                                                                                                                                     <lem>
                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                       <abbr>χ</abbr>
                                                                                                                                                                                                                                                                                                       <ex>α</ex>
                                                                                                                                                                                                                                                                                                       <abbr>ρτελ</abbr>
                                                                                                                                                                                                                                                                                                       <ex>αρίῳ</ex>
                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                     </lem>
                                                                                                                                                                                                                                                                                                     <rdg>
                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                       <ex>χρυσο</ex>
                                                                                                                                                                                                                                                                                                       <abbr>τελ</abbr>
                                                                                                                                                                                                                                                                                                       <ex></ex>
                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                     </rdg>
                                                                                                                                                                                                                                                                                                    </app>
                                                                                                                                                                                                                                                                                                    Note: displayed in the edition as: χ(α)ρτελ(αρίῳ) vel (χρυσο)τελ(ῇ).

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                    2. Alessio Sopracasa, author
                                                                                                                                                                                                                                                                                                    3. Martina Filosa, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ambiguous-pt-br.html b/gl/dev/trans-ambiguous-pt-br.html index 61359beea..51cc59caa 100644 --- a/gl/dev/trans-ambiguous-pt-br.html +++ b/gl/dev/trans-ambiguous-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Caracteres ambíguos (ponto subescrito do Leiden)

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Um caractere que tem traços preservados, mas não o suficiente para que se identifique a letra sem ambiguidade fora de seu contexto.

                                                                                                                                                                                                                                                                                                    Um caractere incompleto ou mal executado, cuja interpretação seja ambígua fora de seu contexto (tradicionalmente representada com um ponto subescrito no Leiden) deve receber a tag do elemento unclear (Veja Caracteres danificados (mas legíveis)). O uso do unclear pelo EpiDoc é voltado apenas para a preservação ou execução física do caractere.

                                                                                                                                                                                                                                                                                                    O elemento unclear pode receber o atributo reason, mas isto não é necessário para o EpiDoc, já que o uso do elemento unclear é suficiente para atender as distinções feitas pelas convenções Leiden.

                                                                                                                                                                                                                                                                                                    É importante observar que o uso do elemento unclear pelo EpiDoc é significativamente mais restrito que a definição default do TEI, que permite que uma ampla variedade de elementos apareçam dentro de unclear. Em EpiDoc, a categoria "unclear" se refere ao estado físico de um caractere específico no suporte, e não a uma ambiguidade editorial ou uma incerteza sobre a interpretação de palavras ou nomes (que é indicado com o uso de <cert>). Pelo fato de unclear se referir apenas ao estado de caracteres no suporte, e não a qualquer interpretação destes caracteres (como a possibilidade de diversos caracteres representarem um número, nome, vel sim.), apenas dados de caractere ou uma tag g pode aparecer dentro do elemento unclear. Da mesma forma, nenhum elemento relacionado com a interpretação do texto deve ficar dentro de unclear; partes de texto ambíguo que incluem palavras, linhas, nomes, datas e outras características com tags devem, portanto, ser marcadas com múltiplos elementos unclear.

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 III.3; Panciera 1991 12.I; Sosin 2011: ạḅc̣

                                                                                                                                                                                                                                                                                                    <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <unclear>T</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">rai</supplied>ani

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ṭ[rai]ani
                                                                                                                                                                                                                                                                                                    (IRT: 27)
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">Δ</supplied>
                                                                                                                                                                                                                                                                                                    <unclear reason="damage">η</unclear>μοφάντου

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: [Δ]η̣μοφάντου
                                                                                                                                                                                                                                                                                                    (InsAph: 11.223)
                                                                                                                                                                                                                                                                                                    συμβόλου μ<unclear>ία</unclear>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: συμβόλου μί̣α̣
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.102)
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>Ἀνέθη</unclear>σα<unclear>ν</unclear>
                                                                                                                                                                                                                                                                                                    </w>
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>οἱ</unclear>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ἀ̣ν̣έ̣θ̣η̣σαν̣ ο̣ἱ̣
                                                                                                                                                                                                                                                                                                    Clau<unclear>dio</unclear>
                                                                                                                                                                                                                                                                                                    <unclear>Tib</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">eriano</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Clauḍịọ Ṭịḅ[eriano]
                                                                                                                                                                                                                                                                                                    (DDbDP: c.ep.lat..142)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Scott DiGiulio, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Caracteres ambíguos (ponto subescrito do Leiden)

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Um caractere que tem traços preservados, mas não o suficiente para que se identifique a letra sem ambiguidade fora de seu contexto.

                                                                                                                                                                                                                                                                                                    Um caractere incompleto ou mal executado, cuja interpretação seja ambígua fora de seu contexto (tradicionalmente representada com um ponto subescrito no Leiden) deve receber a tag do elemento unclear (Veja Caracteres danificados (mas legíveis)). O uso do unclear pelo EpiDoc é voltado apenas para a preservação ou execução física do caractere.

                                                                                                                                                                                                                                                                                                    O elemento unclear pode receber o atributo reason, mas isto não é necessário para o EpiDoc, já que o uso do elemento unclear é suficiente para atender as distinções feitas pelas convenções Leiden.

                                                                                                                                                                                                                                                                                                    É importante observar que o uso do elemento unclear pelo EpiDoc é significativamente mais restrito que a definição default do TEI, que permite que uma ampla variedade de elementos apareçam dentro de unclear. Em EpiDoc, a categoria "unclear" se refere ao estado físico de um caractere específico no suporte, e não a uma ambiguidade editorial ou uma incerteza sobre a interpretação de palavras ou nomes (que é indicado com o uso de <cert>). Pelo fato de unclear se referir apenas ao estado de caracteres no suporte, e não a qualquer interpretação destes caracteres (como a possibilidade de diversos caracteres representarem um número, nome, vel sim.), apenas dados de caractere ou uma tag g pode aparecer dentro do elemento unclear. Da mesma forma, nenhum elemento relacionado com a interpretação do texto deve ficar dentro de unclear; partes de texto ambíguo que incluem palavras, linhas, nomes, datas e outras características com tags devem, portanto, ser marcadas com múltiplos elementos unclear.

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 III.3; Panciera 1991 12.I; Sosin 2011: ạḅc̣

                                                                                                                                                                                                                                                                                                    <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <unclear>T</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">rai</supplied>ani

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ṭ[rai]ani
                                                                                                                                                                                                                                                                                                    (IRT: 27)
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">Δ</supplied>
                                                                                                                                                                                                                                                                                                    <unclear reason="damage">η</unclear>μοφάντου

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: [Δ]η̣μοφάντου
                                                                                                                                                                                                                                                                                                    (InsAph: 11.223)
                                                                                                                                                                                                                                                                                                    συμβόλου μ<unclear>ία</unclear>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: συμβόλου μί̣α̣
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.102)
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>Ἀνέθη</unclear>σα<unclear>ν</unclear>
                                                                                                                                                                                                                                                                                                    </w>
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>οἱ</unclear>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ἀ̣ν̣έ̣θ̣η̣σαν̣ ο̣ἱ̣
                                                                                                                                                                                                                                                                                                    Clau<unclear>dio</unclear>
                                                                                                                                                                                                                                                                                                    <unclear>Tib</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">eriano</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Clauḍịọ Ṭịḅ[eriano]
                                                                                                                                                                                                                                                                                                    (DDbDP: c.ep.lat..142)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Scott DiGiulio, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ambiguous.html b/gl/dev/trans-ambiguous.html index b949a06b9..8ef9e2a8f 100644 --- a/gl/dev/trans-ambiguous.html +++ b/gl/dev/trans-ambiguous.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Ambiguous Characters (Leiden underdotted)

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Character of which at least traces survive, but not adequately to identify the letter unambiguously outside of its context.

                                                                                                                                                                                                                                                                                                    An incomplete or ill-executed character whose interpretation would be ambiguous outside of its context (traditionally rendered with an underdot in Leiden) should be tagged using the unclear element (Cf. Damaged but not ambiguous characters). The EpiDoc use of unclear is concerned specifically with the physical preservation or execution of the characters.

                                                                                                                                                                                                                                                                                                    The unclear element may be given the attribute reason, but this is not required by EpiDoc, as the use of the unclear element is sufficient to meet the distinctions that the Leiden conventions make.

                                                                                                                                                                                                                                                                                                    It is important to note that the EpiDoc use of the unclear element is very significantly more restricted than the default TEI definition, which allows for a large variety of elements to appear within unclear. In EpiDoc, the category "unclear" refers to the physical state of specific characters on the support, and not to editorial ambiguity or uncertainty about the interpretation of words or names (which is indicated using <cert>). Because unclear is only concerned with the state of the characters on the support, and not with any interpretation of those characters (such as whether several characters represent a number, name, vel sim.), only character data or a g tag may appear inside the unclear element. Accordingly, no elements related to the interpretation of the text should nest within unclear; stretches of ambiguous text that span words, lines, names, dates, or other tagged features should therefore be marked with multiple unclear elements.

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 III.3; Panciera 1991 12.I; Sosin 2011: ạḅc̣

                                                                                                                                                                                                                                                                                                    <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <unclear>T</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">rai</supplied>ani

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ṭ[rai]ani
                                                                                                                                                                                                                                                                                                    (IRT: 27)
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">Δ</supplied>
                                                                                                                                                                                                                                                                                                    <unclear reason="damage">η</unclear>μοφάντου

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: [Δ]η̣μοφάντου
                                                                                                                                                                                                                                                                                                    (InsAph: 11.223)
                                                                                                                                                                                                                                                                                                    συμβόλου μ<unclear>ία</unclear>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: συμβόλου μί̣α̣
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.102)
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>Ἀνέθη</unclear>σα<unclear>ν</unclear>
                                                                                                                                                                                                                                                                                                    </w>
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>οἱ</unclear>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ἀ̣ν̣έ̣θ̣η̣σαν̣ ο̣ἱ̣
                                                                                                                                                                                                                                                                                                    Clau<unclear>dio</unclear>
                                                                                                                                                                                                                                                                                                    <unclear>Tib</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">eriano</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Clauḍịọ Ṭịḅ[eriano]
                                                                                                                                                                                                                                                                                                    (DDbDP: c.ep.lat..142)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Scott DiGiulio, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Ambiguous Characters (Leiden underdotted)

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Character of which at least traces survive, but not adequately to identify the letter unambiguously outside of its context.

                                                                                                                                                                                                                                                                                                    An incomplete or ill-executed character whose interpretation would be ambiguous outside of its context (traditionally rendered with an underdot in Leiden) should be tagged using the unclear element (Cf. Damaged but not ambiguous characters). The EpiDoc use of unclear is concerned specifically with the physical preservation or execution of the characters.

                                                                                                                                                                                                                                                                                                    The unclear element may be given the attribute reason, but this is not required by EpiDoc, as the use of the unclear element is sufficient to meet the distinctions that the Leiden conventions make.

                                                                                                                                                                                                                                                                                                    It is important to note that the EpiDoc use of the unclear element is very significantly more restricted than the default TEI definition, which allows for a large variety of elements to appear within unclear. In EpiDoc, the category "unclear" refers to the physical state of specific characters on the support, and not to editorial ambiguity or uncertainty about the interpretation of words or names (which is indicated using <cert>). Because unclear is only concerned with the state of the characters on the support, and not with any interpretation of those characters (such as whether several characters represent a number, name, vel sim.), only character data or a g tag may appear inside the unclear element. Accordingly, no elements related to the interpretation of the text should nest within unclear; stretches of ambiguous text that span words, lines, names, dates, or other tagged features should therefore be marked with multiple unclear elements.

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 III.3; Panciera 1991 12.I; Sosin 2011: ạḅc̣

                                                                                                                                                                                                                                                                                                    <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <unclear>T</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">rai</supplied>ani

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ṭ[rai]ani
                                                                                                                                                                                                                                                                                                    (IRT: 27)
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">Δ</supplied>
                                                                                                                                                                                                                                                                                                    <unclear reason="damage">η</unclear>μοφάντου

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: [Δ]η̣μοφάντου
                                                                                                                                                                                                                                                                                                    (InsAph: 11.223)
                                                                                                                                                                                                                                                                                                    συμβόλου μ<unclear>ία</unclear>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: συμβόλου μί̣α̣
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.102)
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>Ἀνέθη</unclear>σα<unclear>ν</unclear>
                                                                                                                                                                                                                                                                                                    </w>
                                                                                                                                                                                                                                                                                                    <w>
                                                                                                                                                                                                                                                                                                     <unclear>οἱ</unclear>
                                                                                                                                                                                                                                                                                                    </w>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Ἀ̣ν̣έ̣θ̣η̣σαν̣ ο̣ἱ̣
                                                                                                                                                                                                                                                                                                    Clau<unclear>dio</unclear>
                                                                                                                                                                                                                                                                                                    <unclear>Tib</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">eriano</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: Clauḍịọ Ṭịḅ[eriano]
                                                                                                                                                                                                                                                                                                    (DDbDP: c.ep.lat..142)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Scott DiGiulio, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ambiguousalt-pt-br.html b/gl/dev/trans-ambiguousalt-pt-br.html index 13039f56a..ecc2ac9cf 100644 --- a/gl/dev/trans-ambiguousalt-pt-br.html +++ b/gl/dev/trans-ambiguousalt-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Caracteres ambíguos com apresentação de alternativas

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Algumas vezes um editor vai registrar traços de um caractere ambíguo ou danificado, mas em vez de simplesmente aplicar pontos subescritos na interpretação escolhida, serão listadas diversas possibilidades (geralmente em modo apparatus ou note). Este conceito é codificado no EpiDoc com o uso do elemento choice, para agrupar diversos unclears.

                                                                                                                                                                                                                                                                                                    No exemplo a renderização em convenções epigráficas padrão.

                                                                                                                                                                                                                                                                                                    Joyce M. Reynolds http://insaph.kcl.ac.uk/iaph2007/iAph090043.html: What survives of the last letter before the break is consonant with Γ, Ε, Ζ, Ξ, Π, Σ, Τ

                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                     <unclear>Γ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Ε</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Ζ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Ξ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Π</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Σ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Τ</unclear>
                                                                                                                                                                                                                                                                                                    </choice>
                                                                                                                                                                                                                                                                                                    (InsAph: 9.43)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. , autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ambiguousalt.html b/gl/dev/trans-ambiguousalt.html index 4f3bb1d31..2f4efbf7b 100644 --- a/gl/dev/trans-ambiguousalt.html +++ b/gl/dev/trans-ambiguousalt.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Ambiguous Characters with Alternatives Offered

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Sometimes an editor will record traces of a surviving ambiguous or damaged character, but rather than simply underdotting the chosen interpretation, she will list several possibilities (usually in an apparatus or note). This concept is encoded in EpiDoc using the choice element to group several unclears.

                                                                                                                                                                                                                                                                                                    No example rendering in standard epigraphic conventions.

                                                                                                                                                                                                                                                                                                    Joyce M. Reynolds http://insaph.kcl.ac.uk/iaph2007/iAph090043.html: What survives of the last letter before the break is consonant with Γ, Ε, Ζ, Ξ, Π, Σ, Τ

                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                     <unclear>Γ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Ε</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Ζ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Ξ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Π</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Σ</unclear>
                                                                                                                                                                                                                                                                                                     <unclear>Τ</unclear>
                                                                                                                                                                                                                                                                                                    </choice>
                                                                                                                                                                                                                                                                                                    (InsAph: 9.43)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. , author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ancientcorrection-pt-br.html b/gl/dev/trans-ancientcorrection-pt-br.html index 824ffea3f..e1f7c2b3f 100644 --- a/gl/dev/trans-ancientcorrection-pt-br.html +++ b/gl/dev/trans-ancientcorrection-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Correções Antigas (onde tanto o texto novo quanto o antigo são legíveis)

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Panciera 1991 VI.1; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <subst>
                                                                                                                                                                                                                                                                                                     <del rend="corrected">αβ</del>
                                                                                                                                                                                                                                                                                                     <add place="overstrike">γδ</add>
                                                                                                                                                                                                                                                                                                    </subst>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <subst>
                                                                                                                                                                                                                                                                                                     <add place="inline">τέσσαρας</add>
                                                                                                                                                                                                                                                                                                     <del rend="corrected">τεσσαρες</del>
                                                                                                                                                                                                                                                                                                    </subst>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: τέσσαρας
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.183)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ancientcorrection.html b/gl/dev/trans-ancientcorrection.html index eeb3df2fe..0e41f6cf4 100644 --- a/gl/dev/trans-ancientcorrection.html +++ b/gl/dev/trans-ancientcorrection.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Ancient Corrections (Where Both Old and New Text Can Be Read)

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Panciera 1991 VI.1; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <subst>
                                                                                                                                                                                                                                                                                                     <del rend="corrected">αβ</del>
                                                                                                                                                                                                                                                                                                     <add place="overstrike">γδ</add>
                                                                                                                                                                                                                                                                                                    </subst>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    <subst>
                                                                                                                                                                                                                                                                                                     <add place="inline">τέσσαρας</add>
                                                                                                                                                                                                                                                                                                     <del rend="corrected">τεσσαρες</del>
                                                                                                                                                                                                                                                                                                    </subst>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Duke Databank style: τέσσαρας
                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.183)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ancientcorrectionlost-pt-br.html b/gl/dev/trans-ancientcorrectionlost-pt-br.html index dc08c8c7f..46f005b54 100644 --- a/gl/dev/trans-ancientcorrectionlost-pt-br.html +++ b/gl/dev/trans-ancientcorrectionlost-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Correção antiga (original ilegível ou perdido)

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                    substituição, original ilegível ou perdido

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    public<add place="overstrike">a</add>e

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: public«a»e
                                                                                                                                                                                                                                                                                                    (IRT: 50)
                                                                                                                                                                                                                                                                                                    τὸ<add place="overstrike">ν</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: τὸ«ν»
                                                                                                                                                                                                                                                                                                    (InsAph: 15.328)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Correção antiga (original ilegível ou perdido)

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific + customization: add

                                                                                                                                                                                                                                                                                                    substituição, original ilegível ou perdido

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    public<add place="overstrike">a</add>e

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: public«a»e
                                                                                                                                                                                                                                                                                                    (IRT: 50)
                                                                                                                                                                                                                                                                                                    τὸ<add place="overstrike">ν</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: τὸ«ν»
                                                                                                                                                                                                                                                                                                    (InsAph: 15.328)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-ancientcorrectionlost.html b/gl/dev/trans-ancientcorrectionlost.html index 65452479c..48877e924 100644 --- a/gl/dev/trans-ancientcorrectionlost.html +++ b/gl/dev/trans-ancientcorrectionlost.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Ancient Corrections (Old Text Lost)

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                    substitution, original illegible or lost

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    public<add place="overstrike">a</add>e

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: public«a»e
                                                                                                                                                                                                                                                                                                    (IRT: 50)
                                                                                                                                                                                                                                                                                                    τὸ<add place="overstrike">ν</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: τὸ«ν»
                                                                                                                                                                                                                                                                                                    (InsAph: 15.328)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Ancient Corrections (Old Text Lost)

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    • TEI definition: add ; EpiDoc-specific + customization: add

                                                                                                                                                                                                                                                                                                    substitution, original illegible or lost

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    public<add place="overstrike">a</add>e

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: public«a»e
                                                                                                                                                                                                                                                                                                    (IRT: 50)
                                                                                                                                                                                                                                                                                                    τὸ<add place="overstrike">ν</add>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: τὸ«ν»
                                                                                                                                                                                                                                                                                                    (InsAph: 15.328)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-apices-pt-br.html b/gl/dev/trans-apices-pt-br.html index e9b2aad1f..cb035bb40 100644 --- a/gl/dev/trans-apices-pt-br.html +++ b/gl/dev/trans-apices-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Ápices

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Vogais que carregam ápices

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                    Panciera 1991 IV.1; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <hi rend="apex">a</hi>
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Ápices

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Vogais que carregam ápices

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                    Panciera 1991 IV.1; Sosin 2011:

                                                                                                                                                                                                                                                                                                    <hi rend="apex">a</hi>
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-apices.html b/gl/dev/trans-apices.html index 0ae7cb310..e74849d01 100644 --- a/gl/dev/trans-apices.html +++ b/gl/dev/trans-apices.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Apices and other diacritics

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Vowels carrying apices or other diacritics, occasionally other letters marked with diacritical and other non-alphabetic glyphs as part of the writing system (as opposed to marks of abbreviation, numerical marks, metrical or musical symbols, marginal notes, etc.).

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                    Apices

                                                                                                                                                                                                                                                                                                    Characters, principally in Latin inscriptions, marked with the apex character that general indicates a long vowel. Less commonly used over the letter ‘I’, which would tend to be written longa. This diacritic may look very similar to, but from context is usually treated as distinct from, tonos or acute (see below).

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.1 (p. 210): á, é, í, ó, ú

                                                                                                                                                                                                                                                                                                    <hi rend="apex">a</hi>,
                                                                                                                                                                                                                                                                                                    <hi rend="apex">e</hi>,
                                                                                                                                                                                                                                                                                                    <hi rend="apex">i</hi>,
                                                                                                                                                                                                                                                                                                    <hi rend="apex">o</hi>,

                                                                                                                                                                                                                                                                                                    <hi rend="apex">u</hi>
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)

                                                                                                                                                                                                                                                                                                    Panciera 1991 C IV (p. 14): á

                                                                                                                                                                                                                                                                                                    <hi rend="apex">a</hi>
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    Standard Greek diacritics

                                                                                                                                                                                                                                                                                                    Occasionally Ancient Greek inscriptions and papyri (particularly those from later than the classical period) will have diaeresis or other diacriticals written over some of the vowels. Very often these have a different appearance, function and position than the modern ‘katherevousa’ diacriticals used in editions of ancient texts. Classical corpora such as the Duke Databank of Documentary Papyri therefore prefer to separate the modern, purely editorial diacriticals of the standard edition, from the rarer, possibly inconsistent, ancient disacriticals in the diplomatic text itself. In the case, as in the examples below, the text is transcribed using the Unicode characters for Greek and modern diacritics as per expected and interpreted spelling, and the ancient diacritics are encoded purely as XML markup, considered to be highlighting the vowel in question.

                                                                                                                                                                                                                                                                                                    Sosin 2011Leiden+ Documentation: Diacriticals http://papyri.info/docs/leiden_plus#diacriticals: υἱ(¨)οῦ

                                                                                                                                                                                                                                                                                                    υ<hi rend="diaeresis"></hi>οῦ
                                                                                                                                                                                                                                                                                                    (Sosin)

                                                                                                                                                                                                                                                                                                    Sosin 2011Leiden+ Documentation: Diacriticals http://papyri.info/docs/leiden_plus#diacriticals: ὧ(῾)

                                                                                                                                                                                                                                                                                                    <hi rend="asper"></hi>

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Apices and other diacritics

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Vowels carrying apices or other diacritics, occasionally other letters marked with diacritical and other non-alphabetic glyphs as part of the writing system (as opposed to marks of abbreviation, numerical marks, metrical or musical symbols, marginal notes, etc.).

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                    Apices

                                                                                                                                                                                                                                                                                                    Characters, principally in Latin inscriptions, marked with the apex character that general indicates a long vowel. Less commonly used over the letter ‘I’, which would tend to be written longa. This diacritic may look very similar to, but from context is usually treated as distinct from, tonos or acute (see below).

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.1 (p. 210): á, é, í, ó, ú

                                                                                                                                                                                                                                                                                                    <hi rend="apex">a</hi>,
                                                                                                                                                                                                                                                                                                    <hi rend="apex">e</hi>,
                                                                                                                                                                                                                                                                                                    <hi rend="apex">i</hi>,
                                                                                                                                                                                                                                                                                                    <hi rend="apex">o</hi>,

                                                                                                                                                                                                                                                                                                    <hi rend="apex">u</hi>
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)

                                                                                                                                                                                                                                                                                                    Panciera 1991 C IV (p. 14): á

                                                                                                                                                                                                                                                                                                    <hi rend="apex">a</hi>
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    Standard Greek diacritics

                                                                                                                                                                                                                                                                                                    Occasionally Ancient Greek inscriptions and papyri (particularly those from later than the classical period) will have diaeresis or other diacriticals written over some of the vowels. Very often these have a different appearance, function and position than the modern ‘katherevousa’ diacriticals used in editions of ancient texts. Classical corpora such as the Duke Databank of Documentary Papyri therefore prefer to separate the modern, purely editorial diacriticals of the standard edition, from the rarer, possibly inconsistent, ancient disacriticals in the diplomatic text itself. In the case, as in the examples below, the text is transcribed using the Unicode characters for Greek and modern diacritics as per expected and interpreted spelling, and the ancient diacritics are encoded purely as XML markup, considered to be highlighting the vowel in question.

                                                                                                                                                                                                                                                                                                    Sosin 2011Leiden+ Documentation: Diacriticals http://papyri.info/docs/leiden_plus#diacriticals: υἱ(¨)οῦ

                                                                                                                                                                                                                                                                                                    υ<hi rend="diaeresis"></hi>οῦ
                                                                                                                                                                                                                                                                                                    (Sosin)

                                                                                                                                                                                                                                                                                                    Sosin 2011Leiden+ Documentation: Diacriticals http://papyri.info/docs/leiden_plus#diacriticals: ὧ(῾)

                                                                                                                                                                                                                                                                                                    <hi rend="asper"></hi>

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-breviatio-pt-br.html b/gl/dev/trans-breviatio-pt-br.html index 56b69a4bc..6b60714dc 100644 --- a/gl/dev/trans-breviatio-pt-br.html +++ b/gl/dev/trans-breviatio-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Breviatio

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Explicação editorial de um "breviatio".

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    ab eo <supplied reason="explanationcert="high">imperatore</supplied>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    Flavius Vivus Benedictus, excellent
                                                                                                                                                                                                                                                                                                    man <supplied reason="explanation">of equestrian status</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Flavius Vivus Benedictus, excellent man (i.e. of equestrian status)
                                                                                                                                                                                                                                                                                                    (IRT: 103)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Breviatio

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Explicação editorial de um "breviatio".

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    ab eo <supplied reason="explanationcert="high">imperatore</supplied>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    Flavius Vivus Benedictus, excellent
                                                                                                                                                                                                                                                                                                    man <supplied reason="explanation">of equestrian status</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Flavius Vivus Benedictus, excellent man (i.e. of equestrian status)
                                                                                                                                                                                                                                                                                                    (IRT: 103)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-breviatio.html b/gl/dev/trans-breviatio.html index 6c7a204d5..04d1dc418 100644 --- a/gl/dev/trans-breviatio.html +++ b/gl/dev/trans-breviatio.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Breviatio

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Editorial explanation of a "breviatio".

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    ab eo <supplied reason="explanationcert="high">imperatore</supplied>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    Flavius Vivus Benedictus, excellent man <supplied reason="explanation">of equestrian status</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Flavius Vivus Benedictus, excellent man (i.e. of equestrian status)
                                                                                                                                                                                                                                                                                                    (IRT: 103)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. , Charlotte Tupman

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Breviatio

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Editorial explanation of a "breviatio".

                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                    ab eo <supplied reason="explanationcert="high">imperatore</supplied>
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    Flavius Vivus Benedictus, excellent man <supplied reason="explanation">of equestrian status</supplied>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: Flavius Vivus Benedictus, excellent man (i.e. of equestrian status)
                                                                                                                                                                                                                                                                                                    (IRT: 103)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. , Charlotte Tupman

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-charactershighlighted-pt-br.html b/gl/dev/trans-charactershighlighted-pt-br.html index 8ef4ee8cb..66246683e 100644 --- a/gl/dev/trans-charactershighlighted-pt-br.html +++ b/gl/dev/trans-charactershighlighted-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Caracteres ressaltados ou destacados de alguma forma

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Existem muitas maneiras comuns, em inscrições e papiros, de separar letras dos textos que as circundam: os caracteres podem ser maiores, menores, escritos em uma tinta de cor diferente, escritos em letras de estilo diferente, serifadas ou decoradas de diversos modos. O EpiDoc define alguns tipos comuns de destaque, mas o elemento hi pode ser utilizado para caracteres com um destaque arbitrário.

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                    Palavras ou caracteres destacados devem receber marcação com o elemento hi, com um atributo rend que especifique que tipo de destaque foi utilizado. Para se informar sobre os valores mais comuns de rend, vejaas seções listadas abaixo. Se nenhum destes valores se aplica ao caso que você está marcando, novos valores de rend podem ser criados para esta situação. Observe que os Exemplos de Folha de Estilo EpiDoc geralmente não vão lidar com estas variantes "não vinculados" de hi.

                                                                                                                                                                                                                                                                                                    Veja também as seções:

                                                                                                                                                                                                                                                                                                    No examplo, a renderização em convenções epigráficas padrão.

                                                                                                                                                                                                                                                                                                    <hi rend="red">πρεσβύτης</hi>
                                                                                                                                                                                                                                                                                                    <hi rend="italic">legi</hi>

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Caracteres ressaltados ou destacados de alguma forma

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Existem muitas maneiras comuns, em inscrições e papiros, de separar letras dos textos que as circundam: os caracteres podem ser maiores, menores, escritos em uma tinta de cor diferente, escritos em letras de estilo diferente, serifadas ou decoradas de diversos modos. O EpiDoc define alguns tipos comuns de destaque, mas o elemento hi pode ser utilizado para caracteres com um destaque arbitrário.

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                    Palavras ou caracteres destacados devem receber marcação com o elemento hi, com um atributo rend que especifique que tipo de destaque foi utilizado. Para se informar sobre os valores mais comuns de rend, vejaas seções listadas abaixo. Se nenhum destes valores se aplica ao caso que você está marcando, novos valores de rend podem ser criados para esta situação. Observe que os Exemplos de Folha de Estilo EpiDoc geralmente não vão lidar com estas variantes "não vinculados" de hi.

                                                                                                                                                                                                                                                                                                    Veja também as seções:

                                                                                                                                                                                                                                                                                                    No examplo, a renderização em convenções epigráficas padrão.

                                                                                                                                                                                                                                                                                                    <hi rend="red">πρεσβύτης</hi>
                                                                                                                                                                                                                                                                                                    <hi rend="italic">legi</hi>

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-charactershighlighted.html b/gl/dev/trans-charactershighlighted.html index 4bccb7714..72245ef49 100644 --- a/gl/dev/trans-charactershighlighted.html +++ b/gl/dev/trans-charactershighlighted.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Characters highlighted or set apart in some way

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    There are many common ways in which letters are set apart from surrounding text in inscriptions and papyri: characters may be larger, smaller, in different color ink, differently styled letters, serifed or decorated in various ways. EpiDoc defines a few common types of such highlighting, but the hi element may be used for arbitrarily highlighted characters.

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                    Highlighted characters or words should be tagged using the hi element, with a rend attribute specifying the kind of highlighting. For the most common values of rend, see the separate sections listed below. If none of these values apply to the case you are marking up, new values of rend may be coined for this purpose. Note that the EpiDoc example stylesheets will most likely not handle these "unbound" variants of hi.

                                                                                                                                                                                                                                                                                                    See also separate sections on:

                                                                                                                                                                                                                                                                                                    No example rendering in standard epigraphic conventions.

                                                                                                                                                                                                                                                                                                    <hi rend="red">πρεσβύτης</hi>
                                                                                                                                                                                                                                                                                                    <hi rend="italic">legi</hi>

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Characters highlighted or set apart in some way

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    There are many common ways in which letters are set apart from surrounding text in inscriptions and papyri: characters may be larger, smaller, in different color ink, differently styled letters, serifed or decorated in various ways. EpiDoc defines a few common types of such highlighting, but the hi element may be used for arbitrarily highlighted characters.

                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                    Highlighted characters or words should be tagged using the hi element, with a rend attribute specifying the kind of highlighting. For the most common values of rend, see the separate sections listed below. If none of these values apply to the case you are marking up, new values of rend may be coined for this purpose. Note that the EpiDoc example stylesheets will most likely not handle these "unbound" variants of hi.

                                                                                                                                                                                                                                                                                                    See also separate sections on:

                                                                                                                                                                                                                                                                                                    No example rendering in standard epigraphic conventions.

                                                                                                                                                                                                                                                                                                    <hi rend="red">πρεσβύτης</hi>
                                                                                                                                                                                                                                                                                                    <hi rend="italic">legi</hi>

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-claudian-pt-br.html b/gl/dev/trans-claudian-pt-br.html index 244d6c117..27ecd93a1 100644 --- a/gl/dev/trans-claudian-pt-br.html +++ b/gl/dev/trans-claudian-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Letras Claudias

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Três caracteres, criados pelo imperador Claudius para representar sons ou combinações de sons que não eram representados sem ambiguidade pelos caracteres latinos existentes: Ↄ(Unicode 2183: antisigma, representando PS or BS); Ⱶ (Unicode 2C75: sonus medius, representando uma vogal entre U e I; tardiamente representada com Y); Ⅎ (Unicode 2132: digamma inversum, representando o U consonontal U).

                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific - customization: g

                                                                                                                                                                                                                                                                                                    Antes destes caracteres serem representados por código Unicode, os epígrafos latinos tinham o hábito de representá-los usando os caraqcteres latinos correspondentes (PS, BS, Y ou V). Quando se transcreve uma edição assim, deve-se utilizar g com a expansão type (precedida por "claudian_"). Quando o próprio caracter está incluído numa palavra latina, pode-se simplesmente incluir o caracter Unicode no texto, sem marcação. Ou g pode circundar o caracter Unicode.

                                                                                                                                                                                                                                                                                                    Pode ser uma boa ideia, por causa da indexação e da análise das palavras, regularizar (utilizando choice, orig e reg) as palavras que contenham estas letras, utilizando sua escrita latina mais convencional (veja o exemplo abaixo e veja Regularização).

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3; Panciera 1991 19: y, bs, ps, v

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3: Nymphabus Y; privatis V

                                                                                                                                                                                                                                                                                                    Dohnicht 3: ⊂y⊃, ⊂bs⊃, ⊂ps⊃, ⊂v⊃

                                                                                                                                                                                                                                                                                                    : Ⱶ, Ↄ, Ↄ, Ⅎ

                                                                                                                                                                                                                                                                                                    <g type="claudian_y"/>, <g type="claudian_bs"/>, <g type="claudian_ps"/>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"/>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                     Ⱶ, -        Ↄ, Ↄ, Ⅎ 

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Dohnicht style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Duke Databank style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    <g type="claudian_y"></g>, <g type="claudian_bs"></g>, <g type="claudian_ps"></g>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"></g>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    • Duke Databank style: ((claudian_y)) , ((claudian_bs)) , ((claudian_ps)) , ((claudian_v))
                                                                                                                                                                                                                                                                                                    N<g type="claudian_y"></g>mphabus; pri<g type="claudian_v"></g>atis

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: N((claudian_y))mphabus; pri((claudian_v))atis
                                                                                                                                                                                                                                                                                                    • Dohnicht style: N⊂claudian_y⊃mphabus; pri⊂claudian_v⊃atis
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)
                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                     <orig>NⱵmphabus</orig>
                                                                                                                                                                                                                                                                                                     <reg>Nymphabus</reg>
                                                                                                                                                                                                                                                                                                    </choice>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Dohnicht style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Duke Databank style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Letras Claudias

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Três caracteres, criados pelo imperador Claudius para representar sons ou combinações de sons que não eram representados sem ambiguidade pelos caracteres latinos existentes: Ↄ(Unicode 2183: antisigma, representando PS or BS); Ⱶ (Unicode 2C75: sonus medius, representando uma vogal entre U e I; tardiamente representada com Y); Ⅎ (Unicode 2132: digamma inversum, representando o U consonontal U).

                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific + customization: g

                                                                                                                                                                                                                                                                                                    Antes destes caracteres serem representados por código Unicode, os epígrafos latinos tinham o hábito de representá-los usando os caraqcteres latinos correspondentes (PS, BS, Y ou V). Quando se transcreve uma edição assim, deve-se utilizar g com a expansão type (precedida por "claudian_"). Quando o próprio caracter está incluído numa palavra latina, pode-se simplesmente incluir o caracter Unicode no texto, sem marcação. Ou g pode circundar o caracter Unicode.

                                                                                                                                                                                                                                                                                                    Pode ser uma boa ideia, por causa da indexação e da análise das palavras, regularizar (utilizando choice, orig e reg) as palavras que contenham estas letras, utilizando sua escrita latina mais convencional (veja o exemplo abaixo e veja Regularização).

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3; Panciera 1991 19: y, bs, ps, v

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3: Nymphabus Y; privatis V

                                                                                                                                                                                                                                                                                                    Dohnicht 3: ⊂y⊃, ⊂bs⊃, ⊂ps⊃, ⊂v⊃

                                                                                                                                                                                                                                                                                                    : Ⱶ, Ↄ, Ↄ, Ⅎ

                                                                                                                                                                                                                                                                                                    <g type="claudian_y"/>, <g type="claudian_bs"/>, <g type="claudian_ps"/>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"/>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                     Ⱶ, +        Ↄ, Ↄ, Ⅎ 

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Dohnicht style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Duke Databank style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    <g type="claudian_y"></g>, <g type="claudian_bs"></g>, <g type="claudian_ps"></g>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"></g>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    • Duke Databank style: ((claudian_y)) , ((claudian_bs)) , ((claudian_ps)) , ((claudian_v))
                                                                                                                                                                                                                                                                                                    N<g type="claudian_y"></g>mphabus; pri<g type="claudian_v"></g>atis

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: N((claudian_y))mphabus; pri((claudian_v))atis
                                                                                                                                                                                                                                                                                                    • Dohnicht style: N⊂claudian_y⊃mphabus; pri⊂claudian_v⊃atis
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)
                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                     <orig>NⱵmphabus</orig>
                                                                                                                                                                                                                                                                                                     <reg>Nymphabus</reg>
                                                                                                                                                                                                                                                                                                    </choice>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Dohnicht style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Duke Databank style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-claudian.html b/gl/dev/trans-claudian.html index fbc5a8a39..c67590b92 100644 --- a/gl/dev/trans-claudian.html +++ b/gl/dev/trans-claudian.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Claudian letters

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Three characters created by the Emperor Claudius to represent sounds or sound combinations that were not unambiguously represented by existing Latin characters: Ↄ(Unicode 2183: antisigma, representing PS or BS); Ⱶ (Unicode 2C75: sonus medius, representing vowel bwteen U and I; later represented with Y); Ⅎ (Unicode 2132: digamma inversum, representing consonantal U).

                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific - customization: g

                                                                                                                                                                                                                                                                                                    Before these characters were represented by Unicode codepoints, Latin epigraphers were in the habit of transcribing these using the Latin characters to which they correspond (PS, BS, Y or V respectively). When transcribing such an edition, g may be used with the expansion in the type (preceded by "claudian_"). When the character itself is simply included in a Latin word, the Unicode character may simply be included in the text with no markup. Or g might be wrapped around the Unicode character.

                                                                                                                                                                                                                                                                                                    It might also be a good idea, for the sake of indexing and parsing words, to regularize (using choice, orig and reg) words containing these letters to their more conventional Latin spellings (see final example below, and cf. Regularization).

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3; Panciera 1991 19: y, bs, ps, v

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3: Nymphabus Y; privatis V

                                                                                                                                                                                                                                                                                                    Dohnicht 3: ⊂y⊃, ⊂bs⊃, ⊂ps⊃, ⊂v⊃

                                                                                                                                                                                                                                                                                                    : Ⱶ, Ↄ, Ↄ, Ⅎ

                                                                                                                                                                                                                                                                                                    <g type="claudian_y"/>, <g type="claudian_bs"/>, <g type="claudian_ps"/>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"/>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                    +

                                                                                                                                                                                                                                                                                                    Claudian letters

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Three characters created by the Emperor Claudius to represent sounds or sound combinations that were not unambiguously represented by existing Latin characters: Ↄ(Unicode 2183: antisigma, representing PS or BS); Ⱶ (Unicode 2C75: sonus medius, representing vowel bwteen U and I; later represented with Y); Ⅎ (Unicode 2132: digamma inversum, representing consonantal U).

                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific + customization: g

                                                                                                                                                                                                                                                                                                    Before these characters were represented by Unicode codepoints, Latin epigraphers were in the habit of transcribing these using the Latin characters to which they correspond (PS, BS, Y or V respectively). When transcribing such an edition, g may be used with the expansion in the type (preceded by "claudian_"). When the character itself is simply included in a Latin word, the Unicode character may simply be included in the text with no markup. Or g might be wrapped around the Unicode character.

                                                                                                                                                                                                                                                                                                    It might also be a good idea, for the sake of indexing and parsing words, to regularize (using choice, orig and reg) words containing these letters to their more conventional Latin spellings (see final example below, and cf. Regularization).

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3; Panciera 1991 19: y, bs, ps, v

                                                                                                                                                                                                                                                                                                    Krummrey/Panciera 1980 IV.3: Nymphabus Y; privatis V

                                                                                                                                                                                                                                                                                                    Dohnicht 3: ⊂y⊃, ⊂bs⊃, ⊂ps⊃, ⊂v⊃

                                                                                                                                                                                                                                                                                                    : Ⱶ, Ↄ, Ↄ, Ⅎ

                                                                                                                                                                                                                                                                                                    <g type="claudian_y"/>, <g type="claudian_bs"/>, <g type="claudian_ps"/>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"/>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                            Ⱶ, Ↄ, Ↄ, Ⅎ -    

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Dohnicht style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Duke Databank style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    <g type="claudian_y"></g>, <g type="claudian_bs"></g>, <g type="claudian_ps"></g>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"></g>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    • Duke Databank style: ((claudian_y)) , ((claudian_bs)) , ((claudian_ps)) , ((claudian_v))
                                                                                                                                                                                                                                                                                                    N<g type="claudian_y"></g>mphabus;
                                                                                                                                                                                                                                                                                                    pri<g type="claudian_v"></g>atis

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: N((claudian_y))mphabus; pri((claudian_v))atis
                                                                                                                                                                                                                                                                                                    • Dohnicht style: N⊂claudian_y⊃mphabus; pri⊂claudian_v⊃atis
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)
                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                     <orig>NⱵmphabus</orig>
                                                                                                                                                                                                                                                                                                     <reg>Nymphabus</reg>
                                                                                                                                                                                                                                                                                                    </choice>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Dohnicht style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Duke Databank style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)

                                                                                                                                                                                                                                                                                                    Instead of using type in g, the recommended use of <g[@ref]> in Symbol (Non Meaning-Bearing) may be applied.

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +    

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Dohnicht style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    • Duke Databank style: Ⱶ, Ↄ, Ↄ, Ⅎ
                                                                                                                                                                                                                                                                                                    <g type="claudian_y"></g>, <g type="claudian_bs"></g>, <g type="claudian_ps"></g>,
                                                                                                                                                                                                                                                                                                    <g type="claudian_v"></g>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((claudian_y)), ((claudian_bs)), ((claudian_ps)), ((claudian_v))
                                                                                                                                                                                                                                                                                                    • Dohnicht style: ⊂claudian_y⊃, ⊂claudian_bs⊃, ⊂claudian_ps⊃, ⊂claudian_v⊃
                                                                                                                                                                                                                                                                                                    • Duke Databank style: ((claudian_y)) , ((claudian_bs)) , ((claudian_ps)) , ((claudian_v))
                                                                                                                                                                                                                                                                                                    N<g type="claudian_y"></g>mphabus;
                                                                                                                                                                                                                                                                                                    pri<g type="claudian_v"></g>atis

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: N((claudian_y))mphabus; pri((claudian_v))atis
                                                                                                                                                                                                                                                                                                    • Dohnicht style: N⊂claudian_y⊃mphabus; pri⊂claudian_v⊃atis
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)
                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                     <orig>NⱵmphabus</orig>
                                                                                                                                                                                                                                                                                                     <reg>Nymphabus</reg>
                                                                                                                                                                                                                                                                                                    </choice>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Dohnicht style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    • Duke Databank style: NⱵmphabus
                                                                                                                                                                                                                                                                                                    (Krummrey/Panciera)

                                                                                                                                                                                                                                                                                                    Instead of using type in g, the recommended use of <g[@ref]> in Symbol (Non Meaning-Bearing) may be applied.

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-cleartext-pt-br.html b/gl/dev/trans-cleartext-pt-br.html index 4cc101406..edb030e32 100644 --- a/gl/dev/trans-cleartext-pt-br.html +++ b/gl/dev/trans-cleartext-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Texto Claro

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Texto que é inteiramente legível e não requer intervenção editorial deve passar pela transformação sem melhorias ou modificações.

                                                                                                                                                                                                                                                                                                    A única propriedade que deve ser destacada é que a presença ou ausência de espaço em branco no XML será preservada em qualquer renderização final (HTML, ODF, etc.), portanto os espaços de qualquer tipo (inclusive tabulações, novas linhas, etc.) só devem ser inseridos entre palavras. Para preservar este comportamento, recomenda-se que a div contendo o texto transcrito receba o atributo xml:space com o valor "preserve".

                                                                                                                                                                                                                                                                                                    Panciera 1991 III.1: abc

                                                                                                                                                                                                                                                                                                     abc 
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Texto Claro

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Texto que é inteiramente legível e não requer intervenção editorial deve passar pela transformação sem melhorias ou modificações.

                                                                                                                                                                                                                                                                                                    A única propriedade que deve ser destacada é que a presença ou ausência de espaço em branco no XML será preservada em qualquer renderização final (HTML, ODF, etc.), portanto os espaços de qualquer tipo (inclusive tabulações, novas linhas, etc.) só devem ser inseridos entre palavras. Para preservar este comportamento, recomenda-se que a div contendo o texto transcrito receba o atributo xml:space com o valor "preserve".

                                                                                                                                                                                                                                                                                                    Panciera 1991 III.1: abc

                                                                                                                                                                                                                                                                                                     abc 
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-cleartext.html b/gl/dev/trans-cleartext.html index ac4040b11..b29e386c2 100644 --- a/gl/dev/trans-cleartext.html +++ b/gl/dev/trans-cleartext.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Clear text

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Text which is generally legible and requires no editorial intervention should be passed through the transformation with no modification or enhancement.

                                                                                                                                                                                                                                                                                                    The only special feature worth highlighting is that the presence or absence of whitespace in the XML will be preserved in any output (HTML, ODF, etc.), so spaces of any kind (including tabs, new lines, etc.) should only be placed between words. To preserve this behaviour, it is recommended that the div containing the transcribed text should be given the attribute xml:space with a value of "preserve".

                                                                                                                                                                                                                                                                                                    Panciera 1991 III.1: abc

                                                                                                                                                                                                                                                                                                    +

                                                                                                                                                                                                                                                                                                    Clear text

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Text which is generally legible and requires no editorial intervention should be passed through the transformation with no modification or enhancement.

                                                                                                                                                                                                                                                                                                    The only special feature worth highlighting is that the presence or absence of whitespace in the XML will be preserved in any output (HTML, ODF, etc.), so spaces of any kind (including tabs, new lines, etc.) should only be placed between words. To preserve this behaviour, it is recommended that the div containing the transcribed text should be given the attribute xml:space with a value of "preserve".

                                                                                                                                                                                                                                                                                                    Panciera 1991 III.1: abc

                                                                                                                                                                                                                                                                                                            abc  -    
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +    
                                                                                                                                                                                                                                                                                                    (Panciera)

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                    3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-correction-pt-br.html b/gl/dev/trans-correction-pt-br.html index 19715faad..009bcd343 100644 --- a/gl/dev/trans-correction-pt-br.html +++ b/gl/dev/trans-correction-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Correção sem Especificação

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Erros tipográficos podem ser corrigidos silenciosamente, sem a especificação do texto assim corrigido.

                                                                                                                                                                                                                                                                                                    • TEI definition: corr ; EpiDoc-specific - customization: corr

                                                                                                                                                                                                                                                                                                    O texto corrigido é colocado dentro de corr, sem a necessidade de um sic correspondente.

                                                                                                                                                                                                                                                                                                    SEG ; Sosin 2011: <...>

                                                                                                                                                                                                                                                                                                    a<corr>b</corr>c
                                                                                                                                                                                                                                                                                                    ()
                                                                                                                                                                                                                                                                                                    <corr></corr>μῶν

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: μῶν
                                                                                                                                                                                                                                                                                                    (InsAph: 12.921)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Other pages describing <corr>:

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Correção sem Especificação

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Erros tipográficos podem ser corrigidos silenciosamente, sem a especificação do texto assim corrigido.

                                                                                                                                                                                                                                                                                                    • TEI definition: corr ; EpiDoc-specific + customization: corr

                                                                                                                                                                                                                                                                                                    O texto corrigido é colocado dentro de corr, sem a necessidade de um sic correspondente.

                                                                                                                                                                                                                                                                                                    SEG ; Sosin 2011: <...>

                                                                                                                                                                                                                                                                                                    a<corr>b</corr>c
                                                                                                                                                                                                                                                                                                    ()
                                                                                                                                                                                                                                                                                                    <corr></corr>μῶν

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: μῶν
                                                                                                                                                                                                                                                                                                    (InsAph: 12.921)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Other pages describing <corr>:

                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-correction.html b/gl/dev/trans-correction.html index 49c9be1cd..0b42b7c00 100644 --- a/gl/dev/trans-correction.html +++ b/gl/dev/trans-correction.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Correction without Specification

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    Typographic errors may be corrected silently, without specification of the text thus corrected.

                                                                                                                                                                                                                                                                                                    • TEI definition: corr ; EpiDoc-specific - customization: corr

                                                                                                                                                                                                                                                                                                    The corrected text is placed inside a corr, without the need for a corresponding sic.

                                                                                                                                                                                                                                                                                                    SEG ; Sosin 2011: <...>

                                                                                                                                                                                                                                                                                                    a<corr>b</corr>c
                                                                                                                                                                                                                                                                                                    ()
                                                                                                                                                                                                                                                                                                    <corr></corr>μῶν

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: μῶν
                                                                                                                                                                                                                                                                                                    (InsAph: 12.921)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Other pages describing <corr>:

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                    Correction without Specification

                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                    Typographic errors may be corrected silently, without specification of the text thus corrected.

                                                                                                                                                                                                                                                                                                    • TEI definition: corr ; EpiDoc-specific + customization: corr

                                                                                                                                                                                                                                                                                                    The corrected text is placed inside a corr, without the need for a corresponding sic.

                                                                                                                                                                                                                                                                                                    SEG ; Sosin 2011: <...>

                                                                                                                                                                                                                                                                                                    a<corr>b</corr>c
                                                                                                                                                                                                                                                                                                    ()
                                                                                                                                                                                                                                                                                                    <corr></corr>μῶν

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • London style: μῶν
                                                                                                                                                                                                                                                                                                    (InsAph: 12.921)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Other pages describing <corr>:

                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-damaged-pt-br.html b/gl/dev/trans-damaged-pt-br.html index 93e7791b7..9043a9cc9 100644 --- a/gl/dev/trans-damaged-pt-br.html +++ b/gl/dev/trans-damaged-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                    Caracteres Danificados

                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                    O caracter (ou caracteres) no documento fonte que sofreu algum tipo de dano que não necessariamente impede sua interpretação e legibilidade.

                                                                                                                                                                                                                                                                                                    • TEI definition: damage ; EpiDoc-specific - customization: damage

                                                                                                                                                                                                                                                                                                    Caracteres danificados no documento fonte, mas não ambíguos o suficiente para necessitar a tag unclear podem, se desejado, ser marcados com o elemento damage.

                                                                                                                                                                                                                                                                                                    Não existe um equivalente direto Leiden para a categoria de caracteres danificados mas perfeitamente legíveis. Apesar de alguns pesquisadores usarem o ponto subescrito indiscriminadamente para caracteres danificados, sejam eles legíveis ou ambíguos forade contexto, não se revomenda isto, de modo geral, na prática epigráfica e papirológica. Codificar caracteres danificados de forma distinte é portanto opcional, não é central em relação às distinções Leiden que o EpiDoc busca refletir, e pode ou não ser utilizado, de acordo com os projetos individuais. Atualmente não existe uma renderizaçãop recomendada para esta característica, e ela não se apresenta nos Exemplos de Folhas de Estilo EpiDoc.

                                                                                                                                                                                                                                                                                                    Uma razão para a marcação explícita de caracteres danificados pode ser a habilitação de ligação das partes do suporte a imagens (como codificadas no elemento facsimile ) utilizando um atributo facs.

                                                                                                                                                                                                                                                                                                    <damage>abc</damage>

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                    <lb n="46"/>I
                                                                                                                                                                                                                                                                                                    <unclear>m</unclear>
                                                                                                                                                                                                                                                                                                    <supplied reason="lost">p. <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                      evidence="previouseditor">
                                                                                                                                                                                                                                                                                                    ca</supplied>
                                                                                                                                                                                                                                                                                                    </supplied>
                                                                                                                                                                                                                                                                                                    <damage>e</damage>sari <g type="dot"/> augusto

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style:   ←Iṃ[p. ca]esari ((dot)) augusto
                                                                                                                                                                                                                                                                                                    Note: Source: CIL XI, 1421 (encoding: Lamé)

                                                                                                                                                                                                                                                                                                    Além disto, uma quantidade grande de danos que incluem tanto os caracteres legíveis quanto os ilegíveis, e mesmo lacunas, pode estar contida num único elemento damage, que então incluiria unclear, supplied e outras tags dentro dele.

                                                                                                                                                                                                                                                                                                    <lb n="6"/>
                                                                                                                                                                                                                                                                                                    <damage>
                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                     <orig>
                                                                                                                                                                                                                                                                                                      <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                     </orig>
                                                                                                                                                                                                                                                                                                     <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                    </damage>λικη

                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                    • Default (Panciera) style:
                                                                                                                                                                                                                                                                                                      [---]Ιι̣λικη
                                                                                                                                                                                                                                                                                                    (IRT: 469a)

                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                    Other pages describing <damage>:

                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                      2. Marion Lamé, autor
                                                                                                                                                                                                                                                                                                      3. Elli Mylonas, autor
                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                      Caracteres Danificados

                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                      O caracter (ou caracteres) no documento fonte que sofreu algum tipo de dano que não necessariamente impede sua interpretação e legibilidade.

                                                                                                                                                                                                                                                                                                      • TEI definition: damage ; EpiDoc-specific + customization: damage

                                                                                                                                                                                                                                                                                                      Caracteres danificados no documento fonte, mas não ambíguos o suficiente para necessitar a tag unclear podem, se desejado, ser marcados com o elemento damage.

                                                                                                                                                                                                                                                                                                      Não existe um equivalente direto Leiden para a categoria de caracteres danificados mas perfeitamente legíveis. Apesar de alguns pesquisadores usarem o ponto subescrito indiscriminadamente para caracteres danificados, sejam eles legíveis ou ambíguos forade contexto, não se revomenda isto, de modo geral, na prática epigráfica e papirológica. Codificar caracteres danificados de forma distinte é portanto opcional, não é central em relação às distinções Leiden que o EpiDoc busca refletir, e pode ou não ser utilizado, de acordo com os projetos individuais. Atualmente não existe uma renderizaçãop recomendada para esta característica, e ela não se apresenta nos Exemplos de Folhas de Estilo EpiDoc.

                                                                                                                                                                                                                                                                                                      Uma razão para a marcação explícita de caracteres danificados pode ser a habilitação de ligação das partes do suporte a imagens (como codificadas no elemento facsimile ) utilizando um atributo facs.

                                                                                                                                                                                                                                                                                                      <damage>abc</damage>

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                      <lb n="46"/>I
                                                                                                                                                                                                                                                                                                      <unclear>m</unclear>
                                                                                                                                                                                                                                                                                                      <supplied reason="lost">p. <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                        evidence="previouseditor">
                                                                                                                                                                                                                                                                                                      ca</supplied>
                                                                                                                                                                                                                                                                                                      </supplied>
                                                                                                                                                                                                                                                                                                      <damage>e</damage>sari <g type="dot"/> augusto

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style:   ←Iṃ[p. ca]esari ((dot)) augusto
                                                                                                                                                                                                                                                                                                      Note: Source: CIL XI, 1421 (encoding: Lamé)

                                                                                                                                                                                                                                                                                                      Além disto, uma quantidade grande de danos que incluem tanto os caracteres legíveis quanto os ilegíveis, e mesmo lacunas, pode estar contida num único elemento damage, que então incluiria unclear, supplied e outras tags dentro dele.

                                                                                                                                                                                                                                                                                                      <lb n="6"/>
                                                                                                                                                                                                                                                                                                      <damage>
                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                       <orig>
                                                                                                                                                                                                                                                                                                        <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                       </orig>
                                                                                                                                                                                                                                                                                                       <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                      </damage>λικη

                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                      • Default (Panciera) style:
                                                                                                                                                                                                                                                                                                        [---]Ιι̣λικη
                                                                                                                                                                                                                                                                                                      (IRT: 469a)

                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                      Other pages describing <damage>:

                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                        1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                        2. Marion Lamé, autor
                                                                                                                                                                                                                                                                                                        3. Elli Mylonas, autor
                                                                                                                                                                                                                                                                                                        4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                        Date: 2024-03-05

                                                                                                                                                                                                                                                                                                        \ No newline at end of file diff --git a/gl/dev/trans-damaged.html b/gl/dev/trans-damaged.html index d4046b5fc..d44ac029a 100644 --- a/gl/dev/trans-damaged.html +++ b/gl/dev/trans-damaged.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                        Damaged characters

                                                                                                                                                                                                                                                                                                        2023-04-27

                                                                                                                                                                                                                                                                                                        Character or characters on the source document having suffered some kind of damage which does not necessarily impede its interpretation or legibility.

                                                                                                                                                                                                                                                                                                        • TEI definition: damage ; EpiDoc-specific - customization: damage

                                                                                                                                                                                                                                                                                                        Characters damaged on the source document, but not sufficiently ambiguous to require tagging as unclear may if desired be tagged with the damage element.

                                                                                                                                                                                                                                                                                                        There is not strictly any Leiden equivalent to the category of damaged but perfectly legible characters. Although some scholars have used the underdot indiscriminately for damaged characters whether they are legible or ambiguous outside of their context, this is not generally recommended in epigraphic or papyrological practice. Encoding damaged characters distinctly is therefore an optional feature, not core to the Leiden distinctions that EpiDoc aims to reflect, and may be adopted at the discretion of individual projects. There is currently no recommended rendering for this feature, and it is not handled in the EpiDoc Example Stylesheets.

                                                                                                                                                                                                                                                                                                        One reason for tagging damaged characters explicitly might be to enable the linking of parts of the support to images (as encoded in the facsimile element) using a facs attribute.

                                                                                                                                                                                                                                                                                                        <damage>abc</damage>

                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                        <lb n="46"/>I
                                                                                                                                                                                                                                                                                                        <unclear>m</unclear>
                                                                                                                                                                                                                                                                                                        <supplied reason="lost">p.
                                                                                                                                                                                                                                                                                                        <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                          evidence="previouseditor">
                                                                                                                                                                                                                                                                                                        ca</supplied>
                                                                                                                                                                                                                                                                                                        </supplied>
                                                                                                                                                                                                                                                                                                        <damage>e</damage>sari
                                                                                                                                                                                                                                                                                                        <g type="dot"/> augusto

                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: Iṃ[p. ca]esari ((dot)) augusto
                                                                                                                                                                                                                                                                                                        Note: Source: CIL XI, 1421 (encoding: Lamé)

                                                                                                                                                                                                                                                                                                        Further, a larger span of damage that includes both legible and illegible characters and even lacunae might be contained in a single damage element, which would then include unclear, supplied and other tags within it.

                                                                                                                                                                                                                                                                                                        <lb n="6"/>
                                                                                                                                                                                                                                                                                                        <damage>
                                                                                                                                                                                                                                                                                                         <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                          unit="character"/>

                                                                                                                                                                                                                                                                                                         <orig>
                                                                                                                                                                                                                                                                                                          <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                         </orig>
                                                                                                                                                                                                                                                                                                         <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                        </damage>λικη

                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                        • Default (Panciera) style:
                                                                                                                                                                                                                                                                                                          [---]Ιι̣λικη
                                                                                                                                                                                                                                                                                                        (IRT: 469a)

                                                                                                                                                                                                                                                                                                        See also:

                                                                                                                                                                                                                                                                                                        Other pages describing <damage>:

                                                                                                                                                                                                                                                                                                          Responsibility for this section

                                                                                                                                                                                                                                                                                                          1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                          2. Marion Lamé, author
                                                                                                                                                                                                                                                                                                          3. Elli Mylonas, author

                                                                                                                                                                                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                          Date: 2023-04-27

                                                                                                                                                                                                                                                                                                          \ No newline at end of file +

                                                                                                                                                                                                                                                                                                          Damaged characters

                                                                                                                                                                                                                                                                                                          2024-03-05

                                                                                                                                                                                                                                                                                                          Character or characters on the source document having suffered some kind of damage which does not necessarily impede its interpretation or legibility.

                                                                                                                                                                                                                                                                                                          • TEI definition: damage ; EpiDoc-specific + customization: damage

                                                                                                                                                                                                                                                                                                          Characters damaged on the source document, but not sufficiently ambiguous to require tagging as unclear may if desired be tagged with the damage element.

                                                                                                                                                                                                                                                                                                          There is not strictly any Leiden equivalent to the category of damaged but perfectly legible characters. Although some scholars have used the underdot indiscriminately for damaged characters whether they are legible or ambiguous outside of their context, this is not generally recommended in epigraphic or papyrological practice. Encoding damaged characters distinctly is therefore an optional feature, not core to the Leiden distinctions that EpiDoc aims to reflect, and may be adopted at the discretion of individual projects. There is currently no recommended rendering for this feature, and it is not handled in the EpiDoc Example Stylesheets.

                                                                                                                                                                                                                                                                                                          One reason for tagging damaged characters explicitly might be to enable the linking of parts of the support to images (as encoded in the facsimile element) using a facs attribute.

                                                                                                                                                                                                                                                                                                          <damage>abc</damage>

                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                          • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                          <lb n="46"/>I
                                                                                                                                                                                                                                                                                                          <unclear>m</unclear>
                                                                                                                                                                                                                                                                                                          <supplied reason="lost">p.
                                                                                                                                                                                                                                                                                                          <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                            evidence="previouseditor">
                                                                                                                                                                                                                                                                                                          ca</supplied>
                                                                                                                                                                                                                                                                                                          </supplied>
                                                                                                                                                                                                                                                                                                          <damage>e</damage>sari
                                                                                                                                                                                                                                                                                                          <g type="dot"/> augusto

                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                          • Default (Panciera) style: Iṃ[p. ca]esari ((dot)) augusto
                                                                                                                                                                                                                                                                                                          Note: Source: CIL XI, 1421 (encoding: Lamé)

                                                                                                                                                                                                                                                                                                          Further, a larger span of damage that includes both legible and illegible characters and even lacunae might be contained in a single damage element, which would then include unclear, supplied and other tags within it.

                                                                                                                                                                                                                                                                                                          <lb n="6"/>
                                                                                                                                                                                                                                                                                                          <damage>
                                                                                                                                                                                                                                                                                                           <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                            unit="character"/>

                                                                                                                                                                                                                                                                                                           <orig>
                                                                                                                                                                                                                                                                                                            <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                           </orig>
                                                                                                                                                                                                                                                                                                           <unclear>ι</unclear>
                                                                                                                                                                                                                                                                                                          </damage>λικη

                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                          • Default (Panciera) style:
                                                                                                                                                                                                                                                                                                            [---]Ιι̣λικη
                                                                                                                                                                                                                                                                                                          (IRT: 469a)

                                                                                                                                                                                                                                                                                                          See also:

                                                                                                                                                                                                                                                                                                          Other pages describing <damage>:

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                            2. Marion Lamé, author
                                                                                                                                                                                                                                                                                                            3. Elli Mylonas, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-diplomatic-pt-br.html b/gl/dev/trans-diplomatic-pt-br.html index cfef7806a..003348f15 100644 --- a/gl/dev/trans-diplomatic-pt-br.html +++ b/gl/dev/trans-diplomatic-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Transcrições Diplomáticas

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Uma transcrição diplomática, em termos epigráficos ou papirológicos, é aquela que que registra apenas os caracteres como aparecem no suporte, com mínima ou nenhuma intervenção ou interpretação editorial. Ela difere de um desenho, pois as letras individuais são identificadas, geralmente através de seus códigos Unicode, mais muitas vezes estarão digitadas em caixa alta, sem espaços, pontuação ou diacríticos (a não ser que estes estejam no documento fonte), e sem restauração de lacunas ou expansão de abreviaturas.

                                                                                                                                                                                                                                                                                                            De modo geral se assume, no fluxo de trabalho e nas ferramentas, que a transcrição diplomática EpiDoc pode ser gerada do XML subjacente, como uma visão alternativa ou paralela à edição interpretativa que segue normalmente as Convenções Leiden. Nos Exemplos de Folha de Estilo EpiDoc, modificar o parâmetro $edition-type para "diplomatic" fará com que o XSLT deixe as abreviações sem resolução, trate os elementos supplied como gap, transforme os nós de texto em texto caixa alta, sem acentuação ou espaços, assim por diante, criando uma reprodução próxima daquilo que se espera ser uma edição diplomática.

                                                                                                                                                                                                                                                                                                            Estes templates de transformação não lidam muito bem com algumas caracterísitcas diplomáticas, como caracteres de formas incomuns, letras parcialmente perdidas nos finais de linha, espaçamento interno em inscrições imperiais. Além disto, algumas comunidades podem pensar que uma edição diplomática em separado, onde são tomadas decisões diferentes na transcrição, seria mais desejado. Esta edição poderiaser codificada como <div type="edition" subtype="diplomatic">.

                                                                                                                                                                                                                                                                                                            See also:

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                            2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Transcrições Diplomáticas

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            Uma transcrição diplomática, em termos epigráficos ou papirológicos, é aquela que que registra apenas os caracteres como aparecem no suporte, com mínima ou nenhuma intervenção ou interpretação editorial. Ela difere de um desenho, pois as letras individuais são identificadas, geralmente através de seus códigos Unicode, mais muitas vezes estarão digitadas em caixa alta, sem espaços, pontuação ou diacríticos (a não ser que estes estejam no documento fonte), e sem restauração de lacunas ou expansão de abreviaturas.

                                                                                                                                                                                                                                                                                                            De modo geral se assume, no fluxo de trabalho e nas ferramentas, que a transcrição diplomática EpiDoc pode ser gerada do XML subjacente, como uma visão alternativa ou paralela à edição interpretativa que segue normalmente as Convenções Leiden. Nos Exemplos de Folha de Estilo EpiDoc, modificar o parâmetro $edition-type para "diplomatic" fará com que o XSLT deixe as abreviações sem resolução, trate os elementos supplied como gap, transforme os nós de texto em texto caixa alta, sem acentuação ou espaços, assim por diante, criando uma reprodução próxima daquilo que se espera ser uma edição diplomática.

                                                                                                                                                                                                                                                                                                            Estes templates de transformação não lidam muito bem com algumas caracterísitcas diplomáticas, como caracteres de formas incomuns, letras parcialmente perdidas nos finais de linha, espaçamento interno em inscrições imperiais. Além disto, algumas comunidades podem pensar que uma edição diplomática em separado, onde são tomadas decisões diferentes na transcrição, seria mais desejado. Esta edição poderiaser codificada como <div type="edition" subtype="diplomatic">.

                                                                                                                                                                                                                                                                                                            See also:

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                            2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-diplomatic.html b/gl/dev/trans-diplomatic.html index a71828180..fc83b30e6 100644 --- a/gl/dev/trans-diplomatic.html +++ b/gl/dev/trans-diplomatic.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Diplomatic Transcriptions

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            A diplomatic transcription in epigraphic or papyrological terms is one that records only the characters as they appear on the support, with minimal or no editorial intervention or interpretation. It differs from a drawing in that individual letters are identified, usually to Unicode codepoints, but will often be written in uppercase, without spaces, punctuation or diacritics (unless these are in the source document), and without restoring lacunae or expanding abbreviations.

                                                                                                                                                                                                                                                                                                            It is generally an assumption in the EpiDoc workflow and tooling that a diplomatic transcription can be generated from the underlying XML as an alternative, or parallel, view to the interpretive edition following the normal Leiden Conventions. In the EpiDoc Example Stylesheets changing the parameter $edition-type to "diplomatic" will lead the XSLT to leave abbreviations unresolved, treat supplied elements as gaps, transform text nodes to uppercase, unaccented, unspaced text, and so forth, creating a fair reproduction of what a diplomatic edition is expected to look like.

                                                                                                                                                                                                                                                                                                            A few diplomatic features, such as unusually-shaped characters, partially lost letters at the ends of lines, internal spacing in Imperial inscriptions, are not terribly well handled by these transformation templates. In addition, some communities may feel that a separate diplomatic edition, where different decisions in the transcription are made, would be desirable. This could perhaps be encoded as a <div type="edition" subtype="diplomatic">.

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Diplomatic Transcriptions

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            A diplomatic transcription in epigraphic or papyrological terms is one that records only the characters as they appear on the support, with minimal or no editorial intervention or interpretation. It differs from a drawing in that individual letters are identified, usually to Unicode codepoints, but will often be written in uppercase, without spaces, punctuation or diacritics (unless these are in the source document), and without restoring lacunae or expanding abbreviations.

                                                                                                                                                                                                                                                                                                            It is generally an assumption in the EpiDoc workflow and tooling that a diplomatic transcription can be generated from the underlying XML as an alternative, or parallel, view to the interpretive edition following the normal Leiden Conventions. In the EpiDoc Example Stylesheets changing the parameter $edition-type to "diplomatic" will lead the XSLT to leave abbreviations unresolved, treat supplied elements as gaps, transform text nodes to uppercase, unaccented, unspaced text, and so forth, creating a fair reproduction of what a diplomatic edition is expected to look like.

                                                                                                                                                                                                                                                                                                            A few diplomatic features, such as unusually-shaped characters, partially lost letters at the ends of lines, internal spacing in Imperial inscriptions, are not terribly well handled by these transformation templates. In addition, some communities may feel that a separate diplomatic edition, where different decisions in the transcription are made, would be desirable. This could perhaps be encoded as a <div type="edition" subtype="diplomatic">.

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-editorsnote-pt-br.html b/gl/dev/trans-editorsnote-pt-br.html index 94d4fd7f2..23cb38737 100644 --- a/gl/dev/trans-editorsnote-pt-br.html +++ b/gl/dev/trans-editorsnote-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Nota do Editor

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Uma nota explicativa do editor.

                                                                                                                                                                                                                                                                                                            • TEI definition: note ; EpiDoc-specific - customization: note

                                                                                                                                                                                                                                                                                                            A explicaçãodo editor deve ser colocada dentro de uma tag note.

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.1; Sosin 2011: (!)

                                                                                                                                                                                                                                                                                                            <note>!</note>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            in the temple of the Genius of the
                                                                                                                                                                                                                                                                                                            Colony <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                            <note>a further line is erased</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: in the temple of the Genius of the Colony [·· ? ··]

                                                                                                                                                                                                                                                                                                              (a further line is erased)

                                                                                                                                                                                                                                                                                                            (IRT: 6)
                                                                                                                                                                                                                                                                                                            <note>There is a well-cut picture of a scorpion.</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style:

                                                                                                                                                                                                                                                                                                              (There is a well-cut picture of a scorpion.)

                                                                                                                                                                                                                                                                                                            (InsAph: 8.54)

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Nota do Editor

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            Uma nota explicativa do editor.

                                                                                                                                                                                                                                                                                                            • TEI definition: note ; EpiDoc-specific + customization: note

                                                                                                                                                                                                                                                                                                            A explicaçãodo editor deve ser colocada dentro de uma tag note.

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.1; Sosin 2011: (!)

                                                                                                                                                                                                                                                                                                            <note>!</note>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            in the temple of the Genius of the
                                                                                                                                                                                                                                                                                                            Colony <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                            <note>a further line is erased</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: in the temple of the Genius of the Colony [·· ? ··]

                                                                                                                                                                                                                                                                                                              (a further line is erased)

                                                                                                                                                                                                                                                                                                            (IRT: 6)
                                                                                                                                                                                                                                                                                                            <note>There is a well-cut picture of a scorpion.</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style:

                                                                                                                                                                                                                                                                                                              (There is a well-cut picture of a scorpion.)

                                                                                                                                                                                                                                                                                                            (InsAph: 8.54)

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-editorsnote.html b/gl/dev/trans-editorsnote.html index 7969c47ff..f1014e766 100644 --- a/gl/dev/trans-editorsnote.html +++ b/gl/dev/trans-editorsnote.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Editor's Note

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            An explanatory note by the editor.

                                                                                                                                                                                                                                                                                                            • TEI definition: note ; EpiDoc-specific - customization: note

                                                                                                                                                                                                                                                                                                            The editor's explanation should be place inside a note.

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.1; Sosin 2011: (!)

                                                                                                                                                                                                                                                                                                            <note>!</note>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            in the temple of the Genius of the Colony <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                            <note>a further line is erased</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: in the temple of the Genius of the Colony [·· ? ··]

                                                                                                                                                                                                                                                                                                              (a further line is erased)

                                                                                                                                                                                                                                                                                                            (IRT: 6)
                                                                                                                                                                                                                                                                                                            <note>There is a well-cut picture of a scorpion.</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style:

                                                                                                                                                                                                                                                                                                              (There is a well-cut picture of a scorpion.)

                                                                                                                                                                                                                                                                                                            (InsAph: 8.54)

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Editor's Note

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            An explanatory note by the editor.

                                                                                                                                                                                                                                                                                                            • TEI definition: note ; EpiDoc-specific + customization: note

                                                                                                                                                                                                                                                                                                            The editor's explanation should be place inside a note.

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.1; Sosin 2011: (!)

                                                                                                                                                                                                                                                                                                            <note>!</note>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            in the temple of the Genius of the Colony <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                            <note>a further line is erased</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: in the temple of the Genius of the Colony [·· ? ··]

                                                                                                                                                                                                                                                                                                              (a further line is erased)

                                                                                                                                                                                                                                                                                                            (IRT: 6)
                                                                                                                                                                                                                                                                                                            <note>There is a well-cut picture of a scorpion.</note>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style:

                                                                                                                                                                                                                                                                                                              (There is a well-cut picture of a scorpion.)

                                                                                                                                                                                                                                                                                                            (InsAph: 8.54)

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-ellipsis-pt-br.html b/gl/dev/trans-ellipsis-pt-br.html index a6d56affd..c7ee74cf3 100644 --- a/gl/dev/trans-ellipsis-pt-br.html +++ b/gl/dev/trans-ellipsis-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Palavras Omitidas pelo Editor por Brevidade

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Palavra ou palavras omitidas pelo editor, pela brevidade ou por ênfase, quando discute ou cita um texto.

                                                                                                                                                                                                                                                                                                            • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                            As palavras omitidas devem ser colocadas dentro de um elemento gap, cujo atributo reason deve ter um valor "ellipsis".

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.4; Sosin 2011: ... or [...]

                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ...
                                                                                                                                                                                                                                                                                                            (IRT: 738)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsisquantity="1"
                                                                                                                                                                                                                                                                                                             unit="line">

                                                                                                                                                                                                                                                                                                             <desc>Demotic</desc>
                                                                                                                                                                                                                                                                                                            </gap>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: Demotic 1 line
                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.2.459#1)

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Palavras Omitidas pelo Editor por Brevidade

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            Palavra ou palavras omitidas pelo editor, pela brevidade ou por ênfase, quando discute ou cita um texto.

                                                                                                                                                                                                                                                                                                            • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                            As palavras omitidas devem ser colocadas dentro de um elemento gap, cujo atributo reason deve ter um valor "ellipsis".

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.4; Sosin 2011: ... or [...]

                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ...
                                                                                                                                                                                                                                                                                                            (IRT: 738)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsisquantity="1"
                                                                                                                                                                                                                                                                                                             unit="line">

                                                                                                                                                                                                                                                                                                             <desc>Demotic</desc>
                                                                                                                                                                                                                                                                                                            </gap>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: Demotic 1 line
                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.2.459#1)

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-ellipsis.html b/gl/dev/trans-ellipsis.html index 515f2a9a1..1ece0ff20 100644 --- a/gl/dev/trans-ellipsis.html +++ b/gl/dev/trans-ellipsis.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Words Omitted by Editor for Brevity

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Word or words omitted for the sake of brevity or emphasis by the editor while discussing or quoting a text.

                                                                                                                                                                                                                                                                                                            • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                            The omitted words should be placed inside a gap element whose reason attribute should have a value of "ellipsis".

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.4; Sosin 2011: ... or [...]

                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ...
                                                                                                                                                                                                                                                                                                            (IRT: 738)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsisquantity="1"
                                                                                                                                                                                                                                                                                                             unit="line">

                                                                                                                                                                                                                                                                                                             <desc>Demotic</desc>
                                                                                                                                                                                                                                                                                                            </gap>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: Demotic 1 line
                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.2.459#1)

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Words Omitted by Editor for Brevity

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            Word or words omitted for the sake of brevity or emphasis by the editor while discussing or quoting a text.

                                                                                                                                                                                                                                                                                                            • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                            The omitted words should be placed inside a gap element whose reason attribute should have a value of "ellipsis".

                                                                                                                                                                                                                                                                                                            Panciera 1991 XI.4; Sosin 2011: ... or [...]

                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsis"/>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ...
                                                                                                                                                                                                                                                                                                            (IRT: 738)
                                                                                                                                                                                                                                                                                                            <gap reason="ellipsisquantity="1"
                                                                                                                                                                                                                                                                                                             unit="line">

                                                                                                                                                                                                                                                                                                             <desc>Demotic</desc>
                                                                                                                                                                                                                                                                                                            </gap>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: Demotic 1 line
                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.2.459#1)

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erased-pt-br.html b/gl/dev/trans-erased-pt-br.html index 1066603ed..c7f79a36e 100644 --- a/gl/dev/trans-erased-pt-br.html +++ b/gl/dev/trans-erased-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Texto Apagado, mas Legível

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Caracteres apagados na Antiguidade, mas ainda legíveis (com uma certa clareza) devem ser marcados com o elemento del, cujo atributo rend deve ter o valor "erasure". No caso dos caracteres que não estão claros ou não podem ser compreendidos, deve-se utilizar os elementos orig e unclear, respectivamente.

                                                                                                                                                                                                                                                                                                            Panciera 1991 V.1: [[abc]] or [[ABC]] or [[ạḅc̣]]

                                                                                                                                                                                                                                                                                                            Sosin 2011: ⟦αβγ⟧

                                                                                                                                                                                                                                                                                                            <del rend="erasure">abc</del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦abc⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <orig>abc</orig>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦ABC⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦ạḅc̣⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <orig>gn</orig>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦GN⟧
                                                                                                                                                                                                                                                                                                            (IRT: 149)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">Νέρων<sic n="superfluous">ι</sic>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦Νέρωνι⟧
                                                                                                                                                                                                                                                                                                            (InsAph: 9.14)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <unclear>Ε</unclear>ὐπρεπ<unclear>εία</unclear>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: ⟦Ε̣ὐπρεπε̣ί̣α̣⟧

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                            4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erased.html b/gl/dev/trans-erased.html index b2bc495e6..86d3121bf 100644 --- a/gl/dev/trans-erased.html +++ b/gl/dev/trans-erased.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Erased But Legible Text

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Characters erased in antiquity but still legible (more or less clearly) should be tagged using the del element, whose rend should have a value of "erasure". Where the characters cannot be understood or are unclear, orig and unclear elements should be used respectively.

                                                                                                                                                                                                                                                                                                            Panciera 1991 V.1: [[abc]] or [[ABC]] or [[ạḅc̣]]

                                                                                                                                                                                                                                                                                                            Sosin 2011: ⟦αβγ⟧

                                                                                                                                                                                                                                                                                                            <del rend="erasure">abc</del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦abc⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <orig>abc</orig>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦ABC⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦ạḅc̣⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <orig>gn</orig>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦GN⟧
                                                                                                                                                                                                                                                                                                            (IRT: 149)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">Νέρων<sic n="superfluous">ι</sic>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦Νέρωνι⟧
                                                                                                                                                                                                                                                                                                            (InsAph: 9.14)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <unclear>Ε</unclear>ὐπρεπ<unclear>εία</unclear>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: ⟦Ε̣ὐπρεπε̣ί̣α̣⟧

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                            3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erasedillegible-pt-br.html b/gl/dev/trans-erasedillegible-pt-br.html index ce606cf88..c8006e223 100644 --- a/gl/dev/trans-erasedillegible-pt-br.html +++ b/gl/dev/trans-erasedillegible-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Apagado e Ilegível / Restaurado

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Caracteres que foram apagados na antiguidade e são ilegíveis, ou foram restaurados pelo editor moderno, devem ser marcados com o elemnto del, cujo atributo rend deve ter o valor "erasure". O texto fornecido pelo editor deve ser colocado dentro de um elemento supplied, dentro do elemento del. Nos casos em que o caracter não pode ser compreendico ou não está claro, os elementos orig e unclear, respectivamente, devem ser utilizados.

                                                                                                                                                                                                                                                                                                            Panciera 1991 V.2; Sosin 2011: [[abc]] or [[ABC]] or [[ạḅc̣]]

                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                            </del>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">
                                                                                                                                                                                                                                                                                                              <orig>abc</orig>
                                                                                                                                                                                                                                                                                                             </supplied>
                                                                                                                                                                                                                                                                                                            </del>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">
                                                                                                                                                                                                                                                                                                              <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                             </supplied>
                                                                                                                                                                                                                                                                                                            </del>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">
                                                                                                                                                                                                                                                                                                              <unclear>Ε</unclear>ὐπρεπ<unclear>εία</unclear>
                                                                                                                                                                                                                                                                                                             </supplied>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: ⟦[Ε̣ὐπρεπε̣ί̣α̣]⟧
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">Ale</supplied>xandro
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦[Ale]xandro⟧
                                                                                                                                                                                                                                                                                                            (IRT: 908)

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erasedillegible.html b/gl/dev/trans-erasedillegible.html index f8d8f49af..6a4c89713 100644 --- a/gl/dev/trans-erasedillegible.html +++ b/gl/dev/trans-erasedillegible.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Erased and Illegible / Restored

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Characters which have been erased in antiquity and are illegible, or restored by the modern editor, should be tagged using the del element, whose rend should have a value of "erasure". The text supplied by the editor should be placed within a supplied element inside the del element. Where the characters cannot be understood or are unclear, orig and unclear elements should be used respectively.

                                                                                                                                                                                                                                                                                                            Panciera 1991 V.2; Sosin 2011: [[abc]] or [[ABC]] or [[ạḅc̣]]

                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                            </del>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">
                                                                                                                                                                                                                                                                                                              <orig>abc</orig>
                                                                                                                                                                                                                                                                                                             </supplied>
                                                                                                                                                                                                                                                                                                            </del>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">
                                                                                                                                                                                                                                                                                                              <unclear>abc</unclear>
                                                                                                                                                                                                                                                                                                             </supplied>
                                                                                                                                                                                                                                                                                                            </del>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">
                                                                                                                                                                                                                                                                                                              <unclear>Ε</unclear>ὐπρεπ<unclear>εία</unclear>
                                                                                                                                                                                                                                                                                                             </supplied>
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: ⟦[Ε̣ὐπρεπε̣ί̣α̣]⟧
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <supplied reason="lost">Ale</supplied>xandro
                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦[Ale]xandro⟧
                                                                                                                                                                                                                                                                                                            (IRT: 908)

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erasedlost-pt-br.html b/gl/dev/trans-erasedlost-pt-br.html index 5cb0b1b6f..55483c83a 100644 --- a/gl/dev/trans-erasedlost-pt-br.html +++ b/gl/dev/trans-erasedlost-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Apagado e Perdido

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Texto deliberadamente apagado na antiguidade, sem que haja traços remanescentes dele na pedra ou no papiro, e que não pode ser restaurado pelo editor.

                                                                                                                                                                                                                                                                                                            Duas tags TEI diferentes são utilizadas para indicar texto apagado e não restaurado: o elemento del indica que o editor afirma que o texto foi propositadamente apagado por uma mão da antiguidade (em vez de, digamos, danificado por acidente, pelo tempo ou por atividade moderna); o elemento gap indica mais objetivamente que não há mais evidência de qualquer texto ou decoração que estivesse originalmente inscrito naquela superfície.

                                                                                                                                                                                                                                                                                                            Caracteres apoagados na antiguidade e completamente perdidos devem, portanto, ser marcados com o elemento del (se for apropriado, com o atributo rend e o valor mais provável "erasure"). Um elemento gap deve ser posicionado dentro de del, para indicar que o texto apagado não foi restaurado, e receberá atributos reason, unit, e quantity ou extent, como é usual.

                                                                                                                                                                                                                                                                                                            Panciera 1991 V.3: [[[...]]] or [[[c.7]]] or [[[---]]]

                                                                                                                                                                                                                                                                                                            Sosin 2011: ⟦[ - ca.? - ]⟧

                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                              unit="character"/>

                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦ [...] ⟧
                                                                                                                                                                                                                                                                                                            • London style: ⟦ [···] ⟧
                                                                                                                                                                                                                                                                                                            • Duke Databank style: ⟦ [  ̣  ̣  ̣] ⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <gap reason="lostquantity="4"
                                                                                                                                                                                                                                                                                                              unit="character"/>

                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦ [·· 4··] ⟧
                                                                                                                                                                                                                                                                                                            (IRT: 445)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                              unit="character"/>

                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style:  ̣  ̣  ̣
                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.7.1621)

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                            3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                            4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erasedlost.html b/gl/dev/trans-erasedlost.html index b11d20c1f..2d0078925 100644 --- a/gl/dev/trans-erasedlost.html +++ b/gl/dev/trans-erasedlost.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Erased and Lost

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Text deliberately erased in antiquity of which no trace now remains on the stone or papyrus, and which cannot be restored by the editor.

                                                                                                                                                                                                                                                                                                            Two different TEI tags are used to indicate erased and un-restored text: the del element indicates the editor's assertion than the text was purposefully erased by an ancient hand (rather than, say, damaged by accident, weather or modern activity); the gap element indicates more objectively that whatever text or other decoration was originally inscribed on this surface is no longer evident at all.

                                                                                                                                                                                                                                                                                                            Characters erased in antiquity and completely lost should therefore be tagged using the del element (if appropriate assigning to the rend attribue a value, most likely "erasure"). A gap element should be placed inside the del, to indicate that the erased text is not restored, and will be given a reason, unit, and either quantity or extent attributes, as usual.

                                                                                                                                                                                                                                                                                                            Panciera 1991 V.3: [[[...]]] or [[[c.7]]] or [[[---]]]

                                                                                                                                                                                                                                                                                                            Sosin 2011: ⟦[ - ca.? - ]⟧

                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                              unit="character"/>

                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: ⟦[...]⟧
                                                                                                                                                                                                                                                                                                            • London style: ⟦[···]⟧
                                                                                                                                                                                                                                                                                                            • Duke Databank style: ⟦[  ̣  ̣  ̣]⟧
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <gap reason="lostquantity="4"
                                                                                                                                                                                                                                                                                                              unit="character"/>

                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • London style: ⟦[·· 4··]⟧
                                                                                                                                                                                                                                                                                                            (IRT: 445)
                                                                                                                                                                                                                                                                                                            <del rend="erasure">
                                                                                                                                                                                                                                                                                                             <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                              unit="character"/>

                                                                                                                                                                                                                                                                                                            </del>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style:  ̣  ̣  ̣
                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.7.1621)

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                            3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erroneoussubstitution-pt-br.html b/gl/dev/trans-erroneoussubstitution-pt-br.html index 5202205ef..92537b5af 100644 --- a/gl/dev/trans-erroneoussubstitution-pt-br.html +++ b/gl/dev/trans-erroneoussubstitution-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Correção de Caracteres Errôneos

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Caracteres escritos de forma errada ou transpostos na fonte original, corrigidos pelo editor. Veja também a discussão em http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COEDCOR.

                                                                                                                                                                                                                                                                                                            Panciera 1991 9.3: ⌈abc⌉

                                                                                                                                                                                                                                                                                                            SEG; Sosin 2011: <abc>

                                                                                                                                                                                                                                                                                                            <choice>
                                                                                                                                                                                                                                                                                                             <corr>abc</corr>
                                                                                                                                                                                                                                                                                                             <sic>def</sic>
                                                                                                                                                                                                                                                                                                            </choice>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            s<choice>
                                                                                                                                                                                                                                                                                                             <sic>y</sic>
                                                                                                                                                                                                                                                                                                             <corr>u</corr>
                                                                                                                                                                                                                                                                                                            </choice>b

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: s ⸢u⸣ b
                                                                                                                                                                                                                                                                                                            • SEG style: s <u> b
                                                                                                                                                                                                                                                                                                            • London style: s ⸢u⸣ b
                                                                                                                                                                                                                                                                                                            • EDH style: s u b
                                                                                                                                                                                                                                                                                                            (IRT: 207)
                                                                                                                                                                                                                                                                                                            <choice>
                                                                                                                                                                                                                                                                                                             <corr>ἀμπελικοῦ</corr>
                                                                                                                                                                                                                                                                                                             <sic>ἀμπελικὸν</sic>
                                                                                                                                                                                                                                                                                                            </choice>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: ἀμπελικὸν

                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                            2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-erroneoussubstitution.html b/gl/dev/trans-erroneoussubstitution.html index 89896dbb0..da1c953e9 100644 --- a/gl/dev/trans-erroneoussubstitution.html +++ b/gl/dev/trans-erroneoussubstitution.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Erroneous substitution

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Characters written wrongly or transposed in the original source, corrected by the editor. See also discussion in http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COEDCOR.

                                                                                                                                                                                                                                                                                                            Panciera 1991 9.3: ⌈abc⌉

                                                                                                                                                                                                                                                                                                            SEG; Sosin 2011: <abc>

                                                                                                                                                                                                                                                                                                            <choice>
                                                                                                                                                                                                                                                                                                             <corr>abc</corr>
                                                                                                                                                                                                                                                                                                             <sic>def</sic>
                                                                                                                                                                                                                                                                                                            </choice>
                                                                                                                                                                                                                                                                                                            (Panciera)
                                                                                                                                                                                                                                                                                                            s<choice>
                                                                                                                                                                                                                                                                                                             <sic>y</sic>
                                                                                                                                                                                                                                                                                                             <corr>u</corr>
                                                                                                                                                                                                                                                                                                            </choice>b

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: s⸢u⸣b
                                                                                                                                                                                                                                                                                                            • SEG style: s<u>b
                                                                                                                                                                                                                                                                                                            • London style: s⸢u⸣b
                                                                                                                                                                                                                                                                                                            • EDH style: sub
                                                                                                                                                                                                                                                                                                            (IRT: 207)
                                                                                                                                                                                                                                                                                                            <choice>
                                                                                                                                                                                                                                                                                                             <corr>ἀμπελικοῦ</corr>
                                                                                                                                                                                                                                                                                                             <sic>ἀμπελικὸν</sic>
                                                                                                                                                                                                                                                                                                            </choice>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Duke Databank style: ἀμπελικὸν

                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-foreignellipsis-pt-br.html b/gl/dev/trans-foreignellipsis-pt-br.html index dbc0090e7..ddf920d8a 100644 --- a/gl/dev/trans-foreignellipsis-pt-br.html +++ b/gl/dev/trans-foreignellipsis-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Texto Estrangeiro Omitido da Edição

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Texto Estrangeiro Omitido da Edição

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-foreignellipsis.html b/gl/dev/trans-foreignellipsis.html index 707d0b4b6..d7e89d1da 100644 --- a/gl/dev/trans-foreignellipsis.html +++ b/gl/dev/trans-foreignellipsis.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Foreign Ellipsis

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                            Foreign Ellipsis

                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-foreigntext-pt-br.html b/gl/dev/trans-foreigntext-pt-br.html index 8e5af5cef..ab37c7f73 100644 --- a/gl/dev/trans-foreigntext-pt-br.html +++ b/gl/dev/trans-foreigntext-pt-br.html @@ -21,13 +21,13 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                            Textos em vários idiomas

                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                            Caso onde palavras estrangeiras isoladas aparecem em um texto escrito em um únicvo idioma, ou onde um texto tem partes significativas em duas ou mais línguas (bilíngues, glossas, etc.).

                                                                                                                                                                                                                                                                                                            • TEI definition: ab ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                              Textos em vários idiomas

                                                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                                                              Caso onde palavras estrangeiras isoladas aparecem em um texto escrito em um únicvo idioma, ou onde um texto tem partes significativas em duas ou mais línguas (bilíngues, glossas, etc.).

                                                                                                                                                                                                                                                                                                              • TEI definition: ab ; EpiDoc-specific customization: ab
                                                                                                                                                                                                                                                                                                              • TEI definition: div ; EpiDoc-specific customization: div
                                                                                                                                                                                                                                                                                                              • TEI definition: foreign ; EpiDoc-specific customization: foreign
                                                                                                                                                                                                                                                                                                              • TEI definition: gloss ; EpiDoc-specific customization: gloss
                                                                                                                                                                                                                                                                                                              • TEI definition: seg ; EpiDoc-specific customization: seg
                                                                                                                                                                                                                                                                                                              • TEI definition: term ; EpiDoc-specific - customization: term

                                                                                                                                                                                                                                                                                                              1. Palavras estrangeiras

                                                                                                                                                                                                                                                                                                              O elemento foreign identifica uma palavra ou frase como pertencente a uma linguagem diversa do texto que a cerca. Geralmente é útil aplicar o atributo xml:lang com um código de idioma (veja Languages and Scripts) para identificar a língua da palavra ou frase inserida.

                                                                                                                                                                                                                                                                                                              For the lost line 6 Aurigemma,
                                                                                                                                                                                                                                                                                                              loc. cit., suggests <foreign xml:lang="la">matris castrorum</foreign>

                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                              • London style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                              (IRT: 21)

                                                                                                                                                                                                                                                                                                              2. Divisões significativas

                                                                                                                                                                                                                                                                                                              Quando há passagens de um bom tamanho, divididas de modo significativo, é aconselhável utilizar a marcação <div type="textpart"> com um xml:lang em cada passagem, em vez de declarar uma única língua padrão no <div type="edition">.

                                                                                                                                                                                                                                                                                                              <div type="editionxml:space="preserve"> + customization: term

                                                                                                                                                                                                                                                                                                            1. Palavras estrangeiras

                                                                                                                                                                                                                                                                                                            O elemento foreign identifica uma palavra ou frase como pertencente a uma linguagem diversa do texto que a cerca. Geralmente é útil aplicar o atributo xml:lang com um código de idioma (veja Languages and Scripts) para identificar a língua da palavra ou frase inserida.

                                                                                                                                                                                                                                                                                                            For the lost line 6 Aurigemma,
                                                                                                                                                                                                                                                                                                            loc. cit., suggests <foreign xml:lang="la">matris castrorum</foreign>

                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                            • London style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                            (IRT: 21)

                                                                                                                                                                                                                                                                                                            2. Divisões significativas

                                                                                                                                                                                                                                                                                                            Quando há passagens de um bom tamanho, divididas de modo significativo, é aconselhável utilizar a marcação <div type="textpart"> com um xml:lang em cada passagem, em vez de declarar uma única língua padrão no <div type="edition">.

                                                                                                                                                                                                                                                                                                            <div type="editionxml:space="preserve">                 <div type="textpartxml:lang="lan="a">                     <ab><lb/>Caecilius Diodorus <gap reason="lost"/>                         <lb/>Caesaris delubrum a<gap reason="lost"/></ab> @@ -36,9 +36,9 @@                     <ab><lb/>Καικίλιος Διόδωρος ἅμα <gap reason="lost"/>                        <lb/>ἐκ τῶν ἰδίων εὔξατο θ<gap reason="lost"/></ab>                 </div> -            
                                                                                                                                                                                                                                                                                                            </div>
                                                                                                                                                                                                                                                                                                            (IRT: 481)

                                                                                                                                                                                                                                                                                                            3. Blocos arbitrários

                                                                                                                                                                                                                                                                                                            Aonde aparecem blocos multilineares de texto contendo dois ou mais idiomas, mas estes blocos não são considerados significativos ou parte da citação do documento, é suficiente utilizar em cada bloco a tag ab, e a ela o atributo xml:lang pode ser adicionado.

                                                                                                                                                                                                                                                                                                            <div type="editionxml:space="preserve"> +            
                                                                                                                                                                                                                                                                                                            </div>
                                                                                                                                                                                                                                                                                                            (IRT: 481)

                                                                                                                                                                                                                                                                                                            3. Blocos arbitrários

                                                                                                                                                                                                                                                                                                            Aonde aparecem blocos multilineares de texto contendo dois ou mais idiomas, mas estes blocos não são considerados significativos ou parte da citação do documento, é suficiente utilizar em cada bloco a tag ab, e a ela o atributo xml:lang pode ser adicionado.

                                                                                                                                                                                                                                                                                                            <div type="editionxml:space="preserve">                 <ab xml:lang="la"><lb/><gap reason="lost"/>dium murum supra<gap reason="lost"/>                    <lb/><gap reason="lost"/>tribunicia potestate<gap reason="lost"/></ab>                 <ab xml:lang="grc"><lb/><gap reason="lost"/>υς μόνος τὸν ναὸν <gap reason="lost"/>                    <lb/><gap reason="lost"/>δεων αὐτοκράτορ<gap reason="lost"/></ab> -            
                                                                                                                                                                                                                                                                                                            </div>
                                                                                                                                                                                                                                                                                                            (IRT: 481)

                                                                                                                                                                                                                                                                                                            4. Glossas e dicionários

                                                                                                                                                                                                                                                                                                            Um texto composto de palavras e frases em um idioma, com glossas ou traduções em um ou mais idiomas diferentes, pode ser marcado com uma série de elementos term e gloss, ao longo da linha, cada uym carregando seu xml:lang que especifica o idioma da frase curta. De modo alternativo, se a específica e rica semântica de term e gloss tiver de ser evitada, seg pode ser utilizado para marcar pedaços arbitrários de texto de como sendo de um idioma ou outro.

                                                                                                                                                                                                                                                                                                            <ab>
                                                                                                                                                                                                                                                                                                             <term xml:id="seq1xml:lang="san-Brah">mahībhujām·</term>
                                                                                                                                                                                                                                                                                                             <gloss target="#seq1xml:lang="pyx">tg'am·ḥ d'iṁ tiṁ pmir·ḥ CV naḥ</gloss>
                                                                                                                                                                                                                                                                                                             <term xml:id="seq2xml:lang="san-Brah">°unnata</term>
                                                                                                                                                                                                                                                                                                             <gloss target="#seq2xml:lang="pyx">kd'ir·ṁ tra v'a kv'iṁ</gloss>
                                                                                                                                                                                                                                                                                                             <term xml:id="seq3xml:lang="san-Brah">porusa</term>
                                                                                                                                                                                                                                                                                                             <gloss target="#seq3xml:lang="pyx">°o saṁḥ pir·ṁ tg'a</gloss>
                                                                                                                                                                                                                                                                                                            </ab>

                                                                                                                                                                                                                                                                                                            Neste exemplo, do projeto Corpus of Pyu Inscriptions, os atributos xml:id e corresp são utilizados para conectar as glossas Pyu com os termos em Sânscrito que sejam sua tradução ou equivalente.

                                                                                                                                                                                                                                                                                                            See also:

                                                                                                                                                                                                                                                                                                            Other pages describing <ab>:

                                                                                                                                                                                                                                                                                                              Other pages describing <div>:

                                                                                                                                                                                                                                                                                                              Other pages describing <foreign>:

                                                                                                                                                                                                                                                                                                              Other pages describing <gloss>:

                                                                                                                                                                                                                                                                                                                Other pages describing <seg>:

                                                                                                                                                                                                                                                                                                                Other pages describing <term>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Arlo Griffiths, contribuidor
                                                                                                                                                                                                                                                                                                                  4. Marc Miyaki, contribuidor
                                                                                                                                                                                                                                                                                                                  5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +            
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  (IRT: 481)

                                                                                                                                                                                                                                                                                                                  4. Glossas e dicionários

                                                                                                                                                                                                                                                                                                                  Um texto composto de palavras e frases em um idioma, com glossas ou traduções em um ou mais idiomas diferentes, pode ser marcado com uma série de elementos term e gloss, ao longo da linha, cada uym carregando seu xml:lang que especifica o idioma da frase curta. De modo alternativo, se a específica e rica semântica de term e gloss tiver de ser evitada, seg pode ser utilizado para marcar pedaços arbitrários de texto de como sendo de um idioma ou outro.

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq1xml:lang="san-Brah">mahībhujām·</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq1xml:lang="pyx">tg'am·ḥ d'iṁ tiṁ pmir·ḥ CV naḥ</gloss>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq2xml:lang="san-Brah">°unnata</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq2xml:lang="pyx">kd'ir·ṁ tra v'a kv'iṁ</gloss>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq3xml:lang="san-Brah">porusa</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq3xml:lang="pyx">°o saṁḥ pir·ṁ tg'a</gloss>
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Neste exemplo, do projeto Corpus of Pyu Inscriptions, os atributos xml:id e corresp são utilizados para conectar as glossas Pyu com os termos em Sânscrito que sejam sua tradução ou equivalente.

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <ab>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <div>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <foreign>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <gloss>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <seg>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <term>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Arlo Griffiths, contribuidor
                                                                                                                                                                                                                                                                                                                  4. Marc Miyaki, contribuidor
                                                                                                                                                                                                                                                                                                                  5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-foreigntext.html b/gl/dev/trans-foreigntext.html index 2b311ea3b..ada2008ae 100644 --- a/gl/dev/trans-foreigntext.html +++ b/gl/dev/trans-foreigntext.html @@ -21,13 +21,13 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Multi-language texts

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Where isolated foreign words appear in a text otherwise in a single language, or when a text has significant parts in two or more languages (bilinguals, glosses, etc.).

                                                                                                                                                                                                                                                                                                                  • TEI definition: ab ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                    Multi-language texts

                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                    Where isolated foreign words appear in a text otherwise in a single language, or when a text has significant parts in two or more languages (bilinguals, glosses, etc.).

                                                                                                                                                                                                                                                                                                                    • TEI definition: ab ; EpiDoc-specific customization: ab
                                                                                                                                                                                                                                                                                                                    • TEI definition: div ; EpiDoc-specific customization: div
                                                                                                                                                                                                                                                                                                                    • TEI definition: foreign ; EpiDoc-specific customization: foreign
                                                                                                                                                                                                                                                                                                                    • TEI definition: gloss ; EpiDoc-specific customization: gloss
                                                                                                                                                                                                                                                                                                                    • TEI definition: seg ; EpiDoc-specific customization: seg
                                                                                                                                                                                                                                                                                                                    • TEI definition: term ; EpiDoc-specific - customization: term

                                                                                                                                                                                                                                                                                                                    1. Foreign words or phrases

                                                                                                                                                                                                                                                                                                                    The foreign element identifies a word or phrase as belonging to a language other than that of the surrounding text, either in the inscription text or in other parts of the edition. It is usually useful to apply the attribute xml:lang with a language code (see Languages and Scripts) to identify the language of the embedded word.

                                                                                                                                                                                                                                                                                                                    For the lost line 6 Aurigemma, loc. cit., suggests <foreign xml:lang="la">matris castrorum</foreign>

                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                                    • London style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                                    (IRT: 21)

                                                                                                                                                                                                                                                                                                                    2. Multilingual text sections

                                                                                                                                                                                                                                                                                                                    Where significantly sized passages of the inscription text are in different languages, it is advisable to choose a single language as the default one and to declare it with an xml:lang attribute on the <div type="edition">, and then, for any other sections in a different language, to declare it by adding an xml:lang attribute to the block-level containers of that text (e.g. ab, lg, seg, or <div type="textpart"> when the language shift coincides with a semantic and physical break).

                                                                                                                                                                                                                                                                                                                    <div type="editionxml:space="preserve"
                                                                                                                                                                                                                                                                                                                     xml:lang="la">
                                                                                                                                                                                                                                                                                                                    + customization: term

                                                                                                                                                                                                                                                                                                                  1. Foreign words or phrases

                                                                                                                                                                                                                                                                                                                  The foreign element identifies a word or phrase as belonging to a language other than that of the surrounding text, either in the inscription text or in other parts of the edition. It is usually useful to apply the attribute xml:lang with a language code (see Languages and Scripts) to identify the language of the embedded word.

                                                                                                                                                                                                                                                                                                                  For the lost line 6 Aurigemma, loc. cit., suggests <foreign xml:lang="la">matris castrorum</foreign>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                                  • London style: For the lost line 6 Aurigemma, loc. cit., suggests matris castrorum
                                                                                                                                                                                                                                                                                                                  (IRT: 21)

                                                                                                                                                                                                                                                                                                                  2. Multilingual text sections

                                                                                                                                                                                                                                                                                                                  Where significantly sized passages of the inscription text are in different languages, it is advisable to choose a single language as the default one and to declare it with an xml:lang attribute on the <div type="edition">, and then, for any other sections in a different language, to declare it by adding an xml:lang attribute to the block-level containers of that text (e.g. ab, lg, seg, or <div type="textpart"> when the language shift coincides with a semantic and physical break).

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:space="preserve"
                                                                                                                                                                                                                                                                                                                   xml:lang="la">
                                                                                                                                                                                                                                                                                                                                  <ab>                     <lb/><gap reason="lost"/>dium murum supra<gap reason="lost"/>                     <lb/><gap reason="lost"/>tribunicia potestate<gap reason="lost"/> @@ -36,7 +36,7 @@                     <lb/><gap reason="lost"/>υς μόνος τὸν ναὸν <gap reason="lost"/>                     <lb/><gap reason="lost"/>δεων αὐτοκράτορ<gap reason="lost"/>                 </ab> -            
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  (IRT: 481)
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:space="preserve"
                                                                                                                                                                                                                                                                                                                   xml:lang="la">
                                                                                                                                                                                                                                                                                                                  +            
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  (IRT: 481)
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:space="preserve"
                                                                                                                                                                                                                                                                                                                   xml:lang="la">
                                                                                                                                                                                                                                                                                                                                  <div type="textpartn="a">                     <ab>                         <lb/>Caecilius Diodorus <gap reason="lost"/> @@ -49,7 +49,7 @@                         <lb/>ἐκ τῶν ἰδίων εὔξατο θ<gap reason="lost"/>                     </ab>                 </div> -            
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  (IRT: 481)
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:space="preserve"
                                                                                                                                                                                                                                                                                                                   xml:lang="grc">
                                                                                                                                                                                                                                                                                                                  +            
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  (IRT: 481)
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:space="preserve"
                                                                                                                                                                                                                                                                                                                   xml:lang="grc">
                                                                                                                                                                                                                                                                                                                                  <div type="textpartn="a">                     <ab>                         <milestone unit="facen="a"/><lb n="1"/>Greek verse @@ -66,4 +66,4 @@                         <lb n="2"/>Latin prose                     </ab>                 </div> -            
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, inscription text in Sanskrit, with a chunk in Telugu:

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="1"/>svasti śrīmatāṁ sakala-bhuvana-saṁstūyamāna-mānavya-sagotrānāṁ
                                                                                                                                                                                                                                                                                                                   <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                   </ab>
                                                                                                                                                                                                                                                                                                                  <!--text continues in Sanskrit, then switches to Telugu-->
                                                                                                                                                                                                                                                                                                                   <ab xml:lang="tel">
                                                                                                                                                                                                                                                                                                                    <lb n="29"/>puṭṭi-nirugu saveraṁ Iruvadinālgu vuṭla-ni<lb n="30break="no"/>ṇḍṟāyam padu-gaṇḍu padeḻ dumu tamulaṁmula-tūmeṇḍu
                                                                                                                                                                                                                                                                                                                   </ab>
                                                                                                                                                                                                                                                                                                                  <!--switches back to Sanskrit-->
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="30"/>Asyopari na
                                                                                                                                                                                                                                                                                                                   <lb n="31"/>kenacid bā<space type="binding-hole"/>dhā karttavyā yaḥ karoti sa paṁca-mahā-pātaka-saṁyu<lb n="32break="no"/>kto bhavati…
                                                                                                                                                                                                                                                                                                                   </ab>
                                                                                                                                                                                                                                                                                                                  <!--text continues in Sanskrit-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, the text is inscribed on two separate doorjambs, continuing from the bottom of one to the top of the other. The inscription begins with a series of verses in Sanskrit, followed by Khmer prose (starting at some point on the second doorjamb):

                                                                                                                                                                                                                                                                                                                  <div type="edition"
                                                                                                                                                                                                                                                                                                                   xml:lang="x-oldkhmer-Latn">

                                                                                                                                                                                                                                                                                                                   <lg n="1met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                    xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <milestone unit="itemn="S"/>
                                                                                                                                                                                                                                                                                                                     <label xml:lang="en">Southern Doorjamb</label>
                                                                                                                                                                                                                                                                                                                     <lb n="S1"/>jejīyatāṁ vraja <seg met="-+--+-+=">
                                                                                                                                                                                                                                                                                                                      <gap reason="lostquantity="8"
                                                                                                                                                                                                                                                                                                                       unit="character"/>

                                                                                                                                                                                                                                                                                                                     </seg>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                   <lg n="17met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                    xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <milestone unit="itemn="N"/>
                                                                                                                                                                                                                                                                                                                     <label xml:lang="en">Northern Doorjamb</label>
                                                                                                                                                                                                                                                                                                                     <lb n="N1"/>Agre-saraḥ prathita-puṇyavatāṁ sva-puṇyaiś</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here, then a prose section in Khmer-->
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="N17"/>ta duk· śloka neḥ mratāñ· śrī Indrapaṇ<orig>d</orig>ita</ab>
                                                                                                                                                                                                                                                                                                                  <!--more <ab>s here-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  3. Glosses and dictionaries

                                                                                                                                                                                                                                                                                                                  A text that is made up of words or phrases in one language, and glosses or translations in one or more others, may be tagged with a series of term and gloss elements, inline, and each bearing the xml:lang specifying the language of the short phrase. Alternatively, if the specific and rich semantics of term and gloss are to be avoided, seg may be used to mark arbitrary spans of text as being in one language or another.

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq1xml:lang="san-Brah">mahībhujām·</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq1xml:lang="pyx">tg'am·ḥ d'iṁ tiṁ pmir·ḥ CV naḥ</gloss>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq2xml:lang="san-Brah">°unnata</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq2xml:lang="pyx">kd'ir·ṁ tra v'a kv'iṁ</gloss>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq3xml:lang="san-Brah">porusa</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq3xml:lang="pyx">°o saṁḥ pir·ṁ tg'a</gloss>
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  In this example, from the Corpus of Pyu Inscriptions project, xml:id and corresp attributes are used to link the Pyu glosses with the Sanskrit terms of which each is a translation or equivalent.

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Arlo Griffiths, contributor
                                                                                                                                                                                                                                                                                                                  4. Marc Miyaki, contributor
                                                                                                                                                                                                                                                                                                                  5. Irene Vagionakis, contributor

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +            
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, inscription text in Sanskrit, with a chunk in Telugu:

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="1"/>svasti śrīmatāṁ sakala-bhuvana-saṁstūyamāna-mānavya-sagotrānāṁ
                                                                                                                                                                                                                                                                                                                   <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                   </ab>
                                                                                                                                                                                                                                                                                                                  <!--text continues in Sanskrit, then switches to Telugu-->
                                                                                                                                                                                                                                                                                                                   <ab xml:lang="tel">
                                                                                                                                                                                                                                                                                                                    <lb n="29"/>puṭṭi-nirugu saveraṁ Iruvadinālgu vuṭla-ni<lb n="30break="no"/>ṇḍṟāyam padu-gaṇḍu padeḻ dumu tamulaṁmula-tūmeṇḍu
                                                                                                                                                                                                                                                                                                                   </ab>
                                                                                                                                                                                                                                                                                                                  <!--switches back to Sanskrit-->
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="30"/>Asyopari na
                                                                                                                                                                                                                                                                                                                   <lb n="31"/>kenacid bā<space type="binding-hole"/>dhā karttavyā yaḥ karoti sa paṁca-mahā-pātaka-saṁyu<lb n="32break="no"/>kto bhavati…
                                                                                                                                                                                                                                                                                                                   </ab>
                                                                                                                                                                                                                                                                                                                  <!--text continues in Sanskrit-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, the text is inscribed on two separate doorjambs, continuing from the bottom of one to the top of the other. The inscription begins with a series of verses in Sanskrit, followed by Khmer prose (starting at some point on the second doorjamb):

                                                                                                                                                                                                                                                                                                                  <div type="edition"
                                                                                                                                                                                                                                                                                                                   xml:lang="x-oldkhmer-Latn">

                                                                                                                                                                                                                                                                                                                   <lg n="1met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                    xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <milestone unit="itemn="S"/>
                                                                                                                                                                                                                                                                                                                     <label xml:lang="en">Southern Doorjamb</label>
                                                                                                                                                                                                                                                                                                                     <lb n="S1"/>jejīyatāṁ vraja <seg met="-+--+-+=">
                                                                                                                                                                                                                                                                                                                      <gap reason="lostquantity="8"
                                                                                                                                                                                                                                                                                                                       unit="character"/>

                                                                                                                                                                                                                                                                                                                     </seg>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                   <lg n="17met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                    xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <milestone unit="itemn="N"/>
                                                                                                                                                                                                                                                                                                                     <label xml:lang="en">Northern Doorjamb</label>
                                                                                                                                                                                                                                                                                                                     <lb n="N1"/>Agre-saraḥ prathita-puṇyavatāṁ sva-puṇyaiś</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here, then a prose section in Khmer-->
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="N17"/>ta duk· śloka neḥ mratāñ· śrī Indrapaṇ<orig>d</orig>ita</ab>
                                                                                                                                                                                                                                                                                                                  <!--more <ab>s here-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  3. Glosses and dictionaries

                                                                                                                                                                                                                                                                                                                  A text that is made up of words or phrases in one language, and glosses or translations in one or more others, may be tagged with a series of term and gloss elements, inline, and each bearing the xml:lang specifying the language of the short phrase. Alternatively, if the specific and rich semantics of term and gloss are to be avoided, seg may be used to mark arbitrary spans of text as being in one language or another.

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq1xml:lang="san-Brah">mahībhujām·</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq1xml:lang="pyx">tg'am·ḥ d'iṁ tiṁ pmir·ḥ CV naḥ</gloss>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq2xml:lang="san-Brah">°unnata</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq2xml:lang="pyx">kd'ir·ṁ tra v'a kv'iṁ</gloss>
                                                                                                                                                                                                                                                                                                                   <term xml:id="seq3xml:lang="san-Brah">porusa</term>
                                                                                                                                                                                                                                                                                                                   <gloss target="#seq3xml:lang="pyx">°o saṁḥ pir·ṁ tg'a</gloss>
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  In this example, from the Corpus of Pyu Inscriptions project, xml:id and corresp attributes are used to link the Pyu glosses with the Sanskrit terms of which each is a translation or equivalent.

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <ab>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <div>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <foreign>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <gloss>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <seg>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <term>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Arlo Griffiths, contributor
                                                                                                                                                                                                                                                                                                                  4. Marc Miyaki, contributor
                                                                                                                                                                                                                                                                                                                  5. Irene Vagionakis, contributor

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-fractionknown-pt-br.html b/gl/dev/trans-fractionknown-pt-br.html index 13f172cfe..83e4cf0db 100644 --- a/gl/dev/trans-fractionknown-pt-br.html +++ b/gl/dev/trans-fractionknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Frações de Valor Conhecido

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                  Cada num deve receber um value contendo a fração. Quando a fração é conhecida, não há necessidade de fornecer um atributo type.

                                                                                                                                                                                                                                                                                                                  Sosin 2011: λβ

                                                                                                                                                                                                                                                                                                                  Sosin 2011: 𐅵

                                                                                                                                                                                                                                                                                                                  <num value="1/32">λβ</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: λβ
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: λβ
                                                                                                                                                                                                                                                                                                                  • London style: λβ
                                                                                                                                                                                                                                                                                                                  (Sosin)
                                                                                                                                                                                                                                                                                                                  <num value="1/2">𐅵</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: 𐅵
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: 𐅵
                                                                                                                                                                                                                                                                                                                  (Sosin)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Frações de Valor Conhecido

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                  Cada num deve receber um value contendo a fração. Quando a fração é conhecida, não há necessidade de fornecer um atributo type.

                                                                                                                                                                                                                                                                                                                  Sosin 2011: λβ

                                                                                                                                                                                                                                                                                                                  Sosin 2011: 𐅵

                                                                                                                                                                                                                                                                                                                  <num value="1/32">λβ</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: λβ
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: λβ
                                                                                                                                                                                                                                                                                                                  • London style: λβ
                                                                                                                                                                                                                                                                                                                  (Sosin)
                                                                                                                                                                                                                                                                                                                  <num value="1/2">𐅵</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: 𐅵
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: 𐅵
                                                                                                                                                                                                                                                                                                                  (Sosin)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-fractionknown.html b/gl/dev/trans-fractionknown.html index 75f386a28..c7400fb15 100644 --- a/gl/dev/trans-fractionknown.html +++ b/gl/dev/trans-fractionknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Fractions of Known Value

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                  Each num should be given a value containing the fraction. Where the fraction is known, there is no need to provide a type.

                                                                                                                                                                                                                                                                                                                  Sosin 2011: λβ

                                                                                                                                                                                                                                                                                                                  Sosin 2011: 𐅵

                                                                                                                                                                                                                                                                                                                  <num value="1/32">λβ</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: λβ
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: λβ
                                                                                                                                                                                                                                                                                                                  • London style: λβ
                                                                                                                                                                                                                                                                                                                  (Sosin)
                                                                                                                                                                                                                                                                                                                  <num value="1/2">𐅵</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: 𐅵
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: 𐅵
                                                                                                                                                                                                                                                                                                                  (Sosin)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Fractions of Known Value

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                  Each num should be given a value containing the fraction. Where the fraction is known, there is no need to provide a type.

                                                                                                                                                                                                                                                                                                                  Sosin 2011: λβ

                                                                                                                                                                                                                                                                                                                  Sosin 2011: 𐅵

                                                                                                                                                                                                                                                                                                                  <num value="1/32">λβ</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: λβ
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: λβ
                                                                                                                                                                                                                                                                                                                  • London style: λβ
                                                                                                                                                                                                                                                                                                                  (Sosin)
                                                                                                                                                                                                                                                                                                                  <num value="1/2">𐅵</num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: 𐅵
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: 𐅵
                                                                                                                                                                                                                                                                                                                  (Sosin)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-fractionunknown-pt-br.html b/gl/dev/trans-fractionunknown-pt-br.html index dda96868b..3269951f5 100644 --- a/gl/dev/trans-fractionunknown-pt-br.html +++ b/gl/dev/trans-fractionunknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Frações de Valor Desconhecido

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                  A fração deve ser colocada dentro de uma tag num, mas, quando seu valor é desconhecido, não se pode dar um atributo value. A tag deve receber um atributo type com valor "fraction".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <num type="fraction">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="2atMost="4"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Frações de Valor Desconhecido

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                  A fração deve ser colocada dentro de uma tag num, mas, quando seu valor é desconhecido, não se pode dar um atributo value. A tag deve receber um atributo type com valor "fraction".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <num type="fraction">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="2atMost="4"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-fractionunknown.html b/gl/dev/trans-fractionunknown.html index d6aa41b67..c7ea1ee65 100644 --- a/gl/dev/trans-fractionunknown.html +++ b/gl/dev/trans-fractionunknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Fractions of Unknown Value

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                  The fraction should be placed inside a num, but where its value is unknown, no value can be given. It should be given a type of "fraction".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <num type="fraction">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="2atMost="4"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Fractions of Unknown Value

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                  The fraction should be placed inside a num, but where its value is unknown, no value can be given. It should be given a type of "fraction".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <num type="fraction">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="2atMost="4"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-handshift-pt-br.html b/gl/dev/trans-handshift-pt-br.html index 3ea8ac389..7e0410340 100644 --- a/gl/dev/trans-handshift-pt-br.html +++ b/gl/dev/trans-handshift-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Mudança de escriba ou de mão

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Marca o início de uma sequência de texto escrita por nova mão ou o início de um trecho de escriba.

                                                                                                                                                                                                                                                                                                                  Cada nova mão pode ser identificada recebendo um valor para o atributo new, que apontaria para o xml:id de uma handNote no cabeçalho do documento. (Cf Description of hands and letters.)

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  <w lemma="καί">καὶ</w>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: καὶ
                                                                                                                                                                                                                                                                                                                  (InsAph: 11.55)
                                                                                                                                                                                                                                                                                                                  <handShift new="#m2"/>
                                                                                                                                                                                                                                                                                                                  <expan>Ὡρι<ex>γένης</ex>
                                                                                                                                                                                                                                                                                                                  </expan>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: (hand 2) Ὡρι(γένης)
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.116)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Mudança de escriba ou de mão

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Marca o início de uma sequência de texto escrita por nova mão ou o início de um trecho de escriba.

                                                                                                                                                                                                                                                                                                                  Cada nova mão pode ser identificada recebendo um valor para o atributo new, que apontaria para o xml:id de uma handNote no cabeçalho do documento. (Cf Description of hands and letters.)

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  <w lemma="καί">καὶ</w>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: καὶ
                                                                                                                                                                                                                                                                                                                  (InsAph: 11.55)
                                                                                                                                                                                                                                                                                                                  <handShift new="#m2"/>
                                                                                                                                                                                                                                                                                                                  <expan>Ὡρι<ex>γένης</ex>
                                                                                                                                                                                                                                                                                                                  </expan>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: (hand 2) Ὡρι(γένης)
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.116)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-handshift.html b/gl/dev/trans-handshift.html index e0aaa3005..e46385d44 100644 --- a/gl/dev/trans-handshift.html +++ b/gl/dev/trans-handshift.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Handshift

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint.

                                                                                                                                                                                                                                                                                                                  Each new hand can be identified by giving a value to new, which should be a pointer to the xml:id of a handNote in the document header. (Cf Description of hands and letters.)

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  <w lemma="καί">καὶ</w>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: καὶ
                                                                                                                                                                                                                                                                                                                  (InsAph: 11.55)
                                                                                                                                                                                                                                                                                                                  <handShift new="#m2"/>
                                                                                                                                                                                                                                                                                                                  <expan>Ὡρι<ex>γένης</ex>
                                                                                                                                                                                                                                                                                                                  </expan>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: (hand 2) Ὡρι(γένης)
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.116)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Handshift

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint.

                                                                                                                                                                                                                                                                                                                  Each new hand can be identified by giving a value to new, which should be a pointer to the xml:id of a handNote in the document header. (Cf Description of hands and letters.)

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <handShift/>
                                                                                                                                                                                                                                                                                                                  <w lemma="καί">καὶ</w>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: καὶ
                                                                                                                                                                                                                                                                                                                  (InsAph: 11.55)
                                                                                                                                                                                                                                                                                                                  <handShift new="#m2"/>
                                                                                                                                                                                                                                                                                                                  <expan>Ὡρι<ex>γένης</ex>
                                                                                                                                                                                                                                                                                                                  </expan>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: (hand 2) Ὡρι(γένης)
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.116)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblecharapprox-pt-br.html b/gl/dev/trans-illegiblecharapprox-pt-br.html index 37869d075..acc1e95b4 100644 --- a/gl/dev/trans-illegiblecharapprox-pt-br.html +++ b/gl/dev/trans-illegiblecharapprox-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres Ilegíveis, Quantidade Aproximada (Circa ou Range)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos em que vestígios de caracteres permanecem, mas estes não podem ser reconhecfidos e sua quantidade é aproximada, estes devem ser colocados dentro de uma tag gap e receber um atributo reason com o valor "illegible", e um atributo precision com o valor "low" (para expressar 'circa'), ou uma quantidade possível de caracteres perdidos, utilizando atLeast e atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [c.5]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="5"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="4"
                                                                                                                                                                                                                                                                                                                   atMost="6unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· c. 7··
                                                                                                                                                                                                                                                                                                                  (IRT: 560)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="10"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: - ca.10 -
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.4.844)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="4unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: -3-4-
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.17.2683)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Caracteres Ilegíveis, Quantidade Aproximada (Circa ou Range)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos em que vestígios de caracteres permanecem, mas estes não podem ser reconhecfidos e sua quantidade é aproximada, estes devem ser colocados dentro de uma tag gap e receber um atributo reason com o valor "illegible", e um atributo precision com o valor "low" (para expressar 'circa'), ou uma quantidade possível de caracteres perdidos, utilizando atLeast e atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [c.5]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="5"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="4"
                                                                                                                                                                                                                                                                                                                   atMost="6unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· c. 7··
                                                                                                                                                                                                                                                                                                                  (IRT: 560)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="10"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: - ca.10 -
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.4.844)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="4unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: -3-4-
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.17.2683)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblecharapprox.html b/gl/dev/trans-illegiblecharapprox.html index 8c406b93d..35e1a29bc 100644 --- a/gl/dev/trans-illegiblecharapprox.html +++ b/gl/dev/trans-illegiblecharapprox.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Characters, Quantity Approximate (Circa or Range)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of characters remain, but they cannot be recognised and their quantity is approximate, they should be placed in a gap and given a reason with a value of "illegible", and either an attribute of precision with the value "low" (to express 'circa'), or a range of possible characters lost using atLeast and atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [c.5]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="5"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="4"
                                                                                                                                                                                                                                                                                                                   atMost="6unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· c. 7··
                                                                                                                                                                                                                                                                                                                  (IRT: 560)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="10"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: - ca.10 -
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.4.844)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="4unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: -3-4-
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.17.2683)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Characters, Quantity Approximate (Circa or Range)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of characters remain, but they cannot be recognised and their quantity is approximate, they should be placed in a gap and given a reason with a value of "illegible", and either an attribute of precision with the value "low" (to express 'circa'), or a range of possible characters lost using atLeast and atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [c.5]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="5"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="4"
                                                                                                                                                                                                                                                                                                                   atMost="6unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· c. 7··
                                                                                                                                                                                                                                                                                                                  (IRT: 560)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="10"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: - ca.10 -
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.4.844)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="4unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: -3-4-
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.17.2683)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblecharknown-pt-br.html b/gl/dev/trans-illegiblecharknown-pt-br.html index 15a46920a..ff8521782 100644 --- a/gl/dev/trans-illegiblecharknown-pt-br.html +++ b/gl/dev/trans-illegiblecharknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres Ilegíveis, Quantidade Conhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Noscasos onde há vestígios de caracteres, mas estres não podem ser reconhecidos e sua quantidade é conhecida, estes devem ser colocados dentro de uma tag gap e receber um atributo reason com o valor "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·
                                                                                                                                                                                                                                                                                                                  (IRT: 690)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="2"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:   ̣  ̣
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.101)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Caracteres Ilegíveis, Quantidade Conhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Noscasos onde há vestígios de caracteres, mas estres não podem ser reconhecidos e sua quantidade é conhecida, estes devem ser colocados dentro de uma tag gap e receber um atributo reason com o valor "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·
                                                                                                                                                                                                                                                                                                                  (IRT: 690)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="2"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:   ̣  ̣
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.101)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblecharknown.html b/gl/dev/trans-illegiblecharknown.html index 55d7bfe88..1ae89f595 100644 --- a/gl/dev/trans-illegiblecharknown.html +++ b/gl/dev/trans-illegiblecharknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Characters, Quantity Known

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of characters remain, but they cannot be recognised and their quantity is known, they should be placed in a gap and given a reason with a value of "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·
                                                                                                                                                                                                                                                                                                                  (IRT: 690)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="2"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:   ̣  ̣
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.101)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Characters, Quantity Known

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of characters remain, but they cannot be recognised and their quantity is known, they should be placed in a gap and given a reason with a value of "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·
                                                                                                                                                                                                                                                                                                                  (IRT: 690)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="2"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:   ̣  ̣
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.101)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblecharunknown-pt-br.html b/gl/dev/trans-illegiblecharunknown-pt-br.html index c625d5cdd..8caba588f 100644 --- a/gl/dev/trans-illegiblecharunknown-pt-br.html +++ b/gl/dev/trans-illegiblecharunknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres Ilegíveis, Quantidade Desconhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Em casos onde permanecem vestígios dos caracteres, mas eles não podem ser reconhecidos, e sua quantidade é desconhecida, deve-se colocá-los em uma tag gap e receber um atributo reason com o valor "illegible", e um atributo extent com o valor "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [- - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 45)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.10.1926)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Caracteres Ilegíveis, Quantidade Desconhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Em casos onde permanecem vestígios dos caracteres, mas eles não podem ser reconhecidos, e sua quantidade é desconhecida, deve-se colocá-los em uma tag gap e receber um atributo reason com o valor "illegible", e um atributo extent com o valor "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [- - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 45)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.10.1926)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblecharunknown.html b/gl/dev/trans-illegiblecharunknown.html index 6744f7d40..7491772a6 100644 --- a/gl/dev/trans-illegiblecharunknown.html +++ b/gl/dev/trans-illegiblecharunknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Characters, Quantity Unknown

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of characters remain, but they cannot be recognised and their quantity is unknown, they should be placed in a gap and given a reason with a value of "illegible" and an extent with a value of "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [- - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 45)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.10.1926)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Characters, Quantity Unknown

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of characters remain, but they cannot be recognised and their quantity is unknown, they should be placed in a gap and given a reason with a value of "illegible" and an extent with a value of "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.3; Sosin 2011: [- - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 45)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.10.1926)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblelineapprox-pt-br.html b/gl/dev/trans-illegiblelineapprox-pt-br.html index 3d2f96e40..7451e7af5 100644 --- a/gl/dev/trans-illegiblelineapprox-pt-br.html +++ b/gl/dev/trans-illegiblelineapprox-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Linhas Ilegíveis, Quantidade Aproximada (Circa ou Range)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde existem vestígios de linhas, mas estas não podem ser reconhecidas e sua quantidade é aproximada, deve-se colocá-las numa tag gap e receber o atributo reason com o valor "illegible", e um atributo precision com o valor "low" (para expressar 'circa'), ou uma quantidade de linhas possíveis, utilizando atLeast e atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="5unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="4"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces ca.4 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.heid..490)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="2"
                                                                                                                                                                                                                                                                                                                   atMost="3unit="line">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces 2-3 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.3.916)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Linhas Ilegíveis, Quantidade Aproximada (Circa ou Range)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde existem vestígios de linhas, mas estas não podem ser reconhecidas e sua quantidade é aproximada, deve-se colocá-las numa tag gap e receber o atributo reason com o valor "illegible", e um atributo precision com o valor "low" (para expressar 'circa'), ou uma quantidade de linhas possíveis, utilizando atLeast e atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="5unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="4"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces ca.4 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.heid..490)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="2"
                                                                                                                                                                                                                                                                                                                   atMost="3unit="line">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces 2-3 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.3.916)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblelineapprox.html b/gl/dev/trans-illegiblelineapprox.html index 9a23f0838..f989829fc 100644 --- a/gl/dev/trans-illegiblelineapprox.html +++ b/gl/dev/trans-illegiblelineapprox.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Approximate (Circa or Range)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is approximate, they should be placed in a gap and given a reason with a value of "illegible", and either an attribute of precision with the value "low" (to express 'circa'), or a range of possible lines lost using atLeast and atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="5unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="4"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces ca.4 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.heid..490)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="2"
                                                                                                                                                                                                                                                                                                                   atMost="3unit="line">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces 2-3 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.3.916)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Approximate (Circa or Range)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is approximate, they should be placed in a gap and given a reason with a value of "illegible", and either an attribute of precision with the value "low" (to express 'circa'), or a range of possible lines lost using atLeast and atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="3"
                                                                                                                                                                                                                                                                                                                   atMost="5unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="4"
                                                                                                                                                                                                                                                                                                                   unit="lineprecision="low">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces ca.4 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.heid..490)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleatLeast="2"
                                                                                                                                                                                                                                                                                                                   atMost="3unit="line">

                                                                                                                                                                                                                                                                                                                   <desc>vestiges</desc>
                                                                                                                                                                                                                                                                                                                  </gap>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: Traces 2-3 lines
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.3.916)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblelineknown-pt-br.html b/gl/dev/trans-illegiblelineknown-pt-br.html index 3b902548c..e20dbdec7 100644 --- a/gl/dev/trans-illegiblelineknown-pt-br.html +++ b/gl/dev/trans-illegiblelineknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Known

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is known, they should be placed in a gap and given a reason with a value of "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (InsAph: 8.404)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Known

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is known, they should be placed in a gap and given a reason with a value of "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (InsAph: 8.404)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblelineknown.html b/gl/dev/trans-illegiblelineknown.html index 00f522ff7..3744da71f 100644 --- a/gl/dev/trans-illegiblelineknown.html +++ b/gl/dev/trans-illegiblelineknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Known

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is known, they should be placed in a gap and given a reason with a value of "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (InsAph: 8.404)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Known

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is known, they should be placed in a gap and given a reason with a value of "illegible".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (InsAph: 8.404)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblelineunknown-pt-br.html b/gl/dev/trans-illegiblelineunknown-pt-br.html index 8372ac7df..814b10a60 100644 --- a/gl/dev/trans-illegiblelineunknown-pt-br.html +++ b/gl/dev/trans-illegiblelineunknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Linhas Ilegíveis, Quantidade Desconhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde há vestígios de linhas, mas estas não podem ser reconhecidas e sua quantidade também é desconhecida, estas linhas devem ser colocadas numa gap e receber um atributo reason com o valor "illegible" e um extent com um valor "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 972)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2433)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Linhas Ilegíveis, Quantidade Desconhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde há vestígios de linhas, mas estas não podem ser reconhecidas e sua quantidade também é desconhecida, estas linhas devem ser colocadas numa gap e receber um atributo reason com o valor "illegible" e um extent com um valor "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 972)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2433)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegiblelineunknown.html b/gl/dev/trans-illegiblelineunknown.html index c8b504f99..bde009be6 100644 --- a/gl/dev/trans-illegiblelineunknown.html +++ b/gl/dev/trans-illegiblelineunknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Unknown

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is unknown, they should be placed in a gap and given a reason with a value of "illegible" and an extent with a value of "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 972)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2433)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible Lines, Quantity Unknown

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where vestiges of lines remain, but they cannot be recognised and their quantity is unknown, they should be placed in a gap and given a reason with a value of "illegible" and an extent with a value of "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ·· ? ··
                                                                                                                                                                                                                                                                                                                  (IRT: 972)
                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: ⁦ -ca.?- ⁩
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2433)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegibleotherunits-pt-br.html b/gl/dev/trans-illegibleotherunits-pt-br.html index 3d8760d86..c47ac3c6e 100644 --- a/gl/dev/trans-illegibleotherunits-pt-br.html +++ b/gl/dev/trans-illegibleotherunits-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Texto Ilegível, outras unidades (e.g. cm)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde existem vestígios de texto, mas este texto necessita ser medido em outras formas que 'caracter' ou 'linhas', ele deve ser colocado dentro de uma tag gap, receber o atributo reason com o valor "illegible" e um atributo unit com o valor "cm" ou qualquer outra unidade que o editor necessite.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="4.2"
                                                                                                                                                                                                                                                                                                                   unit="cm"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Texto Ilegível, outras unidades (e.g. cm)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde existem vestígios de texto, mas este texto necessita ser medido em outras formas que 'caracter' ou 'linhas', ele deve ser colocado dentro de uma tag gap, receber o atributo reason com o valor "illegible" e um atributo unit com o valor "cm" ou qualquer outra unidade que o editor necessite.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="illegibleextent="4.2"
                                                                                                                                                                                                                                                                                                                   unit="cm"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-illegibleotherunits.html b/gl/dev/trans-illegibleotherunits.html index 3d20c210d..11653bd15 100644 --- a/gl/dev/trans-illegibleotherunits.html +++ b/gl/dev/trans-illegibleotherunits.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Illegible text, other units (e.g. cm)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Illegible text, other units (e.g. cm)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lacunasegmented-pt-br.html b/gl/dev/trans-lacunasegmented-pt-br.html index b17552daf..d2f35104d 100644 --- a/gl/dev/trans-lacunasegmented-pt-br.html +++ b/gl/dev/trans-lacunasegmented-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Restauração Editorial: Lacunas segmentadas ou adjacentes

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Quando uma única lacuna, na edição transcrita, é representada por uma combinação de texto restaurado (supplied) e seções perdidas (gap), estas tags devem ser codificadas como entidades distintas no EpiDoc, apesar de serem vistas como parte de uma única lacuna na representação Leiden. O EpiDoc Example XSLT incli um template que assegura que não haverá colchetes extra impressos entre as duas partes de uma lacuna (por exemplo, "[abc ...]" não "[abc] [...]").

                                                                                                                                                                                                                                                                                                                  : [abc ..?..]

                                                                                                                                                                                                                                                                                                                  <w part="I">
                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                  </w>
                                                                                                                                                                                                                                                                                                                  <gap reason="lost"/>

                                                                                                                                                                                                                                                                                                                  : [.... (nomen auctoris) ἐκ συγγραμμάτω?]ν

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="4unit="chars">
                                                                                                                                                                                                                                                                                                                   <desc>nomen auctoris</desc>
                                                                                                                                                                                                                                                                                                                  </gap>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lostcert="low">ἐκ συγγραμμάτω</supplied>ν

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [.. ? .. nomen auctoris ἐκ συγγραμμάτω?]ν
                                                                                                                                                                                                                                                                                                                  (PHI: 77668)
                                                                                                                                                                                                                                                                                                                  <w part="I">
                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">sta</supplied>
                                                                                                                                                                                                                                                                                                                  </w>
                                                                                                                                                                                                                                                                                                                  <gap reason="lost"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [sta-·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 126)

                                                                                                                                                                                                                                                                                                                  O mesmo se aplica quando dois trechos de texto adjacente precisam ser divididos em dois elementos supplied diferentes, para evitar tags sobrepostas, como por exemplo as partes de um nome ou de uma abreviação.

                                                                                                                                                                                                                                                                                                                  : Au[g(usti) Lici]nia

                                                                                                                                                                                                                                                                                                                  <expan>
                                                                                                                                                                                                                                                                                                                   <abbr>Au</abbr>
                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                    <abbr>g</abbr>
                                                                                                                                                                                                                                                                                                                    <ex>usti</ex>
                                                                                                                                                                                                                                                                                                                   </supplied>
                                                                                                                                                                                                                                                                                                                  </expan>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">Lici</supplied>nia

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: Au[g(usti) Lici]nia
                                                                                                                                                                                                                                                                                                                  <name>Καῖσ<supplied reason="lost">αρ</supplied>
                                                                                                                                                                                                                                                                                                                  </name>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">Σεβαστὸς</supplied>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: Καῖσ[αρ Σεβαστὸς]

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <supplied>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <gap>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Simona Stoyanova, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lacunasegmented.html b/gl/dev/trans-lacunasegmented.html index f073ed0e9..ce4de02d1 100644 --- a/gl/dev/trans-lacunasegmented.html +++ b/gl/dev/trans-lacunasegmented.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Editorial restoration: Segmented or adjacent lacunae

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  When a single lacuna in the transcribed edition is represented by a combination of restored text, (supplied) and lost sections (gap), these need to be encoded as distinct entities in EpiDoc, although they are perceived as part of a single lacuna in the Leiden representation. The EpiDoc Example XSLT includes a template which will ensure extra square brackets are not printed between the two parts of the lacuna (i.e. "[abc ...]" not "[abc] [...]").

                                                                                                                                                                                                                                                                                                                  : [abc ..?..]

                                                                                                                                                                                                                                                                                                                  <w part="I">
                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                  </w>
                                                                                                                                                                                                                                                                                                                  <gap reason="lost"/>

                                                                                                                                                                                                                                                                                                                  : [.... (nomen auctoris) ἐκ συγγραμμάτω?]ν

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="4unit="chars">
                                                                                                                                                                                                                                                                                                                   <desc>nomen auctoris</desc>
                                                                                                                                                                                                                                                                                                                  </gap>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lostcert="low">ἐκ συγγραμμάτω</supplied>ν

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [.. ? ..nomen auctoris ἐκ συγγραμμάτω?]ν
                                                                                                                                                                                                                                                                                                                  (PHI: 77668)
                                                                                                                                                                                                                                                                                                                  <w part="I">
                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">sta</supplied>
                                                                                                                                                                                                                                                                                                                  </w>
                                                                                                                                                                                                                                                                                                                  <gap reason="lost"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [sta-·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 126)

                                                                                                                                                                                                                                                                                                                  The same applies if two spans of adjacent restored text need to be split into distinct supplied elements to avoid overlapping tags, as for example forming part of a personal name or an abbreviation.

                                                                                                                                                                                                                                                                                                                  : Au[g(usti) Lici]nia

                                                                                                                                                                                                                                                                                                                  <expan>
                                                                                                                                                                                                                                                                                                                   <abbr>Au</abbr>
                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                    <abbr>g</abbr>
                                                                                                                                                                                                                                                                                                                    <ex>usti</ex>
                                                                                                                                                                                                                                                                                                                   </supplied>
                                                                                                                                                                                                                                                                                                                  </expan>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">Lici</supplied>nia

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: Au[g(usti) Lici]nia
                                                                                                                                                                                                                                                                                                                  <name>Καῖσ<supplied reason="lost">αρ</supplied>
                                                                                                                                                                                                                                                                                                                  </name>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">Σεβαστὸς</supplied>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: Καῖσ[αρ Σεβαστὸς]

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  2. Simona Stoyanova, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-ligature-pt-br.html b/gl/dev/trans-ligature-pt-br.html index 57d9ea253..16485f457 100644 --- a/gl/dev/trans-ligature-pt-br.html +++ b/gl/dev/trans-ligature-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Letras em ligadura

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Letras unidas em ligadura, tecnicamente aquelas que compartilham um único traço (geralmente um vertical) que faz parte dos dois caracteres, como um M e um N adjacentes; de forma mais ampla, quaisquer dois caracteres unidos ou superpostos.

                                                                                                                                                                                                                                                                                                                  • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                  Panciera 1991 IV.4: a͡ba͡bc

                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ab</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">abc</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b͡c
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ae</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: a͡e
                                                                                                                                                                                                                                                                                                                  (IRT: 991)

                                                                                                                                                                                                                                                                                                                  <!-- example from IOSPE Byz. 18 --> Εὐ<supplied reason="omitted">σ</supplied>εβί
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ου</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Petrae style: Εὐ<σ>εβίο͡υ
                                                                                                                                                                                                                                                                                                                  ἀρχιερέω<hi rend="ligaturexml:id="hi1">ν</hi>
                                                                                                                                                                                                                                                                                                                  <hi rend="ligaturexml:id="hi2"></hi>κγόνου
                                                                                                                                                                                                                                                                                                                  <link target="hi1 hi2"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ἀρχιερέων κγόνου
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.189)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Letras em ligadura

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Letras unidas em ligadura, tecnicamente aquelas que compartilham um único traço (geralmente um vertical) que faz parte dos dois caracteres, como um M e um N adjacentes; de forma mais ampla, quaisquer dois caracteres unidos ou superpostos.

                                                                                                                                                                                                                                                                                                                  • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                  Panciera 1991 IV.4: a͡ba͡bc

                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ab</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">abc</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b͡c
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ae</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: a͡e
                                                                                                                                                                                                                                                                                                                  (IRT: 991)

                                                                                                                                                                                                                                                                                                                  <!-- example from IOSPE Byz. 18 --> Εὐ<supplied reason="omitted">σ</supplied>εβί
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ου</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Petrae style: Εὐ<σ>εβίο͡υ
                                                                                                                                                                                                                                                                                                                  ἀρχιερέω<hi rend="ligaturexml:id="hi1">ν</hi>
                                                                                                                                                                                                                                                                                                                  <hi rend="ligaturexml:id="hi2"></hi>κγόνου
                                                                                                                                                                                                                                                                                                                  <link target="hi1 hi2"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ἀρχιερέων κγόνου
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.189)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-ligature.html b/gl/dev/trans-ligature.html index 1ff0b0c82..230d076d1 100644 --- a/gl/dev/trans-ligature.html +++ b/gl/dev/trans-ligature.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Ligatured letters

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Letters joined in ligature, technically those which share a single stroke (usually an upright) forming part of both characters, such as adjacent M and N, but more broadly any two joined or superimposed characters.

                                                                                                                                                                                                                                                                                                                  • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                  Panciera 1991 IV.4: a͡ba͡bc

                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ab</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">abc</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b͡c
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ae</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: a͡e
                                                                                                                                                                                                                                                                                                                  (IRT: 991)

                                                                                                                                                                                                                                                                                                                  <!-- example from IOSPE Byz. 18 -->
                                                                                                                                                                                                                                                                                                                  Εὐ<supplied reason="omitted">σ</supplied>εβί
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ου</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Petrae style: Εὐ<σ>εβίο͡υ
                                                                                                                                                                                                                                                                                                                  ἀρχιερέω<hi rend="ligaturexml:id="hi1">ν</hi>
                                                                                                                                                                                                                                                                                                                  <hi rend="ligaturexml:id="hi2"></hi>κγόνου
                                                                                                                                                                                                                                                                                                                  <link target="hi1 hi2"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ἀρχιερέων κγόνου
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.189)

                                                                                                                                                                                                                                                                                                                  Note that the ligature in the final example, which spans two words, does not yet render properly.

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Ligatured letters

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Letters joined in ligature, technically those which share a single stroke (usually an upright) forming part of both characters, such as adjacent M and N, but more broadly any two joined or superimposed characters.

                                                                                                                                                                                                                                                                                                                  • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                  Panciera 1991 IV.4: a͡ba͡bc

                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ab</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">abc</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: a͡b͡c
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ae</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: a͡e
                                                                                                                                                                                                                                                                                                                  (IRT: 991)

                                                                                                                                                                                                                                                                                                                  <!-- example from IOSPE Byz. 18 -->
                                                                                                                                                                                                                                                                                                                  Εὐ<supplied reason="omitted">σ</supplied>εβί
                                                                                                                                                                                                                                                                                                                  <hi rend="ligature">ου</hi>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Petrae style: Εὐ<σ>εβίο͡υ
                                                                                                                                                                                                                                                                                                                  ἀρχιερέω<hi rend="ligaturexml:id="hi1">ν</hi>
                                                                                                                                                                                                                                                                                                                  <hi rend="ligaturexml:id="hi2"></hi>κγόνου
                                                                                                                                                                                                                                                                                                                  <link target="hi1 hi2"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: ἀρχιερέων κγόνου
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.189)

                                                                                                                                                                                                                                                                                                                  Note that the ligature in the final example, which spans two words, does not yet render properly.

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-linebreak-pt-br.html b/gl/dev/trans-linebreak-pt-br.html index d1d139b45..b837012c1 100644 --- a/gl/dev/trans-linebreak-pt-br.html +++ b/gl/dev/trans-linebreak-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Quebras de linhaLine breaks

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific - customization: lb

                                                                                                                                                                                                                                                                                                                  O EpiDoc segue a prática TEI de marcação das quebras de linha no suporte (diferente de versos) utilizando o elemento lb, apesar da expansão "line-begins" ser de muitas formas uma maneira mais útil de se pensar este elemento. O lb é um elemento vazio que marca o ponto unde uma linha quebra (ou inicia).

                                                                                                                                                                                                                                                                                                                  Por não haver um elemento que encapsule as linhas, qualquer informação sobre o número, representação ou condição de toda uma linha deve ser marcada em um atributo no lb precedente. Por este motivo, portanto, é nossa convenção colocar um lb no início de cada linha epigráfica da edição, inclusive na primeira. Qualquer rend ou atributos de numeração neste lb se refere a todo o texto entre a atual e a próxima quebra de linha. (Ver exemplo abaixo.)

                                                                                                                                                                                                                                                                                                                  according to london: 5

                                                                                                                                                                                                                                                                                                                  <lb n="5"/>abc

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: abc

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Quebras de linhaLine breaks

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific + customization: lb

                                                                                                                                                                                                                                                                                                                  O EpiDoc segue a prática TEI de marcação das quebras de linha no suporte (diferente de versos) utilizando o elemento lb, apesar da expansão "line-begins" ser de muitas formas uma maneira mais útil de se pensar este elemento. O lb é um elemento vazio que marca o ponto unde uma linha quebra (ou inicia).

                                                                                                                                                                                                                                                                                                                  Por não haver um elemento que encapsule as linhas, qualquer informação sobre o número, representação ou condição de toda uma linha deve ser marcada em um atributo no lb precedente. Por este motivo, portanto, é nossa convenção colocar um lb no início de cada linha epigráfica da edição, inclusive na primeira. Qualquer rend ou atributos de numeração neste lb se refere a todo o texto entre a atual e a próxima quebra de linha. (Ver exemplo abaixo.)

                                                                                                                                                                                                                                                                                                                  according to london: 5

                                                                                                                                                                                                                                                                                                                  <lb n="5"/>abc

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: abc

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-linebreak.html b/gl/dev/trans-linebreak.html index 859a35725..3aafbeb8f 100644 --- a/gl/dev/trans-linebreak.html +++ b/gl/dev/trans-linebreak.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Line breaks

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific - customization: lb

                                                                                                                                                                                                                                                                                                                  EpiDoc follows TEI practice in marking line breaks on the support (as opposed to verse lines) using the lb, though the expansion "line-begins" is in many ways a more useful way of thinking about this element. lb is an empty element to mark the point at which the line breaks (or begins).

                                                                                                                                                                                                                                                                                                                  Because there is no containing element encapsulating lines, any information about the numbering, rendition, or condition of an entire line needs to be marked in an attribute on the preceding lb. For this reason, therefore, it is our convention to place an lb at the beginning of every epigraphic line in the edition, including the first. Any rend or numbering attributes on that lb refer to all text between the current and the following line-break. (See example below.)

                                                                                                                                                                                                                                                                                                                  according to london: 5

                                                                                                                                                                                                                                                                                                                  <lb n="5"/>abc

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: abc

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Line breaks

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific + customization: lb

                                                                                                                                                                                                                                                                                                                  EpiDoc follows TEI practice in marking line breaks on the support (as opposed to verse lines) using the lb, though the expansion "line-begins" is in many ways a more useful way of thinking about this element. lb is an empty element to mark the point at which the line breaks (or begins).

                                                                                                                                                                                                                                                                                                                  Because there is no containing element encapsulating lines, any information about the numbering, rendition, or condition of an entire line needs to be marked in an attribute on the preceding lb. For this reason, therefore, it is our convention to place an lb at the beginning of every epigraphic line in the edition, including the first. Any rend or numbering attributes on that lb refer to all text between the current and the following line-break. (See example below.)

                                                                                                                                                                                                                                                                                                                  according to london: 5

                                                                                                                                                                                                                                                                                                                  <lb n="5"/>abc

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: abc

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-linebreakdirection-pt-br.html b/gl/dev/trans-linebreakdirection-pt-br.html index 744dfd33f..d59fa1ee0 100644 --- a/gl/dev/trans-linebreakdirection-pt-br.html +++ b/gl/dev/trans-linebreakdirection-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Quebras de Linha: Direção do Texto

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific - customization: lb

                                                                                                                                                                                                                                                                                                                  Como cada linha em uma inscrição codificada pelo EpiDoc inicia com um lb, os atributos deste elemento podem ser considerados como referentes ao conteúdo desta linha, ou seja, todo o texto antes do próximo lb (veja também Quebras de Linha). No presente momento, portanto, o EpiDoc recomenda o uso de valores com o atributo style no lb imediatamente anterior à linha de texto em questão:

                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:l-to-r"/>
                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:r-to-l"/>

                                                                                                                                                                                                                                                                                                                  Observe que incluir a direção do texto em um lb é um uso customizado deste elemento, que é um elemento vazio em TEI. A direção de textos também pode ser indicada em elementos superiores, inclusive no div, se o atributo style se aplica a todo o texto dentro daquele elemento.

                                                                                                                                                                                                                                                                                                                  No caso da maioria das inscrições, texto com orientação da esquerda para a direita não precisa ser marcado, é a direçãop padrão da inscrição em questão. Pode-se precisar fazer uso de style no caso de um texto Bustrofédon, por exemplo.

                                                                                                                                                                                                                                                                                                                  Outros valores de style podem ser criados no caso de textos escritos na vertical, em um círculo ou espiral, oude qualquer outra forma pouco usual. (Mas estes valores não são atualmente tratados nosExemplos de Folhas de Estilo.)

                                                                                                                                                                                                                                                                                                                  SEG: abc ←

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb style="text-direction:r-to-l"/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc  ←
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="1style="text-direction:r-to-l"/>Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε<supplied reason="lost">σε</supplied>
                                                                                                                                                                                                                                                                                                                   <lb n="2break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:l-to-r"/>

                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">θ</supplied>ανόντος ⋮ Ἀνφιχάρ<supplied reason="omitted">ες</supplied> ⋮ ἀγαθὸν ⋮ παῖδα ὀ<lb n="3break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:r-to-l"/>
                                                                                                                                                                                                                                                                                                                  λοφυρόμενο<supplied reason="lost">ς. ⋮</supplied> Φαίδιμος ἐποίε.
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε[σε-]
                                                                                                                                                                                                                                                                                                                    [θ]ανόντος ⋮ Ἀνφιχάρ<ες> ⋮ ἀγαθὸν ⋮ παῖδα ὀ-
                                                                                                                                                                                                                                                                                                                    λοφυρόμενο[ς. ⋮] Φαίδιμος ἐποίε.   ←
                                                                                                                                                                                                                                                                                                                  (PHI: 1357)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                                  5. Ilaria Marchesi, autor
                                                                                                                                                                                                                                                                                                                  6. Scott DiGiulio, autor
                                                                                                                                                                                                                                                                                                                  7. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Quebras de Linha: Direção do Texto

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific + customization: lb

                                                                                                                                                                                                                                                                                                                  Como cada linha em uma inscrição codificada pelo EpiDoc inicia com um lb, os atributos deste elemento podem ser considerados como referentes ao conteúdo desta linha, ou seja, todo o texto antes do próximo lb (veja também Quebras de Linha). No presente momento, portanto, o EpiDoc recomenda o uso de valores com o atributo style no lb imediatamente anterior à linha de texto em questão:

                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:l-to-r"/>
                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:r-to-l"/>

                                                                                                                                                                                                                                                                                                                  Observe que incluir a direção do texto em um lb é um uso customizado deste elemento, que é um elemento vazio em TEI. A direção de textos também pode ser indicada em elementos superiores, inclusive no div, se o atributo style se aplica a todo o texto dentro daquele elemento.

                                                                                                                                                                                                                                                                                                                  No caso da maioria das inscrições, texto com orientação da esquerda para a direita não precisa ser marcado, é a direçãop padrão da inscrição em questão. Pode-se precisar fazer uso de style no caso de um texto Bustrofédon, por exemplo.

                                                                                                                                                                                                                                                                                                                  Outros valores de style podem ser criados no caso de textos escritos na vertical, em um círculo ou espiral, oude qualquer outra forma pouco usual. (Mas estes valores não são atualmente tratados nosExemplos de Folhas de Estilo.)

                                                                                                                                                                                                                                                                                                                  SEG: abc ←

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb style="text-direction:r-to-l"/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc  ←
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="1style="text-direction:r-to-l"/>Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε<supplied reason="lost">σε</supplied>
                                                                                                                                                                                                                                                                                                                   <lb n="2break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:l-to-r"/>

                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">θ</supplied>ανόντος ⋮ Ἀνφιχάρ<supplied reason="omitted">ες</supplied> ⋮ ἀγαθὸν ⋮ παῖδα ὀ<lb n="3break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:r-to-l"/>
                                                                                                                                                                                                                                                                                                                  λοφυρόμενο<supplied reason="lost">ς. ⋮</supplied> Φαίδιμος ἐποίε.
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε[σε-]
                                                                                                                                                                                                                                                                                                                    [θ]ανόντος ⋮ Ἀνφιχάρ<ες> ⋮ ἀγαθὸν ⋮ παῖδα ὀ-
                                                                                                                                                                                                                                                                                                                    λοφυρόμενο[ς. ⋮] Φαίδιμος ἐποίε.   ←
                                                                                                                                                                                                                                                                                                                  (PHI: 1357)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                                  5. Ilaria Marchesi, autor
                                                                                                                                                                                                                                                                                                                  6. Scott DiGiulio, autor
                                                                                                                                                                                                                                                                                                                  7. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-linebreakdirection.html b/gl/dev/trans-linebreakdirection.html index 571379fee..a020440d6 100644 --- a/gl/dev/trans-linebreakdirection.html +++ b/gl/dev/trans-linebreakdirection.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Line Breaks: Direction of Text

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific - customization: lb

                                                                                                                                                                                                                                                                                                                  As each line in an EpiDoc encoded inscription begins with an lb, attributes on this element can be understood to refer to the content of that line, i.e. all text before the following lb (see also Line Breaks). At present, therefore, EpiDoc recommends the use of the following values in the style attribute on the lb immediately preceding the line of text in question:

                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:l-to-r"/>
                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:r-to-l"/>

                                                                                                                                                                                                                                                                                                                  Note that including the directionality of the text on lb is a customized usage of the element, which is an empty element in TEI. The direction of texts can also be indicated on higher-level elements, including div, if the style attribute applies to all text within that element.

                                                                                                                                                                                                                                                                                                                  In the case of most inscriptions, left-to-right aligned text does not need to be flagged, if it is the default direction of the script in question. One might need to use style in the case of boustrophedon text, for instance.

                                                                                                                                                                                                                                                                                                                  Other values of style can be created in the case of texts written vertically, in a circle or spiral, or otherwise unusually. (But these values are not currently handled by the Example Stylesheets.)

                                                                                                                                                                                                                                                                                                                  SEG: abc ←

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb style="text-direction:r-to-l"/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc  ←
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="1style="text-direction:r-to-l"/>Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε<supplied reason="lost">σε</supplied>
                                                                                                                                                                                                                                                                                                                   <lb n="2break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:l-to-r"/>

                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">θ</supplied>ανόντος
                                                                                                                                                                                                                                                                                                                  ⋮ Ἀνφιχάρ<supplied reason="omitted">ες</supplied> ⋮ ἀγαθὸν ⋮ παῖδα ὀ<lb n="3break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:r-to-l"/>
                                                                                                                                                                                                                                                                                                                  λοφυρόμενο<supplied reason="lost">ς. ⋮</supplied> Φαίδιμος ἐποίε.

                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε[σε-]
                                                                                                                                                                                                                                                                                                                    [θ]ανόντος ⋮ Ἀνφιχάρ<ες> ⋮ ἀγαθὸν ⋮ παῖδα ὀ-
                                                                                                                                                                                                                                                                                                                    λοφυρόμενο[ς. ⋮] Φαίδιμος ἐποίε.   ←
                                                                                                                                                                                                                                                                                                                  (PHI: 1357)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  4. Tom Elliott, author
                                                                                                                                                                                                                                                                                                                  5. Ilaria Marchesi, author
                                                                                                                                                                                                                                                                                                                  6. Scott DiGiulio, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Line Breaks: Direction of Text

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific + customization: lb

                                                                                                                                                                                                                                                                                                                  As each line in an EpiDoc encoded inscription begins with an lb, attributes on this element can be understood to refer to the content of that line, i.e. all text before the following lb (see also Line Breaks). At present, therefore, EpiDoc recommends the use of the following values in the style attribute on the lb immediately preceding the line of text in question:

                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:l-to-r"/>
                                                                                                                                                                                                                                                                                                                  <lb style="text-direction:r-to-l"/>

                                                                                                                                                                                                                                                                                                                  Note that including the directionality of the text on lb is a customized usage of the element, which is an empty element in TEI. The direction of texts can also be indicated on higher-level elements, including div, if the style attribute applies to all text within that element.

                                                                                                                                                                                                                                                                                                                  In the case of most inscriptions, left-to-right aligned text does not need to be flagged, if it is the default direction of the script in question. One might need to use style in the case of boustrophedon text, for instance.

                                                                                                                                                                                                                                                                                                                  Other values of style can be created in the case of texts written vertically, in a circle or spiral, or otherwise unusually. (But these values are not currently handled by the Example Stylesheets.)

                                                                                                                                                                                                                                                                                                                  SEG: abc ←

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb style="text-direction:r-to-l"/>abc
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    abc  ←
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="1style="text-direction:r-to-l"/>Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε<supplied reason="lost">σε</supplied>
                                                                                                                                                                                                                                                                                                                   <lb n="2break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:l-to-r"/>

                                                                                                                                                                                                                                                                                                                   <supplied reason="lost">θ</supplied>ανόντος
                                                                                                                                                                                                                                                                                                                  ⋮ Ἀνφιχάρ<supplied reason="omitted">ες</supplied> ⋮ ἀγαθὸν ⋮ παῖδα ὀ<lb n="3break="no"
                                                                                                                                                                                                                                                                                                                    style="text-direction:r-to-l"/>
                                                                                                                                                                                                                                                                                                                  λοφυρόμενο<supplied reason="lost">ς. ⋮</supplied> Φαίδιμος ἐποίε.

                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    Χαιρεδέμο ⋮ τόδε σε̑μα ⋮ πατὲρ ἔστε[σε-]
                                                                                                                                                                                                                                                                                                                    [θ]ανόντος ⋮ Ἀνφιχάρ<ες> ⋮ ἀγαθὸν ⋮ παῖδα ὀ-
                                                                                                                                                                                                                                                                                                                    λοφυρόμενο[ς. ⋮] Φαίδιμος ἐποίε.   ←
                                                                                                                                                                                                                                                                                                                  (PHI: 1357)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  4. Tom Elliott, author
                                                                                                                                                                                                                                                                                                                  5. Ilaria Marchesi, author
                                                                                                                                                                                                                                                                                                                  6. Scott DiGiulio, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-linebreakinword-pt-br.html b/gl/dev/trans-linebreakinword-pt-br.html index e20107f81..77c893c86 100644 --- a/gl/dev/trans-linebreakinword-pt-br.html +++ b/gl/dev/trans-linebreakinword-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Quebras de Linha em Palavras

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific - customization: lb

                                                                                                                                                                                                                                                                                                                  Palavras divididas entre linhas (por exemplo, onde uma quebra de linha não indica uma quebra de palavra) devem ser marcadas pelo lb com um break no valor de "no". Isto, entre outras coisas, permite ao XSLT gerar um hífem no final da linha anterior. Paramaiores informações sobre o elemento lb, veja as normas para Quebras de Linha.

                                                                                                                                                                                                                                                                                                                  according to london: proc-
                                                                                                                                                                                                                                                                                                                  urator

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="6"/>imper<lb n="7break="no"/>ator
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator
                                                                                                                                                                                                                                                                                                                  • London style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Quebras de Linha em Palavras

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific + customization: lb

                                                                                                                                                                                                                                                                                                                  Palavras divididas entre linhas (por exemplo, onde uma quebra de linha não indica uma quebra de palavra) devem ser marcadas pelo lb com um break no valor de "no". Isto, entre outras coisas, permite ao XSLT gerar um hífem no final da linha anterior. Paramaiores informações sobre o elemento lb, veja as normas para Quebras de Linha.

                                                                                                                                                                                                                                                                                                                  according to london: proc-
                                                                                                                                                                                                                                                                                                                  urator

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="6"/>imper<lb n="7break="no"/>ator
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator
                                                                                                                                                                                                                                                                                                                  • London style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-linebreakinword.html b/gl/dev/trans-linebreakinword.html index b6e9c7b13..7bd79e811 100644 --- a/gl/dev/trans-linebreakinword.html +++ b/gl/dev/trans-linebreakinword.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Line Breaks In Words

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific - customization: lb

                                                                                                                                                                                                                                                                                                                  Words divided across lines (i.e. where the line-break does not indicate a word-break) should be indicated by lb with a break with a value of "no". This, among other things, allows the XSLT to generate the hyphen at the end of the preceding line. For further explanation of the lb element, see the guidance for Line Breaks.

                                                                                                                                                                                                                                                                                                                  according to london: proc-
                                                                                                                                                                                                                                                                                                                  urator

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="6"/>imper<lb n="7break="no"/>ator
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator
                                                                                                                                                                                                                                                                                                                  • London style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Line Breaks In Words

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: lb ; EpiDoc-specific + customization: lb

                                                                                                                                                                                                                                                                                                                  Words divided across lines (i.e. where the line-break does not indicate a word-break) should be indicated by lb with a break with a value of "no". This, among other things, allows the XSLT to generate the hyphen at the end of the preceding line. For further explanation of the lb element, see the guidance for Line Breaks.

                                                                                                                                                                                                                                                                                                                  according to london: proc-
                                                                                                                                                                                                                                                                                                                  urator

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="6"/>imper<lb n="7break="no"/>ator
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator
                                                                                                                                                                                                                                                                                                                  • London style:

                                                                                                                                                                                                                                                                                                                    imper-
                                                                                                                                                                                                                                                                                                                    ator

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lb>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharapprox-pt-br.html b/gl/dev/trans-lostcharapprox-pt-br.html index cc88cd3c9..873ed92e0 100644 --- a/gl/dev/trans-lostcharapprox-pt-br.html +++ b/gl/dev/trans-lostcharapprox-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, quantidade aproximada

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  O elemento gap indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Nos casos em que o editor pode apresentar apenas um tamanho estimado, o seguinte atributo deve ser utilizado:

                                                                                                                                                                                                                                                                                                                  • precision deve receber um valor "low", para denotar o fato de que existe um grau de imprecisão sobre o valor dado no atributo quantity (portanto, cerca).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [c.7]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="12"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 12··]
                                                                                                                                                                                                                                                                                                                  (IRT: 55)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="19"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.19 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2367)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca.7 -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 7··]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.amst..26)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                    Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, quantidade aproximada

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  O elemento gap indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Nos casos em que o editor pode apresentar apenas um tamanho estimado, o seguinte atributo deve ser utilizado:

                                                                                                                                                                                                                                                                                                                  • precision deve receber um valor "low", para denotar o fato de que existe um grau de imprecisão sobre o valor dado no atributo quantity (portanto, cerca).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [c.7]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="12"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 12··]
                                                                                                                                                                                                                                                                                                                  (IRT: 55)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="19"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.19 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2367)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca.7 -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 7··]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.amst..26)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                    Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharapprox.html b/gl/dev/trans-lostcharapprox.html index 8af759a03..292cc492a 100644 --- a/gl/dev/trans-lostcharapprox.html +++ b/gl/dev/trans-lostcharapprox.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost characters, quantity approximate

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using the gap element. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content .

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is usually given the value "lost" (although other values are possible).
                                                                                                                                                                                                                                                                                                                  • quantity indicates how many characters or lines have been lost (where known).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  For cases in which the editor can provide only an approximate extent, the following attribute should be used:

                                                                                                                                                                                                                                                                                                                  • precision should be given a value of "low" to denotes the fact that there is a degree of imprecision about the value given in quantity (i.e. circa).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [c.7]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="12"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 12··]
                                                                                                                                                                                                                                                                                                                  (IRT: 55)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="19"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.19 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2367)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca.7 -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 7··]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.amst..26)

                                                                                                                                                                                                                                                                                                                  Where the editor prefers to give a range within which the possible extent of the lacuna may fall (e.g. "10-12 characters"), this may be encoded using the atLeast and atMost attibutes:

                                                                                                                                                                                                                                                                                                                  C.427: [— 5-7 —]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="5atMost="7"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· 5-7··]

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lost characters, quantity approximate

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using the gap element. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content .

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is usually given the value "lost" (although other values are possible).
                                                                                                                                                                                                                                                                                                                  • quantity indicates how many characters or lines have been lost (where known).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  For cases in which the editor can provide only an approximate extent, the following attribute should be used:

                                                                                                                                                                                                                                                                                                                  • precision should be given a value of "low" to denotes the fact that there is a degree of imprecision about the value given in quantity (i.e. circa).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [c.7]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="12"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 12··]
                                                                                                                                                                                                                                                                                                                  (IRT: 55)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="19"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.19 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.14.2367)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca.7 -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                   unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.7 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 7]
                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 7··]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.amst..26)

                                                                                                                                                                                                                                                                                                                  Where the editor prefers to give a range within which the possible extent of the lacuna may fall (e.g. "10-12 characters"), this may be encoded using the atLeast and atMost attibutes:

                                                                                                                                                                                                                                                                                                                  C.427: [— 5-7 —]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="5atMost="7"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· 5-7··]

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharknown-pt-br.html b/gl/dev/trans-lostcharknown-pt-br.html index 4fecd2844..52e1d216d 100644 --- a/gl/dev/trans-lostcharknown-pt-br.html +++ b/gl/dev/trans-lostcharknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, quantidade conhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [...]
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ ̣ ̣ ̣ ̣ ̣ ̣]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="6"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 6]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ -ca. 9- ]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="9"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.9 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 9]
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· 5··]
                                                                                                                                                                                                                                                                                                                  (IRT: 126)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="13"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.13 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.109)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, quantidade conhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [...]
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ ̣ ̣ ̣ ̣ ̣ ̣]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="6"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 6]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ -ca. 9- ]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="9"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.9 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 9]
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· 5··]
                                                                                                                                                                                                                                                                                                                  (IRT: 126)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="13"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.13 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.109)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharknown.html b/gl/dev/trans-lostcharknown.html index 4325aa58c..2dc6681bf 100644 --- a/gl/dev/trans-lostcharknown.html +++ b/gl/dev/trans-lostcharknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost characters, quantity known

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  A gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content.

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is usually given the value "lost" (although other values are possible).
                                                                                                                                                                                                                                                                                                                  • quantity indicates how many characters or lines have been lost (where known).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [...]
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ ̣ ̣ ̣ ̣ ̣ ̣]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="6"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 6]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ -ca. 9- ]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="9"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.9 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 9]
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· 5··]
                                                                                                                                                                                                                                                                                                                  (IRT: 126)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="13"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.13 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.109)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lost characters, quantity known

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  A gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content.

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is usually given the value "lost" (although other values are possible).
                                                                                                                                                                                                                                                                                                                  • quantity indicates how many characters or lines have been lost (where known).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [...]
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ ̣ ̣ ̣ ̣ ̣ ̣]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="6"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [  ̣  ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 6]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [ -ca. 9- ]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="9"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.9 -]
                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 9]
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· 5··]
                                                                                                                                                                                                                                                                                                                  (IRT: 126)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="13"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [- ca.13 -]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.109)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharmetre-pt-br.html b/gl/dev/trans-lostcharmetre-pt-br.html index 3a3ccd95f..1b6da7cc8 100644 --- a/gl/dev/trans-lostcharmetre-pt-br.html +++ b/gl/dev/trans-lostcharmetre-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, Métrica Conhecida/Reconstruída

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres perdidos não podem ser restaurados, mas o texto é em versos e os valores métricos ou padrão da lacuna podem ser dados.

                                                                                                                                                                                                                                                                                                                  : χαλκέοισι κάδοις δέχεται [ ˘ ˘ ˉ ]

                                                                                                                                                                                                                                                                                                                  χαλκέοισι κάδοις δέχεται
                                                                                                                                                                                                                                                                                                                  <seg met="--+">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                    unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  </seg>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: χαλκέοισι κάδοις δέχεται [c. 7]
                                                                                                                                                                                                                                                                                                                  • London style: χαλκέοισι κάδοις δέχεται [·· c. 7··]

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharmetre.html b/gl/dev/trans-lostcharmetre.html index bd586a5ff..527068a33 100644 --- a/gl/dev/trans-lostcharmetre.html +++ b/gl/dev/trans-lostcharmetre.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost Characters, Metre Known/Reconstructed

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  When characters are lost and cannot be restored, but the text is in verse and the metrical values or pattern of the lacuna can be given, the lost portion of the verse line is marked using a seg element. The seg element may contain an attribute recording conventional metrical structure by means of either a standard term for the metrical unit (e.g. met with value "dactylic") or a representation for the metrical pattern (e.g. met with value "--|+--|+--|+±").

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                    Lost Characters, Metre Known/Reconstructed

                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                    When characters are lost and cannot be restored, but the text is in verse and the metrical values or pattern of the lacuna can be given, the lost portion of the verse line is marked using a seg element. The seg element may contain an attribute recording conventional metrical structure by means of either a standard term for the metrical unit (e.g. met with value "dactylic") or a representation for the metrical pattern (e.g. met with value "--|+--|+--|+±").

                                                                                                                                                                                                                                                                                                                    • TEI definition: gap ; EpiDoc-specific customization: gap
                                                                                                                                                                                                                                                                                                                    • TEI definition: seg ; EpiDoc-specific - customization: seg

                                                                                                                                                                                                                                                                                                                    A.92: [ ˉ ˘ ˘ ˉ ˘ ]ι̣χ̣ων λουτ̣ρ̣ὸν ἀκηράσιον

                                                                                                                                                                                                                                                                                                                    <seg met="+--+-">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostquantity="9"
                                                                                                                                                                                                                                                                                                                      unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <unclear>ιχ</unclear>ων
                                                                                                                                                                                                                                                                                                                    λου<unclear>τρ</unclear>ὸν ἀκηράσιον

                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                    • London style: [·· c. 9··]ι̣χ̣ων λουτ̣ρ̣ὸν ἀκηράσιον
                                                                                                                                                                                                                                                                                                                    • verse parameter on: [ ˉ  ˘  ˘  ˉ  ˘ ]ι̣χ̣ων λουτ̣ρ̣ὸν ἀκηράσιον
                                                                                                                                                                                                                                                                                                                    ()

                                                                                                                                                                                                                                                                                                                    : χαλκέοισι κάδοις δέχεται [ ˘ ˘ ˉ ]

                                                                                                                                                                                                                                                                                                                    χαλκέοισι κάδοις δέχεται
                                                                                                                                                                                                                                                                                                                    <seg met="--+">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                      unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                    </seg>

                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: χαλκέοισι κάδοις δέχεται [c. 7]
                                                                                                                                                                                                                                                                                                                    • verse parameter on: χαλκέοισι κάδοις δέχεται [ ˘  ˘  ˉ ]
                                                                                                                                                                                                                                                                                                                    <lg met="elegiac couplets">
                                                                                                                                                                                                                                                                                                                     <l n="1met="hexameter">
                                                                                                                                                                                                                                                                                                                      <lb n="15"/>
                                                                                                                                                                                                                                                                                                                      <seg met="+--|+--|+-">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </seg>
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">ἀρ</supplied>ιστοπάτωρ βεβόαται</l>
                                                                                                                                                                                                                                                                                                                     <l n="2met="pentameter">
                                                                                                                                                                                                                                                                                                                      <lb n="16"/>
                                                                                                                                                                                                                                                                                                                      <seg met="+--|+--|+">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </seg>
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"></supplied>ξοχε Δεινομένη.</l>
                                                                                                                                                                                                                                                                                                                     <l n="3met="hexameter">
                                                                                                                                                                                                                                                                                                                      <lb n="17"/>
                                                                                                                                                                                                                                                                                                                      <seg met="+--|+--|+-">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </seg>
                                                                                                                                                                                                                                                                                                                      <unclear>τ</unclear>εὰ πατρὶς οὐκ ἐπὶ μούναι</l>
                                                                                                                                                                                                                                                                                                                     <l n="4met="pentameter">
                                                                                                                                                                                                                                                                                                                      <lb n="18"/>
                                                                                                                                                                                                                                                                                                                      <seg met="+--|+--|+">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </seg>
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">εἵ</supplied>νεκεν ἀγλαΐας.</l>
                                                                                                                                                                                                                                                                                                                     <l n="5met="hexameter">
                                                                                                                                                                                                                                                                                                                      <lb n="19"/>
                                                                                                                                                                                                                                                                                                                      <seg met="+--|+--|+--|+">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </seg>
                                                                                                                                                                                                                                                                                                                      <choice>
                                                                                                                                                                                                                                                                                                                       <unclear>χ</unclear>
                                                                                                                                                                                                                                                                                                                       <unclear>κ</unclear>
                                                                                                                                                                                                                                                                                                                      </choice>μεα τᾶιδε σε μέλπει</l>
                                                                                                                                                                                                                                                                                                                     <l n="6met="pentameter">
                                                                                                                                                                                                                                                                                                                      <lb n="20"/>
                                                                                                                                                                                                                                                                                                                      <seg met="+--|+--|+">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </seg>
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">π</supplied>ρᾶτον ἐν ἠϊθέοις.</l>
                                                                                                                                                                                                                                                                                                                    </lg>

                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                      [--- ἀρ]ιστοπάτωρ βεβόαται
                                                                                                                                                                                                                                                                                                                      [--- ἔ]ξοχε Δεινομένη.
                                                                                                                                                                                                                                                                                                                      [---] τ̣εὰ πατρὶς οὐκ ἐπὶ μούναι
                                                                                                                                                                                                                                                                                                                      [--- εἵ]νεκεν ἀγλαΐας.
                                                                                                                                                                                                                                                                                                                      [---] χ̣μεα τᾶιδε σε μέλπει
                                                                                                                                                                                                                                                                                                                      [--- π]ρᾶτον ἐν ἠϊθέοις.
                                                                                                                                                                                                                                                                                                                    • London style:

                                                                                                                                                                                                                                                                                                                      [·· ? ·· ἀρ]ιστοπάτωρ βεβόαται
                                                                                                                                                                                                                                                                                                                      [·· ? ·· ἔ]ξοχε Δεινομένη.
                                                                                                                                                                                                                                                                                                                      [·· ? ··] τ̣εὰ πατρὶς οὐκ ἐπὶ μούναι
                                                                                                                                                                                                                                                                                                                      [·· ? ·· εἵ]νεκεν ἀγλαΐας.
                                                                                                                                                                                                                                                                                                                      [·· ? ··] χ̣μεα τᾶιδε σε μέλπει
                                                                                                                                                                                                                                                                                                                      [·· ? ·· π]ρᾶτον ἐν ἠϊθέοις.
                                                                                                                                                                                                                                                                                                                    • verse parameter on:

                                                                                                                                                                                                                                                                                                                      | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘  ἀρ]ιστοπάτωρ βεβόαται
                                                                                                                                                                                                                                                                                                                          | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ἔ]ξοχε Δεινομένη.
                                                                                                                                                                                                                                                                                                                      | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘ ] τ̣εὰ πατρὶς οὐκ ἐπὶ μούναι
                                                                                                                                                                                                                                                                                                                          | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  εἵ]νεκεν ἀγλαΐας.
                                                                                                                                                                                                                                                                                                                      | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ ] χ̣μεα τᾶιδε σε μέλπει
                                                                                                                                                                                                                                                                                                                          | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  π]ρᾶτον ἐν ἠϊθέοις.
                                                                                                                                                                                                                                                                                                                    (GVCyr: gvcyr035)

                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                    \ No newline at end of file + customization: seg

                                                                                                                                                                                                                                                                                                                  A.92: [ ˉ ˘ ˘ ˉ ˘ ]ι̣χ̣ων λουτ̣ρ̣ὸν ἀκηράσιον

                                                                                                                                                                                                                                                                                                                  <seg met="+--+-">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostquantity="9"
                                                                                                                                                                                                                                                                                                                    unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  </seg>
                                                                                                                                                                                                                                                                                                                  <unclear>ιχ</unclear>ων
                                                                                                                                                                                                                                                                                                                  λου<unclear>τρ</unclear>ὸν ἀκηράσιον

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· c. 9··]ι̣χ̣ων λουτ̣ρ̣ὸν ἀκηράσιον
                                                                                                                                                                                                                                                                                                                  • verse parameter on: [ ˉ  ˘  ˘  ˉ  ˘ ]ι̣χ̣ων λουτ̣ρ̣ὸν ἀκηράσιον
                                                                                                                                                                                                                                                                                                                  ()

                                                                                                                                                                                                                                                                                                                  : χαλκέοισι κάδοις δέχεται [ ˘ ˘ ˉ ]

                                                                                                                                                                                                                                                                                                                  χαλκέοισι κάδοις δέχεται
                                                                                                                                                                                                                                                                                                                  <seg met="--+">
                                                                                                                                                                                                                                                                                                                   <gap reason="lostquantity="7"
                                                                                                                                                                                                                                                                                                                    unit="characterprecision="low"/>

                                                                                                                                                                                                                                                                                                                  </seg>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: χαλκέοισι κάδοις δέχεται [c. 7]
                                                                                                                                                                                                                                                                                                                  • verse parameter on: χαλκέοισι κάδοις δέχεται [ ˘  ˘  ˉ ]
                                                                                                                                                                                                                                                                                                                  <lg met="elegiac couplets">
                                                                                                                                                                                                                                                                                                                   <l n="1met="hexameter">
                                                                                                                                                                                                                                                                                                                    <lb n="15"/>
                                                                                                                                                                                                                                                                                                                    <seg met="+--|+--|+-">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <supplied reason="lost">ἀρ</supplied>ιστοπάτωρ βεβόαται</l>
                                                                                                                                                                                                                                                                                                                   <l n="2met="pentameter">
                                                                                                                                                                                                                                                                                                                    <lb n="16"/>
                                                                                                                                                                                                                                                                                                                    <seg met="+--|+--|+">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <supplied reason="lost"></supplied>ξοχε Δεινομένη.</l>
                                                                                                                                                                                                                                                                                                                   <l n="3met="hexameter">
                                                                                                                                                                                                                                                                                                                    <lb n="17"/>
                                                                                                                                                                                                                                                                                                                    <seg met="+--|+--|+-">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <unclear>τ</unclear>εὰ πατρὶς οὐκ ἐπὶ μούναι</l>
                                                                                                                                                                                                                                                                                                                   <l n="4met="pentameter">
                                                                                                                                                                                                                                                                                                                    <lb n="18"/>
                                                                                                                                                                                                                                                                                                                    <seg met="+--|+--|+">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <supplied reason="lost">εἵ</supplied>νεκεν ἀγλαΐας.</l>
                                                                                                                                                                                                                                                                                                                   <l n="5met="hexameter">
                                                                                                                                                                                                                                                                                                                    <lb n="19"/>
                                                                                                                                                                                                                                                                                                                    <seg met="+--|+--|+--|+">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <choice>
                                                                                                                                                                                                                                                                                                                     <unclear>χ</unclear>
                                                                                                                                                                                                                                                                                                                     <unclear>κ</unclear>
                                                                                                                                                                                                                                                                                                                    </choice>μεα τᾶιδε σε μέλπει</l>
                                                                                                                                                                                                                                                                                                                   <l n="6met="pentameter">
                                                                                                                                                                                                                                                                                                                    <lb n="20"/>
                                                                                                                                                                                                                                                                                                                    <seg met="+--|+--|+">
                                                                                                                                                                                                                                                                                                                     <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                      unit="character"/>

                                                                                                                                                                                                                                                                                                                    </seg>
                                                                                                                                                                                                                                                                                                                    <supplied reason="lost">π</supplied>ρᾶτον ἐν ἠϊθέοις.</l>
                                                                                                                                                                                                                                                                                                                  </lg>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                    [--- ἀρ]ιστοπάτωρ βεβόαται
                                                                                                                                                                                                                                                                                                                    [--- ἔ]ξοχε Δεινομένη.
                                                                                                                                                                                                                                                                                                                    [---] τ̣εὰ πατρὶς οὐκ ἐπὶ μούναι
                                                                                                                                                                                                                                                                                                                    [--- εἵ]νεκεν ἀγλαΐας.
                                                                                                                                                                                                                                                                                                                    [---] χ̣μεα τᾶιδε σε μέλπει
                                                                                                                                                                                                                                                                                                                    [--- π]ρᾶτον ἐν ἠϊθέοις.
                                                                                                                                                                                                                                                                                                                  • London style:

                                                                                                                                                                                                                                                                                                                    [·· ? ·· ἀρ]ιστοπάτωρ βεβόαται
                                                                                                                                                                                                                                                                                                                    [·· ? ·· ἔ]ξοχε Δεινομένη.
                                                                                                                                                                                                                                                                                                                    [·· ? ··] τ̣εὰ πατρὶς οὐκ ἐπὶ μούναι
                                                                                                                                                                                                                                                                                                                    [·· ? ·· εἵ]νεκεν ἀγλαΐας.
                                                                                                                                                                                                                                                                                                                    [·· ? ··] χ̣μεα τᾶιδε σε μέλπει
                                                                                                                                                                                                                                                                                                                    [·· ? ·· π]ρᾶτον ἐν ἠϊθέοις.
                                                                                                                                                                                                                                                                                                                  • verse parameter on:

                                                                                                                                                                                                                                                                                                                    | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘  ἀρ]ιστοπάτωρ βεβόαται
                                                                                                                                                                                                                                                                                                                        | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ἔ]ξοχε Δεινομένη.
                                                                                                                                                                                                                                                                                                                    | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘ ] τ̣εὰ πατρὶς οὐκ ἐπὶ μούναι
                                                                                                                                                                                                                                                                                                                        | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  εἵ]νεκεν ἀγλαΐας.
                                                                                                                                                                                                                                                                                                                    | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ ] χ̣μεα τᾶιδε σε μέλπει
                                                                                                                                                                                                                                                                                                                        | [ ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  π]ρᾶτον ἐν ἠϊθέοις.
                                                                                                                                                                                                                                                                                                                  (GVCyr: gvcyr035)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharnumeral-pt-br.html b/gl/dev/trans-lostcharnumeral-pt-br.html index 8aa7affeb..2798f1e10 100644 --- a/gl/dev/trans-lostcharnumeral-pt-br.html +++ b/gl/dev/trans-lostcharnumeral-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres Perdidos, Numeral

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  : L[.]

                                                                                                                                                                                                                                                                                                                  <num atLeast="51atMost="55">L<gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: L[.]

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharnumeral.html b/gl/dev/trans-lostcharnumeral.html index 891b06e24..53335ad9e 100644 --- a/gl/dev/trans-lostcharnumeral.html +++ b/gl/dev/trans-lostcharnumeral.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost Characters, Numeral

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  : L[.]

                                                                                                                                                                                                                                                                                                                  <num atLeast="51atMost="55">L<gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: L[.]

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharpraenomen-pt-br.html b/gl/dev/trans-lostcharpraenomen-pt-br.html index 31004f33b..4146228fa 100644 --- a/gl/dev/trans-lostcharpraenomen-pt-br.html +++ b/gl/dev/trans-lostcharpraenomen-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, praenomen

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  name indica um nome próprio ou oração nominal.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Em casos onde um praenomen se perdeu, a quantidade de caracteres perdidos deve ser extrapolada (fica entre 1 e 3 letras). Portanto, além de reason e unit, mais dois atributos devem ser utlizados:

                                                                                                                                                                                                                                                                                                                  • atLeast indica o número mínimo de caracteres perdidos.
                                                                                                                                                                                                                                                                                                                  • atMost indica o númeor máximo de caracteres perdidos.

                                                                                                                                                                                                                                                                                                                  gap também deve ser colocado dentro de name, para denotar o fato que o editor considera que a lacuna continha um nome em vez de outro tipo de palavra.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.4: [-]

                                                                                                                                                                                                                                                                                                                  <name>
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="1atMost="3"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </name>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 1 - 3]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [-1-3-]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <num>
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="12atMost="15"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [-12-15-]
                                                                                                                                                                                                                                                                                                                  (DDbDP: psi.7.769#1)
                                                                                                                                                                                                                                                                                                                  Note: PN does not use this convention specifically for praenomina, but does allow ranges of extent for lacunae, e.g. when known to be a number, or length of lacuna is approximate.

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, Autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, Autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharpraenomen.html b/gl/dev/trans-lostcharpraenomen.html index 3b1d4049d..a7712edbd 100644 --- a/gl/dev/trans-lostcharpraenomen.html +++ b/gl/dev/trans-lostcharpraenomen.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost characters, praenomen

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  A gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  name indicates a proper noun or noun phrase.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content (see sections VIII.7 for examples in which gap can contain other elements).

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is given the value "lost" (other values denote other kinds of non-transcribable text).
                                                                                                                                                                                                                                                                                                                  • quantity indicates how many characters or lines have been lost (where known).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  In cases in which a praenomen has been lost, the quantity of characters missing should be extrapolated (this is usually between 1 and 3 letters). Therefore, in addition to reason and unit, a further two attributes should be used:

                                                                                                                                                                                                                                                                                                                  • atLeast indicates the minimum number of characters lost.
                                                                                                                                                                                                                                                                                                                  • atMost indicates the maximum number of characters lost.

                                                                                                                                                                                                                                                                                                                  gap should also be placed inside name, to denote the fact that the editor considers the lacuna to have contained a name rather than another type of word.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.4: [-]

                                                                                                                                                                                                                                                                                                                  <name>
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="1atMost="3"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </name>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [c. 1 - 3]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [-1-3-]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <num>
                                                                                                                                                                                                                                                                                                                   <gap reason="lostatLeast="12atMost="15"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                  </num>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [-12-15-]
                                                                                                                                                                                                                                                                                                                  (DDbDP: psi.7.769#1)
                                                                                                                                                                                                                                                                                                                  Note: PN does not use this convention specifically for praenomina, but does allow ranges of extent for lacunae, e.g. when known to be a number, or length of lacuna is approximate.

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, Author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, Author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharunknown-pt-br.html b/gl/dev/trans-lostcharunknown-pt-br.html index 4d308e38e..b457a6326 100644 --- a/gl/dev/trans-lostcharunknown-pt-br.html +++ b/gl/dev/trans-lostcharunknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, quantidade desconhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Importante: diferente dos casos onde o número de caracteres perdidos é conhecido pelo editor, quando o elemento quantity é usado, no caso de uma quantidade desconhecida de carateres perdidos usamos extent:

                                                                                                                                                                                                                                                                                                                  • extent com um valor "unknown" denota o fato que não é possível determinar quantos caracteres foram perdidos.

                                                                                                                                                                                                                                                                                                                  gap pode também receber os seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3; SEG: [---]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca. ? -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [---]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 6)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.ashm..22)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Caracteres perdidos, quantidade desconhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Importante: diferente dos casos onde o número de caracteres perdidos é conhecido pelo editor, quando o elemento quantity é usado, no caso de uma quantidade desconhecida de carateres perdidos usamos extent:

                                                                                                                                                                                                                                                                                                                  • extent com um valor "unknown" denota o fato que não é possível determinar quantos caracteres foram perdidos.

                                                                                                                                                                                                                                                                                                                  gap pode também receber os seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3; SEG: [---]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca. ? -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [---]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 6)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.ashm..22)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostcharunknown.html b/gl/dev/trans-lostcharunknown.html index 38e74c5f5..52cb677d1 100644 --- a/gl/dev/trans-lostcharunknown.html +++ b/gl/dev/trans-lostcharunknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost characters, quantity unknown

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  A gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content (see sections VIII.7 for examples in which gap can contain other elements).

                                                                                                                                                                                                                                                                                                                  Important: whereas in cases in which the number of characters lost is known to the editor, quantity is used, in the case of an unknown number of characters being lost we use extent:

                                                                                                                                                                                                                                                                                                                  • extent with a value of "unknown" denotes the fact that it is not possible to determine how many characters have been lost.

                                                                                                                                                                                                                                                                                                                  gap should also take the following attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is usually given the value "lost" (although other values are possible).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3; SEG: [---]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca. ? -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [---]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 6)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.ashm..22)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lost characters, quantity unknown

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  A gap (gap) indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where characters have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content (see sections VIII.7 for examples in which gap can contain other elements).

                                                                                                                                                                                                                                                                                                                  Important: whereas in cases in which the number of characters lost is known to the editor, quantity is used, in the case of an unknown number of characters being lost we use extent:

                                                                                                                                                                                                                                                                                                                  • extent with a value of "unknown" denotes the fact that it is not possible to determine how many characters have been lost.

                                                                                                                                                                                                                                                                                                                  gap should also take the following attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, and for a lacuna is usually given the value "lost" (although other values are possible).
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.3; SEG: [---]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [- ca. ? -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [---]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 6)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [⁦ -ca.?- ⁩]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.ashm..22)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostlineapprox-pt-br.html b/gl/dev/trans-lostlineapprox-pt-br.html index 0618dca44..91d6283be 100644 --- a/gl/dev/trans-lostlineapprox-pt-br.html +++ b/gl/dev/trans-lostlineapprox-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Linhas Perdidas, Quantidade Aproximada (Cerca ou Estimativa)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde linhas parecem perdidas, mas o editor não está certo no número preciso de linhas que se perderam, usamos o elemento gap, que deve receber um atributo precision com o valor "low" (para expressar 'cerca') ou receber uma estimativa de linhas possivelmente perdidas, usando os atributos atLeast e atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="1unit="line"
                                                                                                                                                                                                                                                                                                                   precision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="3atMost="5"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostunit="linequantity="6"
                                                                                                                                                                                                                                                                                                                   precision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [ca.6 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.14)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [1-2 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.3.620)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Linhas Perdidas, Quantidade Aproximada (Cerca ou Estimativa)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde linhas parecem perdidas, mas o editor não está certo no número preciso de linhas que se perderam, usamos o elemento gap, que deve receber um atributo precision com o valor "low" (para expressar 'cerca') ou receber uma estimativa de linhas possivelmente perdidas, usando os atributos atLeast e atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="1unit="line"
                                                                                                                                                                                                                                                                                                                   precision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="3atMost="5"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostunit="linequantity="6"
                                                                                                                                                                                                                                                                                                                   precision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [ca.6 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.14)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [1-2 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.3.620)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostlineapprox.html b/gl/dev/trans-lostlineapprox.html index 06c14c1af..15fb32174 100644 --- a/gl/dev/trans-lostlineapprox.html +++ b/gl/dev/trans-lostlineapprox.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost Lines, Quantity Approximate (Circa or Range)

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where lines appear to be missing but the editor is unsure as to the precise number of lines that have been lost, this is expressed using gap, which should either be given a precision with the value "low" (to express 'circa'), or be given a range of possible lines lost using the atLeast and atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="1unit="line"
                                                                                                                                                                                                                                                                                                                   precision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="3atMost="5"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostunit="linequantity="6"
                                                                                                                                                                                                                                                                                                                   precision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [ca.6 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.14)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [1-2 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.3.620)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lost Lines, Quantity Approximate (Circa or Range)

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where lines appear to be missing but the editor is unsure as to the precise number of lines that have been lost, this is expressed using gap, which should either be given a precision with the value "low" (to express 'circa'), or be given a range of possible lines lost using the atLeast and atMost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.5; Sosin 2011: [- - - - - -]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="1unit="line"
                                                                                                                                                                                                                                                                                                                   precision="low"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="3atMost="5"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostunit="linequantity="6"
                                                                                                                                                                                                                                                                                                                   precision="low"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [ca.6 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.14)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [1-2 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: o.claud.3.620)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostlineknown-pt-br.html b/gl/dev/trans-lostlineknown-pt-br.html index f5c873e72..dfa98b41a 100644 --- a/gl/dev/trans-lostlineknown-pt-br.html +++ b/gl/dev/trans-lostlineknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Linhas perdidas, quantidade conhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.5: [------]
                                                                                                                                                                                                                                                                                                                  [------]
                                                                                                                                                                                                                                                                                                                  [------]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [3 lines missing]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [------]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [3 lines missing]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [5 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.11.2070)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Linhas perdidas, quantidade conhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Um gap (gap) indica um ponto onde material está omitido na transcrição, seja por razões editoriais descritas no TEI header, como parte de uma prática de amostragem, seja porque o material está ilegível, invisível ou inaudível.

                                                                                                                                                                                                                                                                                                                  Nos casos onde caracteres se perderam no suporte original e não há nada que indique ao editor como estes devem ser restaurados, isto se marca como uma lacuna, com o uso do elemento gap. Observe que este é geralmente um elemento vazio, já que marca um ponto onde ocorre uma lacuna, e portento não existe conteúdo .

                                                                                                                                                                                                                                                                                                                  Para uma lacuna simples, cujo tamanho é conhecido, gap pode receber os três seguintes atributos:

                                                                                                                                                                                                                                                                                                                  • reason explica porque o texto foi restaurado, e no caso de uma lacuna geralmente recebe o valor "lost" (apesar de poder receber outros valores).
                                                                                                                                                                                                                                                                                                                  • quantity indica quantos caracteres ou linhas foram perdidos (nos casos em que se sabe).
                                                                                                                                                                                                                                                                                                                  • unit indica que tipo de unidadede texto se perdeu, como "character" ou "line" (ou mesmo algum outro tipo de unidade textual, como "column", "page" etc.).

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.5: [------]
                                                                                                                                                                                                                                                                                                                  [------]
                                                                                                                                                                                                                                                                                                                  [------]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [3 lines missing]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [------]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [3 lines missing]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [5 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.11.2070)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostlineknown.html b/gl/dev/trans-lostlineknown.html index a8949269d..ea0ed5037 100644 --- a/gl/dev/trans-lostlineknown.html +++ b/gl/dev/trans-lostlineknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost lines, quantity known

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  A gap indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where lines have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content.

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, which for a lacuna is the value "lost".
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).
                                                                                                                                                                                                                                                                                                                  • quantity indicates the number of characters, lines, etc. thought to have been lost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.5: [------]
                                                                                                                                                                                                                                                                                                                  [------]
                                                                                                                                                                                                                                                                                                                  [------]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [3 lines missing]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [------]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [3 lines missing]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [5 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.11.2070)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lost lines, quantity known

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  A gap indicates a point at which material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

                                                                                                                                                                                                                                                                                                                  Where lines have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. Note that this is usually an empty element, as it marks a point at which the lacuna occurs, and therefore does not contain any content.

                                                                                                                                                                                                                                                                                                                  For a straightforward lacuna whose extent is known, gap should take the following three attributes:

                                                                                                                                                                                                                                                                                                                  • reason explains why the text has been restored, which for a lacuna is the value "lost".
                                                                                                                                                                                                                                                                                                                  • unit indicates what kind of textual unit has been lost, such as "character" or "line" (or indeed some other type of textual unit such as "column", "page" etc.).
                                                                                                                                                                                                                                                                                                                  • quantity indicates the number of characters, lines, etc. thought to have been lost.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 8.5: [------]
                                                                                                                                                                                                                                                                                                                  [------]
                                                                                                                                                                                                                                                                                                                  [------]

                                                                                                                                                                                                                                                                                                                  Sosin 2011: [3 lines missing]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="3unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: [------]
                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [3 lines missing]
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostquantity="5unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style: [5 lines missing]
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.11.2070)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostlineunknown-pt-br.html b/gl/dev/trans-lostlineunknown-pt-br.html index 18b97933d..9b2559f5f 100644 --- a/gl/dev/trans-lostlineunknown-pt-br.html +++ b/gl/dev/trans-lostlineunknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Linhas Perdidas, Quantidade Desconhecida

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde linhas se perderam no suporte original e não há nada que indique ao editor como estas devem ser restauradas, isto se marca como uma lacuna, com o uso do elemento gap. Se o númerro de linhas é desconhecido, extent deve receber um valor "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.6; Sosin 2011: - - - - - -

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 177)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:
                                                                                                                                                                                                                                                                                                                    -- -- -- -- -- -- -- -- -- --
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.12.2207)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Linhas Perdidas, Quantidade Desconhecida

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde linhas se perderam no suporte original e não há nada que indique ao editor como estas devem ser restauradas, isto se marca como uma lacuna, com o uso do elemento gap. Se o númerro de linhas é desconhecido, extent deve receber um valor "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.6; Sosin 2011: - - - - - -

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 177)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:
                                                                                                                                                                                                                                                                                                                    -- -- -- -- -- -- -- -- -- --
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.12.2207)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostlineunknown.html b/gl/dev/trans-lostlineunknown.html index d5225d998..e7d16db3a 100644 --- a/gl/dev/trans-lostlineunknown.html +++ b/gl/dev/trans-lostlineunknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lost Lines, Quantity Unknown

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Where lines have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. If the number of lines is unknown, extent should be given a value of "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.6; Sosin 2011: - - - - - -

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 177)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:
                                                                                                                                                                                                                                                                                                                    -- -- -- -- -- -- -- -- -- --
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.12.2207)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lost Lines, Quantity Unknown

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Where lines have been lost on the original support and there is nothing to indicate to the editor how these should be restored, this is marked up as a lacuna using gap. If the number of lines is unknown, extent should be given a value of "unknown".

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.6; Sosin 2011: - - - - - -

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: [·· ? ··]
                                                                                                                                                                                                                                                                                                                  (IRT: 177)
                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • Duke Databank style:
                                                                                                                                                                                                                                                                                                                    -- -- -- -- -- -- -- -- -- --
                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.12.2207)

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostotherunits-pt-br.html b/gl/dev/trans-lostotherunits-pt-br.html index 96c594120..0de3edae1 100644 --- a/gl/dev/trans-lostotherunits-pt-br.html +++ b/gl/dev/trans-lostotherunits-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lacunas, Outras Unidades

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  (Por exemplo, coluna, página, cm, mm, etc.)

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde texto se perdeu, mas deve ser medido em unidades diferentes de 'caracter' ou 'linha', este texto deve ser colocado em um gap e receber um atributo reason com o valor "lost" e um atributo unit com valor "cm", ou qualquer outra undade que o editor necessitar.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="4.2unit="cm"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lacunas, Outras Unidades

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  (Por exemplo, coluna, página, cm, mm, etc.)

                                                                                                                                                                                                                                                                                                                  • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                  Nos casos onde texto se perdeu, mas deve ser medido em unidades diferentes de 'caracter' ou 'linha', este texto deve ser colocado em um gap e receber um atributo reason com o valor "lost" e um atributo unit com valor "cm", ou qualquer outra undade que o editor necessitar.

                                                                                                                                                                                                                                                                                                                  Panciera 1991 VIII.2; Sosin 2011: [...]

                                                                                                                                                                                                                                                                                                                  <gap reason="lostextent="4.2unit="cm"/>
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-lostotherunits.html b/gl/dev/trans-lostotherunits.html index 1befbab7a..7a7a59edc 100644 --- a/gl/dev/trans-lostotherunits.html +++ b/gl/dev/trans-lostotherunits.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Lacunas, Other Units

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Lacunas, Other Units

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-markeddeletion-pt-br.html b/gl/dev/trans-markeddeletion-pt-br.html index 3ca49f883..8722399ab 100644 --- a/gl/dev/trans-markeddeletion-pt-br.html +++ b/gl/dev/trans-markeddeletion-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Marcado para ser Apagado por Barras / Traços Cruzados

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:


                                                                                                                                                                                                                                                                                                                  <!-- example markup -->
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Marcado para ser Apagado por Barras / Traços Cruzados

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:


                                                                                                                                                                                                                                                                                                                  <!-- example markup -->
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-markeddeletion.html b/gl/dev/trans-markeddeletion.html index f5cbebd69..bbc2fd133 100644 --- a/gl/dev/trans-markeddeletion.html +++ b/gl/dev/trans-markeddeletion.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Marked for Deletion by Slashes/Cross Strokes

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:


                                                                                                                                                                                                                                                                                                                  <!-- example markup -->
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Marked for Deletion by Slashes/Cross Strokes

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Panciera 1991 ...; Sosin 2011:


                                                                                                                                                                                                                                                                                                                  <!-- example markup -->
                                                                                                                                                                                                                                                                                                                  (Panciera)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-metricalelements.html b/gl/dev/trans-metricalelements.html index 5630001c8..39a2fe054 100644 --- a/gl/dev/trans-metricalelements.html +++ b/gl/dev/trans-metricalelements.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Metrical elements

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  ....

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <metDecl>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Alice Bencivenni, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-metricaltypology.html b/gl/dev/trans-metricaltypology.html index c79f3a878..458ae3bf7 100644 --- a/gl/dev/trans-metricaltypology.html +++ b/gl/dev/trans-metricaltypology.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Metrical typology

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  • TEI definition: lg ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                    Metrical typology

                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                    • TEI definition: lg ; EpiDoc-specific customization: lg
                                                                                                                                                                                                                                                                                                                    • TEI definition: l ; EpiDoc-specific - customization: l
                                                                                                                                                                                                                                                                                                                    • TEI definition: metDecl

                                                                                                                                                                                                                                                                                                                    ....

                                                                                                                                                                                                                                                                                                                    Example of a taxonomy of types of metre and some metrical features:

                                                                                                                                                                                                                                                                                                                    <classDecl xml:lang="en">
                                                                                                                                                                                                                                                                                                                    <taxonomy xml:id="verse">
                                                                                                                                                                                                                                                                                                                    <category xml:id="dactylic">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Dactylic</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    <category xml:id="dactylic.hexameter">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Dactylic hexameter</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="dactylic.pentameter">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Dactylic pentameter</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="dactylic.elegiac">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Dactylic: elegiac</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="iambo-trochaic">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Iambo-trochaic</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    <category xml:id="iambo-trochaic.senarius">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Iambic senarius</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="iambo-trochaic.septenarius">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Trochaic septenarius</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="nonstandard">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Nonstandard metre</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    </taxonomy>
                                                                                                                                                                                                                                                                                                                    <taxonomy xml:id="scheme">
                                                                                                                                                                                                                                                                                                                    <category xml:id="quantitative">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Quantitative</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="accentuating">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Accentuating</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="mixed">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>mixed</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    </taxonomy>
                                                                                                                                                                                                                                                                                                                    <taxonomy xml:id="pause">
                                                                                                                                                                                                                                                                                                                    <category xml:id="caesura">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Caesura</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="diaeresis">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Diaeresis</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="penthemimeral">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Penthemimeral</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="trithemimeral">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Trithemimeral</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="hephthemimeral">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Hephthemimeral</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    <category xml:id="trochaic">
                                                                                                                                                                                                                                                                                                                    <catDesc>
                                                                                                                                                                                                                                                                                                                    <gloss>Trochaic</gloss>
                                                                                                                                                                                                                                                                                                                    </catDesc>
                                                                                                                                                                                                                                                                                                                    </category>
                                                                                                                                                                                                                                                                                                                    </taxonomy>
                                                                                                                                                                                                                                                                                                                    </classDecl>

                                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                                    Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                    Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                    Other pages describing <metDecl>:

                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                    1. Simona Stoyanova, author
                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                    \ No newline at end of file + customization: l
                                                                                                                                                                                                                                                                                                                  • TEI definition: metDecl

                                                                                                                                                                                                                                                                                                                  ....

                                                                                                                                                                                                                                                                                                                  Example of a taxonomy of types of metre and some metrical features:

                                                                                                                                                                                                                                                                                                                  <classDecl xml:lang="en">
                                                                                                                                                                                                                                                                                                                  <taxonomy xml:id="verse">
                                                                                                                                                                                                                                                                                                                  <category xml:id="dactylic">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Dactylic</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  <category xml:id="dactylic.hexameter">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Dactylic hexameter</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="dactylic.pentameter">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Dactylic pentameter</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="dactylic.elegiac">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Dactylic: elegiac</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="iambo-trochaic">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Iambo-trochaic</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  <category xml:id="iambo-trochaic.senarius">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Iambic senarius</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="iambo-trochaic.septenarius">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Trochaic septenarius</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="nonstandard">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Nonstandard metre</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  </taxonomy>
                                                                                                                                                                                                                                                                                                                  <taxonomy xml:id="scheme">
                                                                                                                                                                                                                                                                                                                  <category xml:id="quantitative">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Quantitative</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="accentuating">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Accentuating</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="mixed">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>mixed</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  </taxonomy>
                                                                                                                                                                                                                                                                                                                  <taxonomy xml:id="pause">
                                                                                                                                                                                                                                                                                                                  <category xml:id="caesura">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Caesura</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="diaeresis">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Diaeresis</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="penthemimeral">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Penthemimeral</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="trithemimeral">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Trithemimeral</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="hephthemimeral">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Hephthemimeral</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  <category xml:id="trochaic">
                                                                                                                                                                                                                                                                                                                  <catDesc>
                                                                                                                                                                                                                                                                                                                  <gloss>Trochaic</gloss>
                                                                                                                                                                                                                                                                                                                  </catDesc>
                                                                                                                                                                                                                                                                                                                  </category>
                                                                                                                                                                                                                                                                                                                  </taxonomy>
                                                                                                                                                                                                                                                                                                                  </classDecl>

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                  Other pages describing <metDecl>:

                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                  1. Simona Stoyanova, author
                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-nonstructural-pt-br.html b/gl/dev/trans-nonstructural-pt-br.html index 4f8ee32be..2cf96a75e 100644 --- a/gl/dev/trans-nonstructural-pt-br.html +++ b/gl/dev/trans-nonstructural-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Partes de Texto Não-Estrutural

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Partes de texto não-estruturtal, por exemplo entre blocos

                                                                                                                                                                                                                                                                                                                  O elemento milestone é utilizado para descrever o suporte, mais que a estrutura do texto. Pode ser usado para marcar um ponto no texto em que o suporte muda de alguma forma , como por exemplo nos casos em que um texto é inscrito em diversos blocos e o editor quer marcar o ponto em que um bloco acaba e outro inicia. Isto pode ser representado dando ao elemento milestone o atributo unit com valor "block". Cada milestone pode também receber um atributo n, permitindo que os blocos (ou quaisquer partes de texto não estrutural que estejam sendo descritas) sejam numerados.

                                                                                                                                                                                                                                                                                                                  according to london: κblock αὶ

                                                                                                                                                                                                                                                                                                                  ὁ Ῥωμαίω<milestone unit="blockn="iii"/>ν καθὼς καὶ τὰ
                                                                                                                                                                                                                                                                                                                  <unclear reason="damage">τ</unclear>
                                                                                                                                                                                                                                                                                                                  <milestone unit="block"/>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">οῦ</supplied>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: τ̣ | [οῦ]
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.174)
                                                                                                                                                                                                                                                                                                                  Clau<milestone unit="unspecifiedrend="bay"/>dio

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: Claudio
                                                                                                                                                                                                                                                                                                                  (IRT: 534)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <milestone>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                  Partes de Texto Não-Estrutural

                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                  Partes de texto não-estruturtal, por exemplo entre blocos

                                                                                                                                                                                                                                                                                                                  O elemento milestone é utilizado para descrever o suporte, mais que a estrutura do texto. Pode ser usado para marcar um ponto no texto em que o suporte muda de alguma forma , como por exemplo nos casos em que um texto é inscrito em diversos blocos e o editor quer marcar o ponto em que um bloco acaba e outro inicia. Isto pode ser representado dando ao elemento milestone o atributo unit com valor "block". Cada milestone pode também receber um atributo n, permitindo que os blocos (ou quaisquer partes de texto não estrutural que estejam sendo descritas) sejam numerados.

                                                                                                                                                                                                                                                                                                                  according to london: κblock αὶ

                                                                                                                                                                                                                                                                                                                  ὁ Ῥωμαίω<milestone unit="blockn="iii"/>ν καθὼς καὶ τὰ
                                                                                                                                                                                                                                                                                                                  <unclear reason="damage">τ</unclear>
                                                                                                                                                                                                                                                                                                                  <milestone unit="block"/>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">οῦ</supplied>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: τ̣ | [οῦ]
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.174)
                                                                                                                                                                                                                                                                                                                  Clau<milestone unit="unspecifiedrend="bay"/>dio

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: Claudio
                                                                                                                                                                                                                                                                                                                  (IRT: 534)

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <milestone>:

                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                  2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                  3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                  Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                  \ No newline at end of file diff --git a/gl/dev/trans-nonstructural.html b/gl/dev/trans-nonstructural.html index c2e9e5d5a..276c62521 100644 --- a/gl/dev/trans-nonstructural.html +++ b/gl/dev/trans-nonstructural.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                  Non-Structural Text-Parts

                                                                                                                                                                                                                                                                                                                  2023-04-27

                                                                                                                                                                                                                                                                                                                  Non-structural text-parts, e.g. between blocks

                                                                                                                                                                                                                                                                                                                  • TEI definition: cb ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                    Non-Structural Text-Parts

                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                    Non-structural text-parts, e.g. between blocks

                                                                                                                                                                                                                                                                                                                    • TEI definition: cb ; EpiDoc-specific customization: cb
                                                                                                                                                                                                                                                                                                                    • TEI definition: milestone ; EpiDoc-specific customization: milestone
                                                                                                                                                                                                                                                                                                                    • TEI definition: pb ; EpiDoc-specific - customization: pb

                                                                                                                                                                                                                                                                                                                    When a physical break in the support does not coincide with a major semantic break in the text and the physical division of the text does not need to be part of the citation scheme for the text as a whole, the milestone or cb or pb elements should be used (instead of <div type="textpart">) to mark the point at which a break in the support occurs.

                                                                                                                                                                                                                                                                                                                    Text flowing through successive zones

                                                                                                                                                                                                                                                                                                                    This can be the case of text laid out in consecutively readable zones (e.g. text split in two or more consecutive columns), or on multiple faces of an object, or on multiple linked objects.

                                                                                                                                                                                                                                                                                                                    If a text is split in two (or more) consecutive columns, the cb (column beginning) element should be used. It is highly recommended to provide an n attribute specifying an identifier for each cb.

                                                                                                                                                                                                                                                                                                                    <ab>
                                                                                                                                                                                                                                                                                                                     <cb n="i"/>
                                                                                                                                                                                                                                                                                                                     <lb n="1"/>... <lb n="2"/>... <cb n="ii"/>
                                                                                                                                                                                                                                                                                                                     <lb n="3"/>... <lb n="4"/>...
                                                                                                                                                                                                                                                                                                                    </ab>
                                                                                                                                                                                                                                                                                                                    <div type="editionxml:lang="grc"
                                                                                                                                                                                                                                                                                                                     xml:space="preserve">
                                                                                                                                                                                                                                                                                                                    + customization: pb

                                                                                                                                                                                                                                                                                                                  When a physical break in the support does not coincide with a major semantic break in the text and the physical division of the text does not need to be part of the citation scheme for the text as a whole, the milestone or cb or pb elements should be used (instead of <div type="textpart">) to mark the point at which a break in the support occurs.

                                                                                                                                                                                                                                                                                                                  Text flowing through successive zones

                                                                                                                                                                                                                                                                                                                  This can be the case of text laid out in consecutively readable zones (e.g. text split in two or more consecutive columns), or on multiple faces of an object, or on multiple linked objects.

                                                                                                                                                                                                                                                                                                                  If a text is split in two (or more) consecutive columns, the cb (column beginning) element should be used. It is highly recommended to provide an n attribute specifying an identifier for each cb.

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <cb n="i"/>
                                                                                                                                                                                                                                                                                                                   <lb n="1"/>... <lb n="2"/>... <cb n="ii"/>
                                                                                                                                                                                                                                                                                                                   <lb n="3"/>... <lb n="4"/>...
                                                                                                                                                                                                                                                                                                                  </ab>
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="grc"
                                                                                                                                                                                                                                                                                                                   xml:space="preserve">
                                                                                                                                                                                                                                                                                                                                          <ab>                             <cb n="A"/>                             <lb n="0"/><gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                  @@ -64,7 +64,7 @@                             ναεύ<lb break="non="32"/>ηι, ἐμπανία                              δεικσάτ<lb break="non="33"/>ο.                         </ab> -                    
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="la"
                                                                                                                                                                                                                                                                                                                   xml:space="preserve">
                                                                                                                                                                                                                                                                                                                  +                    
                                                                                                                                                                                                                                                                                                                  </div>
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="la"
                                                                                                                                                                                                                                                                                                                   xml:space="preserve">
                                                                                                                                                                                                                                                                                                                                  <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                   n="b">
                                                                                                                                                                                                                                                                                                                                      <ab>                         <cb n="ii"/> @@ -81,7 +81,7 @@                         <lb n="iii.4"/>sim actura haec <unclear>no</unclear>bi<unclear>s</unclear>                     </ab>                 </div> -            
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  If a text is split in two (or more) consecutive zones that could be considered as pages, the pb (page beginning) element should be used. It is highly recommended to provide an n attribute specifying an identifier for each pb. This can be the case of Indian copper plates bound together with a ring passed through a hole on each plate (a photo of one of these copper plates sets can be found here: https://commons.wikimedia.org/wiki/File:BLL826_INDCH64R_01_L.jpg). Here an example from the DHARMA project:

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <pb n="1v"/>
                                                                                                                                                                                                                                                                                                                    <lb n="1"/>svasti śrīmaT-calukya-kula-jalanidhi-samudito
                                                                                                                                                                                                                                                                                                                     nr̥pati-niśākaraḥ sva<lb n="2break="no"/>... ... <lb n="5break="no"/>...
                                                                                                                                                                                                                                                                                                                     yuvatiṣu madanāyamāna-cāru-śarīratvān makara-dhvajaḥ <pb n="2r"/>
                                                                                                                                                                                                                                                                                                                    <lb n="6"/>sva-dānārṇṇaveṣu parimagna-kali-prabhāvaḥ ... ... <lb n="10break="no"/>...
                                                                                                                                                                                                                                                                                                                     brahmaśarmmaṇaḥ pautrābhyāṁ Adhi<pb n="2vbreak="no"/>
                                                                                                                                                                                                                                                                                                                    <lb n="11break="no"/>gata-sva-śākhā-codita-sva-karmmānuṣṭhāna-tatparasya ...
                                                                                                                                                                                                                                                                                                                     ...<lb n="15break="no"/>... grāmo yaṁ dattaḥ Asya <pb n="3r"/>
                                                                                                                                                                                                                                                                                                                    <lb n="16"/>kaiścid api na
                                                                                                                                                                                                                                                                                                                     bādhā karaṇīyā ... </ab>
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  If a text is split in more consecutively readable zones (not columns or pages), the milestone element should be used. In this case, it is highly recommended to provide both an n attribute specifying an identifier for each milestone and a unit attribute specifying the kind of subdivision of text being recorded (common values for the unit attribute might be "face", "area", "zone", "item", etc.).

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <milestone unit="facen="a"/>
                                                                                                                                                                                                                                                                                                                   <lb n="1"/>... <lb n="2"/>... <milestone unit="facen="b"/>
                                                                                                                                                                                                                                                                                                                   <lb n="3"/>... <lb n="4"/>...
                                                                                                                                                                                                                                                                                                                  </ab>
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="la"
                                                                                                                                                                                                                                                                                                                   xml:space="preserve">
                                                                                                                                                                                                                                                                                                                  +            
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  If a text is split in two (or more) consecutive zones that could be considered as pages, the pb (page beginning) element should be used. It is highly recommended to provide an n attribute specifying an identifier for each pb. This can be the case of Indian copper plates bound together with a ring passed through a hole on each plate (a photo of one of these copper plates sets can be found here: https://commons.wikimedia.org/wiki/File:BLL826_INDCH64R_01_L.jpg). Here an example from the DHARMA project:

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <pb n="1v"/>
                                                                                                                                                                                                                                                                                                                    <lb n="1"/>svasti śrīmaT-calukya-kula-jalanidhi-samudito
                                                                                                                                                                                                                                                                                                                     nr̥pati-niśākaraḥ sva<lb n="2break="no"/>... ... <lb n="5break="no"/>...
                                                                                                                                                                                                                                                                                                                     yuvatiṣu madanāyamāna-cāru-śarīratvān makara-dhvajaḥ <pb n="2r"/>
                                                                                                                                                                                                                                                                                                                    <lb n="6"/>sva-dānārṇṇaveṣu parimagna-kali-prabhāvaḥ ... ... <lb n="10break="no"/>...
                                                                                                                                                                                                                                                                                                                     brahmaśarmmaṇaḥ pautrābhyāṁ Adhi<pb n="2vbreak="no"/>
                                                                                                                                                                                                                                                                                                                    <lb n="11break="no"/>gata-sva-śākhā-codita-sva-karmmānuṣṭhāna-tatparasya ...
                                                                                                                                                                                                                                                                                                                     ...<lb n="15break="no"/>... grāmo yaṁ dattaḥ Asya <pb n="3r"/>
                                                                                                                                                                                                                                                                                                                    <lb n="16"/>kaiścid api na
                                                                                                                                                                                                                                                                                                                     bādhā karaṇīyā ... </ab>
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  If a text is split in more consecutively readable zones (not columns or pages), the milestone element should be used. In this case, it is highly recommended to provide both an n attribute specifying an identifier for each milestone and a unit attribute specifying the kind of subdivision of text being recorded (common values for the unit attribute might be "face", "area", "zone", "item", etc.).

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <milestone unit="facen="a"/>
                                                                                                                                                                                                                                                                                                                   <lb n="1"/>... <lb n="2"/>... <milestone unit="facen="b"/>
                                                                                                                                                                                                                                                                                                                   <lb n="3"/>... <lb n="4"/>...
                                                                                                                                                                                                                                                                                                                  </ab>
                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="la"
                                                                                                                                                                                                                                                                                                                   xml:space="preserve">
                                                                                                                                                                                                                                                                                                                                  <ab>                     <milestone unit="tabletn="1"/>                     <lb n="i.1"/><gap reason="illegiblequantity="9"
                                                                                                                                                                                                                                                                                                                   unit="line">
                                                                                                                                                                                                                                                                                                                  <desc>traces of nine lines</desc></gap> @@ -91,4 +91,4 @@                     <lb n="ii.1"/><supplied reason="lost">pertinebit</supplied> <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="character"/>
                                                                                                                                                                                                                                                                                                                                      <lb/><gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                   unit="line"/>
                                                                                                                                                                                                                                                                                                                                  </ab> -            
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, two connected fragments where the break is fortuitously between lines, so that no epigraphic line is interrupted by the fracture. The text on the second fragment is the continuation of that on the first, so textparts were not deemed appropriate here:

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="1"/>
                                                                                                                                                                                                                                                                                                                    <milestone unit="fragmentn="A"/>siddhaM</ab>
                                                                                                                                                                                                                                                                                                                   <lg n="1met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                    <l n="a">sahasra-śirase tasmai</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                   <lg n="14met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                    <l n="a">duhitur bbalaśūrāyā<supplied reason="omitted"></supplied>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                    <l n="b">satputro jayamit<unclear>r</unclear>a<unclear>y</unclear>ā</l>
                                                                                                                                                                                                                                                                                                                    <l n="c">
                                                                                                                                                                                                                                                                                                                     <lb n="10"/>
                                                                                                                                                                                                                                                                                                                     <milestone unit="fragmentn="B"/>gārggāyaṇa-sagotro
                                                                                                                                                                                                                                                                                                                       vai</l>
                                                                                                                                                                                                                                                                                                                    <l n="d">jāti<unclear>ta</unclear>
                                                                                                                                                                                                                                                                                                                     <supplied reason="lost"></supplied>
                                                                                                                                                                                                                                                                                                                     <seg met="=-+-=">
                                                                                                                                                                                                                                                                                                                      <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                       unit="character"/>

                                                                                                                                                                                                                                                                                                                     </seg>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, the text is inscribed on two separate doorjambs, continuing from the bottom of one to the top of the other. The inscription begins with a series of verses in Sanskrit, followed by Khmer prose (starting at some point on the second doorjamb):

                                                                                                                                                                                                                                                                                                                  <div type="edition"
                                                                                                                                                                                                                                                                                                                   xml:lang="x-oldkhmer-Latn">

                                                                                                                                                                                                                                                                                                                   <lg n="1met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                    xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <milestone unit="itemn="S"/>
                                                                                                                                                                                                                                                                                                                     <label xml:lang="en">Southern
                                                                                                                                                                                                                                                                                                                         Doorjamb</label>
                                                                                                                                                                                                                                                                                                                     <lb n="S1"/>jejīyatāṁ vraja <seg met="-+--+-+=">
                                                                                                                                                                                                                                                                                                                      <gap reason="lostquantity="8"
                                                                                                                                                                                                                                                                                                                       unit="character"/>

                                                                                                                                                                                                                                                                                                                     </seg>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                   <lg n="17met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                    xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <milestone unit="itemn="N"/>
                                                                                                                                                                                                                                                                                                                     <label xml:lang="en">Northern
                                                                                                                                                                                                                                                                                                                         Doorjamb</label>
                                                                                                                                                                                                                                                                                                                     <lb n="N1"/>Agre-saraḥ prathita-puṇyavatāṁ
                                                                                                                                                                                                                                                                                                                       sva-puṇyaiś</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--more <lg>s here, then a prose section in Khmer-->
                                                                                                                                                                                                                                                                                                                   <ab>
                                                                                                                                                                                                                                                                                                                    <lb n="N17"/>ta duk· śloka neḥ mratāñ· śrī Indrapaṇ<orig>d</orig>ita</ab>
                                                                                                                                                                                                                                                                                                                  <!--more <ab>s here-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  Text running across contiguous zones

                                                                                                                                                                                                                                                                                                                  This can be the case of a surface vertically segmented into units where each line runs across two or more visually demarcated areas such as a surface with each line running across several building blocks, quasi-columns consisting of a metrical unit, a surface with each line running across two or more subsurfaces (e.g. two or more adjacent faces of a stele or pillar), a broken support where a fracture cuts across some or all lines (i.e. contiguous fragments).

                                                                                                                                                                                                                                                                                                                  In these cases, an iterated milestone should be used to show the points at which one zone ends and another begins. It is highly recommended to provide both an n attribute specifying an identifier for each milestone and a unit attribute specifying the kind of subdivision of text being recorded (common values for the unit attribute might be "block", "face", "area", "zone", "column", etc.).

                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="1"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="blockn="i"/>...<milestone unit="blockn="ii"/> ...
                                                                                                                                                                                                                                                                                                                  <lb n="2"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="blockn="i"/>...<milestone unit="blockn="ii"/>
                                                                                                                                                                                                                                                                                                                  ... <lb n="3"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="blockn="i"/>...<milestone unit="blockn="ii"/>
                                                                                                                                                                                                                                                                                                                  ...
                                                                                                                                                                                                                                                                                                                  </ab>
                                                                                                                                                                                                                                                                                                                  ὁ Ῥωμαίω<milestone unit="blockn="iii"/>ν καθὼς καὶ τὰ
                                                                                                                                                                                                                                                                                                                  <unclear reason="damage">τ</unclear>
                                                                                                                                                                                                                                                                                                                  <milestone unit="block"/>
                                                                                                                                                                                                                                                                                                                  <supplied reason="lost">οῦ</supplied>

                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                  • London style: τ̣ | [οῦ]
                                                                                                                                                                                                                                                                                                                  (InsAph: 1.174)
                                                                                                                                                                                                                                                                                                                  <lg>
                                                                                                                                                                                                                                                                                                                   <l>
                                                                                                                                                                                                                                                                                                                    <lb n="1"/>
                                                                                                                                                                                                                                                                                                                    <milestone unit="zonen="a"/>...</l>
                                                                                                                                                                                                                                                                                                                   <l>
                                                                                                                                                                                                                                                                                                                    <milestone unit="zonen="b"/>...</l>
                                                                                                                                                                                                                                                                                                                  </lg>
                                                                                                                                                                                                                                                                                                                  <lg>
                                                                                                                                                                                                                                                                                                                   <l>
                                                                                                                                                                                                                                                                                                                    <lb n="2"/>
                                                                                                                                                                                                                                                                                                                    <milestone unit="zonen="a"/>...</l>
                                                                                                                                                                                                                                                                                                                   <l>
                                                                                                                                                                                                                                                                                                                    <milestone unit="zonen="b"/>...</l>
                                                                                                                                                                                                                                                                                                                  </lg>
                                                                                                                                                                                                                                                                                                                  <ab>
                                                                                                                                                                                                                                                                                                                   <lb n="1"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="a"/>...<gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="b"/>... <lb n="2"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="a"/>...<gap reason="lostquantity="2"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="b"/>... <lb n="3"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="a"/>...<gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                    unit="character"/>

                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="b"/>... <lb n="4"/>
                                                                                                                                                                                                                                                                                                                   <milestone unit="fragmentn="a"/>...<milestone unit="fragmentn="b"/>...
                                                                                                                                                                                                                                                                                                                  </ab>

                                                                                                                                                                                                                                                                                                                  In the following example from DHARMA, two fragments with the break cutting across lines, so that the milestone for fragment A is iterated at the beginning of each epigraphic line, and that for fragment B at some point within each epigraphic line:

                                                                                                                                                                                                                                                                                                                  <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                   <lg n="1met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                    <l n="a">
                                                                                                                                                                                                                                                                                                                     <lb n="1"/>
                                                                                                                                                                                                                                                                                                                     <milestone unit="fragmentn="A"/>guptānāṁ samatikrānte</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">sapta-paṁcāśad-uttare</l>
                                                                                                                                                                                                                                                                                                                    <l n="c">śate samānāṁ pr̥thivīṁ</l>
                                                                                                                                                                                                                                                                                                                    <l n="d">budhagu<supplied reason="lost">pte</supplied>
                                                                                                                                                                                                                                                                                                                     <milestone unit="fragmentn="B"/>praśāsati<unclear>||</unclear>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                   <lg n="2met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                    <l n="a">vaiśākha-māsa-saptamyāṁ</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">mūle śma<lb n="2break="no"/>
                                                                                                                                                                                                                                                                                                                     <milestone unit="fragmentn="A"/>-<unclear cert="low">pragate</unclear>
                                                                                                                                                                                                                                                                                                                     <lb n="2"/>mayā</l>
                                                                                                                                                                                                                                                                                                                    <l n="c">
                                                                                                                                                                                                                                                                                                                     <unclear cert="low">kāritābhayamitreṇa</unclear>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                    <l n="d">pratimā śākya-bhikṣuṇā||</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                   <lg n="3met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                    <l n="aenjamb="yes">imām <supplied reason="lostcert="low">uddhasta-sa</supplied>
                                                                                                                                                                                                                                                                                                                     <milestone unit="fragmentn="B"/>
                                                                                                                                                                                                                                                                                                                     <unclear>ccha</unclear>ttra</l>
                                                                                                                                                                                                                                                                                                                    <l n="b">-padmāsana-vibhūṣitāṁ</l>
                                                                                                                                                                                                                                                                                                                    <l n="c">deva-puttravato <unclear>divyāṁ</unclear>
                                                                                                                                                                                                                                                                                                                    </l>
                                                                                                                                                                                                                                                                                                                    <l n="d">
                                                                                                                                                                                                                                                                                                                     <lb n="3"/>
                                                                                                                                                                                                                                                                                                                     <milestone unit="fragmentn="A"/>...</l>
                                                                                                                                                                                                                                                                                                                   </lg>
                                                                                                                                                                                                                                                                                                                  <!--etc.-->
                                                                                                                                                                                                                                                                                                                  </div>

                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                  Other pages describing <cb>:

                                                                                                                                                                                                                                                                                                                    Other pages describing <milestone>:

                                                                                                                                                                                                                                                                                                                    Other pages describing <pb>:

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                      3. Irene Vagionakis, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +            
                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                      (Source)

                                                                                                                                                                                                                                                                                                                      In the following example from DHARMA, two connected fragments where the break is fortuitously between lines, so that no epigraphic line is interrupted by the fracture. The text on the second fragment is the continuation of that on the first, so textparts were not deemed appropriate here:

                                                                                                                                                                                                                                                                                                                      <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                       <ab>
                                                                                                                                                                                                                                                                                                                        <lb n="1"/>
                                                                                                                                                                                                                                                                                                                        <milestone unit="fragmentn="A"/>siddhaM</ab>
                                                                                                                                                                                                                                                                                                                       <lg n="1met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                        <l n="a">sahasra-śirase tasmai</l>
                                                                                                                                                                                                                                                                                                                        <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                      <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                       <lg n="14met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                        <l n="a">duhitur bbalaśūrāyā<supplied reason="omitted"></supplied>
                                                                                                                                                                                                                                                                                                                        </l>
                                                                                                                                                                                                                                                                                                                        <l n="b">satputro jayamit<unclear>r</unclear>a<unclear>y</unclear>ā</l>
                                                                                                                                                                                                                                                                                                                        <l n="c">
                                                                                                                                                                                                                                                                                                                         <lb n="10"/>
                                                                                                                                                                                                                                                                                                                         <milestone unit="fragmentn="B"/>gārggāyaṇa-sagotro
                                                                                                                                                                                                                                                                                                                           vai</l>
                                                                                                                                                                                                                                                                                                                        <l n="d">jāti<unclear>ta</unclear>
                                                                                                                                                                                                                                                                                                                         <supplied reason="lost"></supplied>
                                                                                                                                                                                                                                                                                                                         <seg met="=-+-=">
                                                                                                                                                                                                                                                                                                                          <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                           unit="character"/>

                                                                                                                                                                                                                                                                                                                         </seg>
                                                                                                                                                                                                                                                                                                                        </l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                      <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                      In the following example from DHARMA, the text is inscribed on two separate doorjambs, continuing from the bottom of one to the top of the other. The inscription begins with a series of verses in Sanskrit, followed by Khmer prose (starting at some point on the second doorjamb):

                                                                                                                                                                                                                                                                                                                      <div type="edition"
                                                                                                                                                                                                                                                                                                                       xml:lang="x-oldkhmer-Latn">

                                                                                                                                                                                                                                                                                                                       <lg n="1met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                        xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                        <l n="a">
                                                                                                                                                                                                                                                                                                                         <milestone unit="itemn="S"/>
                                                                                                                                                                                                                                                                                                                         <label xml:lang="en">Southern
                                                                                                                                                                                                                                                                                                                             Doorjamb</label>
                                                                                                                                                                                                                                                                                                                         <lb n="S1"/>jejīyatāṁ vraja <seg met="-+--+-+=">
                                                                                                                                                                                                                                                                                                                          <gap reason="lostquantity="8"
                                                                                                                                                                                                                                                                                                                           unit="character"/>

                                                                                                                                                                                                                                                                                                                         </seg>
                                                                                                                                                                                                                                                                                                                        </l>
                                                                                                                                                                                                                                                                                                                        <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                      <!--more <lg>s here-->
                                                                                                                                                                                                                                                                                                                       <lg n="17met="vasantatilakā"
                                                                                                                                                                                                                                                                                                                        xml:lang="san-Latn">

                                                                                                                                                                                                                                                                                                                        <l n="a">
                                                                                                                                                                                                                                                                                                                         <milestone unit="itemn="N"/>
                                                                                                                                                                                                                                                                                                                         <label xml:lang="en">Northern
                                                                                                                                                                                                                                                                                                                             Doorjamb</label>
                                                                                                                                                                                                                                                                                                                         <lb n="N1"/>Agre-saraḥ prathita-puṇyavatāṁ
                                                                                                                                                                                                                                                                                                                           sva-puṇyaiś</l>
                                                                                                                                                                                                                                                                                                                        <l n="b">...</l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                      <!--more <lg>s here, then a prose section in Khmer-->
                                                                                                                                                                                                                                                                                                                       <ab>
                                                                                                                                                                                                                                                                                                                        <lb n="N17"/>ta duk· śloka neḥ mratāñ· śrī Indrapaṇ<orig>d</orig>ita</ab>
                                                                                                                                                                                                                                                                                                                      <!--more <ab>s here-->
                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                      Text running across contiguous zones

                                                                                                                                                                                                                                                                                                                      This can be the case of a surface vertically segmented into units where each line runs across two or more visually demarcated areas such as a surface with each line running across several building blocks, quasi-columns consisting of a metrical unit, a surface with each line running across two or more subsurfaces (e.g. two or more adjacent faces of a stele or pillar), a broken support where a fracture cuts across some or all lines (i.e. contiguous fragments).

                                                                                                                                                                                                                                                                                                                      In these cases, an iterated milestone should be used to show the points at which one zone ends and another begins. It is highly recommended to provide both an n attribute specifying an identifier for each milestone and a unit attribute specifying the kind of subdivision of text being recorded (common values for the unit attribute might be "block", "face", "area", "zone", "column", etc.).

                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                       <lb n="1"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="blockn="i"/>...<milestone unit="blockn="ii"/> ...
                                                                                                                                                                                                                                                                                                                      <lb n="2"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="blockn="i"/>...<milestone unit="blockn="ii"/>
                                                                                                                                                                                                                                                                                                                      ... <lb n="3"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="blockn="i"/>...<milestone unit="blockn="ii"/>
                                                                                                                                                                                                                                                                                                                      ...
                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                      ὁ Ῥωμαίω<milestone unit="blockn="iii"/>ν καθὼς καὶ τὰ
                                                                                                                                                                                                                                                                                                                      <unclear reason="damage">τ</unclear>
                                                                                                                                                                                                                                                                                                                      <milestone unit="block"/>
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">οῦ</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: τ̣ | [οῦ]
                                                                                                                                                                                                                                                                                                                      (InsAph: 1.174)
                                                                                                                                                                                                                                                                                                                      <lg>
                                                                                                                                                                                                                                                                                                                       <l>
                                                                                                                                                                                                                                                                                                                        <lb n="1"/>
                                                                                                                                                                                                                                                                                                                        <milestone unit="zonen="a"/>...</l>
                                                                                                                                                                                                                                                                                                                       <l>
                                                                                                                                                                                                                                                                                                                        <milestone unit="zonen="b"/>...</l>
                                                                                                                                                                                                                                                                                                                      </lg>
                                                                                                                                                                                                                                                                                                                      <lg>
                                                                                                                                                                                                                                                                                                                       <l>
                                                                                                                                                                                                                                                                                                                        <lb n="2"/>
                                                                                                                                                                                                                                                                                                                        <milestone unit="zonen="a"/>...</l>
                                                                                                                                                                                                                                                                                                                       <l>
                                                                                                                                                                                                                                                                                                                        <milestone unit="zonen="b"/>...</l>
                                                                                                                                                                                                                                                                                                                      </lg>
                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                       <lb n="1"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="a"/>...<gap reason="lostquantity="3"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="b"/>... <lb n="2"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="a"/>...<gap reason="lostquantity="2"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="b"/>... <lb n="3"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="a"/>...<gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="b"/>... <lb n="4"/>
                                                                                                                                                                                                                                                                                                                       <milestone unit="fragmentn="a"/>...<milestone unit="fragmentn="b"/>...
                                                                                                                                                                                                                                                                                                                      </ab>

                                                                                                                                                                                                                                                                                                                      In the following example from DHARMA, two fragments with the break cutting across lines, so that the milestone for fragment A is iterated at the beginning of each epigraphic line, and that for fragment B at some point within each epigraphic line:

                                                                                                                                                                                                                                                                                                                      <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                       <lg n="1met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                        <l n="a">
                                                                                                                                                                                                                                                                                                                         <lb n="1"/>
                                                                                                                                                                                                                                                                                                                         <milestone unit="fragmentn="A"/>guptānāṁ samatikrānte</l>
                                                                                                                                                                                                                                                                                                                        <l n="b">sapta-paṁcāśad-uttare</l>
                                                                                                                                                                                                                                                                                                                        <l n="c">śate samānāṁ pr̥thivīṁ</l>
                                                                                                                                                                                                                                                                                                                        <l n="d">budhagu<supplied reason="lost">pte</supplied>
                                                                                                                                                                                                                                                                                                                         <milestone unit="fragmentn="B"/>praśāsati<unclear>||</unclear>
                                                                                                                                                                                                                                                                                                                        </l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                       <lg n="2met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                        <l n="a">vaiśākha-māsa-saptamyāṁ</l>
                                                                                                                                                                                                                                                                                                                        <l n="b">mūle śma<lb n="2break="no"/>
                                                                                                                                                                                                                                                                                                                         <milestone unit="fragmentn="A"/>-<unclear cert="low">pragate</unclear>
                                                                                                                                                                                                                                                                                                                         <lb n="2"/>mayā</l>
                                                                                                                                                                                                                                                                                                                        <l n="c">
                                                                                                                                                                                                                                                                                                                         <unclear cert="low">kāritābhayamitreṇa</unclear>
                                                                                                                                                                                                                                                                                                                        </l>
                                                                                                                                                                                                                                                                                                                        <l n="d">pratimā śākya-bhikṣuṇā||</l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                       <lg n="3met="anuṣṭubh">
                                                                                                                                                                                                                                                                                                                        <l n="aenjamb="yes">imām <supplied reason="lostcert="low">uddhasta-sa</supplied>
                                                                                                                                                                                                                                                                                                                         <milestone unit="fragmentn="B"/>
                                                                                                                                                                                                                                                                                                                         <unclear>ccha</unclear>ttra</l>
                                                                                                                                                                                                                                                                                                                        <l n="b">-padmāsana-vibhūṣitāṁ</l>
                                                                                                                                                                                                                                                                                                                        <l n="c">deva-puttravato <unclear>divyāṁ</unclear>
                                                                                                                                                                                                                                                                                                                        </l>
                                                                                                                                                                                                                                                                                                                        <l n="d">
                                                                                                                                                                                                                                                                                                                         <lb n="3"/>
                                                                                                                                                                                                                                                                                                                         <milestone unit="fragmentn="A"/>...</l>
                                                                                                                                                                                                                                                                                                                       </lg>
                                                                                                                                                                                                                                                                                                                      <!--etc.-->
                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                      Other pages describing <cb>:

                                                                                                                                                                                                                                                                                                                      Other pages describing <milestone>:

                                                                                                                                                                                                                                                                                                                      Other pages describing <pb>:

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                      3. Irene Vagionakis, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numacrophonic-pt-br.html b/gl/dev/trans-numacrophonic-pt-br.html index 386e25729..e06750130 100644 --- a/gl/dev/trans-numacrophonic-pt-br.html +++ b/gl/dev/trans-numacrophonic-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Números Acrofônicos

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      Sinais de numeral acrofônico usam a primeira letra de certos números e valores de moeda para representar o todo: pi representa πέντε, delta representa δέκα, heta representa ἑκατόν, e assim por diante. Sinais individuais podem ser combinados dentro de um único caracter pararepresentar valores compostos: o valor 50, por exemplo, no sistema acrofônico, é representado por um delta (δέκα: 10) escrito dentro de um pi (πέντε: 5), para indicar 5 x 10.

                                                                                                                                                                                                                                                                                                                      Os numerais acrofônicos gregos estão agora em Unicode, e o EpiDoc recomenda que estes caracteres sejam utilizados e recebam a marcação normal para qualquer outro numeral ou símbolo monetário.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <measure type="currencyunit="stater">
                                                                                                                                                                                                                                                                                                                       <num value="50type="acrophonic"/>
                                                                                                                                                                                                                                                                                                                      </measure>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Números Acrofônicos

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      Sinais de numeral acrofônico usam a primeira letra de certos números e valores de moeda para representar o todo: pi representa πέντε, delta representa δέκα, heta representa ἑκατόν, e assim por diante. Sinais individuais podem ser combinados dentro de um único caracter pararepresentar valores compostos: o valor 50, por exemplo, no sistema acrofônico, é representado por um delta (δέκα: 10) escrito dentro de um pi (πέντε: 5), para indicar 5 x 10.

                                                                                                                                                                                                                                                                                                                      Os numerais acrofônicos gregos estão agora em Unicode, e o EpiDoc recomenda que estes caracteres sejam utilizados e recebam a marcação normal para qualquer outro numeral ou símbolo monetário.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <measure type="currencyunit="stater">
                                                                                                                                                                                                                                                                                                                       <num value="50type="acrophonic"/>
                                                                                                                                                                                                                                                                                                                      </measure>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numacrophonic.html b/gl/dev/trans-numacrophonic.html index 246d45b89..e2082df46 100644 --- a/gl/dev/trans-numacrophonic.html +++ b/gl/dev/trans-numacrophonic.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Acrophonic Numbers

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      Acrophonic numeral signs use the first letter of certain numbers and currency values to stand for the whole: pi stands for πέντε, delta for δέκα, heta for ἑκατόν, and so on. Individual signs may be combined within a single character to represent compound values: the value 50, for example, in the acrophonic system is represented by a delta (δέκα: 10) written within a pi (πέντε: 5), to indicate 5 x 10.

                                                                                                                                                                                                                                                                                                                      The Greek acrophonic numerals are now in Unicode, and EpiDoc recommends that these characters now be used and simply tagged as any other numeral or currency measure.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <measure type="currencyunit="stater">
                                                                                                                                                                                                                                                                                                                       <num value="50type="acrophonic"/>
                                                                                                                                                                                                                                                                                                                      </measure>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Acrophonic Numbers

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      Acrophonic numeral signs use the first letter of certain numbers and currency values to stand for the whole: pi stands for πέντε, delta for δέκα, heta for ἑκατόν, and so on. Individual signs may be combined within a single character to represent compound values: the value 50, for example, in the acrophonic system is represented by a delta (δέκα: 10) written within a pi (πέντε: 5), to indicate 5 x 10.

                                                                                                                                                                                                                                                                                                                      The Greek acrophonic numerals are now in Unicode, and EpiDoc recommends that these characters now be used and simply tagged as any other numeral or currency measure.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <measure type="currencyunit="stater">
                                                                                                                                                                                                                                                                                                                       <num value="50type="acrophonic"/>
                                                                                                                                                                                                                                                                                                                      </measure>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numknown-pt-br.html b/gl/dev/trans-numknown-pt-br.html index c52741066..c5d6c4cf1 100644 --- a/gl/dev/trans-numknown-pt-br.html +++ b/gl/dev/trans-numknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Números/Numerais de Valor Conhecido

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      O numeral deve ser colocado dentro de um elemento num e receber o atributo value apropriado, como "8", "42", etc. Se for um tipo particular de numeral, por exemplo, acrofônico, pode receber um atributo type com o valor "acrophonic".

                                                                                                                                                                                                                                                                                                                      Sosin 2011: XII

                                                                                                                                                                                                                                                                                                                      <num value="12">XII</num>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <num value="12">ιβ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: ιβ´
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ιβ
                                                                                                                                                                                                                                                                                                                      (InsAph: 8.58)
                                                                                                                                                                                                                                                                                                                      <num value="24">XXIIII</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: XXIIII
                                                                                                                                                                                                                                                                                                                      (IRT: 22)
                                                                                                                                                                                                                                                                                                                      <num value="54">νδ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: νδ
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.10#8)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Números/Numerais de Valor Conhecido

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      O numeral deve ser colocado dentro de um elemento num e receber o atributo value apropriado, como "8", "42", etc. Se for um tipo particular de numeral, por exemplo, acrofônico, pode receber um atributo type com o valor "acrophonic".

                                                                                                                                                                                                                                                                                                                      Sosin 2011: XII

                                                                                                                                                                                                                                                                                                                      <num value="12">XII</num>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <num value="12">ιβ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: ιβ´
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ιβ
                                                                                                                                                                                                                                                                                                                      (InsAph: 8.58)
                                                                                                                                                                                                                                                                                                                      <num value="24">XXIIII</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: XXIIII
                                                                                                                                                                                                                                                                                                                      (IRT: 22)
                                                                                                                                                                                                                                                                                                                      <num value="54">νδ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: νδ
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.10#8)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numknown.html b/gl/dev/trans-numknown.html index 5fa4fcdbe..068b889da 100644 --- a/gl/dev/trans-numknown.html +++ b/gl/dev/trans-numknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Numbers/numerals of Known Value

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      The numeral should be placed inside a num and given an appropriate value, e.g. "8", "42", etc. If it is a particular kind of numeral, e.g. acrophonic, it can be given a type with a value of "acrophonic".

                                                                                                                                                                                                                                                                                                                      Panciera 1991: XII

                                                                                                                                                                                                                                                                                                                      <num value="12">XII</num>

                                                                                                                                                                                                                                                                                                                      The following examples, taken from real EpiDoc projects, show a few more kinds of numerals and their rendition.

                                                                                                                                                                                                                                                                                                                      <num value="12">ιβ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: ιβ´
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ιβ
                                                                                                                                                                                                                                                                                                                      (InsAph: 8.58)
                                                                                                                                                                                                                                                                                                                      <num value="24">XXIIII</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: XXIIII
                                                                                                                                                                                                                                                                                                                      (IRT: 22)
                                                                                                                                                                                                                                                                                                                      <num value="54">νδ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: νδ´
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: νδ
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.10#8)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Numbers/numerals of Known Value

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      The numeral should be placed inside a num and given an appropriate value, e.g. "8", "42", etc. If it is a particular kind of numeral, e.g. acrophonic, it can be given a type with a value of "acrophonic".

                                                                                                                                                                                                                                                                                                                      Panciera 1991: XII

                                                                                                                                                                                                                                                                                                                      <num value="12">XII</num>

                                                                                                                                                                                                                                                                                                                      The following examples, taken from real EpiDoc projects, show a few more kinds of numerals and their rendition.

                                                                                                                                                                                                                                                                                                                      <num value="12">ιβ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: ιβ´
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ιβ
                                                                                                                                                                                                                                                                                                                      (InsAph: 8.58)
                                                                                                                                                                                                                                                                                                                      <num value="24">XXIIII</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: XXIIII
                                                                                                                                                                                                                                                                                                                      (IRT: 22)
                                                                                                                                                                                                                                                                                                                      <num value="54">νδ</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: νδ´
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: νδ
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.10#8)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numnoncongruent-pt-br.html b/gl/dev/trans-numnoncongruent-pt-br.html index e9016882a..8778b186c 100644 --- a/gl/dev/trans-numnoncongruent-pt-br.html +++ b/gl/dev/trans-numnoncongruent-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Números com Valores Não-Sequenciais

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Números com valores possíveis que não ser expressos dentro de uma sequência ou espectro.

                                                                                                                                                                                                                                                                                                                      • TEI definition: certainty ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                        Números com Valores Não-Sequenciais

                                                                                                                                                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                                                                                                                                                        Números com valores possíveis que não ser expressos dentro de uma sequência ou espectro.

                                                                                                                                                                                                                                                                                                                        • TEI definition: certainty ; EpiDoc-specific customization: certainty
                                                                                                                                                                                                                                                                                                                        • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                        Alguns números, principalmente se estiverem danificados ou incompletos, podem ser parcialmente mas não completamente interpretados. Diferentes daqueles números cujos valores possíveis podem ser expressos em uma sequência numérica, os exemplos oferecidos aqui são de números cujos valores são não-sequenciais; por exemplo, um número de dois dígitos onde o algarismo referente à unidade sobrevive, mas aquele referente à dezena não.

                                                                                                                                                                                                                                                                                                                        Nenhuma renderização de exemplo em convenções epigráficas padrão.

                                                                                                                                                                                                                                                                                                                        Φαῶφι <num value="11">
                                                                                                                                                                                                                                                                                                                         <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                          unit="character"/>
                                                                                                                                                                                                                                                                                                                        α <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Duke Databank style: Φαῶφι [  ̣
                                                                                                                                                                                                                                                                                                                        <num value="4">
                                                                                                                                                                                                                                                                                                                         <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                          unit="character"/>
                                                                                                                                                                                                                                                                                                                        III <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="8"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="13"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="53"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="103"/>

                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: [.]III
                                                                                                                                                                                                                                                                                                                        <num value="1">
                                                                                                                                                                                                                                                                                                                         <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                          unit="character"/>
                                                                                                                                                                                                                                                                                                                        α <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="11"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="31"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="41"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="51"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="61"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="71"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="81"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="91"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="101"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="201"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="301"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="401"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="501"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="601"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="701"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="801"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="901"/>

                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Duke Databank style: [  ̣
                                                                                                                                                                                                                                                                                                                        (DDbDP: bgu.3.734)

                                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                        1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                        2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                        Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                        \ No newline at end of file + customization: num

                                                                                                                                                                                                                                                                                                                      Alguns números, principalmente se estiverem danificados ou incompletos, podem ser parcialmente mas não completamente interpretados. Diferentes daqueles números cujos valores possíveis podem ser expressos em uma sequência numérica, os exemplos oferecidos aqui são de números cujos valores são não-sequenciais; por exemplo, um número de dois dígitos onde o algarismo referente à unidade sobrevive, mas aquele referente à dezena não.

                                                                                                                                                                                                                                                                                                                      Nenhuma renderização de exemplo em convenções epigráficas padrão.

                                                                                                                                                                                                                                                                                                                      Φαῶφι <num value="11">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>
                                                                                                                                                                                                                                                                                                                      α <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: Φαῶφι [  ̣
                                                                                                                                                                                                                                                                                                                      <num value="4">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>
                                                                                                                                                                                                                                                                                                                      III <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="8"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="13"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="53"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="103"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: [.]III
                                                                                                                                                                                                                                                                                                                      <num value="1">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>
                                                                                                                                                                                                                                                                                                                      α <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="11"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="31"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="41"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="51"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="61"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="71"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="81"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="91"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="101"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="201"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="301"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="401"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="501"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="601"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="701"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="801"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="901"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [  ̣
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.3.734)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numnoncongruent.html b/gl/dev/trans-numnoncongruent.html index b614648cf..3a7fa9348 100644 --- a/gl/dev/trans-numnoncongruent.html +++ b/gl/dev/trans-numnoncongruent.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Numbers with Non-sequential Values

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Numbers with possible values that cannot be expressed as a range.

                                                                                                                                                                                                                                                                                                                      • TEI definition: certainty ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                        Numbers with Non-sequential Values

                                                                                                                                                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                                                                                                                                                        Numbers with possible values that cannot be expressed as a range.

                                                                                                                                                                                                                                                                                                                        • TEI definition: certainty ; EpiDoc-specific customization: certainty
                                                                                                                                                                                                                                                                                                                        • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                        Some numbers, especially if they are damaged or incomplete, can be partially but not completely interpreted. Unlike those whose possible values can be expressed as a numerical range, the examples offered here are of numbers whose values are non-sequential; for instance, a two-digit number where the units value survives, but the tens unit does not.

                                                                                                                                                                                                                                                                                                                        No example rendering in standard epigraphic conventions.

                                                                                                                                                                                                                                                                                                                        Φαῶφι <num value="11">
                                                                                                                                                                                                                                                                                                                         <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                          unit="character"/>
                                                                                                                                                                                                                                                                                                                        α
                                                                                                                                                                                                                                                                                                                        <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Duke Databank style: Φαῶφι [  ̣
                                                                                                                                                                                                                                                                                                                        <num value="4">
                                                                                                                                                                                                                                                                                                                         <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                          unit="character"/>
                                                                                                                                                                                                                                                                                                                        III
                                                                                                                                                                                                                                                                                                                        <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="8"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="13"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="53"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="103"/>

                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: [.]III
                                                                                                                                                                                                                                                                                                                        <num value="1">
                                                                                                                                                                                                                                                                                                                         <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                          unit="character"/>
                                                                                                                                                                                                                                                                                                                        α
                                                                                                                                                                                                                                                                                                                        <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="11"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="31"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="41"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="51"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="61"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="71"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="81"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="91"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="101"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="201"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="301"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="401"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="501"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="601"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="701"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="801"/>

                                                                                                                                                                                                                                                                                                                         <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                          assertedValue="901"/>

                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Duke Databank style: [  ̣
                                                                                                                                                                                                                                                                                                                        (DDbDP: bgu.3.734)

                                                                                                                                                                                                                                                                                                                        Responsibility for this section

                                                                                                                                                                                                                                                                                                                        1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                        Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                        \ No newline at end of file + customization: num

                                                                                                                                                                                                                                                                                                                      Some numbers, especially if they are damaged or incomplete, can be partially but not completely interpreted. Unlike those whose possible values can be expressed as a numerical range, the examples offered here are of numbers whose values are non-sequential; for instance, a two-digit number where the units value survives, but the tens unit does not.

                                                                                                                                                                                                                                                                                                                      No example rendering in standard epigraphic conventions.

                                                                                                                                                                                                                                                                                                                      Φαῶφι <num value="11">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>
                                                                                                                                                                                                                                                                                                                      α
                                                                                                                                                                                                                                                                                                                      <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: Φαῶφι [  ̣
                                                                                                                                                                                                                                                                                                                      <num value="4">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>
                                                                                                                                                                                                                                                                                                                      III
                                                                                                                                                                                                                                                                                                                      <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="8"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="13"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="53"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="103"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: [.]III
                                                                                                                                                                                                                                                                                                                      <num value="1">
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>
                                                                                                                                                                                                                                                                                                                      α
                                                                                                                                                                                                                                                                                                                      <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="11"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="21"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="31"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="41"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="51"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="61"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="71"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="81"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="91"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="101"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="201"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="301"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="401"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="501"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="601"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="701"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="801"/>

                                                                                                                                                                                                                                                                                                                       <certainty match="../@valuelocus="value"
                                                                                                                                                                                                                                                                                                                        assertedValue="901"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [  ̣
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.3.734)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numrange-pt-br.html b/gl/dev/trans-numrange-pt-br.html index 259d9b7ef..4ee50da3b 100644 --- a/gl/dev/trans-numrange-pt-br.html +++ b/gl/dev/trans-numrange-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Números com uma Gama de Valores Possíveis

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      Use o elemento num com valores para os atributos atLeast e atMost.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num atLeast="26atMost="29">XXVI<gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: XXVI[---]
                                                                                                                                                                                                                                                                                                                      <num atLeast="30atMost="39">
                                                                                                                                                                                                                                                                                                                       <supplied reason="lost">τρι</supplied>άκον<supplied reason="lost">τα </supplied>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [τρι]άκον[τα   ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.11.2050#4)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Números com uma Gama de Valores Possíveis

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      Use o elemento num com valores para os atributos atLeast e atMost.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num atLeast="26atMost="29">XXVI<gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: XXVI[---]
                                                                                                                                                                                                                                                                                                                      <num atLeast="30atMost="39">
                                                                                                                                                                                                                                                                                                                       <supplied reason="lost">τρι</supplied>άκον<supplied reason="lost">τα </supplied>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [τρι]άκον[τα   ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.11.2050#4)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numrange.html b/gl/dev/trans-numrange.html index 599642924..b251ecb9a 100644 --- a/gl/dev/trans-numrange.html +++ b/gl/dev/trans-numrange.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Numbers With a Range of Values

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      Use num with atLeast and atMost values.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num atLeast="26atMost="29">XXVI<gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: XXVI[---]
                                                                                                                                                                                                                                                                                                                      <num atLeast="30atMost="39">
                                                                                                                                                                                                                                                                                                                       <supplied reason="lost">τρι</supplied>άκον<supplied reason="lost">τα </supplied>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [τρι]άκον[τα   ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.11.2050#4)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Numbers With a Range of Values

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      Use num with atLeast and atMost values.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num atLeast="26atMost="29">XXVI<gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: XXVI[---]
                                                                                                                                                                                                                                                                                                                      <num atLeast="30atMost="39">
                                                                                                                                                                                                                                                                                                                       <supplied reason="lost">τρι</supplied>άκον<supplied reason="lost">τα </supplied>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostquantity="5"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [τρι]άκον[τα   ̣  ̣  ̣  ̣  ̣]
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.11.2050#4)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numtick-pt-br.html b/gl/dev/trans-numtick-pt-br.html index 583c1d98c..1c51d87b0 100644 --- a/gl/dev/trans-numtick-pt-br.html +++ b/gl/dev/trans-numtick-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Números com um sinal de visto/diacríticos

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num value="1rend="tick">α</num>
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1670rend="tick">αχο</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: αχο´
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1/8rend="tick">η</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: η´
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.7.1636#31)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Números com um sinal de visto/diacríticos

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num value="1rend="tick">α</num>
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1670rend="tick">αχο</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: αχο´
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1/8rend="tick">η</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: η´
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.7.1636#31)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numtick.html b/gl/dev/trans-numtick.html index 7cc944abe..440b28855 100644 --- a/gl/dev/trans-numtick.html +++ b/gl/dev/trans-numtick.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Numbers with a tick symbol/diacritic

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num value="1rend="tick">α</num>
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1670rend="tick">αχο</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: αχο´
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1/8rend="tick">η</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: η´
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.7.1636#31)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Numbers with a tick symbol/diacritic

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num value="1rend="tick">α</num>
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1670rend="tick">αχο</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: αχο´
                                                                                                                                                                                                                                                                                                                      (Sosin)
                                                                                                                                                                                                                                                                                                                      <num value="1/8rend="tick">η</num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: η´
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.7.1636#31)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numunknown-pt-br.html b/gl/dev/trans-numunknown-pt-br.html index 2a885e962..7912e6b88 100644 --- a/gl/dev/trans-numunknown-pt-br.html +++ b/gl/dev/trans-numunknown-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Números/Numerais de Valor Desconhecido

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      O numeral deve ser colocado dentro de um elemento num mas, como seu valor é desconhecido, não pode receber um atributo value.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num/>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostatLeast="1atMost="4"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: [·· 1-4··]
                                                                                                                                                                                                                                                                                                                      (IRT: 21)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style:   ̣

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Números/Numerais de Valor Desconhecido

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      O numeral deve ser colocado dentro de um elemento num mas, como seu valor é desconhecido, não pode receber um atributo value.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num/>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostatLeast="1atMost="4"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: [·· 1-4··]
                                                                                                                                                                                                                                                                                                                      (IRT: 21)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style:   ̣

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-numunknown.html b/gl/dev/trans-numunknown.html index 0e9d45389..e4b851643 100644 --- a/gl/dev/trans-numunknown.html +++ b/gl/dev/trans-numunknown.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Numbers/numerals of Unknown Value

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific - customization: num

                                                                                                                                                                                                                                                                                                                      The numeral should be placed inside a num, but where its value is unknown, no value can be given.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num/>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostatLeast="1atMost="4"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: [·· 1-4··]
                                                                                                                                                                                                                                                                                                                      (IRT: 21)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style:   ̣

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Numbers/numerals of Unknown Value

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      • TEI definition: num ; EpiDoc-specific + customization: num

                                                                                                                                                                                                                                                                                                                      The numeral should be placed inside a num, but where its value is unknown, no value can be given.

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <num/>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="lostatLeast="1atMost="4"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: [·· 1-4··]
                                                                                                                                                                                                                                                                                                                      (IRT: 21)
                                                                                                                                                                                                                                                                                                                      <num>
                                                                                                                                                                                                                                                                                                                       <gap reason="illegiblequantity="1"
                                                                                                                                                                                                                                                                                                                        unit="character"/>

                                                                                                                                                                                                                                                                                                                      </num>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style:   ̣

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-omitted-pt-br.html b/gl/dev/trans-omitted-pt-br.html index d098e126f..cf37c5ba4 100644 --- a/gl/dev/trans-omitted-pt-br.html +++ b/gl/dev/trans-omitted-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Letras Omitidas

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Letras erroneamente omitidas do texto, adicionadas pelo editor.

                                                                                                                                                                                                                                                                                                                      As letras omitidas devem ser colocadas dentro de um elemento supplied, cujo atributo reason deve receber o valor "omitted".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 IX.2; Sosin 2011: <abc>

                                                                                                                                                                                                                                                                                                                      <supplied reason="omitted">αβ</supplied>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      Valent<supplied reason="omitted">in</supplied>iani

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: Valent<in>iani
                                                                                                                                                                                                                                                                                                                      (IRT: 103)
                                                                                                                                                                                                                                                                                                                      <choice>
                                                                                                                                                                                                                                                                                                                       <reg>προ<supplied reason="omitted">γα</supplied>μούσης</reg>
                                                                                                                                                                                                                                                                                                                       <orig>προ<unclear>μο</unclear>υσης</orig>
                                                                                                                                                                                                                                                                                                                      </choice>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προμ̣ο̣υσης
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.183#29)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Letras Omitidas

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      Letras erroneamente omitidas do texto, adicionadas pelo editor.

                                                                                                                                                                                                                                                                                                                      As letras omitidas devem ser colocadas dentro de um elemento supplied, cujo atributo reason deve receber o valor "omitted".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 IX.2; Sosin 2011: <abc>

                                                                                                                                                                                                                                                                                                                      <supplied reason="omitted">αβ</supplied>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      Valent<supplied reason="omitted">in</supplied>iani

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: Valent<in>iani
                                                                                                                                                                                                                                                                                                                      (IRT: 103)
                                                                                                                                                                                                                                                                                                                      <choice>
                                                                                                                                                                                                                                                                                                                       <reg>προ<supplied reason="omitted">γα</supplied>μούσης</reg>
                                                                                                                                                                                                                                                                                                                       <orig>προ<unclear>μο</unclear>υσης</orig>
                                                                                                                                                                                                                                                                                                                      </choice>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προμ̣ο̣υσης
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.183#29)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-omitted.html b/gl/dev/trans-omitted.html index a7800ce65..fef44457b 100644 --- a/gl/dev/trans-omitted.html +++ b/gl/dev/trans-omitted.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Omitted letters

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Letters erroneously omitted from the text, which the editor adds.

                                                                                                                                                                                                                                                                                                                      The omitted letters should be enclosed within supplied, whose reason should be given a value of "omitted".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 IX.2; Sosin 2011: <abc>

                                                                                                                                                                                                                                                                                                                      <supplied reason="omitted">αβ</supplied>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Valent<supplied reason="omitted">in</supplied>iani

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: Valent<in>iani
                                                                                                                                                                                                                                                                                                                      (IRT: 103)
                                                                                                                                                                                                                                                                                                                      <choice>
                                                                                                                                                                                                                                                                                                                       <reg>προ<supplied reason="omitted">γα</supplied>μούσης</reg>
                                                                                                                                                                                                                                                                                                                       <orig>προ<unclear>μο</unclear>υσης</orig>
                                                                                                                                                                                                                                                                                                                      </choice>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προμ̣ο̣υσης
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.183#29)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Omitted letters

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      Letters erroneously omitted from the text, which the editor adds.

                                                                                                                                                                                                                                                                                                                      The omitted letters should be enclosed within supplied, whose reason should be given a value of "omitted".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 IX.2; Sosin 2011: <abc>

                                                                                                                                                                                                                                                                                                                      <supplied reason="omitted">αβ</supplied>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Valent<supplied reason="omitted">in</supplied>iani

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: Valent<in>iani
                                                                                                                                                                                                                                                                                                                      (IRT: 103)
                                                                                                                                                                                                                                                                                                                      <choice>
                                                                                                                                                                                                                                                                                                                       <reg>προ<supplied reason="omitted">γα</supplied>μούσης</reg>
                                                                                                                                                                                                                                                                                                                       <orig>προ<unclear>μο</unclear>υσης</orig>
                                                                                                                                                                                                                                                                                                                      </choice>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προμ̣ο̣υσης
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.183#29)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-paragraphos-pt-br.html b/gl/dev/trans-paragraphos-pt-br.html index fa28da8eb..10203eb4b 100644 --- a/gl/dev/trans-paragraphos-pt-br.html +++ b/gl/dev/trans-paragraphos-pt-br.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Paragraphos

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      paragraphos/régua horizontal/caixa? (valor especial ddbdp)

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <lb n="25"/>προσαγγελῶ<unclear>ν</unclear>, ὡς <choice>
                                                                                                                                                                                                                                                                                                                       <reg>ἐκελεύσθη</reg>
                                                                                                                                                                                                                                                                                                                       <orig>εκελευσθηι</orig>
                                                                                                                                                                                                                                                                                                                      </choice>.
                                                                                                                                                                                                                                                                                                                      <milestone rend="paragraphos"
                                                                                                                                                                                                                                                                                                                       unit="undefined"/>

                                                                                                                                                                                                                                                                                                                      <lb n="26"/>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προσαγγελῶν̣, ὡς εκελευσθηι .
                                                                                                                                                                                                                                                                                                                        ——
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.112)

                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                      Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                                      2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Paragraphos

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      paragraphos/régua horizontal/caixa? (valor especial ddbdp)

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <lb n="25"/>προσαγγελῶ<unclear>ν</unclear>, ὡς <choice>
                                                                                                                                                                                                                                                                                                                       <reg>ἐκελεύσθη</reg>
                                                                                                                                                                                                                                                                                                                       <orig>εκελευσθηι</orig>
                                                                                                                                                                                                                                                                                                                      </choice>.
                                                                                                                                                                                                                                                                                                                      <milestone rend="paragraphos"
                                                                                                                                                                                                                                                                                                                       unit="undefined"/>

                                                                                                                                                                                                                                                                                                                      <lb n="26"/>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προσαγγελῶν̣, ὡς εκελευσθηι .
                                                                                                                                                                                                                                                                                                                        ——
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.112)

                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                      Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                                      2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-paragraphos.html b/gl/dev/trans-paragraphos.html index 6503ae761..df8997d62 100644 --- a/gl/dev/trans-paragraphos.html +++ b/gl/dev/trans-paragraphos.html @@ -21,4 +21,4 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Paragraphos

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      paragraphos/horizontal rule/box? (ddbdp special value)

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <lb n="25"/>προσαγγελῶ<unclear>ν</unclear>, ὡς <choice>
                                                                                                                                                                                                                                                                                                                       <reg>ἐκελεύσθη</reg>
                                                                                                                                                                                                                                                                                                                       <orig>εκελευσθηι</orig>
                                                                                                                                                                                                                                                                                                                      </choice>.

                                                                                                                                                                                                                                                                                                                      <milestone rend="paragraphos"
                                                                                                                                                                                                                                                                                                                       unit="undefined"/>

                                                                                                                                                                                                                                                                                                                      <lb n="26"/>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προσαγγελῶν̣, ὡς εκελευσθηι.
                                                                                                                                                                                                                                                                                                                        ——
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.112)

                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                      Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Paragraphos

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      paragraphos/horizontal rule/box? (ddbdp special value)

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                      <lb n="25"/>προσαγγελῶ<unclear>ν</unclear>, ὡς <choice>
                                                                                                                                                                                                                                                                                                                       <reg>ἐκελεύσθη</reg>
                                                                                                                                                                                                                                                                                                                       <orig>εκελευσθηι</orig>
                                                                                                                                                                                                                                                                                                                      </choice>.

                                                                                                                                                                                                                                                                                                                      <milestone rend="paragraphos"
                                                                                                                                                                                                                                                                                                                       unit="undefined"/>

                                                                                                                                                                                                                                                                                                                      <lb n="26"/>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: προσαγγελῶν̣, ὡς εκελευσθηι.
                                                                                                                                                                                                                                                                                                                        ——
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.112)

                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                      Other pages describing <elements>:

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-parallelcopy-pt-br.html b/gl/dev/trans-parallelcopy-pt-br.html index 096589da1..187d6159e 100644 --- a/gl/dev/trans-parallelcopy-pt-br.html +++ b/gl/dev/trans-parallelcopy-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Texto Paralelo

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Texto restaurado de uma cópia paralela

                                                                                                                                                                                                                                                                                                                      Nos casos em que o texto restaurado pelo editor vem de uma cópia paralela (por exemplo, de um papiro com o mesmo texto literário, ou de uma inscrição com uma versão mais completa de um decreto ou carta imperial), isto deve ser indicado com o elemento supplied, indicando a fonte paralela pelo atributo evidence com o valor "parallel".

                                                                                                                                                                                                                                                                                                                      Pelo fato de reason ser um atributo necessário em supplied dentro do EpiDoc (para se fazer a distinção entre os suplementos perdido, omitido, subaudível no Leiden), no caso de texto restaurado de uma cópia paralela, onde o Leiden é tipicamente ambíguo sobre o atual estado de preservação, o valor de reason = "undefined" é permitido, para refletir esta ambiguidade.

                                                                                                                                                                                                                                                                                                                      Na maior parte dos estilos epigráficos/papirológicos, este texto será apresentado apenas com um sublinhado (da mesma forma que em Editor Anterior), mas no Duke Databank o texto também pode estar dentro de colchetes para indicar o fato de que o texto está completamente perdido (em vez de apenas pouco claro, corrupto ou incerto).

                                                                                                                                                                                                                                                                                                                      Sosin 2011: a̲b̲c̲ or [a̲b̲c̲]

                                                                                                                                                                                                                                                                                                                      O primeiro exemplo demonstra que, quando o reason para suplementação paralela tem valor "undefined", o Duke Databank segue o padrão geral.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      O segundo exemplo ilustra a diferença de tratamento entre o Duke Databank e outros estilos, quando a razão para a suplementação é a perda completa.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallelreason="lost">abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [abc]
                                                                                                                                                                                                                                                                                                                      (Sosin)

                                                                                                                                                                                                                                                                                                                      Um exemplo mais complexo ilustra a capacidade expressiva do tratamento dado pelo Duke Databank quando lida com lacunas ou texto danificado.

                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">καὶ ἀναγν</supplied>ωσθείσης̣
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">τῆ</supplied>
                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      ς ἐπιστολῆς
                                                                                                                                                                                                                                                                                                                      Θεοδώρου</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [καὶ ἀναγν]ωσθείσης̣ [τῆ]ς ἐπιστολῆς Θεοδώρου
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.13.2216#4)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Texto Paralelo

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      Texto restaurado de uma cópia paralela

                                                                                                                                                                                                                                                                                                                      Nos casos em que o texto restaurado pelo editor vem de uma cópia paralela (por exemplo, de um papiro com o mesmo texto literário, ou de uma inscrição com uma versão mais completa de um decreto ou carta imperial), isto deve ser indicado com o elemento supplied, indicando a fonte paralela pelo atributo evidence com o valor "parallel".

                                                                                                                                                                                                                                                                                                                      Pelo fato de reason ser um atributo necessário em supplied dentro do EpiDoc (para se fazer a distinção entre os suplementos perdido, omitido, subaudível no Leiden), no caso de texto restaurado de uma cópia paralela, onde o Leiden é tipicamente ambíguo sobre o atual estado de preservação, o valor de reason = "undefined" é permitido, para refletir esta ambiguidade.

                                                                                                                                                                                                                                                                                                                      Na maior parte dos estilos epigráficos/papirológicos, este texto será apresentado apenas com um sublinhado (da mesma forma que em Editor Anterior), mas no Duke Databank o texto também pode estar dentro de colchetes para indicar o fato de que o texto está completamente perdido (em vez de apenas pouco claro, corrupto ou incerto).

                                                                                                                                                                                                                                                                                                                      Sosin 2011: a̲b̲c̲ or [a̲b̲c̲]

                                                                                                                                                                                                                                                                                                                      O primeiro exemplo demonstra que, quando o reason para suplementação paralela tem valor "undefined", o Duke Databank segue o padrão geral.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      O segundo exemplo ilustra a diferença de tratamento entre o Duke Databank e outros estilos, quando a razão para a suplementação é a perda completa.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallelreason="lost">abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [abc]
                                                                                                                                                                                                                                                                                                                      (Sosin)

                                                                                                                                                                                                                                                                                                                      Um exemplo mais complexo ilustra a capacidade expressiva do tratamento dado pelo Duke Databank quando lida com lacunas ou texto danificado.

                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">καὶ ἀναγν</supplied>ωσθείσης̣
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">τῆ</supplied>
                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      ς ἐπιστολῆς
                                                                                                                                                                                                                                                                                                                      Θεοδώρου</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [καὶ ἀναγν]ωσθείσης̣ [τῆ]ς ἐπιστολῆς Θεοδώρου
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.13.2216#4)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-parallelcopy.html b/gl/dev/trans-parallelcopy.html index 14ff4460e..c1b9d8cc3 100644 --- a/gl/dev/trans-parallelcopy.html +++ b/gl/dev/trans-parallelcopy.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Parallel Text

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Text restored from parallel copy

                                                                                                                                                                                                                                                                                                                      Where text is restored by the editor from a parallel copy (e.g. a papyrus with the same literary text, or an inscription with a more complete version of a decree or imperial letter), this should be indicated with a supplied element, indicating the parallel source by evidence with a value of "parallel".

                                                                                                                                                                                                                                                                                                                      Because reason is a required attribute on supplied in EpiDoc (to distinguish between lost, omitted, subaudible etc. supplements in Leiden) in the case of text restored from a parallel copy, where Leiden is typically ambiguous about the current state of preservation, the value of reason = "undefined" is permitted to reflect this ambiguity.

                                                                                                                                                                                                                                                                                                                      In most epigraphic/papyrological styles this text will be displayed with underline only (similarly to Previous Editor), but in the Duke Databank the text may also be enclosed in square brackets to indicate the fact that the text is now completely lost (as opposed to merely unclear, corrupt or uncertain).

                                                                                                                                                                                                                                                                                                                      Sosin 2011: a̲b̲c̲ or [a̲b̲c̲]

                                                                                                                                                                                                                                                                                                                      The first example demonstrates that, when the reason for the parallel supplementation is "undefined", the Duke Databank follows the general pattern.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      The second example illustrates the different in approach between the Duke Databank and other styles when the reason for supplementation is complete loss.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallelreason="lost">abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [abc]
                                                                                                                                                                                                                                                                                                                      (Sosin)

                                                                                                                                                                                                                                                                                                                      A more complex example illustrates the expressiveness of the Duke Databank approach when dealing with a lacunose and damaged text.

                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">καὶ ἀναγν</supplied>ωσθείσης̣
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">τῆ</supplied>
                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      ς ἐπιστολῆς Θεοδώρου</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [καὶ ἀναγν]ωσθείσης̣ [τῆ]ς ἐπιστολῆς Θεοδώρου
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.13.2216#4)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Parallel Text

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      Text restored from parallel copy

                                                                                                                                                                                                                                                                                                                      Where text is restored by the editor from a parallel copy (e.g. a papyrus with the same literary text, or an inscription with a more complete version of a decree or imperial letter), this should be indicated with a supplied element, indicating the parallel source by evidence with a value of "parallel".

                                                                                                                                                                                                                                                                                                                      Because reason is a required attribute on supplied in EpiDoc (to distinguish between lost, omitted, subaudible etc. supplements in Leiden) in the case of text restored from a parallel copy, where Leiden is typically ambiguous about the current state of preservation, the value of reason = "undefined" is permitted to reflect this ambiguity.

                                                                                                                                                                                                                                                                                                                      In most epigraphic/papyrological styles this text will be displayed with underline only (similarly to Previous Editor), but in the Duke Databank the text may also be enclosed in square brackets to indicate the fact that the text is now completely lost (as opposed to merely unclear, corrupt or uncertain).

                                                                                                                                                                                                                                                                                                                      Sosin 2011: a̲b̲c̲ or [a̲b̲c̲]

                                                                                                                                                                                                                                                                                                                      The first example demonstrates that, when the reason for the parallel supplementation is "undefined", the Duke Databank follows the general pattern.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      The second example illustrates the different in approach between the Duke Databank and other styles when the reason for supplementation is complete loss.

                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallelreason="lost">abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      • London style: abc
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [abc]
                                                                                                                                                                                                                                                                                                                      (Sosin)

                                                                                                                                                                                                                                                                                                                      A more complex example illustrates the expressiveness of the Duke Databank approach when dealing with a lacunose and damaged text.

                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">καὶ ἀναγν</supplied>ωσθείσης̣
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost">τῆ</supplied>
                                                                                                                                                                                                                                                                                                                      <supplied evidence="parallel"
                                                                                                                                                                                                                                                                                                                       reason="undefined">
                                                                                                                                                                                                                                                                                                                      ς ἐπιστολῆς Θεοδώρου</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [καὶ ἀναγν]ωσθείσης̣ [τῆ]ς ἐπιστολῆς Θεοδώρου
                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.13.2216#4)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-possiblevacat-pt-br.html b/gl/dev/trans-possiblevacat-pt-br.html index 06c4b71d1..7f0740ed8 100644 --- a/gl/dev/trans-possiblevacat-pt-br.html +++ b/gl/dev/trans-possiblevacat-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Possível Vacat

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Editor marca espaço deixado sem inscrição no suporte, mas expressa dúvida a respeito desta ser a codificação correta.

                                                                                                                                                                                                                                                                                                                      Um elemento space deve ser usado sempre que houver espaço intencionalmente deixado no suporte, isto é, um espaço que nunca conteve texto (vacat). Para expressar incerteza a respeito de haver ou não a presença de um vacat (em vez de um texto apagado ou perdido, por exemplo), um elemento certainty com um atributo match correspondente ao elemento maior (por exemplo,o elemento space) deve receber um atributo locus com o valor "name" (o que significa que o elemento space pode não estar correto).

                                                                                                                                                                                                                                                                                                                      Panciera 1991 XI.3; Sosin 2011: (vac.?)

                                                                                                                                                                                                                                                                                                                      <space quantity="5unit="character">
                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </space>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      4. Tom Elliott, contribuidor
                                                                                                                                                                                                                                                                                                                      5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-possiblevacat.html b/gl/dev/trans-possiblevacat.html index ca3ae53c7..50771aa97 100644 --- a/gl/dev/trans-possiblevacat.html +++ b/gl/dev/trans-possiblevacat.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Possible Vacat

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Editor marks space left uninscribed on the support, but expresses doubt as to whether this is the correct encoding.

                                                                                                                                                                                                                                                                                                                      A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). To express uncertainty as to whether or not a vacat is actually present (as opposed to text erased or lost, say), a certainty element with a match corresponding to the parent element (i.e. the space element) should be given a locus with a value of "name" (meaning the space element may not be correct).

                                                                                                                                                                                                                                                                                                                      Panciera 1991 XI.3; Sosin 2011: (vac.?)

                                                                                                                                                                                                                                                                                                                      <space quantity="5unit="character">
                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </space>
                                                                                                                                                                                                                                                                                                                      (Panciera)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                      3. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      4. Tom Elliott, contributor

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-possiblyillegible-pt-br.html b/gl/dev/trans-possiblyillegible-pt-br.html index 15264dcaf..19d186932 100644 --- a/gl/dev/trans-possiblyillegible-pt-br.html +++ b/gl/dev/trans-possiblyillegible-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Caracteres/Linhas Possivelmente Ilegíveis

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Nos casos onde vestígios de caracteres ou linhas permanecem, mas não podem ser reconhecidos e sua quantidade é desconhecida, um gap deve ser utilizado e receber um atributo reason com o valor "illegible" e um atributo extent com o valor "unknown". Para expressar incerteza em relação à presença real de um caracter ou linha ilegível, um elemento certainty com um atributo match correspondente ao elemento maior (por exemplo, o gap) deve receber um locus com o valor "name".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 VIII.7; Sosin 2011: [- - -?]

                                                                                                                                                                                                                                                                                                                      <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="character">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                       unit="character">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ?  ̣  ̣  ̣
                                                                                                                                                                                                                                                                                                                      (DDbDP: chla.5.286)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-possiblyillegible.html b/gl/dev/trans-possiblyillegible.html index 3f17072b7..06ff5a701 100644 --- a/gl/dev/trans-possiblyillegible.html +++ b/gl/dev/trans-possiblyillegible.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Possible Illegible Characters/Lines

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Where vestiges of characters or lines possibly remain, but they cannot be recognised and their quantity is unknown, a gap should be used, and given a reason attribute with a value of "illegible" and an extent with a value of "unknown". To express uncertainty as to whether or not an illegible character or line is actually present, a certainty with a match corresponding to the parent element (i.e. the gap) should be given a locus with a value of "name".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 VIII.7; Sosin 2011: [- - -?]

                                                                                                                                                                                                                                                                                                                      <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <gap reason="illegibleextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="character">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <gap reason="illegiblequantity="3"
                                                                                                                                                                                                                                                                                                                       unit="character">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ?  ̣  ̣  ̣
                                                                                                                                                                                                                                                                                                                      (DDbDP: chla.5.286)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-possiblylost-pt-br.html b/gl/dev/trans-possiblylost-pt-br.html index 3bdd282e6..f12ddadd4 100644 --- a/gl/dev/trans-possiblylost-pt-br.html +++ b/gl/dev/trans-possiblylost-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Linhas Possivelmente Perdidas / Quebra Possível de Texto

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Nos casos onde há linhas possivelmente perdidas ou uma quebra possível de texto, deve-se usar gap. Para expressar incerteza na existência ou não de uma linha, um elemento certainty com um atributo match correspondente ao elemento maior (por exemplo, o gap) deve receber um locus com o valor "name".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 VIII.7; Sosin 2011: - - - - - - -?

                                                                                                                                                                                                                                                                                                                      <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: [·· ? ··?]
                                                                                                                                                                                                                                                                                                                      (IRT: 289)
                                                                                                                                                                                                                                                                                                                      <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style:
                                                                                                                                                                                                                                                                                                                        -- -- -- -- -- -- -- -- -- --(?)
                                                                                                                                                                                                                                                                                                                      (DDbDP: chla.4.249)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-possiblylost.html b/gl/dev/trans-possiblylost.html index 8ee123e12..47ee31cb0 100644 --- a/gl/dev/trans-possiblylost.html +++ b/gl/dev/trans-possiblylost.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Lines Possibly Lost / Text Possibly Breaks

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Where lines are possibly lost or the text possibly breaks, gap should be used. To express uncertainty as to whether or not a line is actually present, a certainty element with a match corresponding to the parent element (i.e. gap) should be given a locus with a value of "name".

                                                                                                                                                                                                                                                                                                                      Panciera 1991 VIII.7; Sosin 2011: - - - - - - -?

                                                                                                                                                                                                                                                                                                                      <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: [·· ? ··?]
                                                                                                                                                                                                                                                                                                                      (IRT: 289)
                                                                                                                                                                                                                                                                                                                      <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                       unit="line">

                                                                                                                                                                                                                                                                                                                       <certainty match="..locus="name"/>
                                                                                                                                                                                                                                                                                                                      </gap>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style:
                                                                                                                                                                                                                                                                                                                        -- -- -- -- -- -- -- -- -- --(?)
                                                                                                                                                                                                                                                                                                                      (DDbDP: chla.4.249)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-previouseditor-pt-br.html b/gl/dev/trans-previouseditor-pt-br.html index 4f2f0ea62..4f714417d 100644 --- a/gl/dev/trans-previouseditor-pt-br.html +++ b/gl/dev/trans-previouseditor-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Editor Anterior

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Letras lidas por um observador moderno anterior, que não podem mais ser lidas.

                                                                                                                                                                                                                                                                                                                      Um texto que foi visível para um editor anterior, mas que está agora ilegível ou perdido, deve ser marcado com um elemento supplied, que recebe um atributo evidence com o valor "previouseditor".

                                                                                                                                                                                                                                                                                                                      Na maior parte dos estilos epigráficos/papirológicos, este texto seria apresentado apenas com um sublinhado (similar ao caso Cópia Paralela), e não é, portanto, importante se o valor do necessário atributo reason é "lost" ou o mais genérico "undefined", mas no Duke Databank o texto pode estar também entre colchetes para indicar o fato que o texto está, hoje, completamente perdido (em vez de apenas pouco claro, corrupto ou incerto).

                                                                                                                                                                                                                                                                                                                      Panciera 1991 III.5: a̲b̲c̲

                                                                                                                                                                                                                                                                                                                      <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      αβγ</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: αβγ
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      ὑπ</supplied>ὲρ τῆς τῶν | <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      κυ</supplied>ρίων Αὐτοκρα|<supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      τ</supplied>όρων

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • London style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [ὑπ]ὲρ τῆς τῶν | [κυ]ρίων Αὐτοκρα|[τ]όρων
                                                                                                                                                                                                                                                                                                                      (InsAph: 12.108)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Editor Anterior

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      Letras lidas por um observador moderno anterior, que não podem mais ser lidas.

                                                                                                                                                                                                                                                                                                                      Um texto que foi visível para um editor anterior, mas que está agora ilegível ou perdido, deve ser marcado com um elemento supplied, que recebe um atributo evidence com o valor "previouseditor".

                                                                                                                                                                                                                                                                                                                      Na maior parte dos estilos epigráficos/papirológicos, este texto seria apresentado apenas com um sublinhado (similar ao caso Cópia Paralela), e não é, portanto, importante se o valor do necessário atributo reason é "lost" ou o mais genérico "undefined", mas no Duke Databank o texto pode estar também entre colchetes para indicar o fato que o texto está, hoje, completamente perdido (em vez de apenas pouco claro, corrupto ou incerto).

                                                                                                                                                                                                                                                                                                                      Panciera 1991 III.5: a̲b̲c̲

                                                                                                                                                                                                                                                                                                                      <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      αβγ</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: αβγ
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      ὑπ</supplied>ὲρ τῆς τῶν | <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      κυ</supplied>ρίων Αὐτοκρα|<supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      τ</supplied>όρων

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • London style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [ὑπ]ὲρ τῆς τῶν | [κυ]ρίων Αὐτοκρα|[τ]όρων
                                                                                                                                                                                                                                                                                                                      (InsAph: 12.108)

                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-previouseditor.html b/gl/dev/trans-previouseditor.html index 2bffb9d2b..945f7bc24 100644 --- a/gl/dev/trans-previouseditor.html +++ b/gl/dev/trans-previouseditor.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Previous Editor

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      Letters read by a previous modern observer, but which cannot now be read.

                                                                                                                                                                                                                                                                                                                      The text which was visible to a previous editor but is now lost or illegible should be indicated with a supplied element with evidence with a value of "previouseditor".

                                                                                                                                                                                                                                                                                                                      In most epigraphic/papyrological styles this text will be displayed with underline only (similarly to Parallel Copy), and so it is largely academic whether the required reason attribute has a value of "lost" or the more generic "undefined", but in the Duke Databank the text may also be enclosed in square brackets to indicate the fact that the text is now completely lost (as opposed to merely unclear, corrupt or uncertain).

                                                                                                                                                                                                                                                                                                                      Panciera 1991 III.5: a̲b̲c̲

                                                                                                                                                                                                                                                                                                                      <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      αβγ</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: αβγ
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      ὑπ</supplied>ὲρ τῆς τῶν | <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      κυ</supplied>ρίων Αὐτοκρα|<supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      τ</supplied>όρων

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • London style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [ὑπ]ὲρ τῆς τῶν | [κυ]ρίων Αὐτοκρα|[τ]όρων
                                                                                                                                                                                                                                                                                                                      (InsAph: 12.108)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                      Previous Editor

                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                      Letters read by a previous modern observer, but which cannot now be read.

                                                                                                                                                                                                                                                                                                                      The text which was visible to a previous editor but is now lost or illegible should be indicated with a supplied element with evidence with a value of "previouseditor".

                                                                                                                                                                                                                                                                                                                      In most epigraphic/papyrological styles this text will be displayed with underline only (similarly to Parallel Copy), and so it is largely academic whether the required reason attribute has a value of "lost" or the more generic "undefined", but in the Duke Databank the text may also be enclosed in square brackets to indicate the fact that the text is now completely lost (as opposed to merely unclear, corrupt or uncertain).

                                                                                                                                                                                                                                                                                                                      Panciera 1991 III.5: a̲b̲c̲

                                                                                                                                                                                                                                                                                                                      <supplied reason="undefined"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      abc</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      αβγ</supplied>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • London style: αβγ
                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                      <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      ὑπ</supplied>ὲρ τῆς τῶν | <supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      κυ</supplied>ρίων Αὐτοκρα|<supplied reason="lost"
                                                                                                                                                                                                                                                                                                                       evidence="previouseditor">
                                                                                                                                                                                                                                                                                                                      τ</supplied>όρων

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • London style: ὑπὲρ τῆς τῶν | κυρίων Αὐτοκρα|τόρων
                                                                                                                                                                                                                                                                                                                      • Duke Databank style: [ὑπ]ὲρ τῆς τῶν | [κυ]ρίων Αὐτοκρα|[τ]όρων
                                                                                                                                                                                                                                                                                                                      (InsAph: 12.108)

                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                      1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                      2. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                      Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                      \ No newline at end of file diff --git a/gl/dev/trans-quotation-pt-br.html b/gl/dev/trans-quotation-pt-br.html index 0d0effafe..b239b6fb0 100644 --- a/gl/dev/trans-quotation-pt-br.html +++ b/gl/dev/trans-quotation-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                      Aspas

                                                                                                                                                                                                                                                                                                                      2023-04-27

                                                                                                                                                                                                                                                                                                                      • TEI definition: q ; EpiDoc-specific - customization: q

                                                                                                                                                                                                                                                                                                                      Panciera 1991 ...; Sosin 2011: "abc"

                                                                                                                                                                                                                                                                                                                      We are the Knights who say
                                                                                                                                                                                                                                                                                                                      <q>Ni!</q>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Default (Panciera) style: We are the Knights who say Ni!
                                                                                                                                                                                                                                                                                                                      ὅτι <q>πέμψον μοι τὰ σιδήρια</q>

                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                      • Duke Databank style: ὅτι 'πέμψον μοι τὰ σιδήρια'

                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                      Other pages describing <q>:

                                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                        1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                        2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                        Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                        \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                        Aspas

                                                                                                                                                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                                                                                                                                                        • TEI definition: q ; EpiDoc-specific + customization: q

                                                                                                                                                                                                                                                                                                                        Panciera 1991 ...; Sosin 2011: "abc"

                                                                                                                                                                                                                                                                                                                        We are the Knights who say
                                                                                                                                                                                                                                                                                                                        <q>Ni!</q>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: We are the Knights who say Ni!
                                                                                                                                                                                                                                                                                                                        ὅτι <q>πέμψον μοι τὰ σιδήρια</q>

                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                        • Duke Databank style: ὅτι 'πέμψον μοι τὰ σιδήρια'

                                                                                                                                                                                                                                                                                                                        See also:

                                                                                                                                                                                                                                                                                                                        Other pages describing <q>:

                                                                                                                                                                                                                                                                                                                          Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                          1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                          2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                          Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                          \ No newline at end of file diff --git a/gl/dev/trans-quotation.html b/gl/dev/trans-quotation.html index a31a639e2..36bb6f36f 100644 --- a/gl/dev/trans-quotation.html +++ b/gl/dev/trans-quotation.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                          Quotation Marks

                                                                                                                                                                                                                                                                                                                          2023-04-27

                                                                                                                                                                                                                                                                                                                          • TEI definition: q ; EpiDoc-specific - customization: q

                                                                                                                                                                                                                                                                                                                          Panciera 1991 ...; Sosin 2011: "abc"

                                                                                                                                                                                                                                                                                                                          We are the Knights who say <q>Ni!</q>

                                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                          • Default (Panciera) style: We are the Knights who say Ni!
                                                                                                                                                                                                                                                                                                                          ὅτι <q>πέμψον μοι τὰ σιδήρια</q>

                                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                          • Duke Databank style: ὅτι 'πέμψον μοι τὰ σιδήρια'

                                                                                                                                                                                                                                                                                                                          See also:

                                                                                                                                                                                                                                                                                                                          Other pages describing <q>:

                                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                                            1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                            \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                            Quotation Marks

                                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                                            • TEI definition: q ; EpiDoc-specific + customization: q

                                                                                                                                                                                                                                                                                                                            Panciera 1991 ...; Sosin 2011: "abc"

                                                                                                                                                                                                                                                                                                                            We are the Knights who say <q>Ni!</q>

                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: We are the Knights who say Ni!
                                                                                                                                                                                                                                                                                                                            ὅτι <q>πέμψον μοι τὰ σιδήρια</q>

                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                            • Duke Databank style: ὅτι 'πέμψον μοι τὰ σιδήρια'

                                                                                                                                                                                                                                                                                                                            See also:

                                                                                                                                                                                                                                                                                                                            Other pages describing <q>:

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-raisedlowered-pt-br.html b/gl/dev/trans-raisedlowered-pt-br.html index 3e61b3263..761ad8169 100644 --- a/gl/dev/trans-raisedlowered-pt-br.html +++ b/gl/dev/trans-raisedlowered-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Caracteres Elevados ou Rebaixados

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Caracteres escritos acima ou abaixo da linha, elevados ou rebaixados em relação aos outros caracteres, ou escritos como superescrito ou subescrito.

                                                                                                                                                                                                                                                                                                                              • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                              Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                              ab<hi rend="superscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              ab<hi rend="subscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <expan>πρ<hi rend="superscript">οσ</hi>
                                                                                                                                                                                                                                                                                                                               <ex>γίνεται</ex>
                                                                                                                                                                                                                                                                                                                              </expan>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: προσ(γίνεται)
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.14.2432)
                                                                                                                                                                                                                                                                                                                              <hi rend="subscript">
                                                                                                                                                                                                                                                                                                                               <num value="10">ι</num>
                                                                                                                                                                                                                                                                                                                               <num value="1/16rend="tick">ιϛ</num>
                                                                                                                                                                                                                                                                                                                              </hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: ι ιϛ´
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.153)

                                                                                                                                                                                                                                                                                                                              Em alguns casos podemos ter uma letra diretamente acima de uma outra, superposta, como uma variação de manuscrito, em vez de uma correção. Não existe uma norma TEI adequada para este fenômeno, portanto, até este momento, usamos um valor do atributo rend, 'stacked'. Aqui está um exemplo do segundo volume do Fragmenta Historicorum Graecorum. Esta é uma codificação de uma edição (presumivelmente referente a um manuscrito), não letras superpostas em uma inscrição ou papiro, e a interpretação desta superposição não está clara, portanto vamos apenas codificar a aparência da edição:

                                                                                                                                                                                                                                                                                                                              Κάδμο<hi rend="stacked">ο</hi>ν

                                                                                                                                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                              2. Simona Stoyanova, autor
                                                                                                                                                                                                                                                                                                                              3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                              4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                              Caracteres Elevados ou Rebaixados

                                                                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                                                                              Caracteres escritos acima ou abaixo da linha, elevados ou rebaixados em relação aos outros caracteres, ou escritos como superescrito ou subescrito.

                                                                                                                                                                                                                                                                                                                              • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                              Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                              ab<hi rend="superscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              ab<hi rend="subscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <expan>πρ<hi rend="superscript">οσ</hi>
                                                                                                                                                                                                                                                                                                                               <ex>γίνεται</ex>
                                                                                                                                                                                                                                                                                                                              </expan>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: προσ(γίνεται)
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.14.2432)
                                                                                                                                                                                                                                                                                                                              <hi rend="subscript">
                                                                                                                                                                                                                                                                                                                               <num value="10">ι</num>
                                                                                                                                                                                                                                                                                                                               <num value="1/16rend="tick">ιϛ</num>
                                                                                                                                                                                                                                                                                                                              </hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: ι ιϛ´
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.153)

                                                                                                                                                                                                                                                                                                                              Em alguns casos podemos ter uma letra diretamente acima de uma outra, superposta, como uma variação de manuscrito, em vez de uma correção. Não existe uma norma TEI adequada para este fenômeno, portanto, até este momento, usamos um valor do atributo rend, 'stacked'. Aqui está um exemplo do segundo volume do Fragmenta Historicorum Graecorum. Esta é uma codificação de uma edição (presumivelmente referente a um manuscrito), não letras superpostas em uma inscrição ou papiro, e a interpretação desta superposição não está clara, portanto vamos apenas codificar a aparência da edição:

                                                                                                                                                                                                                                                                                                                              Κάδμο<hi rend="stacked">ο</hi>ν

                                                                                                                                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                              2. Simona Stoyanova, autor
                                                                                                                                                                                                                                                                                                                              3. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                              4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-raisedlowered.html b/gl/dev/trans-raisedlowered.html index bf53d1b5f..d516145be 100644 --- a/gl/dev/trans-raisedlowered.html +++ b/gl/dev/trans-raisedlowered.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Raised/Lowered characters

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Characters written above or below the line, raised or lowered with respect to other characters, or written superscript of subscript.

                                                                                                                                                                                                                                                                                                                              • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                              Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                              ab<hi rend="superscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              ab<hi rend="subscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <expan>πρ<hi rend="superscript">οσ</hi>
                                                                                                                                                                                                                                                                                                                               <ex>γίνεται</ex>
                                                                                                                                                                                                                                                                                                                              </expan>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: προσ(γίνεται)
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.14.2432)
                                                                                                                                                                                                                                                                                                                              <hi rend="subscript">
                                                                                                                                                                                                                                                                                                                               <num value="10">ι</num>
                                                                                                                                                                                                                                                                                                                               <num value="1/16rend="tick">ιϛ</num>
                                                                                                                                                                                                                                                                                                                              </hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: ι ιϛ´
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.153)

                                                                                                                                                                                                                                                                                                                              In some cases we can have one letter directly on top of another, as a manuscript variant, rather than a correction. There is no adequate TEI guidance for this phenomenon, so for the moment we have used another value of the rend attribute, 'stacked'. Here is an example from the second volume of Fragmenta Historicorum Graecorum. This is an encoding of an edition (presumably referencing a manuscript), not stacked letters in an inscription/papyrus, and the interpretation of this stacking is rather unclear, so we will only tag the appearance of the edition:

                                                                                                                                                                                                                                                                                                                              Κάδμο<hi rend="stacked">ο</hi>ν

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                              2. Simona Stoyanova, author
                                                                                                                                                                                                                                                                                                                              3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                              Raised/Lowered characters

                                                                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                                                                              Characters written above or below the line, raised or lowered with respect to other characters, or written superscript of subscript.

                                                                                                                                                                                                                                                                                                                              • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                              Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                              ab<hi rend="superscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              ab<hi rend="subscript">c</hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <expan>πρ<hi rend="superscript">οσ</hi>
                                                                                                                                                                                                                                                                                                                               <ex>γίνεται</ex>
                                                                                                                                                                                                                                                                                                                              </expan>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: προσ(γίνεται)
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.14.2432)
                                                                                                                                                                                                                                                                                                                              <hi rend="subscript">
                                                                                                                                                                                                                                                                                                                               <num value="10">ι</num>
                                                                                                                                                                                                                                                                                                                               <num value="1/16rend="tick">ιϛ</num>
                                                                                                                                                                                                                                                                                                                              </hi>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: ι ιϛ´
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.153)

                                                                                                                                                                                                                                                                                                                              In some cases we can have one letter directly on top of another, as a manuscript variant, rather than a correction. There is no adequate TEI guidance for this phenomenon, so for the moment we have used another value of the rend attribute, 'stacked'. Here is an example from the second volume of Fragmenta Historicorum Graecorum. This is an encoding of an edition (presumably referencing a manuscript), not stacked letters in an inscription/papyrus, and the interpretation of this stacking is rather unclear, so we will only tag the appearance of the edition:

                                                                                                                                                                                                                                                                                                                              Κάδμο<hi rend="stacked">ο</hi>ν

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                              2. Simona Stoyanova, author
                                                                                                                                                                                                                                                                                                                              3. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-regularization-pt-br.html b/gl/dev/trans-regularization-pt-br.html index 10625194b..ed7f077d7 100644 --- a/gl/dev/trans-regularization-pt-br.html +++ b/gl/dev/trans-regularization-pt-br.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Regularização

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Regularização da escrita de formas irregulares, como dialetos, grafia tardia, grafia fonética, , etc.

                                                                                                                                                                                                                                                                                                                              • TEI definition: choice ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                Regularização

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Regularização da escrita de formas irregulares, como dialetos, grafia tardia, grafia fonética, , etc.

                                                                                                                                                                                                                                                                                                                                • TEI definition: choice ; EpiDoc-specific customization: choice
                                                                                                                                                                                                                                                                                                                                • TEI definition: reg ; EpiDoc-specific customization: reg
                                                                                                                                                                                                                                                                                                                                • TEI definition: orig ; EpiDoc-specific - customization: orig

                                                                                                                                                                                                                                                                                                                                Se o seu projeto faz distinção entre texto corrigido como resultado de erro do escriba (como em Correção de Caracteres Errôneos) e o texto normalizado ou regularizado de um dialeto ou grafia fonética, forma gramatical, etc., talvez por considerar que estes últimos não são estritamente errados, então estas normalizações podem ser marcadas com o elemento orig (a forma original do escriba) e reg (a forma regularizada. Como em sic e corr, estes elementos serão agrupados num elemento choice, indicando que são duas versões editoriais do mesmo trecho de texto, devendo ser lidas como alternativas e não mostradas lado a lado.

                                                                                                                                                                                                                                                                                                                                É mais comum marcar uma regularização deste tipo a nível da palavra, em vez de marcar os caracteres afetados, como nos exemplos de DDbDP e IOSPE mostrados abaixo. Isto torna mais fácil de gerar uma leitura de aparato da forma regularizada (ou da forma original, dependendo de qual você pretende enfatizar), mas também pode trornar impossível de identificar os caracteres individualmente afetados em uma grafia de dialeto ou forma gramatical. Por outro lado, marcar os caracteres individualmente pode tornar mais fácil indexar ou buscar por caraterísticas específicas, como o iotacismo de ι e ει no exemplo final abaixo.

                                                                                                                                                                                                                                                                                                                                Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                <choice>
                                                                                                                                                                                                                                                                                                                                 <reg>def</reg>
                                                                                                                                                                                                                                                                                                                                 <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                                </choice>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                (Sosin)
                                                                                                                                                                                                                                                                                                                                <choice>
                                                                                                                                                                                                                                                                                                                                 <reg>τιμὴν</reg>
                                                                                                                                                                                                                                                                                                                                 <orig>τειμην</orig>
                                                                                                                                                                                                                                                                                                                                </choice>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: τειμην
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.100#7)
                                                                                                                                                                                                                                                                                                                                <choice>
                                                                                                                                                                                                                                                                                                                                 <orig>κέντ<supplied reason="lost">ρον</supplied>
                                                                                                                                                                                                                                                                                                                                 </orig>
                                                                                                                                                                                                                                                                                                                                 <reg>κάστρον</reg>
                                                                                                                                                                                                                                                                                                                                </choice>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • IOSPE style: κέντ[ρον]
                                                                                                                                                                                                                                                                                                                                τ<choice>
                                                                                                                                                                                                                                                                                                                                 <reg>ι</reg>
                                                                                                                                                                                                                                                                                                                                 <orig>ει</orig>
                                                                                                                                                                                                                                                                                                                                </choice>μὴν

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Default (Panciera) style: τ ει μὴν

                                                                                                                                                                                                                                                                                                                                Como foi mostrado neste último exemplo, a regularização dentro da palavra não aparecerá em qualquer $leiden-style, porque não existe siglum no Leiden para "grafias regularizadas"; geralmente, a prática editorial é imprimir grafias irregulares sem correção, ou algumas vezes tratá-las como erros (e portanto mostrá-las como no caso de Substituição Errônea). Vai ser, portanto, necessária uma customização das folhas de estilo para utilizar a regularização de forma diferente das utilizadas em DDbDP ou IOSPE.

                                                                                                                                                                                                                                                                                                                                Responsabillidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file + customization: orig

                                                                                                                                                                                                                                                                                                                              Se o seu projeto faz distinção entre texto corrigido como resultado de erro do escriba (como em Correção de Caracteres Errôneos) e o texto normalizado ou regularizado de um dialeto ou grafia fonética, forma gramatical, etc., talvez por considerar que estes últimos não são estritamente errados, então estas normalizações podem ser marcadas com o elemento orig (a forma original do escriba) e reg (a forma regularizada. Como em sic e corr, estes elementos serão agrupados num elemento choice, indicando que são duas versões editoriais do mesmo trecho de texto, devendo ser lidas como alternativas e não mostradas lado a lado.

                                                                                                                                                                                                                                                                                                                              É mais comum marcar uma regularização deste tipo a nível da palavra, em vez de marcar os caracteres afetados, como nos exemplos de DDbDP e IOSPE mostrados abaixo. Isto torna mais fácil de gerar uma leitura de aparato da forma regularizada (ou da forma original, dependendo de qual você pretende enfatizar), mas também pode trornar impossível de identificar os caracteres individualmente afetados em uma grafia de dialeto ou forma gramatical. Por outro lado, marcar os caracteres individualmente pode tornar mais fácil indexar ou buscar por caraterísticas específicas, como o iotacismo de ι e ει no exemplo final abaixo.

                                                                                                                                                                                                                                                                                                                              Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                              <choice>
                                                                                                                                                                                                                                                                                                                               <reg>def</reg>
                                                                                                                                                                                                                                                                                                                               <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                              </choice>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Sosin)
                                                                                                                                                                                                                                                                                                                              <choice>
                                                                                                                                                                                                                                                                                                                               <reg>τιμὴν</reg>
                                                                                                                                                                                                                                                                                                                               <orig>τειμην</orig>
                                                                                                                                                                                                                                                                                                                              </choice>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: τειμην
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.100#7)
                                                                                                                                                                                                                                                                                                                              <choice>
                                                                                                                                                                                                                                                                                                                               <orig>κέντ<supplied reason="lost">ρον</supplied>
                                                                                                                                                                                                                                                                                                                               </orig>
                                                                                                                                                                                                                                                                                                                               <reg>κάστρον</reg>
                                                                                                                                                                                                                                                                                                                              </choice>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • IOSPE style: κέντ[ρον]
                                                                                                                                                                                                                                                                                                                              τ<choice>
                                                                                                                                                                                                                                                                                                                               <reg>ι</reg>
                                                                                                                                                                                                                                                                                                                               <orig>ει</orig>
                                                                                                                                                                                                                                                                                                                              </choice>μὴν

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: τ ει μὴν

                                                                                                                                                                                                                                                                                                                              Como foi mostrado neste último exemplo, a regularização dentro da palavra não aparecerá em qualquer $leiden-style, porque não existe siglum no Leiden para "grafias regularizadas"; geralmente, a prática editorial é imprimir grafias irregulares sem correção, ou algumas vezes tratá-las como erros (e portanto mostrá-las como no caso de Substituição Errônea). Vai ser, portanto, necessária uma customização das folhas de estilo para utilizar a regularização de forma diferente das utilizadas em DDbDP ou IOSPE.

                                                                                                                                                                                                                                                                                                                              Responsabillidade por esta seção

                                                                                                                                                                                                                                                                                                                              1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                              2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                              3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-regularization.html b/gl/dev/trans-regularization.html index 66ec3fe54..4d5ed1ea7 100644 --- a/gl/dev/trans-regularization.html +++ b/gl/dev/trans-regularization.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Regularization

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Regularized spellings of irregular forms, such as dialect forms, late spellings, phonetic spellings, etc.

                                                                                                                                                                                                                                                                                                                              • TEI definition: choice ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                Regularization

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Regularized spellings of irregular forms, such as dialect forms, late spellings, phonetic spellings, etc.

                                                                                                                                                                                                                                                                                                                                • TEI definition: choice ; EpiDoc-specific customization: choice
                                                                                                                                                                                                                                                                                                                                • TEI definition: reg ; EpiDoc-specific customization: reg
                                                                                                                                                                                                                                                                                                                                • TEI definition: orig ; EpiDoc-specific - customization: orig

                                                                                                                                                                                                                                                                                                                                If your project makes a distinction between text corrected as a result of scribal error (i.e. Correction of Erroneous Characters) and text normalized or regularized from a dialect or phonetic spelling, grammatical form, etc., perhaps because of the consideration that the latter is not strictly speaking wrong, then these normalizations can be tagged with orig (the original, scribal form) and reg (the regularized form). As with sic and corr, these will be grouped in a choice element, indicating that they are two editorial versions of the same span of text, and should be read as alternatives, not shown side by side.

                                                                                                                                                                                                                                                                                                                                It is most common to mark a regularization of this kind at the level of the whole word, rather than of individual characters affected, as in the DDbDP and IOSPE examples given below. This will make it easier to generate an apparatus reading for the regularized form (or the original form, depending on which you want to privilege), but it may also be impossible to identify individual affected characters in a dialect spelling or grammatical form. On the other hand, tagging the individial characters might make it easier to index or search for specific features, such as the iotacism of ι and ει in the final example below.

                                                                                                                                                                                                                                                                                                                                Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                <choice>
                                                                                                                                                                                                                                                                                                                                 <reg>def</reg>
                                                                                                                                                                                                                                                                                                                                 <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                                </choice>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                (Sosin)
                                                                                                                                                                                                                                                                                                                                <choice>
                                                                                                                                                                                                                                                                                                                                 <reg>τιμὴν</reg>
                                                                                                                                                                                                                                                                                                                                 <orig>τειμην</orig>
                                                                                                                                                                                                                                                                                                                                </choice>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: τειμην
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.100#7)
                                                                                                                                                                                                                                                                                                                                <choice>
                                                                                                                                                                                                                                                                                                                                 <orig>κέντ<supplied reason="lost">ρον</supplied>
                                                                                                                                                                                                                                                                                                                                 </orig>
                                                                                                                                                                                                                                                                                                                                 <reg>κάστρον</reg>
                                                                                                                                                                                                                                                                                                                                </choice>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • IOSPE style: κέντ[ρον]
                                                                                                                                                                                                                                                                                                                                τ<choice>
                                                                                                                                                                                                                                                                                                                                 <reg>ι</reg>
                                                                                                                                                                                                                                                                                                                                 <orig>ει</orig>
                                                                                                                                                                                                                                                                                                                                </choice>μὴν

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Default (Panciera) style: τειμὴν

                                                                                                                                                                                                                                                                                                                                As shown in this last example, the in-word regularization does not currently display anything in any $leiden-style, because there is no Leiden siglum for "regularized spellings"; editorial practice is usually to print irregular spellings uncorrected, or sometimes to treat them as errors (and therefore display as in Erroneous Substitution). Customization of the stylesheets will therefore be required to use regularization in a different way from DDbDP or IOSPE.

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file + customization: orig

                                                                                                                                                                                                                                                                                                                              If your project makes a distinction between text corrected as a result of scribal error (i.e. Correction of Erroneous Characters) and text normalized or regularized from a dialect or phonetic spelling, grammatical form, etc., perhaps because of the consideration that the latter is not strictly speaking wrong, then these normalizations can be tagged with orig (the original, scribal form) and reg (the regularized form). As with sic and corr, these will be grouped in a choice element, indicating that they are two editorial versions of the same span of text, and should be read as alternatives, not shown side by side.

                                                                                                                                                                                                                                                                                                                              It is most common to mark a regularization of this kind at the level of the whole word, rather than of individual characters affected, as in the DDbDP and IOSPE examples given below. This will make it easier to generate an apparatus reading for the regularized form (or the original form, depending on which you want to privilege), but it may also be impossible to identify individual affected characters in a dialect spelling or grammatical form. On the other hand, tagging the individial characters might make it easier to index or search for specific features, such as the iotacism of ι and ει in the final example below.

                                                                                                                                                                                                                                                                                                                              Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                              <choice>
                                                                                                                                                                                                                                                                                                                               <reg>def</reg>
                                                                                                                                                                                                                                                                                                                               <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                              </choice>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                              (Sosin)
                                                                                                                                                                                                                                                                                                                              <choice>
                                                                                                                                                                                                                                                                                                                               <reg>τιμὴν</reg>
                                                                                                                                                                                                                                                                                                                               <orig>τειμην</orig>
                                                                                                                                                                                                                                                                                                                              </choice>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: τειμην
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.100#7)
                                                                                                                                                                                                                                                                                                                              <choice>
                                                                                                                                                                                                                                                                                                                               <orig>κέντ<supplied reason="lost">ρον</supplied>
                                                                                                                                                                                                                                                                                                                               </orig>
                                                                                                                                                                                                                                                                                                                               <reg>κάστρον</reg>
                                                                                                                                                                                                                                                                                                                              </choice>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • IOSPE style: κέντ[ρον]
                                                                                                                                                                                                                                                                                                                              τ<choice>
                                                                                                                                                                                                                                                                                                                               <reg>ι</reg>
                                                                                                                                                                                                                                                                                                                               <orig>ει</orig>
                                                                                                                                                                                                                                                                                                                              </choice>μὴν

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: τειμὴν

                                                                                                                                                                                                                                                                                                                              As shown in this last example, the in-word regularization does not currently display anything in any $leiden-style, because there is no Leiden siglum for "regularized spellings"; editorial practice is usually to print irregular spellings uncorrected, or sometimes to treat them as errors (and therefore display as in Erroneous Substitution). Customization of the stylesheets will therefore be required to use regularization in a different way from DDbDP or IOSPE.

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                              2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-restored-pt-br.html b/gl/dev/trans-restored-pt-br.html index 6d6aa9c83..b0ae797ca 100644 --- a/gl/dev/trans-restored-pt-br.html +++ b/gl/dev/trans-restored-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Restauração Editorial: Caracteres perdidos mas restaurados por um editor moderno

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Nos casos em que o texto que não está presente na fonte é fornecido (seja com base em conjecturas ou vindo de outras testemunhas) para preencher um espaço aparente no texto, pode-se usar supplied. O elemento supplied significa um texto fornecido pelo transcritor ou editor por qualquer motivo, tipicamente porque o original não pode ser lido devido a dano físico ou perda no original.

                                                                                                                                                                                                                                                                                                                              reason indica porque o texto teve de ser fornecido.

                                                                                                                                                                                                                                                                                                                              supplied indica texto perdido no suporte original, restaurado pelo editor, seja por comparação com outros textos, seja por outro conhecimento contextual.

                                                                                                                                                                                                                                                                                                                              Atributos necessários:

                                                                                                                                                                                                                                                                                                                              • reason explica porque o texto foi restaurado; para textos restaurados em lacunas, este atributo recebe o valor "lost" (apesarde outros valores serem possíveis).

                                                                                                                                                                                                                                                                                                                              Panciera 1991 8.1; SEG; Sosin 2011: [abc]

                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">In</supplied>comparabilis

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [In]comparabilis
                                                                                                                                                                                                                                                                                                                              (IRT: 986)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lostcert="low">ὁμο</supplied>λογῶ

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: [ὁμο(?)]λογῶ
                                                                                                                                                                                                                                                                                                                              Note: Se um trecho de texto restaurado for interrompido por outro tipo de marcação estrutural (como tags para palavras ou nomes, ou mesmo se estas não forem usadas, abreviações e números), o texto pode ser dividido em dois ou mais elementos supplied, e a renderização XSLT vai omitir com correção os colchetes redundantes entre estes trechos.
                                                                                                                                                                                                                                                                                                                              <w>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">diui</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <name>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">Tra</supplied>iani
                                                                                                                                                                                                                                                                                                                              </name>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [diui Tra]iani
                                                                                                                                                                                                                                                                                                                              (IRT: 27)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                               <expan>co<ex>n</ex>s<ex>uli</ex>
                                                                                                                                                                                                                                                                                                                               </expan>
                                                                                                                                                                                                                                                                                                                              </supplied>
                                                                                                                                                                                                                                                                                                                              <num>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">I</supplied>V
                                                                                                                                                                                                                                                                                                                              </num>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [co(n)s(uli) I]V
                                                                                                                                                                                                                                                                                                                              (IRT: 28)
                                                                                                                                                                                                                                                                                                                              κεχαραγμένο<supplied reason="lost">ν</supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: κεχαραγμένο[ν]
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.100)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Καῖσαρ καὶ ἡ σύ</supplied>νκλητος

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [Καῖσαρ καὶ ἡ σύ]νκλητος
                                                                                                                                                                                                                                                                                                                              (InsAph: 1.1)

                                                                                                                                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, autor Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                              Restauração Editorial: Caracteres perdidos mas restaurados por um editor moderno

                                                                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                                                                              Nos casos em que o texto que não está presente na fonte é fornecido (seja com base em conjecturas ou vindo de outras testemunhas) para preencher um espaço aparente no texto, pode-se usar supplied. O elemento supplied significa um texto fornecido pelo transcritor ou editor por qualquer motivo, tipicamente porque o original não pode ser lido devido a dano físico ou perda no original.

                                                                                                                                                                                                                                                                                                                              reason indica porque o texto teve de ser fornecido.

                                                                                                                                                                                                                                                                                                                              supplied indica texto perdido no suporte original, restaurado pelo editor, seja por comparação com outros textos, seja por outro conhecimento contextual.

                                                                                                                                                                                                                                                                                                                              Atributos necessários:

                                                                                                                                                                                                                                                                                                                              • reason explica porque o texto foi restaurado; para textos restaurados em lacunas, este atributo recebe o valor "lost" (apesarde outros valores serem possíveis).

                                                                                                                                                                                                                                                                                                                              Panciera 1991 8.1; SEG; Sosin 2011: [abc]

                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">In</supplied>comparabilis

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [In]comparabilis
                                                                                                                                                                                                                                                                                                                              (IRT: 986)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lostcert="low">ὁμο</supplied>λογῶ

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: [ὁμο(?)]λογῶ
                                                                                                                                                                                                                                                                                                                              Note: Se um trecho de texto restaurado for interrompido por outro tipo de marcação estrutural (como tags para palavras ou nomes, ou mesmo se estas não forem usadas, abreviações e números), o texto pode ser dividido em dois ou mais elementos supplied, e a renderização XSLT vai omitir com correção os colchetes redundantes entre estes trechos.
                                                                                                                                                                                                                                                                                                                              <w>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">diui</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <name>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">Tra</supplied>iani
                                                                                                                                                                                                                                                                                                                              </name>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [diui Tra]iani
                                                                                                                                                                                                                                                                                                                              (IRT: 27)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                               <expan>co<ex>n</ex>s<ex>uli</ex>
                                                                                                                                                                                                                                                                                                                               </expan>
                                                                                                                                                                                                                                                                                                                              </supplied>
                                                                                                                                                                                                                                                                                                                              <num>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">I</supplied>V
                                                                                                                                                                                                                                                                                                                              </num>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [co(n)s(uli) I]V
                                                                                                                                                                                                                                                                                                                              (IRT: 28)
                                                                                                                                                                                                                                                                                                                              κεχαραγμένο<supplied reason="lost">ν</supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: κεχαραγμένο[ν]
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.100)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Καῖσαρ καὶ ἡ σύ</supplied>νκλητος

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [Καῖσαρ καὶ ἡ σύ]νκλητος
                                                                                                                                                                                                                                                                                                                              (InsAph: 1.1)

                                                                                                                                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, autor Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-restored.html b/gl/dev/trans-restored.html index 2b659423b..942c1a779 100644 --- a/gl/dev/trans-restored.html +++ b/gl/dev/trans-restored.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Editorial restoration: Characters lost but restored by modern editor

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Where text not present in the source is supplied (whether conjecturally or from other witnesses) to fill an apparent gap in the text, supplied may be used. supplied signifies text supplied by the transcriber or editor for any reason, typically because the original cannot be read because of physical damage or loss to the original.

                                                                                                                                                                                                                                                                                                                              reason indicates why the text has had to be supplied.

                                                                                                                                                                                                                                                                                                                              supplied indicates text lost from the original support, restored by the editor either by comparison with other texts or through other contextual knowledge.

                                                                                                                                                                                                                                                                                                                              Required attributes:

                                                                                                                                                                                                                                                                                                                              • reason explains why the text has been restored, and for text restored in lacunae, is given the value "lost" (although other values are possible).

                                                                                                                                                                                                                                                                                                                              Panciera 1991 8.1; SEG; Sosin 2011: [abc]

                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">In</supplied>comparabilis

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [In]comparabilis
                                                                                                                                                                                                                                                                                                                              (IRT: 986)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lostcert="low">ὁμο</supplied>λογῶ

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: [ὁμο(?)]λογῶ
                                                                                                                                                                                                                                                                                                                              Note: If a span of restored text is broken by other intervening structural markup (e.g. word and name tags, or even if these are not used, abbreviations and numbers), the text may be divided between two or more supplied elements, and the rendering XSLT will correctly omit redundant square brackets between these spans.
                                                                                                                                                                                                                                                                                                                              <w>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">diui</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <name>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">Tra</supplied>iani
                                                                                                                                                                                                                                                                                                                              </name>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [diui Tra]iani
                                                                                                                                                                                                                                                                                                                              (IRT: 27)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                               <expan>co<ex>n</ex>s<ex>uli</ex>
                                                                                                                                                                                                                                                                                                                               </expan>
                                                                                                                                                                                                                                                                                                                              </supplied>
                                                                                                                                                                                                                                                                                                                              <num>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">I</supplied>V
                                                                                                                                                                                                                                                                                                                              </num>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [co(n)s(uli) I]V
                                                                                                                                                                                                                                                                                                                              (IRT: 28)
                                                                                                                                                                                                                                                                                                                              κεχαραγμένο<supplied reason="lost">ν</supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: κεχαραγμένο[ν]
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.100)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Καῖσαρ καὶ ἡ σύ</supplied>νκλητος

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [Καῖσαρ καὶ ἡ σύ]νκλητος
                                                                                                                                                                                                                                                                                                                              (InsAph: 1.1)

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, author Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                              Editorial restoration: Characters lost but restored by modern editor

                                                                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                                                                              Where text not present in the source is supplied (whether conjecturally or from other witnesses) to fill an apparent gap in the text, supplied may be used. supplied signifies text supplied by the transcriber or editor for any reason, typically because the original cannot be read because of physical damage or loss to the original.

                                                                                                                                                                                                                                                                                                                              reason indicates why the text has had to be supplied.

                                                                                                                                                                                                                                                                                                                              supplied indicates text lost from the original support, restored by the editor either by comparison with other texts or through other contextual knowledge.

                                                                                                                                                                                                                                                                                                                              Required attributes:

                                                                                                                                                                                                                                                                                                                              • reason explains why the text has been restored, and for text restored in lacunae, is given the value "lost" (although other values are possible).

                                                                                                                                                                                                                                                                                                                              Panciera 1991 8.1; SEG; Sosin 2011: [abc]

                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">In</supplied>comparabilis

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [In]comparabilis
                                                                                                                                                                                                                                                                                                                              (IRT: 986)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lostcert="low">ὁμο</supplied>λογῶ

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: [ὁμο(?)]λογῶ
                                                                                                                                                                                                                                                                                                                              Note: If a span of restored text is broken by other intervening structural markup (e.g. word and name tags, or even if these are not used, abbreviations and numbers), the text may be divided between two or more supplied elements, and the rendering XSLT will correctly omit redundant square brackets between these spans.
                                                                                                                                                                                                                                                                                                                              <w>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">diui</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <name>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">Tra</supplied>iani
                                                                                                                                                                                                                                                                                                                              </name>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [diui Tra]iani
                                                                                                                                                                                                                                                                                                                              (IRT: 27)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                               <expan>co<ex>n</ex>s<ex>uli</ex>
                                                                                                                                                                                                                                                                                                                               </expan>
                                                                                                                                                                                                                                                                                                                              </supplied>
                                                                                                                                                                                                                                                                                                                              <num>
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">I</supplied>V
                                                                                                                                                                                                                                                                                                                              </num>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [co(n)s(uli) I]V
                                                                                                                                                                                                                                                                                                                              (IRT: 28)
                                                                                                                                                                                                                                                                                                                              κεχαραγμένο<supplied reason="lost">ν</supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Duke Databank style: κεχαραγμένο[ν]
                                                                                                                                                                                                                                                                                                                              (DDbDP: bgu.1.100)
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Καῖσαρ καὶ ἡ σύ</supplied>νκλητος

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [Καῖσαρ καὶ ἡ σύ]νκλητος
                                                                                                                                                                                                                                                                                                                              (InsAph: 1.1)

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Charlotte Tupman, author Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-restoredillustrative-pt-br.html b/gl/dev/trans-restoredillustrative-pt-br.html index c58fbf6d1..251a7212d 100644 --- a/gl/dev/trans-restoredillustrative-pt-br.html +++ b/gl/dev/trans-restoredillustrative-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Restauração Editorial: exemplo ou suplemento ilustrativo

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              Uma nota editorial dentro de uma restauração pode significar coisas diferentes. Nos primeiros exemplos, o editor esclarece algo sobre o que foi restaurado. No EpiDoc esta nota é colocada dentro de um elemento note, dentro do elemento supplied.

                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Αὐτοκράτορος <note>κτλ</note>
                                                                                                                                                                                                                                                                                                                              </supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [Αὐτοκράτορος

                                                                                                                                                                                                                                                                                                                                (κτλ)

                                                                                                                                                                                                                                                                                                                                ]
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                               <note>e.g.</note> ἵνα τὸν
                                                                                                                                                                                                                                                                                                                              </supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [

                                                                                                                                                                                                                                                                                                                                (e.g.)

                                                                                                                                                                                                                                                                                                                                ἵνα τὸν]

                                                                                                                                                                                                                                                                                                                              Nos exemplos seguintes, o editor não pode oferecer uma restauração, apenas pode apontar a categoria geral do que poderia estar ali. Este comentário é marcado como uma descrição de gap, em um elemento desc.

                                                                                                                                                                                                                                                                                                                              <gap reason="lostquantity="1unit="line">
                                                                                                                                                                                                                                                                                                                               <desc>mileage figure</desc>
                                                                                                                                                                                                                                                                                                                              </gap>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [------]
                                                                                                                                                                                                                                                                                                                              <gap reason="lostquantity="4unit="chars">
                                                                                                                                                                                                                                                                                                                               <desc>nomen auctoris</desc>
                                                                                                                                                                                                                                                                                                                              </gap>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [.. ? .. nomen auctoris]
                                                                                                                                                                                                                                                                                                                              (PHI: 77668)

                                                                                                                                                                                                                                                                                                                              See also:

                                                                                                                                                                                                                                                                                                                              Other pages describing <desc>:

                                                                                                                                                                                                                                                                                                                              Other pages describing <gap>:

                                                                                                                                                                                                                                                                                                                              Other pages describing <note>:

                                                                                                                                                                                                                                                                                                                              Other pages describing <supplied>:

                                                                                                                                                                                                                                                                                                                              Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                              1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                              2. Simona Stoyanova, autor
                                                                                                                                                                                                                                                                                                                              3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-restoredillustrative.html b/gl/dev/trans-restoredillustrative.html index 75e794e01..8b9c74417 100644 --- a/gl/dev/trans-restoredillustrative.html +++ b/gl/dev/trans-restoredillustrative.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Editorial restoration: example or illustrative supplement

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              An editorial note inside a restoration may mean different things. In the first examples the editor clarifies something about what has been restored. In EpiDoc this is put in a note inside the supplied.

                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Αὐτοκράτορος <note>κτλ</note>
                                                                                                                                                                                                                                                                                                                              </supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [Αὐτοκράτορος

                                                                                                                                                                                                                                                                                                                                (κτλ)

                                                                                                                                                                                                                                                                                                                                ]
                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">
                                                                                                                                                                                                                                                                                                                               <note>e.g.</note> ἵνα τὸν
                                                                                                                                                                                                                                                                                                                              </supplied>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [

                                                                                                                                                                                                                                                                                                                                (e.g.)

                                                                                                                                                                                                                                                                                                                                ἵνα τὸν]

                                                                                                                                                                                                                                                                                                                              In the following examples the editor cannot supply a restoration, but can only give the general category of what may have stood there. This comment is tagged as a description of the gap, in a desc.

                                                                                                                                                                                                                                                                                                                              <gap reason="lostquantity="1unit="line">
                                                                                                                                                                                                                                                                                                                               <desc>mileage figure</desc>
                                                                                                                                                                                                                                                                                                                              </gap>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [------]
                                                                                                                                                                                                                                                                                                                              <gap reason="lostquantity="4unit="chars">
                                                                                                                                                                                                                                                                                                                               <desc>nomen auctoris</desc>
                                                                                                                                                                                                                                                                                                                              </gap>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: [.. ? ..nomen auctoris]
                                                                                                                                                                                                                                                                                                                              (PHI: 77668)

                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                              1. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                              2. Simona Stoyanova, author

                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                              Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                              \ No newline at end of file diff --git a/gl/dev/trans-restoredincomplete-pt-br.html b/gl/dev/trans-restoredincomplete-pt-br.html index a05ed76fa..c1c04f606 100644 --- a/gl/dev/trans-restoredincomplete-pt-br.html +++ b/gl/dev/trans-restoredincomplete-pt-br.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                              Restauração Editorial: palavra com restauro incompleto

                                                                                                                                                                                                                                                                                                                              2023-04-27

                                                                                                                                                                                                                                                                                                                              O elemento supplied indica texto perdido no suporte original, restaurado pelo editor, seja por comparação com outros textos ou através de conhecimento contextual. Quando uma palavra nãopode ser completamente restaurada, a parte perdida deve ser marcada por um gap. Um elemento w deve ser utilizado com um atributo part, que indica qual parte da palavra está faltando:

                                                                                                                                                                                                                                                                                                                              • 'I' (início)
                                                                                                                                                                                                                                                                                                                              • "M" (meio)
                                                                                                                                                                                                                                                                                                                              • "F" (final)

                                                                                                                                                                                                                                                                                                                              : abc[..?..]

                                                                                                                                                                                                                                                                                                                              <w part="I">
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              Note: Note que os elementos adjacentes supplied e gap não irão resultar em colchetes redundantes dentro de uma mesma lacuna no Example EpiDoc XSLT (veja Lacunas Segmentadas ou Adjacentes).
                                                                                                                                                                                                                                                                                                                              <w part="I">
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">sta</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <gap reason="lost"/>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [sta-·· ? ··]
                                                                                                                                                                                                                                                                                                                              (IRT: 126)
                                                                                                                                                                                                                                                                                                                              <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                              <w part="M">
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">ae</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                              <w part="F">
                                                                                                                                                                                                                                                                                                                               <supplied reason="lost">e</supplied>
                                                                                                                                                                                                                                                                                                                              </w>
                                                                                                                                                                                                                                                                                                                              <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                              (Panciera)
                                                                                                                                                                                                                                                                                                                              <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                               unit="character"/>

                                                                                                                                                                                                                                                                                                                              <w part="F">ui</w>

                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                              • London style: [·· ? ··-]ui
                                                                                                                                                                                                                                                                                                                              (IRT: 87)

                                                                                                                                                                                                                                                                                                                              See also:

                                                                                                                                                                                                                                                                                                                              Other pages describing <supplied>:

                                                                                                                                                                                                                                                                                                                              Other pages describing <w>:

                                                                                                                                                                                                                                                                                                                                Other pages describing <seg>:

                                                                                                                                                                                                                                                                                                                                Other pages describing <gap>:

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-restoredincomplete.html b/gl/dev/trans-restoredincomplete.html index e4a1740ab..b270712dc 100644 --- a/gl/dev/trans-restoredincomplete.html +++ b/gl/dev/trans-restoredincomplete.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Editorial restoration: Word incompletely restored

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                supplied indicates text lost from the original support, restored by the editor either by comparison with other texts or through other contextual knowledge. Where a word cannot be completely restored, the missing part should be indicated by a gap. A w element should be used with a part attribute that explains which part of the word is missing:

                                                                                                                                                                                                                                                                                                                                • 'I' (initial)
                                                                                                                                                                                                                                                                                                                                • "M" (middle)
                                                                                                                                                                                                                                                                                                                                • "F" (final)

                                                                                                                                                                                                                                                                                                                                : abc[..?..]

                                                                                                                                                                                                                                                                                                                                <w part="I">
                                                                                                                                                                                                                                                                                                                                 <supplied reason="lost">abc</supplied>
                                                                                                                                                                                                                                                                                                                                </w>
                                                                                                                                                                                                                                                                                                                                <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Note: Note that adjacent supplied and gap elements will not result in redundant square brackets within a single lacune in the Example EpiDoc XSLT (see Segmented or adjacent lacunae).
                                                                                                                                                                                                                                                                                                                                <w part="I">
                                                                                                                                                                                                                                                                                                                                 <supplied reason="lost">sta</supplied>
                                                                                                                                                                                                                                                                                                                                </w>
                                                                                                                                                                                                                                                                                                                                <gap reason="lost"/>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: [sta-·· ? ··]
                                                                                                                                                                                                                                                                                                                                (IRT: 126)
                                                                                                                                                                                                                                                                                                                                <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                                <w part="M">
                                                                                                                                                                                                                                                                                                                                 <supplied reason="lost">ae</supplied>
                                                                                                                                                                                                                                                                                                                                </w>
                                                                                                                                                                                                                                                                                                                                <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                                <w part="F">
                                                                                                                                                                                                                                                                                                                                 <supplied reason="lost">e</supplied>
                                                                                                                                                                                                                                                                                                                                </w>
                                                                                                                                                                                                                                                                                                                                <gap reason="lost"/>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                                 unit="character"/>

                                                                                                                                                                                                                                                                                                                                <w part="F">ui</w>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: [·· ? ··-]ui
                                                                                                                                                                                                                                                                                                                                (IRT: 87)

                                                                                                                                                                                                                                                                                                                                See also:

                                                                                                                                                                                                                                                                                                                                Other pages describing <supplied>:

                                                                                                                                                                                                                                                                                                                                Other pages describing <w>:

                                                                                                                                                                                                                                                                                                                                Other pages describing <seg>:

                                                                                                                                                                                                                                                                                                                                Other pages describing <gap>:

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-restoreduncert-pt-br.html b/gl/dev/trans-restoreduncert-pt-br.html index b6418989c..aa79f0c24 100644 --- a/gl/dev/trans-restoreduncert-pt-br.html +++ b/gl/dev/trans-restoreduncert-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Restauração Editorial: Caracteres perdidos e restaurados de modo incerto

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Nos casos em que o texto que não está presente na fonte é fornecido (seja por conjectura ou por outras testemunhas) para preencher uma falha aparente no texto, pode-se usar o elemento supplied. supplied significa que o texto foi fornecido pelo transcritor ou editor por qualquer razão, tipicamente porque o original não pode ser lido devido a dano físico ou perda no original.

                                                                                                                                                                                                                                                                                                                                reason indica porque o texto teve de ser fornecido.

                                                                                                                                                                                                                                                                                                                                supplied indica texto perdido no suporte original, restaurado pelo editor, seja por comparação com outros textos, seja por conhecimento contextual.

                                                                                                                                                                                                                                                                                                                                Atributos necessários:

                                                                                                                                                                                                                                                                                                                                • reason explica porque o texto foi restaurado; para textos restaurados dentro de lacunas, este elemento recebe o valor "lost" (apesar de outros valores serem possíveis).

                                                                                                                                                                                                                                                                                                                                Atributos opcionais incluem:

                                                                                                                                                                                                                                                                                                                                • cert com o valor "low" indica texto que foi restaurado de maneira incerta.

                                                                                                                                                                                                                                                                                                                                Panciera 1991: [?abc]

                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">abc</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                ἡμετέρ<supplied reason="lostcert="low">α μήτηρ</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Bon<supplied reason="lostcert="low">ifatius</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Bon[ifatius?]
                                                                                                                                                                                                                                                                                                                                (IRT: 13)
                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">τόκους</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: [τόκους(?)]
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.101#34)

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, autor

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                Restauração Editorial: Caracteres perdidos e restaurados de modo incerto

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Nos casos em que o texto que não está presente na fonte é fornecido (seja por conjectura ou por outras testemunhas) para preencher uma falha aparente no texto, pode-se usar o elemento supplied. supplied significa que o texto foi fornecido pelo transcritor ou editor por qualquer razão, tipicamente porque o original não pode ser lido devido a dano físico ou perda no original.

                                                                                                                                                                                                                                                                                                                                reason indica porque o texto teve de ser fornecido.

                                                                                                                                                                                                                                                                                                                                supplied indica texto perdido no suporte original, restaurado pelo editor, seja por comparação com outros textos, seja por conhecimento contextual.

                                                                                                                                                                                                                                                                                                                                Atributos necessários:

                                                                                                                                                                                                                                                                                                                                • reason explica porque o texto foi restaurado; para textos restaurados dentro de lacunas, este elemento recebe o valor "lost" (apesar de outros valores serem possíveis).

                                                                                                                                                                                                                                                                                                                                Atributos opcionais incluem:

                                                                                                                                                                                                                                                                                                                                • cert com o valor "low" indica texto que foi restaurado de maneira incerta.

                                                                                                                                                                                                                                                                                                                                Panciera 1991: [?abc]

                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">abc</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                ἡμετέρ<supplied reason="lostcert="low">α μήτηρ</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Bon<supplied reason="lostcert="low">ifatius</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Bon[ifatius?]
                                                                                                                                                                                                                                                                                                                                (IRT: 13)
                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">τόκους</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: [τόκους(?)]
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.101#34)

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, autor

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-restoreduncert.html b/gl/dev/trans-restoreduncert.html index e96c2be7c..79c3f2adf 100644 --- a/gl/dev/trans-restoreduncert.html +++ b/gl/dev/trans-restoreduncert.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Editorial restoration: Characters lost and restored tentatively

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Where text not present in the source is supplied (whether conjecturally or from other witnesses) to fill an apparent gap in the text, supplied may be used. supplied signifies text supplied by the transcriber or editor for any reason, typically because the original cannot be read because of physical damage or loss to the original.

                                                                                                                                                                                                                                                                                                                                reason indicates why the text has had to be supplied.

                                                                                                                                                                                                                                                                                                                                supplied indicates text lost from the original support, restored by the editor either by comparison with other texts or through other contextual knowledge.

                                                                                                                                                                                                                                                                                                                                Required attributes:

                                                                                                                                                                                                                                                                                                                                • reason explains why the text has been restored, and for text restored in lacunae, is given the value "lost" (although other values are possible).

                                                                                                                                                                                                                                                                                                                                Optional attributes include:

                                                                                                                                                                                                                                                                                                                                • cert with a value of "low" indicates text that is uncertainly restored.

                                                                                                                                                                                                                                                                                                                                Panciera 1991: [?abc]

                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">abc</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)

                                                                                                                                                                                                                                                                                                                                ἡμετέρ<supplied reason="lostcert="low">α μήτηρ</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)

                                                                                                                                                                                                                                                                                                                                Bon<supplied reason="lostcert="low">ifatius</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Bon[ifatius?]
                                                                                                                                                                                                                                                                                                                                (IRT: 13)
                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">τόκους</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: [τόκους(?)]
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.101#34)

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                Editorial restoration: Characters lost and restored tentatively

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Where text not present in the source is supplied (whether conjecturally or from other witnesses) to fill an apparent gap in the text, supplied may be used. supplied signifies text supplied by the transcriber or editor for any reason, typically because the original cannot be read because of physical damage or loss to the original.

                                                                                                                                                                                                                                                                                                                                reason indicates why the text has had to be supplied.

                                                                                                                                                                                                                                                                                                                                supplied indicates text lost from the original support, restored by the editor either by comparison with other texts or through other contextual knowledge.

                                                                                                                                                                                                                                                                                                                                Required attributes:

                                                                                                                                                                                                                                                                                                                                • reason explains why the text has been restored, and for text restored in lacunae, is given the value "lost" (although other values are possible).

                                                                                                                                                                                                                                                                                                                                Optional attributes include:

                                                                                                                                                                                                                                                                                                                                • cert with a value of "low" indicates text that is uncertainly restored.

                                                                                                                                                                                                                                                                                                                                Panciera 1991: [?abc]

                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">abc</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)

                                                                                                                                                                                                                                                                                                                                ἡμετέρ<supplied reason="lostcert="low">α μήτηρ</supplied>
                                                                                                                                                                                                                                                                                                                                (Panciera)

                                                                                                                                                                                                                                                                                                                                Bon<supplied reason="lostcert="low">ifatius</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Bon[ifatius?]
                                                                                                                                                                                                                                                                                                                                (IRT: 13)
                                                                                                                                                                                                                                                                                                                                <supplied reason="lostcert="low">τόκους</supplied>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: [τόκους(?)]
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.101#34)

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-reversed-pt-br.html b/gl/dev/trans-reversed-pt-br.html index 60a2b8bb7..8a54c75e1 100644 --- a/gl/dev/trans-reversed-pt-br.html +++ b/gl/dev/trans-reversed-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Letras reversas, rotacionadas ou invertidas

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Letras reversas (com orientação da direita para a esquerda) ou invertidas (rotacionadas) em relação ao alinhamento do texto que as cerca. Estes caracteres são considerados como separados do corpo do texto por causa de sua orientação modificada, e são marcados com a tag hi. Este elemento não deve ser usado para indicar texto que estiver todo escrito em reverso, ou documentos bustrofédon (para estes veja Direção do Texto).

                                                                                                                                                                                                                                                                                                                                • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                                Panciera 1991 ...:

                                                                                                                                                                                                                                                                                                                                a<hi rend="reversed">b</hi>c
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Εὐα<hi rend="reversed">ν</hi>τήτῳ

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Εὐα((ν))τήτῳ
                                                                                                                                                                                                                                                                                                                                (InsAph: 15.101)

                                                                                                                                                                                                                                                                                                                                <!-- in RIB 1483 --><hi rend="inverted">F</hi>VRIO

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • RIB style: ((F))VRIO
                                                                                                                                                                                                                                                                                                                                ()

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                Letras reversas, rotacionadas ou invertidas

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Letras reversas (com orientação da direita para a esquerda) ou invertidas (rotacionadas) em relação ao alinhamento do texto que as cerca. Estes caracteres são considerados como separados do corpo do texto por causa de sua orientação modificada, e são marcados com a tag hi. Este elemento não deve ser usado para indicar texto que estiver todo escrito em reverso, ou documentos bustrofédon (para estes veja Direção do Texto).

                                                                                                                                                                                                                                                                                                                                • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                                Panciera 1991 ...:

                                                                                                                                                                                                                                                                                                                                a<hi rend="reversed">b</hi>c
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Εὐα<hi rend="reversed">ν</hi>τήτῳ

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Εὐα((ν))τήτῳ
                                                                                                                                                                                                                                                                                                                                (InsAph: 15.101)

                                                                                                                                                                                                                                                                                                                                <!-- in RIB 1483 --><hi rend="inverted">F</hi>VRIO

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • RIB style: ((F))VRIO
                                                                                                                                                                                                                                                                                                                                ()

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-reversed.html b/gl/dev/trans-reversed.html index 8487d1ad5..f7b5f725d 100644 --- a/gl/dev/trans-reversed.html +++ b/gl/dev/trans-reversed.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Reversed letters; inverted (or rotated) letters

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Letters that are reversed (e.g. right-to-left) or inverted (rotated) with respect to the alignment of the surrounding text. These characters are considered to be set apart from the main body of text by their changed orientation, and so are marked with the hi tag. This element should not be used to indicate text that is all written in reverse, or boustrophedon documents (for which see Direction of Text).

                                                                                                                                                                                                                                                                                                                                • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                                Panciera 1991 ...:

                                                                                                                                                                                                                                                                                                                                a<hi rend="reversed">b</hi>c
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Εὐα<hi rend="reversed">ν</hi>τήτῳ

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Εὐα((ν))τήτῳ
                                                                                                                                                                                                                                                                                                                                (InsAph: 15.101)

                                                                                                                                                                                                                                                                                                                                <!-- in RIB 1483 --><hi rend="inverted">F</hi>VRIO

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • RIB style: ((F))VRIO
                                                                                                                                                                                                                                                                                                                                ()

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                Reversed letters; inverted (or rotated) letters

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Letters that are reversed (e.g. right-to-left) or inverted (rotated) with respect to the alignment of the surrounding text. These characters are considered to be set apart from the main body of text by their changed orientation, and so are marked with the hi tag. This element should not be used to indicate text that is all written in reverse, or boustrophedon documents (for which see Direction of Text).

                                                                                                                                                                                                                                                                                                                                • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                                Panciera 1991 ...:

                                                                                                                                                                                                                                                                                                                                a<hi rend="reversed">b</hi>c
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                Εὐα<hi rend="reversed">ν</hi>τήτῳ

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: Εὐα((ν))τήτῳ
                                                                                                                                                                                                                                                                                                                                (InsAph: 15.101)

                                                                                                                                                                                                                                                                                                                                <!-- in RIB 1483 --><hi rend="inverted">F</hi>VRIO

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • RIB style: ((F))VRIO
                                                                                                                                                                                                                                                                                                                                ()

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-struckovererasure-pt-br.html b/gl/dev/trans-struckovererasure-pt-br.html index 38d7818f0..f5cd84eb3 100644 --- a/gl/dev/trans-struckovererasure-pt-br.html +++ b/gl/dev/trans-struckovererasure-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Texto Escrito Sobre Texto Apagado

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                • TEI definition: subst ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                  Texto Escrito Sobre Texto Apagado

                                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                                  • TEI definition: subst ; EpiDoc-specific customization: subst
                                                                                                                                                                                                                                                                                                                                  • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                                                  Nos casos em que texto foi apagado e reescrito ou corrigido, ele deve ser colocado dentro de um elemento subst. Dentro do subst, o texto apagado deve ser colocado dentro de um elemento del, e a correção e reinscrição dentro de um elemento add, que deve ter um atributo place com o valor "overstrike".

                                                                                                                                                                                                                                                                                                                                  Panciera 1991 VI.1: <<abc>>

                                                                                                                                                                                                                                                                                                                                  Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                  <add place="overstrike">abc</add>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: «abc»
                                                                                                                                                                                                                                                                                                                                  • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                                  <subst>
                                                                                                                                                                                                                                                                                                                                   <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                                                   <del>δεζ</del>
                                                                                                                                                                                                                                                                                                                                  </subst>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: «αβγ»
                                                                                                                                                                                                                                                                                                                                  • Duke Databank style: αβγ
                                                                                                                                                                                                                                                                                                                                  (Sosin)
                                                                                                                                                                                                                                                                                                                                  <add place="overstrike">
                                                                                                                                                                                                                                                                                                                                   <space dim="horizontalextent="7"/>
                                                                                                                                                                                                                                                                                                                                   <g type="scroll"/>
                                                                                                                                                                                                                                                                                                                                   <w lemma="ῥώννυμι">ἔρρωσο</w>
                                                                                                                                                                                                                                                                                                                                  </add>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • London style: «vac scroll ἔρρωσο»
                                                                                                                                                                                                                                                                                                                                  (InsAph: 9.43)
                                                                                                                                                                                                                                                                                                                                  <subst>
                                                                                                                                                                                                                                                                                                                                   <del rend="erasure">Imilchonis</del>
                                                                                                                                                                                                                                                                                                                                   <add place="overstrike">Himilcho</add>
                                                                                                                                                                                                                                                                                                                                  </subst>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • London style: «Himilcho»
                                                                                                                                                                                                                                                                                                                                  (IRT: 319)

                                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                  \ No newline at end of file + customization: add

                                                                                                                                                                                                                                                                                                                                Nos casos em que texto foi apagado e reescrito ou corrigido, ele deve ser colocado dentro de um elemento subst. Dentro do subst, o texto apagado deve ser colocado dentro de um elemento del, e a correção e reinscrição dentro de um elemento add, que deve ter um atributo place com o valor "overstrike".

                                                                                                                                                                                                                                                                                                                                Panciera 1991 VI.1: <<abc>>

                                                                                                                                                                                                                                                                                                                                Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                <add place="overstrike">abc</add>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Default (Panciera) style: «abc»
                                                                                                                                                                                                                                                                                                                                • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                <subst>
                                                                                                                                                                                                                                                                                                                                 <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                                                 <del>δεζ</del>
                                                                                                                                                                                                                                                                                                                                </subst>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Default (Panciera) style: «αβγ»
                                                                                                                                                                                                                                                                                                                                • Duke Databank style: αβγ
                                                                                                                                                                                                                                                                                                                                (Sosin)
                                                                                                                                                                                                                                                                                                                                <add place="overstrike">
                                                                                                                                                                                                                                                                                                                                 <space dim="horizontalextent="7"/>
                                                                                                                                                                                                                                                                                                                                 <g type="scroll"/>
                                                                                                                                                                                                                                                                                                                                 <w lemma="ῥώννυμι">ἔρρωσο</w>
                                                                                                                                                                                                                                                                                                                                </add>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: «vac scroll ἔρρωσο»
                                                                                                                                                                                                                                                                                                                                (InsAph: 9.43)
                                                                                                                                                                                                                                                                                                                                <subst>
                                                                                                                                                                                                                                                                                                                                 <del rend="erasure">Imilchonis</del>
                                                                                                                                                                                                                                                                                                                                 <add place="overstrike">Himilcho</add>
                                                                                                                                                                                                                                                                                                                                </subst>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: «Himilcho»
                                                                                                                                                                                                                                                                                                                                (IRT: 319)

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-struckovererasure.html b/gl/dev/trans-struckovererasure.html index fb42f06a0..b87298512 100644 --- a/gl/dev/trans-struckovererasure.html +++ b/gl/dev/trans-struckovererasure.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Text Struck Over Erasure

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                • TEI definition: subst ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                  Text Struck Over Erasure

                                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                                  • TEI definition: subst ; EpiDoc-specific customization: subst
                                                                                                                                                                                                                                                                                                                                  • TEI definition: add ; EpiDoc-specific - customization: add

                                                                                                                                                                                                                                                                                                                                  Where text has been erased and overstruck or corrected, it should be placed inside a subst. Inside the subst, the erased text should be placed within a del, and the correction or overstrike inside an add, which should have a place with a value of "overstrike".

                                                                                                                                                                                                                                                                                                                                  Panciera 1991 VI.1: <<abc>>

                                                                                                                                                                                                                                                                                                                                  Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                  <add place="overstrike">abc</add>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: «abc»
                                                                                                                                                                                                                                                                                                                                  • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                                  <subst>
                                                                                                                                                                                                                                                                                                                                   <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                                                   <del>δεζ</del>
                                                                                                                                                                                                                                                                                                                                  </subst>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • Default (Panciera) style: «αβγ»
                                                                                                                                                                                                                                                                                                                                  • Duke Databank style: αβγ
                                                                                                                                                                                                                                                                                                                                  (Sosin)
                                                                                                                                                                                                                                                                                                                                  <add place="overstrike">
                                                                                                                                                                                                                                                                                                                                   <space dim="horizontalextent="7"/>
                                                                                                                                                                                                                                                                                                                                   <g type="scroll"/>
                                                                                                                                                                                                                                                                                                                                   <w lemma="ῥώννυμι">ἔρρωσο</w>
                                                                                                                                                                                                                                                                                                                                  </add>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • London style: «vac scroll ἔρρωσο»
                                                                                                                                                                                                                                                                                                                                  (InsAph: 9.43)
                                                                                                                                                                                                                                                                                                                                  <subst>
                                                                                                                                                                                                                                                                                                                                   <del rend="erasure">Imilchonis</del>
                                                                                                                                                                                                                                                                                                                                   <add place="overstrike">Himilcho</add>
                                                                                                                                                                                                                                                                                                                                  </subst>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • London style: «Himilcho»
                                                                                                                                                                                                                                                                                                                                  (IRT: 319)

                                                                                                                                                                                                                                                                                                                                  Responsibility for this section

                                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                  \ No newline at end of file + customization: add

                                                                                                                                                                                                                                                                                                                                Where text has been erased and overstruck or corrected, it should be placed inside a subst. Inside the subst, the erased text should be placed within a del, and the correction or overstrike inside an add, which should have a place with a value of "overstrike".

                                                                                                                                                                                                                                                                                                                                Panciera 1991 VI.1: <<abc>>

                                                                                                                                                                                                                                                                                                                                Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                <add place="overstrike">abc</add>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Default (Panciera) style: «abc»
                                                                                                                                                                                                                                                                                                                                • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                <subst>
                                                                                                                                                                                                                                                                                                                                 <add place="overstrike">αβγ</add>
                                                                                                                                                                                                                                                                                                                                 <del>δεζ</del>
                                                                                                                                                                                                                                                                                                                                </subst>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Default (Panciera) style: «αβγ»
                                                                                                                                                                                                                                                                                                                                • Duke Databank style: αβγ
                                                                                                                                                                                                                                                                                                                                (Sosin)
                                                                                                                                                                                                                                                                                                                                <add place="overstrike">
                                                                                                                                                                                                                                                                                                                                 <space dim="horizontalextent="7"/>
                                                                                                                                                                                                                                                                                                                                 <g type="scroll"/>
                                                                                                                                                                                                                                                                                                                                 <w lemma="ῥώννυμι">ἔρρωσο</w>
                                                                                                                                                                                                                                                                                                                                </add>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: «vac scroll ἔρρωσο»
                                                                                                                                                                                                                                                                                                                                (InsAph: 9.43)
                                                                                                                                                                                                                                                                                                                                <subst>
                                                                                                                                                                                                                                                                                                                                 <del rend="erasure">Imilchonis</del>
                                                                                                                                                                                                                                                                                                                                 <add place="overstrike">Himilcho</add>
                                                                                                                                                                                                                                                                                                                                </subst>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: «Himilcho»
                                                                                                                                                                                                                                                                                                                                (IRT: 319)

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-subaudible-pt-br.html b/gl/dev/trans-subaudible-pt-br.html index db2840258..24d7cbf46 100644 --- a/gl/dev/trans-subaudible-pt-br.html +++ b/gl/dev/trans-subaudible-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Palavra Subaudível

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Suplemento editorial onde o editor torna manifesta uma palavra subaudível

                                                                                                                                                                                                                                                                                                                                Caracteres subaudíveis devem ser colocados dentro de um elemento supplied cujo atributo reason deve ter o valor "subaudible".

                                                                                                                                                                                                                                                                                                                                Panciera 1991 X.4; Sosin 2011: (scil. abc)

                                                                                                                                                                                                                                                                                                                                clarissima <supplied reason="subaudiblecert="high">femina</supplied> Iulia
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                flamen <supplied reason="subaudible">priest</supplied> of Liber Pater

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: flamen (scil. priest) of Liber Pater
                                                                                                                                                                                                                                                                                                                                (IRT: 126)

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                Palavra Subaudível

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Suplemento editorial onde o editor torna manifesta uma palavra subaudível

                                                                                                                                                                                                                                                                                                                                Caracteres subaudíveis devem ser colocados dentro de um elemento supplied cujo atributo reason deve ter o valor "subaudible".

                                                                                                                                                                                                                                                                                                                                Panciera 1991 X.4; Sosin 2011: (scil. abc)

                                                                                                                                                                                                                                                                                                                                clarissima <supplied reason="subaudiblecert="high">femina</supplied> Iulia
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                flamen <supplied reason="subaudible">priest</supplied> of Liber Pater

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: flamen (scil. priest) of Liber Pater
                                                                                                                                                                                                                                                                                                                                (IRT: 126)

                                                                                                                                                                                                                                                                                                                                Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-subaudible.html b/gl/dev/trans-subaudible.html index 5b84fa9bd..023ee9e36 100644 --- a/gl/dev/trans-subaudible.html +++ b/gl/dev/trans-subaudible.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Subaudible Word

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Editorial supplement in which the editor makes a "subaudible" word manifest

                                                                                                                                                                                                                                                                                                                                Subaudible characters should be placed within a supplied whose reason should have a value of "subaudible".

                                                                                                                                                                                                                                                                                                                                Panciera 1991 X.4; Sosin 2011: (scil. abc)

                                                                                                                                                                                                                                                                                                                                clarissima <supplied reason="subaudiblecert="high">femina</supplied> Iulia
                                                                                                                                                                                                                                                                                                                                (Panciera)

                                                                                                                                                                                                                                                                                                                                flamen <supplied reason="subaudible">priest</supplied> of Liber Pater

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: flamen (scil. priest) of Liber Pater
                                                                                                                                                                                                                                                                                                                                (IRT: 126)

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                Subaudible Word

                                                                                                                                                                                                                                                                                                                                2024-03-05

                                                                                                                                                                                                                                                                                                                                Editorial supplement in which the editor makes a "subaudible" word manifest

                                                                                                                                                                                                                                                                                                                                Subaudible characters should be placed within a supplied whose reason should have a value of "subaudible".

                                                                                                                                                                                                                                                                                                                                Panciera 1991 X.4; Sosin 2011: (scil. abc)

                                                                                                                                                                                                                                                                                                                                clarissima <supplied reason="subaudiblecert="high">femina</supplied> Iulia
                                                                                                                                                                                                                                                                                                                                (Panciera)

                                                                                                                                                                                                                                                                                                                                flamen <supplied reason="subaudible">priest</supplied> of Liber Pater

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: flamen (scil. priest) of Liber Pater
                                                                                                                                                                                                                                                                                                                                (IRT: 126)

                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                \ No newline at end of file diff --git a/gl/dev/trans-superfluous-pt-br.html b/gl/dev/trans-superfluous-pt-br.html index e8c83d937..515aa9172 100644 --- a/gl/dev/trans-superfluous-pt-br.html +++ b/gl/dev/trans-superfluous-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                Texto Supérfluo

                                                                                                                                                                                                                                                                                                                                2023-04-27

                                                                                                                                                                                                                                                                                                                                Letras erroneamente incluídas no texto, suprimidas pelo editor.

                                                                                                                                                                                                                                                                                                                                http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHOM

                                                                                                                                                                                                                                                                                                                                As letras que foram erroneamente incluídas no texto devem ser colocadas dentro de um elemento surplus.

                                                                                                                                                                                                                                                                                                                                Panciera 1991 IX.1; Sosin 2011: Valeria{a}nus

                                                                                                                                                                                                                                                                                                                                Valeria<surplus>a</surplus>nus
                                                                                                                                                                                                                                                                                                                                (Panciera)
                                                                                                                                                                                                                                                                                                                                <w lemma="pax">pac<surplus>a</surplus>e</w>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • London style: pac{a}e
                                                                                                                                                                                                                                                                                                                                (IRT: 835)
                                                                                                                                                                                                                                                                                                                                <surplus>τ<unclear>ο</unclear>ῖς</surplus>

                                                                                                                                                                                                                                                                                                                                Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                • Duke Databank style: {το̣ῖς}
                                                                                                                                                                                                                                                                                                                                (DDbDP: bgu.1.183#40)

                                                                                                                                                                                                                                                                                                                                See also:

                                                                                                                                                                                                                                                                                                                                Other pages describing <surplus>:

                                                                                                                                                                                                                                                                                                                                  Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                  1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                  2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                  3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                  4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                  EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                  Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                  \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                  Texto Supérfluo

                                                                                                                                                                                                                                                                                                                                  2024-03-05

                                                                                                                                                                                                                                                                                                                                  Letras erroneamente incluídas no texto, suprimidas pelo editor.

                                                                                                                                                                                                                                                                                                                                  http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHOM

                                                                                                                                                                                                                                                                                                                                  As letras que foram erroneamente incluídas no texto devem ser colocadas dentro de um elemento surplus.

                                                                                                                                                                                                                                                                                                                                  Panciera 1991 IX.1; Sosin 2011: Valeria{a}nus

                                                                                                                                                                                                                                                                                                                                  Valeria<surplus>a</surplus>nus
                                                                                                                                                                                                                                                                                                                                  (Panciera)
                                                                                                                                                                                                                                                                                                                                  <w lemma="pax">pac<surplus>a</surplus>e</w>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • London style: pac{a}e
                                                                                                                                                                                                                                                                                                                                  (IRT: 835)
                                                                                                                                                                                                                                                                                                                                  <surplus>τ<unclear>ο</unclear>ῖς</surplus>

                                                                                                                                                                                                                                                                                                                                  Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                  • Duke Databank style: {το̣ῖς}
                                                                                                                                                                                                                                                                                                                                  (DDbDP: bgu.1.183#40)

                                                                                                                                                                                                                                                                                                                                  See also:

                                                                                                                                                                                                                                                                                                                                  Other pages describing <surplus>:

                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-superfluous.html b/gl/dev/trans-superfluous.html index 2fcc70ba2..cd4f80e02 100644 --- a/gl/dev/trans-superfluous.html +++ b/gl/dev/trans-superfluous.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                    Superfluous Text

                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                    Letters erroneously included in the text, which the editor suppresses.

                                                                                                                                                                                                                                                                                                                                    http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHOM

                                                                                                                                                                                                                                                                                                                                    The letters which have been erroneously included in the text should be placed within a surplus.

                                                                                                                                                                                                                                                                                                                                    Panciera 1991 IX.1; Sosin 2011: Valeria{a}nus

                                                                                                                                                                                                                                                                                                                                    Valeria<surplus>a</surplus>nus
                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                    <w lemma="pax">pac<surplus>a</surplus>e</w>

                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                    • London style: pac{a}e
                                                                                                                                                                                                                                                                                                                                    (IRT: 835)
                                                                                                                                                                                                                                                                                                                                    <surplus>τ<unclear>ο</unclear>ῖς</surplus>

                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: {το̣ῖς}
                                                                                                                                                                                                                                                                                                                                    (DDbDP: bgu.1.183#40)

                                                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                                                    Other pages describing <surplus>:

                                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                      \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                      Superfluous Text

                                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                                      Letters erroneously included in the text, which the editor suppresses.

                                                                                                                                                                                                                                                                                                                                      http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHOM

                                                                                                                                                                                                                                                                                                                                      The letters which have been erroneously included in the text should be placed within a surplus.

                                                                                                                                                                                                                                                                                                                                      Panciera 1991 IX.1; Sosin 2011: Valeria{a}nus

                                                                                                                                                                                                                                                                                                                                      Valeria<surplus>a</surplus>nus
                                                                                                                                                                                                                                                                                                                                      (Panciera)
                                                                                                                                                                                                                                                                                                                                      <w lemma="pax">pac<surplus>a</surplus>e</w>

                                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                      • London style: pac{a}e
                                                                                                                                                                                                                                                                                                                                      (IRT: 835)
                                                                                                                                                                                                                                                                                                                                      <surplus>τ<unclear>ο</unclear>ῖς</surplus>

                                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                      • Duke Databank style: {το̣ῖς}
                                                                                                                                                                                                                                                                                                                                      (DDbDP: bgu.1.183#40)

                                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                                      Other pages describing <surplus>:

                                                                                                                                                                                                                                                                                                                                        Responsibility for this section

                                                                                                                                                                                                                                                                                                                                        1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                        2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                        3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file diff --git a/gl/dev/trans-supralinearetc-pt-br.html b/gl/dev/trans-supralinearetc-pt-br.html index 588f427a2..c702c40b9 100644 --- a/gl/dev/trans-supralinearetc-pt-br.html +++ b/gl/dev/trans-supralinearetc-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                        Linha Supralinear, sublinhado ou strikethrough

                                                                                                                                                                                                                                                                                                                                        2023-04-27

                                                                                                                                                                                                                                                                                                                                        Características lineares como linhas supralineares, sublinhado ou tachado devem ser indicadas com o elemento hi com o valor apropriado do atributo rend.

                                                                                                                                                                                                                                                                                                                                        • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                                        O uso de hi para indicar a aparência física ou decoração de caracteres na pedra ou página é algo separado de qualquer marcação ou daquilo que a decoração possa representar no texto. (Veja, como exemplo, números e numerais).

                                                                                                                                                                                                                                                                                                                                        Estes exemplos mostran amarcação e o tratamento dado a uma linha acimado texto (uma "linha supralinear"):

                                                                                                                                                                                                                                                                                                                                        Panciera 1991 IV.2; Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                                        (Panciera)
                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">θε</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: θε
                                                                                                                                                                                                                                                                                                                                        (DDbDP: bgu.1.153)
                                                                                                                                                                                                                                                                                                                                        <num value="8000">
                                                                                                                                                                                                                                                                                                                                         <hi rend="supraline">VIII</hi>
                                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • London style: VIII
                                                                                                                                                                                                                                                                                                                                        (IRT: 22)

                                                                                                                                                                                                                                                                                                                                        Este exemplo mostra amarcação e o tratamento dado a uma linha abaixo do texto (um "sublinhado"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="underline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        Este exemplo mostra a marcação e o tratamento dado a uma linha que cruza o texto (uma "linha intralinear"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="intraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                        1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                        2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                        3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                        4. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                                                        5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                        Linha Supralinear, sublinhado ou strikethrough

                                                                                                                                                                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                                                                                                                                                                        Características lineares como linhas supralineares, sublinhado ou tachado devem ser indicadas com o elemento hi com o valor apropriado do atributo rend.

                                                                                                                                                                                                                                                                                                                                        • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                                        O uso de hi para indicar a aparência física ou decoração de caracteres na pedra ou página é algo separado de qualquer marcação ou daquilo que a decoração possa representar no texto. (Veja, como exemplo, números e numerais).

                                                                                                                                                                                                                                                                                                                                        Estes exemplos mostran amarcação e o tratamento dado a uma linha acimado texto (uma "linha supralinear"):

                                                                                                                                                                                                                                                                                                                                        Panciera 1991 IV.2; Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                                        (Panciera)
                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">θε</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: θε
                                                                                                                                                                                                                                                                                                                                        (DDbDP: bgu.1.153)
                                                                                                                                                                                                                                                                                                                                        <num value="8000">
                                                                                                                                                                                                                                                                                                                                         <hi rend="supraline">VIII</hi>
                                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • London style: VIII
                                                                                                                                                                                                                                                                                                                                        (IRT: 22)

                                                                                                                                                                                                                                                                                                                                        Este exemplo mostra amarcação e o tratamento dado a uma linha abaixo do texto (um "sublinhado"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="underline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        Este exemplo mostra a marcação e o tratamento dado a uma linha que cruza o texto (uma "linha intralinear"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="intraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                        1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                        2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                        3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                        4. Tom Elliott, autor
                                                                                                                                                                                                                                                                                                                                        5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file diff --git a/gl/dev/trans-supralinearetc.html b/gl/dev/trans-supralinearetc.html index 135544fab..7d575ffb7 100644 --- a/gl/dev/trans-supralinearetc.html +++ b/gl/dev/trans-supralinearetc.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                        Supralinear line, underline or strikethrough

                                                                                                                                                                                                                                                                                                                                        2023-04-27

                                                                                                                                                                                                                                                                                                                                        Linear features such supralinear lines, underlining, or strikethrough should be indicated using hi with an appropriate rend value.

                                                                                                                                                                                                                                                                                                                                        • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                                        The use of hi to indicate the physical appearance or decoration of characters on the stone or page is separate from any tagging of what that decoration might represent in the text. (See, e.g., numbers and numerals).

                                                                                                                                                                                                                                                                                                                                        These examples show the encoding and handling of a line above the text (a "supra-linear line"):

                                                                                                                                                                                                                                                                                                                                        Panciera 1991 IV.2; Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                                        (Panciera)
                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">θε</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: θε
                                                                                                                                                                                                                                                                                                                                        (DDbDP: bgu.1.153)
                                                                                                                                                                                                                                                                                                                                        <num value="8000">
                                                                                                                                                                                                                                                                                                                                         <hi rend="supraline">VIII</hi>
                                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • London style: VIII
                                                                                                                                                                                                                                                                                                                                        (IRT: 22)

                                                                                                                                                                                                                                                                                                                                        This example shows the encoding and handling of a line below the text (a "sub-linear line"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="underline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        This example shows the encoding and handling of a line through the text (a "intra-linear line"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="intraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        Responsibility for this section

                                                                                                                                                                                                                                                                                                                                        1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                        2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                        3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                        4. Tom Elliott, author

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                        Supralinear line, underline or strikethrough

                                                                                                                                                                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                                                                                                                                                                        Linear features such supralinear lines, underlining, or strikethrough should be indicated using hi with an appropriate rend value.

                                                                                                                                                                                                                                                                                                                                        • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                                        The use of hi to indicate the physical appearance or decoration of characters on the stone or page is separate from any tagging of what that decoration might represent in the text. (See, e.g., numbers and numerals).

                                                                                                                                                                                                                                                                                                                                        These examples show the encoding and handling of a line above the text (a "supra-linear line"):

                                                                                                                                                                                                                                                                                                                                        Panciera 1991 IV.2; Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: abc
                                                                                                                                                                                                                                                                                                                                        (Panciera)
                                                                                                                                                                                                                                                                                                                                        <hi rend="supraline">θε</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: θε
                                                                                                                                                                                                                                                                                                                                        (DDbDP: bgu.1.153)
                                                                                                                                                                                                                                                                                                                                        <num value="8000">
                                                                                                                                                                                                                                                                                                                                         <hi rend="supraline">VIII</hi>
                                                                                                                                                                                                                                                                                                                                        </num>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • London style: VIII
                                                                                                                                                                                                                                                                                                                                        (IRT: 22)

                                                                                                                                                                                                                                                                                                                                        This example shows the encoding and handling of a line below the text (a "sub-linear line"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="underline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        This example shows the encoding and handling of a line through the text (a "intra-linear line"):

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: abc

                                                                                                                                                                                                                                                                                                                                        <hi rend="intraline">abc</hi>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: abc
                                                                                                                                                                                                                                                                                                                                        (Sosin)

                                                                                                                                                                                                                                                                                                                                        Responsibility for this section

                                                                                                                                                                                                                                                                                                                                        1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                        2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                        3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                        4. Tom Elliott, author

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file diff --git a/gl/dev/trans-symbol-pt-br.html b/gl/dev/trans-symbol-pt-br.html index ac987a251..c42002e67 100644 --- a/gl/dev/trans-symbol-pt-br.html +++ b/gl/dev/trans-symbol-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                        Símbolo (não carrega significado)

                                                                                                                                                                                                                                                                                                                                        2023-04-27

                                                                                                                                                                                                                                                                                                                                        • TEI definition: g ; EpiDoc-specific - customization: g

                                                                                                                                                                                                                                                                                                                                        g (caracter ou glifo) representa um caracter ou glifo fora do padrão.

                                                                                                                                                                                                                                                                                                                                        Nos casos em que um símbolo não carrega significado, ele deve ser representado com o uso do elemento g, com o seguinte atributo:

                                                                                                                                                                                                                                                                                                                                        • type indica o nome do símbolo decorativo, como folha.

                                                                                                                                                                                                                                                                                                                                        Um caracter Unicode que represente o símbolo também pode aparecer dentro do elemento g, se desejado.

                                                                                                                                                                                                                                                                                                                                        Panciera 1991 19: ((crux))

                                                                                                                                                                                                                                                                                                                                        Dohnicht 4: ⊂crux⊃

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: /

                                                                                                                                                                                                                                                                                                                                        SEG: dr.

                                                                                                                                                                                                                                                                                                                                        <g type="crux"/>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: ((crux))
                                                                                                                                                                                                                                                                                                                                        • Dohnicht style: ⊂crux⊃
                                                                                                                                                                                                                                                                                                                                        (IRT: 203)
                                                                                                                                                                                                                                                                                                                                        <g type="slanting-stroke"/>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: ((slanting-stroke))
                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: /
                                                                                                                                                                                                                                                                                                                                        (DDbDP: p.worp..48#4)
                                                                                                                                                                                                                                                                                                                                        <g type="scroll"/>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: ((scroll))
                                                                                                                                                                                                                                                                                                                                        • London style: scroll
                                                                                                                                                                                                                                                                                                                                        (InsAph: 1.121)

                                                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                        1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                        2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                        Símbolo (não carrega significado)

                                                                                                                                                                                                                                                                                                                                        2024-03-05

                                                                                                                                                                                                                                                                                                                                        • TEI definition: g ; EpiDoc-specific + customization: g

                                                                                                                                                                                                                                                                                                                                        g (caracter ou glifo) representa um caracter ou glifo fora do padrão.

                                                                                                                                                                                                                                                                                                                                        Nos casos em que um símbolo não carrega significado, ele deve ser representado com o uso do elemento g, com o seguinte atributo:

                                                                                                                                                                                                                                                                                                                                        • type indica o nome do símbolo decorativo, como folha.

                                                                                                                                                                                                                                                                                                                                        Um caracter Unicode que represente o símbolo também pode aparecer dentro do elemento g, se desejado.

                                                                                                                                                                                                                                                                                                                                        Panciera 1991 19: ((crux))

                                                                                                                                                                                                                                                                                                                                        Dohnicht 4: ⊂crux⊃

                                                                                                                                                                                                                                                                                                                                        Sosin 2011: /

                                                                                                                                                                                                                                                                                                                                        SEG: dr.

                                                                                                                                                                                                                                                                                                                                        <g type="crux"/>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: ((crux))
                                                                                                                                                                                                                                                                                                                                        • Dohnicht style: ⊂crux⊃
                                                                                                                                                                                                                                                                                                                                        (IRT: 203)
                                                                                                                                                                                                                                                                                                                                        <g type="slanting-stroke"/>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: ((slanting-stroke))
                                                                                                                                                                                                                                                                                                                                        • Duke Databank style: /
                                                                                                                                                                                                                                                                                                                                        (DDbDP: p.worp..48#4)
                                                                                                                                                                                                                                                                                                                                        <g type="scroll"/>

                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                        • Default (Panciera) style: ((scroll))
                                                                                                                                                                                                                                                                                                                                        • London style: scroll
                                                                                                                                                                                                                                                                                                                                        (InsAph: 1.121)

                                                                                                                                                                                                                                                                                                                                        Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                        1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                        2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                        EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                        Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                        \ No newline at end of file diff --git a/gl/dev/trans-symbol.html b/gl/dev/trans-symbol.html index 0749fd544..65322c1d0 100644 --- a/gl/dev/trans-symbol.html +++ b/gl/dev/trans-symbol.html @@ -21,8 +21,8 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                        Symbol (non meaning-bearing)

                                                                                                                                                                                                                                                                                                                                        2023-04-27

                                                                                                                                                                                                                                                                                                                                        • TEI definition: g ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                          Symbol (non meaning-bearing)

                                                                                                                                                                                                                                                                                                                                          2024-03-05

                                                                                                                                                                                                                                                                                                                                          • TEI definition: g ; EpiDoc-specific customization: g
                                                                                                                                                                                                                                                                                                                                          • TEI definition: glyph ; EpiDoc-specific customization: glyph
                                                                                                                                                                                                                                                                                                                                          • TEI definition: mapping ; EpiDoc-specific customization: mapping
                                                                                                                                                                                                                                                                                                                                          • TEI definition: prefixDef ; EpiDoc-specific - customization: prefixDef

                                                                                                                                                                                                                                                                                                                                          g (character or glyph) represents a non-standard character or glyph.

                                                                                                                                                                                                                                                                                                                                          Where a symbol is non meaning-bearing, it should be represented using the element g, with the following attribute:

                                                                                                                                                                                                                                                                                                                                          • ref pointing to a glyph listed in charDecl.
                                                                                                                                                                                                                                                                                                                                          • in the past many projects used type.

                                                                                                                                                                                                                                                                                                                                          A Unicode character representing the symbol may also appear inside the g if desired.

                                                                                                                                                                                                                                                                                                                                          The ref attribute in g can be used in various ways.

                                                                                                                                                                                                                                                                                                                                          The following encoding

                                                                                                                                                                                                                                                                                                                                          <g ref="#crux"/>

                                                                                                                                                                                                                                                                                                                                          exepcts that a charDecl is present in the document. This will look like the following.

                                                                                                                                                                                                                                                                                                                                          <charDecl>
                                                                                                                                                                                                                                                                                                                                           <glyph xml:id="crux">
                                                                                                                                                                                                                                                                                                                                            <mapping type="standard"></mapping>
                                                                                                                                                                                                                                                                                                                                            <mapping type="simplified">(crux)</mapping>
                                                                                                                                                                                                                                                                                                                                            <mapping type="g-london-diplomatic"></mapping>
                                                                                                                                                                                                                                                                                                                                           </glyph>
                                                                                                                                                                                                                                                                                                                                          </charDecl>

                                                                                                                                                                                                                                                                                                                                          You may add this to your files, or include it as appropriate. A list is available with the example stylesheets (with variable solutions according to the parameters settings), which is used as a default where charDecl is not explicitly added in the XML file.

                                                                                                                                                                                                                                                                                                                                          You may wish to point to this list of glyphs in a separate file, in which case you can use in ref of g a path to this resource.

                                                                                                                                                                                                                                                                                                                                          <g ref="/path/to/your/chardecl.xml#crux"/>

                                                                                                                                                                                                                                                                                                                                          If you use prefixes, defined in prefixDef, you may use a shorthand. Assuming you have defined this prefix to be glyph, you may use

                                                                                                                                                                                                                                                                                                                                          <prefixDef ident="glyph"
                                                                                                                                                                                                                                                                                                                                           matchPattern="([a-zA-Z0-9]+)"
                                                                                                                                                                                                                                                                                                                                           replacementPattern="/path/to/your/chardecl.xml#$1"/>

                                                                                                                                                                                                                                                                                                                                          ...

                                                                                                                                                                                                                                                                                                                                          <g ref="glyph:crux"/>

                                                                                                                                                                                                                                                                                                                                          The full path or prefixed method allows also to define different sources for your charDecl, so that you may only have to add the one which are missing, unless you want to contribute them directly to the default charDecl in the stylesheet repository.

                                                                                                                                                                                                                                                                                                                                          Panciera 1991 19: ((crux))

                                                                                                                                                                                                                                                                                                                                          Dohnicht 4: ⊂crux⊃

                                                                                                                                                                                                                                                                                                                                          Sosin 2011: /

                                                                                                                                                                                                                                                                                                                                          SEG: dr.

                                                                                                                                                                                                                                                                                                                                          The projects providing the following examples used type when this was the suggested way of encoding.

                                                                                                                                                                                                                                                                                                                                          <g type="crux"/>

                                                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                          • Default (Panciera) style: ((crux))
                                                                                                                                                                                                                                                                                                                                          • Dohnicht style: ⊂crux⊃
                                                                                                                                                                                                                                                                                                                                          (IRT: 203)
                                                                                                                                                                                                                                                                                                                                          <g type="slanting-stroke"/>

                                                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                          • Default (Panciera) style: ((slanting-stroke))
                                                                                                                                                                                                                                                                                                                                          • Duke Databank style: /
                                                                                                                                                                                                                                                                                                                                          (DDbDP: p.worp..48#4)
                                                                                                                                                                                                                                                                                                                                          <g type="scroll"/>

                                                                                                                                                                                                                                                                                                                                          Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                          • Default (Panciera) style: ((scroll))
                                                                                                                                                                                                                                                                                                                                          • London style: scroll
                                                                                                                                                                                                                                                                                                                                          (InsAph: 1.121)
                                                                                                                                                                                                                                                                                                                                          xml:id
                                                                                                                                                                                                                                                                                                                                          apostrophe
                                                                                                                                                                                                                                                                                                                                          diastole
                                                                                                                                                                                                                                                                                                                                          barless-A
                                                                                                                                                                                                                                                                                                                                          center-brace-closing
                                                                                                                                                                                                                                                                                                                                          center-brace-opening
                                                                                                                                                                                                                                                                                                                                          century
                                                                                                                                                                                                                                                                                                                                          check
                                                                                                                                                                                                                                                                                                                                          check-mark
                                                                                                                                                                                                                                                                                                                                          chi-rho
                                                                                                                                                                                                                                                                                                                                          chirho
                                                                                                                                                                                                                                                                                                                                          crux
                                                                                                                                                                                                                                                                                                                                          crosses
                                                                                                                                                                                                                                                                                                                                          cross
                                                                                                                                                                                                                                                                                                                                          dash
                                                                                                                                                                                                                                                                                                                                          dipunct
                                                                                                                                                                                                                                                                                                                                          denarius
                                                                                                                                                                                                                                                                                                                                          dot
                                                                                                                                                                                                                                                                                                                                          double-vertical-bar
                                                                                                                                                                                                                                                                                                                                          drachma
                                                                                                                                                                                                                                                                                                                                          filled-circle
                                                                                                                                                                                                                                                                                                                                          filler
                                                                                                                                                                                                                                                                                                                                          hourglass
                                                                                                                                                                                                                                                                                                                                          interpunct
                                                                                                                                                                                                                                                                                                                                          latin-interpunct
                                                                                                                                                                                                                                                                                                                                          leaf
                                                                                                                                                                                                                                                                                                                                          linear-B-je
                                                                                                                                                                                                                                                                                                                                          long-vertical-bar
                                                                                                                                                                                                                                                                                                                                          lower-brace-closing
                                                                                                                                                                                                                                                                                                                                          lower-brace-opening
                                                                                                                                                                                                                                                                                                                                          middot
                                                                                                                                                                                                                                                                                                                                          mid-punctus
                                                                                                                                                                                                                                                                                                                                          low-punctus
                                                                                                                                                                                                                                                                                                                                          high-punctus
                                                                                                                                                                                                                                                                                                                                          milliaria
                                                                                                                                                                                                                                                                                                                                          monogram
                                                                                                                                                                                                                                                                                                                                          palm
                                                                                                                                                                                                                                                                                                                                          palmula
                                                                                                                                                                                                                                                                                                                                          parens-middle-closing
                                                                                                                                                                                                                                                                                                                                          parens-middle-opening
                                                                                                                                                                                                                                                                                                                                          parens-lower-closing
                                                                                                                                                                                                                                                                                                                                          parens-lower-opening
                                                                                                                                                                                                                                                                                                                                          parens-upper-closing
                                                                                                                                                                                                                                                                                                                                          parens-upper-opening
                                                                                                                                                                                                                                                                                                                                          rho-cross
                                                                                                                                                                                                                                                                                                                                          sestercius
                                                                                                                                                                                                                                                                                                                                          sestertius
                                                                                                                                                                                                                                                                                                                                          slanting-stroke
                                                                                                                                                                                                                                                                                                                                          star
                                                                                                                                                                                                                                                                                                                                          stauros
                                                                                                                                                                                                                                                                                                                                          staurogram
                                                                                                                                                                                                                                                                                                                                          stop
                                                                                                                                                                                                                                                                                                                                          swastika
                                                                                                                                                                                                                                                                                                                                          tachygraphic_marks
                                                                                                                                                                                                                                                                                                                                          taurho
                                                                                                                                                                                                                                                                                                                                          tripunct
                                                                                                                                                                                                                                                                                                                                          upper-brace-closing
                                                                                                                                                                                                                                                                                                                                          upper-brace-opening
                                                                                                                                                                                                                                                                                                                                          year
                                                                                                                                                                                                                                                                                                                                          diple
                                                                                                                                                                                                                                                                                                                                          diple-obelismene
                                                                                                                                                                                                                                                                                                                                          diple-periestigmene
                                                                                                                                                                                                                                                                                                                                          asteriskos
                                                                                                                                                                                                                                                                                                                                          parens-punctuation-closing
                                                                                                                                                                                                                                                                                                                                          parens-punctuation-openinig
                                                                                                                                                                                                                                                                                                                                          downwards-ancora
                                                                                                                                                                                                                                                                                                                                          upwards-ancora
                                                                                                                                                                                                                                                                                                                                          antisigma
                                                                                                                                                                                                                                                                                                                                          antisigma-periestigmene
                                                                                                                                                                                                                                                                                                                                          hypodiastole
                                                                                                                                                                                                                                                                                                                                          swungdash
                                                                                                                                                                                                                                                                                                                                          tetrapunct
                                                                                                                                                                                                                                                                                                                                          chi-periestigmenon
                                                                                                                                                                                                                                                                                                                                          dotted-obelos
                                                                                                                                                                                                                                                                                                                                          obelos
                                                                                                                                                                                                                                                                                                                                          x
                                                                                                                                                                                                                                                                                                                                          xs

                                                                                                                                                                                                                                                                                                                                          See also:

                                                                                                                                                                                                                                                                                                                                          Other pages describing <g>:

                                                                                                                                                                                                                                                                                                                                          Other pages describing <glyph>:

                                                                                                                                                                                                                                                                                                                                            Other pages describing <mapping>:

                                                                                                                                                                                                                                                                                                                                              Other pages describing <prefixDef>:

                                                                                                                                                                                                                                                                                                                                                Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                2. Pietro Maria Liuzzo, Added g/@ref as per FR 81

                                                                                                                                                                                                                                                                                                                                                EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                \ No newline at end of file + customization: prefixDef

                                                                                                                                                                                                                                                                                                                                              g (character or glyph) represents a non-standard character or glyph.

                                                                                                                                                                                                                                                                                                                                              Where a symbol is non meaning-bearing, it should be represented using the element g, with the following attribute:

                                                                                                                                                                                                                                                                                                                                              • ref pointing to a glyph listed in charDecl.
                                                                                                                                                                                                                                                                                                                                              • in the past many projects used type.

                                                                                                                                                                                                                                                                                                                                              A Unicode character representing the symbol may also appear inside the g if desired.

                                                                                                                                                                                                                                                                                                                                              The ref attribute in g can be used in various ways.

                                                                                                                                                                                                                                                                                                                                              The following encoding

                                                                                                                                                                                                                                                                                                                                              <g ref="#crux"/>

                                                                                                                                                                                                                                                                                                                                              exepcts that a charDecl is present in the document. This will look like the following.

                                                                                                                                                                                                                                                                                                                                              <charDecl>
                                                                                                                                                                                                                                                                                                                                               <glyph xml:id="crux">
                                                                                                                                                                                                                                                                                                                                                <mapping type="standard"></mapping>
                                                                                                                                                                                                                                                                                                                                                <mapping type="simplified">(crux)</mapping>
                                                                                                                                                                                                                                                                                                                                                <mapping type="g-london-diplomatic"></mapping>
                                                                                                                                                                                                                                                                                                                                               </glyph>
                                                                                                                                                                                                                                                                                                                                              </charDecl>

                                                                                                                                                                                                                                                                                                                                              You may add this to your files, or include it as appropriate. A list is available with the example stylesheets (with variable solutions according to the parameters settings), which is used as a default where charDecl is not explicitly added in the XML file.

                                                                                                                                                                                                                                                                                                                                              You may wish to point to this list of glyphs in a separate file, in which case you can use in ref of g a path to this resource.

                                                                                                                                                                                                                                                                                                                                              <g ref="/path/to/your/chardecl.xml#crux"/>

                                                                                                                                                                                                                                                                                                                                              If you use prefixes, defined in prefixDef, you may use a shorthand. Assuming you have defined this prefix to be glyph, you may use

                                                                                                                                                                                                                                                                                                                                              <prefixDef ident="glyph"
                                                                                                                                                                                                                                                                                                                                               matchPattern="([a-zA-Z0-9]+)"
                                                                                                                                                                                                                                                                                                                                               replacementPattern="/path/to/your/chardecl.xml#$1"/>

                                                                                                                                                                                                                                                                                                                                              ...

                                                                                                                                                                                                                                                                                                                                              <g ref="glyph:crux"/>

                                                                                                                                                                                                                                                                                                                                              The full path or prefixed method allows also to define different sources for your charDecl, so that you may only have to add the one which are missing, unless you want to contribute them directly to the default charDecl in the stylesheet repository.

                                                                                                                                                                                                                                                                                                                                              Panciera 1991 19: ((crux))

                                                                                                                                                                                                                                                                                                                                              Dohnicht 4: ⊂crux⊃

                                                                                                                                                                                                                                                                                                                                              Sosin 2011: /

                                                                                                                                                                                                                                                                                                                                              SEG: dr.

                                                                                                                                                                                                                                                                                                                                              The projects providing the following examples used type when this was the suggested way of encoding.

                                                                                                                                                                                                                                                                                                                                              <g type="crux"/>

                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: ((crux))
                                                                                                                                                                                                                                                                                                                                              • Dohnicht style: ⊂crux⊃
                                                                                                                                                                                                                                                                                                                                              (IRT: 203)
                                                                                                                                                                                                                                                                                                                                              <g type="slanting-stroke"/>

                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: ((slanting-stroke))
                                                                                                                                                                                                                                                                                                                                              • Duke Databank style: /
                                                                                                                                                                                                                                                                                                                                              (DDbDP: p.worp..48#4)
                                                                                                                                                                                                                                                                                                                                              <g type="scroll"/>

                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style: ((scroll))
                                                                                                                                                                                                                                                                                                                                              • London style: scroll
                                                                                                                                                                                                                                                                                                                                              (InsAph: 1.121)
                                                                                                                                                                                                                                                                                                                                              xml:id
                                                                                                                                                                                                                                                                                                                                              apostrophe
                                                                                                                                                                                                                                                                                                                                              diastole
                                                                                                                                                                                                                                                                                                                                              barless-A
                                                                                                                                                                                                                                                                                                                                              center-brace-closing
                                                                                                                                                                                                                                                                                                                                              center-brace-opening
                                                                                                                                                                                                                                                                                                                                              century
                                                                                                                                                                                                                                                                                                                                              check
                                                                                                                                                                                                                                                                                                                                              check-mark
                                                                                                                                                                                                                                                                                                                                              chi-rho
                                                                                                                                                                                                                                                                                                                                              chirho
                                                                                                                                                                                                                                                                                                                                              crux
                                                                                                                                                                                                                                                                                                                                              crosses
                                                                                                                                                                                                                                                                                                                                              cross
                                                                                                                                                                                                                                                                                                                                              dash
                                                                                                                                                                                                                                                                                                                                              dipunct
                                                                                                                                                                                                                                                                                                                                              denarius
                                                                                                                                                                                                                                                                                                                                              dot
                                                                                                                                                                                                                                                                                                                                              double-vertical-bar
                                                                                                                                                                                                                                                                                                                                              drachma
                                                                                                                                                                                                                                                                                                                                              filled-circle
                                                                                                                                                                                                                                                                                                                                              filler
                                                                                                                                                                                                                                                                                                                                              hourglass
                                                                                                                                                                                                                                                                                                                                              interpunct
                                                                                                                                                                                                                                                                                                                                              latin-interpunct
                                                                                                                                                                                                                                                                                                                                              leaf
                                                                                                                                                                                                                                                                                                                                              linear-B-je
                                                                                                                                                                                                                                                                                                                                              long-vertical-bar
                                                                                                                                                                                                                                                                                                                                              lower-brace-closing
                                                                                                                                                                                                                                                                                                                                              lower-brace-opening
                                                                                                                                                                                                                                                                                                                                              middot
                                                                                                                                                                                                                                                                                                                                              mid-punctus
                                                                                                                                                                                                                                                                                                                                              low-punctus
                                                                                                                                                                                                                                                                                                                                              high-punctus
                                                                                                                                                                                                                                                                                                                                              milliaria
                                                                                                                                                                                                                                                                                                                                              monogram
                                                                                                                                                                                                                                                                                                                                              palm
                                                                                                                                                                                                                                                                                                                                              palmula
                                                                                                                                                                                                                                                                                                                                              parens-middle-closing
                                                                                                                                                                                                                                                                                                                                              parens-middle-opening
                                                                                                                                                                                                                                                                                                                                              parens-lower-closing
                                                                                                                                                                                                                                                                                                                                              parens-lower-opening
                                                                                                                                                                                                                                                                                                                                              parens-upper-closing
                                                                                                                                                                                                                                                                                                                                              parens-upper-opening
                                                                                                                                                                                                                                                                                                                                              rho-cross
                                                                                                                                                                                                                                                                                                                                              sestercius
                                                                                                                                                                                                                                                                                                                                              sestertius
                                                                                                                                                                                                                                                                                                                                              slanting-stroke
                                                                                                                                                                                                                                                                                                                                              star
                                                                                                                                                                                                                                                                                                                                              stauros
                                                                                                                                                                                                                                                                                                                                              staurogram
                                                                                                                                                                                                                                                                                                                                              stop
                                                                                                                                                                                                                                                                                                                                              swastika
                                                                                                                                                                                                                                                                                                                                              tachygraphic_marks
                                                                                                                                                                                                                                                                                                                                              taurho
                                                                                                                                                                                                                                                                                                                                              tripunct
                                                                                                                                                                                                                                                                                                                                              upper-brace-closing
                                                                                                                                                                                                                                                                                                                                              upper-brace-opening
                                                                                                                                                                                                                                                                                                                                              year
                                                                                                                                                                                                                                                                                                                                              diple
                                                                                                                                                                                                                                                                                                                                              diple-obelismene
                                                                                                                                                                                                                                                                                                                                              diple-periestigmene
                                                                                                                                                                                                                                                                                                                                              asteriskos
                                                                                                                                                                                                                                                                                                                                              parens-punctuation-closing
                                                                                                                                                                                                                                                                                                                                              parens-punctuation-openinig
                                                                                                                                                                                                                                                                                                                                              downwards-ancora
                                                                                                                                                                                                                                                                                                                                              upwards-ancora
                                                                                                                                                                                                                                                                                                                                              antisigma
                                                                                                                                                                                                                                                                                                                                              antisigma-periestigmene
                                                                                                                                                                                                                                                                                                                                              hypodiastole
                                                                                                                                                                                                                                                                                                                                              swungdash
                                                                                                                                                                                                                                                                                                                                              tetrapunct
                                                                                                                                                                                                                                                                                                                                              chi-periestigmenon
                                                                                                                                                                                                                                                                                                                                              dotted-obelos
                                                                                                                                                                                                                                                                                                                                              obelos
                                                                                                                                                                                                                                                                                                                                              x
                                                                                                                                                                                                                                                                                                                                              xs

                                                                                                                                                                                                                                                                                                                                              See also:

                                                                                                                                                                                                                                                                                                                                              Other pages describing <g>:

                                                                                                                                                                                                                                                                                                                                              Other pages describing <glyph>:

                                                                                                                                                                                                                                                                                                                                                Other pages describing <mapping>:

                                                                                                                                                                                                                                                                                                                                                  Other pages describing <prefixDef>:

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    2. Pietro Maria Liuzzo, Added g/@ref as per FR 81

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-symbolchirho-pt-br.html b/gl/dev/trans-symbolchirho-pt-br.html index 774a488be..0484c8f94 100644 --- a/gl/dev/trans-symbolchirho-pt-br.html +++ b/gl/dev/trans-symbolchirho-pt-br.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Chi-Rho

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    expan (expansão) contém a forma expandida de uma palavra abreviada.

                                                                                                                                                                                                                                                                                                                                                    abbr (abreviação) contém uma abreviação de qualquer tipo.

                                                                                                                                                                                                                                                                                                                                                    am (abbreviation marker - marcador de abreviação) contém uma sequência de letras ou sinais presentes em uma abreviação que são omitidos ou substituídos nas versão expandida da abreviação

                                                                                                                                                                                                                                                                                                                                                    g (caracter ou glifo) representa um caracter ou glifo fora do padrão; type indica o nome do símbolo decorativo. como folha.

                                                                                                                                                                                                                                                                                                                                                    ex (expansão editorial) contém uma sequência de letras acrescentadas pelo editor ou transcritor quando expande uma abreviação.

                                                                                                                                                                                                                                                                                                                                                    hi (highlighted) marca uma palavra ou frase como graficamente distinta do texto que a cerca, sem que seja feita qualquer declaração a respeito das razõesdesta diferença.

                                                                                                                                                                                                                                                                                                                                                    Quando um símbolo Chi-Rho aparece, ele pode ter uma série de diferentes valores semânticos (abreviação ou logograma para "Cristo" ou "Cristão"; uma indicação geral e não-verbal de fé ou afiliação; ligadura do Χ e do Ρ for a de qualquer contexto cristão), ou o editos pode preferir não dar qualquer interpretação a respeito do símbolo. Os exemplos abaixo mostram algumasdas maneiras de se lidar com esta variedade.

                                                                                                                                                                                                                                                                                                                                                    Um valor Unicode (por exemplo U+2627) pode ser usado dentrodo elemento g, se desejado.

                                                                                                                                                                                                                                                                                                                                                    Sosin 2011:

                                                                                                                                                                                                                                                                                                                                                    <g type="chi-rho"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: ((chi-rho))
                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((chi-rho))
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    <g type="chi-rho"></g>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: ((chi-rho))
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                                                                       <g type="chi-rho"/>
                                                                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>Χρίστος</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: (Χρίστος)
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                                                                       <g type="chi-rho"/>
                                                                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>Christ</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>opher

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: (Christ) opher
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="ligature">Χρ</hi>υσοφόρος

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: Χ͡ρυσοφόρος
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    Α<g type="chi-rho"/>Ω

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: Αchi-rhoΩ
                                                                                                                                                                                                                                                                                                                                                    (IRT: 863)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-symbolchirho.html b/gl/dev/trans-symbolchirho.html index 743a91ddb..0ff9f6718 100644 --- a/gl/dev/trans-symbolchirho.html +++ b/gl/dev/trans-symbolchirho.html @@ -21,10 +21,10 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Chi-Rho

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    expan (expansion) contains the fully expanded form of an abbreviated word.

                                                                                                                                                                                                                                                                                                                                                    abbr (abbreviation) contains an abbreviation of any sort.

                                                                                                                                                                                                                                                                                                                                                    am (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation

                                                                                                                                                                                                                                                                                                                                                    g (character or glyph) represents a non-standard character or glyph; type indicates the name of the decorative symbol, e.g. leaf..

                                                                                                                                                                                                                                                                                                                                                    ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation.

                                                                                                                                                                                                                                                                                                                                                    hi (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made.

                                                                                                                                                                                                                                                                                                                                                    Where a Chi-Rho symbol appears, it may have a range of different semantic values (abbreviation or logogram for "Christ" or "Christian"; a general nonverbal indication of faith or affiliation; ligature of Χ and Ρ outside of any Christian context), or the editor may prefer not to give any interpretation of the import of the symbol. The examples below show a few of the ways in which this variety might be handled.

                                                                                                                                                                                                                                                                                                                                                    A Unicode value (for example U+2627) may be used inside the g if desired.

                                                                                                                                                                                                                                                                                                                                                    Sosin 2011:

                                                                                                                                                                                                                                                                                                                                                    <g ref="#chi-rho"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: (())
                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ((chi-rho))
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    <g ref="#chi-rho"></g>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: (())
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                                                                       <g ref="#chi-rho"/>
                                                                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>Χρίστος</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: (Χρίστος)
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                                                                       <g ref="#chi-rho"/>
                                                                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>Christ</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>opher

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: (Christ) opher
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="ligature">Χρ</hi>υσοφόρος

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: Χ͡ρυσοφόρος
                                                                                                                                                                                                                                                                                                                                                    (Sosin)
                                                                                                                                                                                                                                                                                                                                                    Α<g type="chi-rho"/>Ω

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: Αchi-rhoΩ
                                                                                                                                                                                                                                                                                                                                                    (IRT: 863)

                                                                                                                                                                                                                                                                                                                                                    Instead of using type in g, as the project providing this example did when this was the suggested way of encoding, the recommended use of <g[@ref]> in Symbol (Non Meaning-Bearing) should be preferred now.

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-symbolinterpunct-pt-br.html b/gl/dev/trans-symbolinterpunct-pt-br.html index 456dbcea0..95a60918e 100644 --- a/gl/dev/trans-symbolinterpunct-pt-br.html +++ b/gl/dev/trans-symbolinterpunct-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Símbolo: ponto mediano

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific - customization: g

                                                                                                                                                                                                                                                                                                                                                    g (caracter ou glifo) representa um carcter ou glifo não alfabético ou fora do padrão.

                                                                                                                                                                                                                                                                                                                                                    (discuss typology of interpuncts?)

                                                                                                                                                                                                                                                                                                                                                    M <g type="stop"/> Fydel et F <g type="stop"/> Thesylgum
                                                                                                                                                                                                                                                                                                                                                    (IRT: 900)
                                                                                                                                                                                                                                                                                                                                                    Flauii Diodo <g type="interpunct"/>
                                                                                                                                                                                                                                                                                                                                                    (IRT: 116)
                                                                                                                                                                                                                                                                                                                                                    posita super sacta <g type="dipunct"/>
                                                                                                                                                                                                                                                                                                                                                    evvangelia <g type="dipunct"/> actionariis sce

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Símbolo: ponto mediano

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific + customization: g

                                                                                                                                                                                                                                                                                                                                                    g (caracter ou glifo) representa um carcter ou glifo não alfabético ou fora do padrão.

                                                                                                                                                                                                                                                                                                                                                    (discuss typology of interpuncts?)

                                                                                                                                                                                                                                                                                                                                                    M <g type="stop"/> Fydel et F <g type="stop"/> Thesylgum
                                                                                                                                                                                                                                                                                                                                                    (IRT: 900)
                                                                                                                                                                                                                                                                                                                                                    Flauii Diodo <g type="interpunct"/>
                                                                                                                                                                                                                                                                                                                                                    (IRT: 116)
                                                                                                                                                                                                                                                                                                                                                    posita super sacta <g type="dipunct"/>
                                                                                                                                                                                                                                                                                                                                                    evvangelia <g type="dipunct"/> actionariis sce

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-symbolinterpunct.html b/gl/dev/trans-symbolinterpunct.html index ea1f51f3f..c7f077b33 100644 --- a/gl/dev/trans-symbolinterpunct.html +++ b/gl/dev/trans-symbolinterpunct.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Symbol: interpuncts

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific - customization: g

                                                                                                                                                                                                                                                                                                                                                    g (character or glyph) represents a non-standard or non-alphabetic character or glyph.

                                                                                                                                                                                                                                                                                                                                                    Instead of using type in g, as the project providing this example did when this was the suggested way of encoding, the recommended use of <g[@ref]> in Symbol (Non Meaning-Bearing) should be preferred now.

                                                                                                                                                                                                                                                                                                                                                    M <g type="stop"/> Fydel et F <g type="stop"/> Thesylgum
                                                                                                                                                                                                                                                                                                                                                    (IRT: 900)
                                                                                                                                                                                                                                                                                                                                                    Flauii Diodo <g type="interpunct"/>
                                                                                                                                                                                                                                                                                                                                                    (IRT: 116)
                                                                                                                                                                                                                                                                                                                                                    posita super sacta <g type="dipunct"/> evvangelia <g type="dipunct"/> actionariis sce

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Symbol: interpuncts

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: g ; EpiDoc-specific + customization: g

                                                                                                                                                                                                                                                                                                                                                    g (character or glyph) represents a non-standard or non-alphabetic character or glyph.

                                                                                                                                                                                                                                                                                                                                                    Instead of using type in g, as the project providing this example did when this was the suggested way of encoding, the recommended use of <g[@ref]> in Symbol (Non Meaning-Bearing) should be preferred now.

                                                                                                                                                                                                                                                                                                                                                    M <g type="stop"/> Fydel et F <g type="stop"/> Thesylgum
                                                                                                                                                                                                                                                                                                                                                    (IRT: 900)
                                                                                                                                                                                                                                                                                                                                                    Flauii Diodo <g type="interpunct"/>
                                                                                                                                                                                                                                                                                                                                                    (IRT: 116)
                                                                                                                                                                                                                                                                                                                                                    posita super sacta <g type="dipunct"/> evvangelia <g type="dipunct"/> actionariis sce

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-symbolmonogr-pt-br.html b/gl/dev/trans-symbolmonogr-pt-br.html index f472cf6c4..975081264 100644 --- a/gl/dev/trans-symbolmonogr-pt-br.html +++ b/gl/dev/trans-symbolmonogr-pt-br.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Monogramas

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    expan (expansão) contém a expansão de uma abreviação.

                                                                                                                                                                                                                                                                                                                                                    abbr (abreviação) contém uma abreviação de qualquer tipo.

                                                                                                                                                                                                                                                                                                                                                    am (abbreviation marker - marcador de abreviação) contém uma sequência de letras ou sinais presentes em uma abreviação que são omitidos ou substituídos na versão expandida da abreviação

                                                                                                                                                                                                                                                                                                                                                    g (caracter ou glifo) representa um caracter ou glifo fora do padrão.

                                                                                                                                                                                                                                                                                                                                                    ex (expansão editorial) contém uma sequência de letras acrescentadas pelo editor ou transcritor quando expande uma abreviação.

                                                                                                                                                                                                                                                                                                                                                    figure agrupa elementos que representam ou contém informação gráfica, como uma ilustração ou uma figura.

                                                                                                                                                                                                                                                                                                                                                    figDesc (descrição da figura) contém uma breve descrição em prosa da aparência ou conteúdo de uma imagem gráfica , para uso quando se está documentando uma imagem, sem precisar mostrá-la.

                                                                                                                                                                                                                                                                                                                                                    Nos casos em que o monograma aparece como parte de um texto transcrito de uma inscrição, existe uma série de maneiras diferentes de lidar com isso através de codificação, dependendo da intenção de pesquisa e na nossa habilidade de ler e expandir qualquer conteúdo textual.

                                                                                                                                                                                                                                                                                                                                                    according to iAph: (νικᾷ ἡ τύχη τῶν Πρασίνων.)

                                                                                                                                                                                                                                                                                                                                                    <g type="monogram"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: monogram
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.404)
                                                                                                                                                                                                                                                                                                                                                    <figure>
                                                                                                                                                                                                                                                                                                                                                     <figDesc>monogram</figDesc>
                                                                                                                                                                                                                                                                                                                                                    </figure>
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                                                                       <g type="monogram"/>
                                                                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>Συμβατικίου</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: (Συμβατικίου)
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 7.16)
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                                                                       <abbr>
                                                                                                                                                                                                                                                                                                                                                        <am>
                                                                                                                                                                                                                                                                                                                                                         <g type="monogram"/>
                                                                                                                                                                                                                                                                                                                                                        </am>
                                                                                                                                                                                                                                                                                                                                                       </abbr>
                                                                                                                                                                                                                                                                                                                                                       <ex>Ποστύμ</ex>
                                                                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>ιος</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: (Ποστύμ) (ιος)
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 12.541)
                                                                                                                                                                                                                                                                                                                                                    <figure>
                                                                                                                                                                                                                                                                                                                                                     <head>monogram</head>
                                                                                                                                                                                                                                                                                                                                                    </figure>
                                                                                                                                                                                                                                                                                                                                                    <!-- This uses <head> rather than <figDesc> - is it ok? -->

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: monogram
                                                                                                                                                                                                                                                                                                                                                    (IRT: 863)
                                                                                                                                                                                                                                                                                                                                                    δι εμυ απα ολ επιφανιυ <g type="monogram"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: δι εμυ απα ολ επιφανιυ monogr.
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.col.8.244)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-symbolmonogr.html b/gl/dev/trans-symbolmonogr.html index 1f534da92..a7af56e58 100644 --- a/gl/dev/trans-symbolmonogr.html +++ b/gl/dev/trans-symbolmonogr.html @@ -21,11 +21,11 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Monograms

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    expan (expansion) contains the expansion of an abbreviation.

                                                                                                                                                                                                                                                                                                                                                    abbr (abbreviation) contains an abbreviation of any sort.

                                                                                                                                                                                                                                                                                                                                                    am (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation

                                                                                                                                                                                                                                                                                                                                                    g (character or glyph) represents a non-standard character or glyph.

                                                                                                                                                                                                                                                                                                                                                    ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation.

                                                                                                                                                                                                                                                                                                                                                    figure groups elements representing or containing graphic information such as an illustration or figure.

                                                                                                                                                                                                                                                                                                                                                    figDesc (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it.

                                                                                                                                                                                                                                                                                                                                                    Where a monogram appears as part of the transcribed text of an inscription, there are a range of different ways to handle this in encoding, depending on the scholarly intent, and our ability to read and expand any textual content.

                                                                                                                                                                                                                                                                                                                                                    according to iAph: (νικᾷ ἡ τύχη τῶν Πρασίνων.)

                                                                                                                                                                                                                                                                                                                                                    <g type="monogram"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: monogram
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.404)
                                                                                                                                                                                                                                                                                                                                                    <figure>
                                                                                                                                                                                                                                                                                                                                                     <figDesc>monogram</figDesc>
                                                                                                                                                                                                                                                                                                                                                    </figure>
                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <am>
                                                                                                                                                                                                                                                                                                                                                       <g type="monogram"/>
                                                                                                                                                                                                                                                                                                                                                      </am>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>Συμβατικίου</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: (Συμβατικίου)
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 7.16)

                                                                                                                                                                                                                                                                                                                                                    Instead of using type in g, as the project providing this example did when this was the suggested way of encoding, the recommended use of <g[@ref]> in Symbol (Non Meaning-Bearing) should be preferred now.

                                                                                                                                                                                                                                                                                                                                                    <expan>
                                                                                                                                                                                                                                                                                                                                                     <abbr>
                                                                                                                                                                                                                                                                                                                                                      <expan>
                                                                                                                                                                                                                                                                                                                                                       <abbr>
                                                                                                                                                                                                                                                                                                                                                        <am>
                                                                                                                                                                                                                                                                                                                                                         <g type="monogram"/>
                                                                                                                                                                                                                                                                                                                                                        </am>
                                                                                                                                                                                                                                                                                                                                                       </abbr>
                                                                                                                                                                                                                                                                                                                                                       <ex>Ποστύμ</ex>
                                                                                                                                                                                                                                                                                                                                                      </expan>
                                                                                                                                                                                                                                                                                                                                                     </abbr>
                                                                                                                                                                                                                                                                                                                                                     <ex>ιος</ex>
                                                                                                                                                                                                                                                                                                                                                    </expan>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: (Ποστύμ) (ιος)
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 12.541)
                                                                                                                                                                                                                                                                                                                                                    <figure>
                                                                                                                                                                                                                                                                                                                                                     <head>monogram</head>
                                                                                                                                                                                                                                                                                                                                                    </figure>
                                                                                                                                                                                                                                                                                                                                                    <!-- This uses <head> rather than <figDesc> - is it ok? -->

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: monogram
                                                                                                                                                                                                                                                                                                                                                    (IRT: 863)
                                                                                                                                                                                                                                                                                                                                                    δι εμυ απα ολ επιφανιυ <g type="monogram"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: δι εμυ απα ολ επιφανιυ monogr.
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.col.8.244)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-tallorsmall-pt-br.html b/gl/dev/trans-tallorsmall-pt-br.html index 0f5fc658d..af9098d91 100644 --- a/gl/dev/trans-tallorsmall-pt-br.html +++ b/gl/dev/trans-tallorsmall-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Caracteres Altos ou Pequenos

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                                                    Marcar um caracter como "tall" (alto) ou "small" (pequeno) é puramente descritivo. Observações editoriais a respetio do significado da altura do caracter deve receber marcação separada.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                                                    d<hi rend="tall">i</hi>s
                                                                                                                                                                                                                                                                                                                                                    manibus
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    a<hi rend="small">b</hi>c
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall"></hi>ψικλέους

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ψικλέους
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 12.712)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall">σφυρ<unclear>ε</unclear>ζμαρα</hi>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: σφυρε̣ζμαρα
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: o.claud.4.799)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Caracteres Altos ou Pequenos

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                                                    Marcar um caracter como "tall" (alto) ou "small" (pequeno) é puramente descritivo. Observações editoriais a respetio do significado da altura do caracter deve receber marcação separada.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                                                    d<hi rend="tall">i</hi>s
                                                                                                                                                                                                                                                                                                                                                    manibus
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    a<hi rend="small">b</hi>c
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall"></hi>ψικλέους

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ψικλέους
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 12.712)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall">σφυρ<unclear>ε</unclear>ζμαρα</hi>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: σφυρε̣ζμαρα
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: o.claud.4.799)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    2. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-tallorsmall.html b/gl/dev/trans-tallorsmall.html index 717e75cf5..a5576b562 100644 --- a/gl/dev/trans-tallorsmall.html +++ b/gl/dev/trans-tallorsmall.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Tall or Small Characters

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific - customization: hi

                                                                                                                                                                                                                                                                                                                                                    Marking a character as "tall" or "small" is purely descriptive. Editorial observations concerning the significance of the character height should be marked up separately.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                                                    d<hi rend="tall">i</hi>s manibus
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    a<hi rend="small">b</hi>c
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall"></hi>ψικλέους

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ψικλέους
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 12.712)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall">σφυρ<unclear>ε</unclear>ζμαρα</hi>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: σφυρε̣ζμαρα
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: o.claud.4.799)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Tall or Small Characters

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: hi ; EpiDoc-specific + customization: hi

                                                                                                                                                                                                                                                                                                                                                    Marking a character as "tall" or "small" is purely descriptive. Editorial observations concerning the significance of the character height should be marked up separately.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 ...; Sosin 2011:

                                                                                                                                                                                                                                                                                                                                                    d<hi rend="tall">i</hi>s manibus
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    a<hi rend="small">b</hi>c
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall"></hi>ψικλέους

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ψικλέους
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 12.712)
                                                                                                                                                                                                                                                                                                                                                    <hi rend="tall">σφυρ<unclear>ε</unclear>ζμαρα</hi>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: σφυρε̣ζμαρα
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: o.claud.4.799)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-textnotcompleted-pt-br.html b/gl/dev/trans-textnotcompleted-pt-br.html index 9860de08d..3d2ea9297 100644 --- a/gl/dev/trans-textnotcompleted-pt-br.html +++ b/gl/dev/trans-textnotcompleted-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Texto incompleto (omissão não restaurada)

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Letras omitidas (e não restauradas) porque o entalhador não levou o texto até o final.

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                                                    Nos casos em que o texto foi omitido e não restaurado, um elemento gap deve ser usado, com um atributo reason com o valor "omitted".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 X.5; Sosin 2011: (---)

                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: <·· ? ··>
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 9.25)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: <⁦ -ca.?- ⁩>
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.oxy.70.4776)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Texto incompleto (omissão não restaurada)

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Letras omitidas (e não restauradas) porque o entalhador não levou o texto até o final.

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                                                    Nos casos em que o texto foi omitido e não restaurado, um elemento gap deve ser usado, com um atributo reason com o valor "omitted".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 X.5; Sosin 2011: (---)

                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: <·· ? ··>
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 9.25)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: <⁦ -ca.?- ⁩>
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.oxy.70.4776)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-textnotcompleted.html b/gl/dev/trans-textnotcompleted.html index e9cd600e0..c321ed6b9 100644 --- a/gl/dev/trans-textnotcompleted.html +++ b/gl/dev/trans-textnotcompleted.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Text not completed (omission not restored)

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Letters omitted (but not restored) because the stonecutter did not carry out the text to the end.

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: gap ; EpiDoc-specific - customization: gap

                                                                                                                                                                                                                                                                                                                                                    Where text has been omitted and is not restored, a gap should be used, with a reason with a value of "omitted".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 X.5; Sosin 2011: (---)

                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: <·· ? ··>
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 9.25)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: <⁦ -ca.?- ⁩>
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.oxy.70.4776)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Text not completed (omission not restored)

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Letters omitted (but not restored) because the stonecutter did not carry out the text to the end.

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: gap ; EpiDoc-specific + customization: gap

                                                                                                                                                                                                                                                                                                                                                    Where text has been omitted and is not restored, a gap should be used, with a reason with a value of "omitted".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 X.5; Sosin 2011: (---)

                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: <·· ? ··>
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 9.25)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="omittedextent="unknown"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: <⁦ -ca.?- ⁩>
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.oxy.70.4776)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-textpart-pt-br.html b/gl/dev/trans-textpart-pt-br.html index 0918ba224..30f0e4ccf 100644 --- a/gl/dev/trans-textpart-pt-br.html +++ b/gl/dev/trans-textpart-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Textpart

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Divisões do texto editado, como fragmentos, colunas, capítulos ou versões em diferentes línguas.

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: div ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                                      Textpart

                                                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                                                      Divisões do texto editado, como fragmentos, colunas, capítulos ou versões em diferentes línguas.

                                                                                                                                                                                                                                                                                                                                                      • TEI definition: div ; EpiDoc-specific customization: div
                                                                                                                                                                                                                                                                                                                                                      • TEI definition: milestone ; EpiDoc-specific - customization: milestone

                                                                                                                                                                                                                                                                                                                                                      Unidades de texto que são separadas e geralmente numeradas de forma independente por epígrafos e papirólogos — inclusive fragmentos, colunas, seções, capítulos, textos independentes em uma única pedra, marcos, selos, ou grafiti agrupado — que devem serdivididos e numerados na mesma base no EpiDoc. O uso de XML não deve mudar a necessidade de dividir e numerar o texto de uma maneira que façasentido intuitivo e semântico para o editor.

                                                                                                                                                                                                                                                                                                                                                      Cada divisão contendo uma parte separada do texto deve estar dentro de um elemento ab separado, e dentro de um div com um atributo type="textpart". É muitas vezes útil (apesar de não obrigatório) fornecer também um atributo subtype dando um nome para o tipo de subdivisão de texto gravado aqui; subtype não é restrito, mas alguns dos valores comuns podem incluir "fragment", "column", "section", etc.

                                                                                                                                                                                                                                                                                                                                                      Estas unidades podem, é claro, se encaixar em quase qualquer combinação. Se existirem sobreposições não hierárquicas entre as unidades (como seções e colunas), então uma unidade deve ser escolhida como a divisão "top level", e as outras repartidas dentro da divisão maior. Estas divisões menores, repartidas, podem ser interligadas com o uso de um atributo n ou do elemento link.

                                                                                                                                                                                                                                                                                                                                                      Nos casos em que uma unidade dentro de um texto contínuo deve receber marcação (por exemplo, múltiplos blocos de um texto longo) o elemento milestone deve ser utilizado, paramarcar o ponto em que ocorre uma quebra no suporte.

                                                                                                                                                                                                                                                                                                                                                      Nos casos em que dois textos distintos aparecem no mesmo suporte (como, por exemplo, duas inscrições distintas numa mesma pedra), eles podem ser codificados em um único arquivo EpiDoc file ou em dois arquivos separados. Esta é uma decisão editorial, e o EpiDoc nãodita a escolah de um método sobre outro. Se a codificação dos dois textos for em um único arquivo, dois div separados com o type "textpart" deve ser utilizado dentro da divisão de edição. Cada tradução, comentário, bibliografia, etc. deve também ser divididas em dois textparts, de modo a registrarinformação separadamente para cada texto. Se a codificação for feita em dois arquivos separados, pode ser criado um link (ou ao menos ele pode ser mencionado) no comentário, direcionando o leitor ao outro texto que aparece no mesmo suporte.

                                                                                                                                                                                                                                                                                                                                                      according to london: Section A

                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="sectionn="A"/>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                       n="a">

                                                                                                                                                                                                                                                                                                                                                       <ab/>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                       n="b">

                                                                                                                                                                                                                                                                                                                                                       <ab/>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                       n="c">

                                                                                                                                                                                                                                                                                                                                                       <ab/>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="sectionn="i">
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="a">

                                                                                                                                                                                                                                                                                                                                                        <ab/>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="b">

                                                                                                                                                                                                                                                                                                                                                        <ab/>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="section"
                                                                                                                                                                                                                                                                                                                                                       n="ii">

                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="c">

                                                                                                                                                                                                                                                                                                                                                        <ab/>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="d">

                                                                                                                                                                                                                                                                                                                                                        <ab/>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                                                      Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                      4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                      \ No newline at end of file + customization: milestone

                                                                                                                                                                                                                                                                                                                                                    Unidades de texto que são separadas e geralmente numeradas de forma independente por epígrafos e papirólogos — inclusive fragmentos, colunas, seções, capítulos, textos independentes em uma única pedra, marcos, selos, ou grafiti agrupado — que devem serdivididos e numerados na mesma base no EpiDoc. O uso de XML não deve mudar a necessidade de dividir e numerar o texto de uma maneira que façasentido intuitivo e semântico para o editor.

                                                                                                                                                                                                                                                                                                                                                    Cada divisão contendo uma parte separada do texto deve estar dentro de um elemento ab separado, e dentro de um div com um atributo type="textpart". É muitas vezes útil (apesar de não obrigatório) fornecer também um atributo subtype dando um nome para o tipo de subdivisão de texto gravado aqui; subtype não é restrito, mas alguns dos valores comuns podem incluir "fragment", "column", "section", etc.

                                                                                                                                                                                                                                                                                                                                                    Estas unidades podem, é claro, se encaixar em quase qualquer combinação. Se existirem sobreposições não hierárquicas entre as unidades (como seções e colunas), então uma unidade deve ser escolhida como a divisão "top level", e as outras repartidas dentro da divisão maior. Estas divisões menores, repartidas, podem ser interligadas com o uso de um atributo n ou do elemento link.

                                                                                                                                                                                                                                                                                                                                                    Nos casos em que uma unidade dentro de um texto contínuo deve receber marcação (por exemplo, múltiplos blocos de um texto longo) o elemento milestone deve ser utilizado, paramarcar o ponto em que ocorre uma quebra no suporte.

                                                                                                                                                                                                                                                                                                                                                    Nos casos em que dois textos distintos aparecem no mesmo suporte (como, por exemplo, duas inscrições distintas numa mesma pedra), eles podem ser codificados em um único arquivo EpiDoc file ou em dois arquivos separados. Esta é uma decisão editorial, e o EpiDoc nãodita a escolah de um método sobre outro. Se a codificação dos dois textos for em um único arquivo, dois div separados com o type "textpart" deve ser utilizado dentro da divisão de edição. Cada tradução, comentário, bibliografia, etc. deve também ser divididas em dois textparts, de modo a registrarinformação separadamente para cada texto. Se a codificação for feita em dois arquivos separados, pode ser criado um link (ou ao menos ele pode ser mencionado) no comentário, direcionando o leitor ao outro texto que aparece no mesmo suporte.

                                                                                                                                                                                                                                                                                                                                                    according to london: Section A

                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="sectionn="A"/>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                     n="a">

                                                                                                                                                                                                                                                                                                                                                     <ab/>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                     n="b">

                                                                                                                                                                                                                                                                                                                                                     <ab/>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                     n="c">

                                                                                                                                                                                                                                                                                                                                                     <ab/>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="sectionn="i">
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="a">

                                                                                                                                                                                                                                                                                                                                                      <ab/>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="b">

                                                                                                                                                                                                                                                                                                                                                      <ab/>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="section"
                                                                                                                                                                                                                                                                                                                                                     n="ii">

                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="c">

                                                                                                                                                                                                                                                                                                                                                      <ab/>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="d">

                                                                                                                                                                                                                                                                                                                                                      <ab/>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-textpart.html b/gl/dev/trans-textpart.html index 71052a627..902311eb6 100644 --- a/gl/dev/trans-textpart.html +++ b/gl/dev/trans-textpart.html @@ -21,7 +21,7 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Textpart

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Divisions of the edited text such as fragments, columns, chapters or versions in different languages.

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: ab ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                                      Textpart

                                                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                                                      Divisions of the edited text such as fragments, columns, chapters or versions in different languages.

                                                                                                                                                                                                                                                                                                                                                      • TEI definition: ab ; EpiDoc-specific customization: ab
                                                                                                                                                                                                                                                                                                                                                      • TEI definition: div ; EpiDoc-specific customization: div
                                                                                                                                                                                                                                                                                                                                                      • TEI definition: milestone ; EpiDoc-specific - customization: milestone

                                                                                                                                                                                                                                                                                                                                                      Units of the text that are separated and usually numbered independently by epigraphers and papyrologists—including fragments, columns, sections, chapters, independent texts on a single stone, marks, stamps, or graffiti grouped together—should be divided and numbered on the same basis in EpiDoc. The use of XML should not change the need for dividing and numbering the text in a way that makes semantic and intuitive sense to the editor.

                                                                                                                                                                                                                                                                                                                                                      When a physical break in the support coincides with a major semantic break in the text, each text section should be wrapped in a separate ab inside a div with a type="textpart". This can be the case of non-contiguous fragments, inscriptions consisting of physically distinct parts with the same text in more languages, or columns with loosely related content.

                                                                                                                                                                                                                                                                                                                                                      It is highly recommended to provide an n attribute specifying an identifier for each <div type="textpart">. It is often useful (although not obligatory) also to provide a subtype attribute naming the kind of subdivision of text being recorded; subtype is not constrained, but common values might include "fragment", "column", "face", "section", etc.

                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                       n="a">

                                                                                                                                                                                                                                                                                                                                                       <ab>
                                                                                                                                                                                                                                                                                                                                                        <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                       <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                       </ab>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                       n="b">

                                                                                                                                                                                                                                                                                                                                                       <ab>
                                                                                                                                                                                                                                                                                                                                                        <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                       <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                       </ab>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                       n="c">

                                                                                                                                                                                                                                                                                                                                                       <ab>
                                                                                                                                                                                                                                                                                                                                                        <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                       <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                       </ab>
                                                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                                                      In the following example from DHARMA, a set of inscribed copper plates with an inscribed seal attached to the ring that binds the plates together:

                                                                                                                                                                                                                                                                                                                                                      <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartn="A">
                                                                                                                                                                                                                                                                                                                                                        <head xml:lang="en">Seal</head>
                                                                                                                                                                                                                                                                                                                                                        <ab>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>śrī-tribhuvanāṁkuśa
                                                                                                                                                                                                                                                                                                                                                        </ab>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartn="B">
                                                                                                                                                                                                                                                                                                                                                        <head xml:lang="en">Plates</head>
                                                                                                                                                                                                                                                                                                                                                        <ab>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>svasti śrīmatāṁ sakala-bhuvana-saṁstūyamāna-mānavya-sagotrānāṁ
                                                                                                                                                                                                                                                                                                                                                        <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                        </ab>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                                                      These units may, of course, nest in almost any combination. If there are non-hierarchical overlaps between units (e.g. sections and columns) then one unit has to be selected as the "top level" division, and the other broken up between the larger division. These smaller, broken divisions may be connected using the n attribute or a link element.

                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="sectionn="i">
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="a">

                                                                                                                                                                                                                                                                                                                                                        <ab>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                        <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                        </ab>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="b">

                                                                                                                                                                                                                                                                                                                                                        <ab>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                        <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                        </ab>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                      </div>
                                                                                                                                                                                                                                                                                                                                                      <div type="textpartsubtype="section"
                                                                                                                                                                                                                                                                                                                                                       n="ii">

                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="c">

                                                                                                                                                                                                                                                                                                                                                        <ab>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                        <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                        </ab>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                       <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                        n="d">

                                                                                                                                                                                                                                                                                                                                                        <ab>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                        <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                        </ab>
                                                                                                                                                                                                                                                                                                                                                       </div>
                                                                                                                                                                                                                                                                                                                                                      </div>

                                                                                                                                                                                                                                                                                                                                                      Where two distinct texts appear on one support (e.g. two distinct inscriptions on one stone), they can either be encoded in one single EpiDoc file or in two separate files. This is an editorial decision and EpiDoc does not dictate the use of one method over the other. If encoding the two texts in a single file, two separate divs with type of "textpart" should be used within the edition division. Each translation, commentary, bibliography etc. should also be divided into two textparts in order to record information separately about each text. If encoding the texts in two separate files, a link can be provided (or at the least a mention can be made) in the commentary directing the reader to the other text that appears on the same support.

                                                                                                                                                                                                                                                                                                                                                      When a physical break in the support does not coincide with a major semantic break in the text and the physical division of the text does not need to be part of the citation scheme for the text as a whole (for example, multiple blocks in a long relief text, or text split in two consecutive columns), the milestone or cb or pb elements should be used instead to mark the point at which a break in the support occurs.

                                                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                                                      Other pages describing <ab>:

                                                                                                                                                                                                                                                                                                                                                      Other pages describing <div>:

                                                                                                                                                                                                                                                                                                                                                      Other pages describing <milestone>:

                                                                                                                                                                                                                                                                                                                                                      Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                      1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                      2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                      3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                      4. Irene Vagionakis, author

                                                                                                                                                                                                                                                                                                                                                      EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                      Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                      \ No newline at end of file + customization: milestone

                                                                                                                                                                                                                                                                                                                                                    Units of the text that are separated and usually numbered independently by epigraphers and papyrologists—including fragments, columns, sections, chapters, independent texts on a single stone, marks, stamps, or graffiti grouped together—should be divided and numbered on the same basis in EpiDoc. The use of XML should not change the need for dividing and numbering the text in a way that makes semantic and intuitive sense to the editor.

                                                                                                                                                                                                                                                                                                                                                    When a physical break in the support coincides with a major semantic break in the text, each text section should be wrapped in a separate ab inside a div with a type="textpart". This can be the case of non-contiguous fragments, inscriptions consisting of physically distinct parts with the same text in more languages, or columns with loosely related content.

                                                                                                                                                                                                                                                                                                                                                    It is highly recommended to provide an n attribute specifying an identifier for each <div type="textpart">. It is often useful (although not obligatory) also to provide a subtype attribute naming the kind of subdivision of text being recorded; subtype is not constrained, but common values might include "fragment", "column", "face", "section", etc.

                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                     n="a">

                                                                                                                                                                                                                                                                                                                                                     <ab>
                                                                                                                                                                                                                                                                                                                                                      <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                     <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                     </ab>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                     n="b">

                                                                                                                                                                                                                                                                                                                                                     <ab>
                                                                                                                                                                                                                                                                                                                                                      <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                     <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                     </ab>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                     n="c">

                                                                                                                                                                                                                                                                                                                                                     <ab>
                                                                                                                                                                                                                                                                                                                                                      <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                     <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                     </ab>
                                                                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                                                                    In the following example from DHARMA, a set of inscribed copper plates with an inscribed seal attached to the ring that binds the plates together:

                                                                                                                                                                                                                                                                                                                                                    <div type="editionxml:lang="san-Latn">
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartn="A">
                                                                                                                                                                                                                                                                                                                                                      <head xml:lang="en">Seal</head>
                                                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>śrī-tribhuvanāṁkuśa
                                                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartn="B">
                                                                                                                                                                                                                                                                                                                                                      <head xml:lang="en">Plates</head>
                                                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>svasti śrīmatāṁ sakala-bhuvana-saṁstūyamāna-mānavya-sagotrānāṁ
                                                                                                                                                                                                                                                                                                                                                      <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                                                                    These units may, of course, nest in almost any combination. If there are non-hierarchical overlaps between units (e.g. sections and columns) then one unit has to be selected as the "top level" division, and the other broken up between the larger division. These smaller, broken divisions may be connected using the n attribute or a link element.

                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="sectionn="i">
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="a">

                                                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                      <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="b">

                                                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                      <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                    </div>
                                                                                                                                                                                                                                                                                                                                                    <div type="textpartsubtype="section"
                                                                                                                                                                                                                                                                                                                                                     n="ii">

                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="c">

                                                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                      <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                     <div type="textpartsubtype="fragment"
                                                                                                                                                                                                                                                                                                                                                      n="d">

                                                                                                                                                                                                                                                                                                                                                      <ab>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>...
                                                                                                                                                                                                                                                                                                                                                      <lb n="2"/>...
                                                                                                                                                                                                                                                                                                                                                      </ab>
                                                                                                                                                                                                                                                                                                                                                     </div>
                                                                                                                                                                                                                                                                                                                                                    </div>

                                                                                                                                                                                                                                                                                                                                                    Where two distinct texts appear on one support (e.g. two distinct inscriptions on one stone), they can either be encoded in one single EpiDoc file or in two separate files. This is an editorial decision and EpiDoc does not dictate the use of one method over the other. If encoding the two texts in a single file, two separate divs with type of "textpart" should be used within the edition division. Each translation, commentary, bibliography etc. should also be divided into two textparts in order to record information separately about each text. If encoding the texts in two separate files, a link can be provided (or at the least a mention can be made) in the commentary directing the reader to the other text that appears on the same support.

                                                                                                                                                                                                                                                                                                                                                    When a physical break in the support does not coincide with a major semantic break in the text and the physical division of the text does not need to be part of the citation scheme for the text as a whole (for example, multiple blocks in a long relief text, or text split in two consecutive columns), the milestone or cb or pb elements should be used instead to mark the point at which a break in the support occurs.

                                                                                                                                                                                                                                                                                                                                                    See also:

                                                                                                                                                                                                                                                                                                                                                    Other pages describing <ab>:

                                                                                                                                                                                                                                                                                                                                                    Other pages describing <div>:

                                                                                                                                                                                                                                                                                                                                                    Other pages describing <milestone>:

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    4. Irene Vagionakis, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-uninterpreted-pt-br.html b/gl/dev/trans-uninterpreted-pt-br.html index 3229a5699..69b2dbf92 100644 --- a/gl/dev/trans-uninterpreted-pt-br.html +++ b/gl/dev/trans-uninterpreted-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Caracteres não-interpretados

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Letras claras mas incompreensíveis

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: orig ; EpiDoc-specific - customization: orig

                                                                                                                                                                                                                                                                                                                                                    Caracteres com leitura fácil mas não interpretados pelo editor, convencionalmente escritos em caixa alta numa transcrição Leiden, devem ser codificados com o elemento orig. Os caracteres não precisam ser escritos em caixa alta (na verdade, pode-se até dizer que é melhor se eles não forem), apesar de caracteres como o V latino ou o Σ,grego, que não conseguem ter uma forma sem ambiguidade em caixa baixa, quando não interpretados, ficam mais seguros em caixa alta. As folhas de estilo example EpiDoc P5 atualmente fazem output de letras caixa alta em HTML independente do tipo de letra no XML.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 III.2; SEG: ABC

                                                                                                                                                                                                                                                                                                                                                    <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>V</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>Σ</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>sppo</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • SEG style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • London style: SPPO
                                                                                                                                                                                                                                                                                                                                                    (IRT: 480)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: [·· 1-2··]A[·· 1-2··]A
                                                                                                                                                                                                                                                                                                                                                    (IRT: 6)
                                                                                                                                                                                                                                                                                                                                                    <orig n="unresolved">ε<unclear reason="damage">κ</unclear>
                                                                                                                                                                                                                                                                                                                                                    </orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ΕΚ
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.120)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Caracteres não-interpretados

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Letras claras mas incompreensíveis

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: orig ; EpiDoc-specific + customization: orig

                                                                                                                                                                                                                                                                                                                                                    Caracteres com leitura fácil mas não interpretados pelo editor, convencionalmente escritos em caixa alta numa transcrição Leiden, devem ser codificados com o elemento orig. Os caracteres não precisam ser escritos em caixa alta (na verdade, pode-se até dizer que é melhor se eles não forem), apesar de caracteres como o V latino ou o Σ,grego, que não conseguem ter uma forma sem ambiguidade em caixa baixa, quando não interpretados, ficam mais seguros em caixa alta. As folhas de estilo example EpiDoc P5 atualmente fazem output de letras caixa alta em HTML independente do tipo de letra no XML.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 III.2; SEG: ABC

                                                                                                                                                                                                                                                                                                                                                    <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>V</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>Σ</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>sppo</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • SEG style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • London style: SPPO
                                                                                                                                                                                                                                                                                                                                                    (IRT: 480)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: [·· 1-2··]A[·· 1-2··]A
                                                                                                                                                                                                                                                                                                                                                    (IRT: 6)
                                                                                                                                                                                                                                                                                                                                                    <orig n="unresolved">ε<unclear reason="damage">κ</unclear>
                                                                                                                                                                                                                                                                                                                                                    </orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ΕΚ
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.120)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-uninterpreted.html b/gl/dev/trans-uninterpreted.html index 13f542122..934e2a0a4 100644 --- a/gl/dev/trans-uninterpreted.html +++ b/gl/dev/trans-uninterpreted.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Uninterpreted characters

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Clear but incomprehensible letters

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: orig ; EpiDoc-specific - customization: orig

                                                                                                                                                                                                                                                                                                                                                    Characters clearly read but not interpreted by the editor, conventionally written in uppercase in a Leiden transcription, should be tagged using the orig element. The characters need not be written in uppercase (in fact arguably it may be better if they were not), although characters such as Latin V or Greek Σ, which cannot be assigned an unambiguous lowercase form when uninterpreted, may be safer in uppercase. The example EpiDoc P5 stylesheets currently output uppercase letters in the HTML whether or not the letters are in lower or uppercase in the XML.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 III.2; SEG: ABC

                                                                                                                                                                                                                                                                                                                                                    <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>V</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>Σ</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>sppo</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • SEG style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • London style: SPPO
                                                                                                                                                                                                                                                                                                                                                    (IRT: 480)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: [·· 1-2··]A[·· 1-2··]A
                                                                                                                                                                                                                                                                                                                                                    (IRT: 6)
                                                                                                                                                                                                                                                                                                                                                    <orig n="unresolved">ε<unclear reason="damage">κ</unclear>
                                                                                                                                                                                                                                                                                                                                                    </orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ΕΚ
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.120)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Uninterpreted characters

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Clear but incomprehensible letters

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: orig ; EpiDoc-specific + customization: orig

                                                                                                                                                                                                                                                                                                                                                    Characters clearly read but not interpreted by the editor, conventionally written in uppercase in a Leiden transcription, should be tagged using the orig element. The characters need not be written in uppercase (in fact arguably it may be better if they were not), although characters such as Latin V or Greek Σ, which cannot be assigned an unambiguous lowercase form when uninterpreted, may be safer in uppercase. The example EpiDoc P5 stylesheets currently output uppercase letters in the HTML whether or not the letters are in lower or uppercase in the XML.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 III.2; SEG: ABC

                                                                                                                                                                                                                                                                                                                                                    <orig>abc</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>V</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>Σ</orig>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <orig>sppo</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • SEG style: SPPO
                                                                                                                                                                                                                                                                                                                                                    • London style: SPPO
                                                                                                                                                                                                                                                                                                                                                    (IRT: 480)
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>
                                                                                                                                                                                                                                                                                                                                                    <gap reason="lostatLeast="1atMost="2"
                                                                                                                                                                                                                                                                                                                                                     unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    <orig>a</orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: [·· 1-2··]A[·· 1-2··]A
                                                                                                                                                                                                                                                                                                                                                    (IRT: 6)
                                                                                                                                                                                                                                                                                                                                                    <orig n="unresolved">ε<unclear reason="damage">κ</unclear>
                                                                                                                                                                                                                                                                                                                                                    </orig>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: ΕΚ
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.120)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Beatrice Lietz, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-vacatchar-pt-br.html b/gl/dev/trans-vacatchar-pt-br.html index 6822c5020..3a46de4a2 100644 --- a/gl/dev/trans-vacatchar-pt-br.html +++ b/gl/dev/trans-vacatchar-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Vacat Medido em Caracteres

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Espaço deixado na pedra

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific - customization: space

                                                                                                                                                                                                                                                                                                                                                    Um elemento space deve ser utilizado cada vez que houver um espaço intencional deixado no suporte, isto é, um espaço q2ue nunca conteve texto (vacat). Se o espaço for medido em caracteres, o atributo unit deve ter o valor "character".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="3unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: v
                                                                                                                                                                                                                                                                                                                                                    (IRT: 993)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="16unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: ⁦ vac. 16⁩
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.narm.2006.4)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Vacat Medido em Caracteres

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Espaço deixado na pedra

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific + customization: space

                                                                                                                                                                                                                                                                                                                                                    Um elemento space deve ser utilizado cada vez que houver um espaço intencional deixado no suporte, isto é, um espaço q2ue nunca conteve texto (vacat). Se o espaço for medido em caracteres, o atributo unit deve ter o valor "character".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="3unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: v
                                                                                                                                                                                                                                                                                                                                                    (IRT: 993)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="16unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: ⁦ vac. 16⁩
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.narm.2006.4)

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-vacatchar.html b/gl/dev/trans-vacatchar.html index 82500f9fb..17db192cf 100644 --- a/gl/dev/trans-vacatchar.html +++ b/gl/dev/trans-vacatchar.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Vacat Measured in Characters

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Space left on stone

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific - customization: space

                                                                                                                                                                                                                                                                                                                                                    A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). If the space is measured in characters, the unit should have a value of "character".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="3unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: v
                                                                                                                                                                                                                                                                                                                                                    (IRT: 993)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="16unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: ⁦ vac. 16⁩
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.narm.2006.4)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Vacat Measured in Characters

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Space left on stone

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific + customization: space

                                                                                                                                                                                                                                                                                                                                                    A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). If the space is measured in characters, the unit should have a value of "character".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="3unit="character"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="1unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style: v
                                                                                                                                                                                                                                                                                                                                                    (IRT: 993)
                                                                                                                                                                                                                                                                                                                                                    <space quantity="16unit="character"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Duke Databank style: ⁦ vac. 16⁩
                                                                                                                                                                                                                                                                                                                                                    (DDbDP: p.narm.2006.4)

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-vacatline-pt-br.html b/gl/dev/trans-vacatline-pt-br.html index 2a203f7e0..b492c1a0f 100644 --- a/gl/dev/trans-vacatline-pt-br.html +++ b/gl/dev/trans-vacatline-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Vacat Medido em Linhas

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Espaço deixado na pedra

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific - customization: space

                                                                                                                                                                                                                                                                                                                                                    Um elemento space deve ser usado cada vez que houver um espaço intencionalmente deixado no suporte: um espaço que nunca conteve texto (vacat). Se o espaço for medido em linhas, unit deve ter o valor "line".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space extent="3unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space dim="horizontalextent="1"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style:      vacat
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.24)

                                                                                                                                                                                                                                                                                                                                                    O atributo dim não é mais recomendado, já que a unidade já passa esta informação.

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    3. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Vacat Medido em Linhas

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Espaço deixado na pedra

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific + customization: space

                                                                                                                                                                                                                                                                                                                                                    Um elemento space deve ser usado cada vez que houver um espaço intencionalmente deixado no suporte: um espaço que nunca conteve texto (vacat). Se o espaço for medido em linhas, unit deve ter o valor "line".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space extent="3unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space dim="horizontalextent="1"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style:      vacat
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.24)

                                                                                                                                                                                                                                                                                                                                                    O atributo dim não é mais recomendado, já que a unidade já passa esta informação.

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    3. Pietro Liuzzo, autor
                                                                                                                                                                                                                                                                                                                                                    4. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-vacatline.html b/gl/dev/trans-vacatline.html index e3df4dfd1..544219ce9 100644 --- a/gl/dev/trans-vacatline.html +++ b/gl/dev/trans-vacatline.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Vacat Measured in Lines

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Space left on stone

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific - customization: space

                                                                                                                                                                                                                                                                                                                                                    A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). If the space is measured in lines, the unit should have a value of "line".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space extent="3unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space dim="horizontalextent="1"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style:      vacat
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.24)

                                                                                                                                                                                                                                                                                                                                                    The attribute dim is not recomended any more as the unit already gives this information.

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    3. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Vacat Measured in Lines

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Space left on stone

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific + customization: space

                                                                                                                                                                                                                                                                                                                                                    A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). If the space is measured in lines, the unit should have a value of "line".

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.3)

                                                                                                                                                                                                                                                                                                                                                    <space extent="3unit="line"/>
                                                                                                                                                                                                                                                                                                                                                    (Panciera)
                                                                                                                                                                                                                                                                                                                                                    <space dim="horizontalextent="1"
                                                                                                                                                                                                                                                                                                                                                     unit="line"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • London style:      vacat
                                                                                                                                                                                                                                                                                                                                                    (InsAph: 1.24)

                                                                                                                                                                                                                                                                                                                                                    The attribute dim is not recomended any more as the unit already gives this information.

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    3. Pietro Liuzzo, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-vacatotherunits-pt-br.html b/gl/dev/trans-vacatotherunits-pt-br.html index 3a0ad09d2..1c5c30d10 100644 --- a/gl/dev/trans-vacatotherunits-pt-br.html +++ b/gl/dev/trans-vacatotherunits-pt-br.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Vacat Medido em Outras Unidades

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Espaço deixado na pedra, Space left on stone, descrito em unidades difierentes de caracteres ou linhas (como páginas, cm)

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific - customization: space

                                                                                                                                                                                                                                                                                                                                                    Um elemento space deve ser usado sempre que houver espaço intencionalmente deixado no suporte, um espaço que nunca conteve texto (vacat). Um atributo unit deve registrar a unidade de medida, na forma que o editor necessitar (os valores mais comuns incluem "metre", "cm"), e o atributo quantity deve registrar o número destas unidades de medida. Um atributo type também pode ser utilizado para indicar o motivo do espaço vazio; valofres possíveis incluem buraco, dano, decoração, entalhe, etc.).

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.4.2cm)

                                                                                                                                                                                                                                                                                                                                                    <space extent="4.2unit="cm"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ( vac. )

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    4. Scott DiGiulio, autor
                                                                                                                                                                                                                                                                                                                                                    5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Vacat Medido em Outras Unidades

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Espaço deixado na pedra, Space left on stone, descrito em unidades difierentes de caracteres ou linhas (como páginas, cm)

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific + customization: space

                                                                                                                                                                                                                                                                                                                                                    Um elemento space deve ser usado sempre que houver espaço intencionalmente deixado no suporte, um espaço que nunca conteve texto (vacat). Um atributo unit deve registrar a unidade de medida, na forma que o editor necessitar (os valores mais comuns incluem "metre", "cm"), e o atributo quantity deve registrar o número destas unidades de medida. Um atributo type também pode ser utilizado para indicar o motivo do espaço vazio; valofres possíveis incluem buraco, dano, decoração, entalhe, etc.).

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.4.2cm)

                                                                                                                                                                                                                                                                                                                                                    <space extent="4.2unit="cm"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ( vac. )

                                                                                                                                                                                                                                                                                                                                                    Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, autor
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                    4. Scott DiGiulio, autor
                                                                                                                                                                                                                                                                                                                                                    5. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-vacatotherunits.html b/gl/dev/trans-vacatotherunits.html index 49d9ea34a..dc0df8537 100644 --- a/gl/dev/trans-vacatotherunits.html +++ b/gl/dev/trans-vacatotherunits.html @@ -21,5 +21,5 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Vacat Measured in Other Units

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    Space left on stone, expressed in units other than characters or lines (e.g. pages, cm)

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific - customization: space

                                                                                                                                                                                                                                                                                                                                                    A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). A unit attribute should record the units of measurement in whatever form the editor requires (common values include "metre", "cm"), and a quantity attribute should record the number of such units measured.

                                                                                                                                                                                                                                                                                                                                                    A type attribute may be used in order to indicate the reason for the empty space; possible values may include hole, damage, decoration, indent, etc. For instance, if a hole existed in the support prior to the addition of the text, this would best be represented with the value "hole;" however, this value would be less applicable if the hole was made after the the addition of text. Similarly, if intentional space was left to avoid existing damage on the support, a type attribute with value "damage" should be used, but not if the support was damaged after text was added; in the latter instance, if text was affected, gap should be used instead.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.4.2cm)

                                                                                                                                                                                                                                                                                                                                                    <space extent="4.2unit="cm"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ( vac. )

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    4. Scott DiGiulio, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file +

                                                                                                                                                                                                                                                                                                                                                    Vacat Measured in Other Units

                                                                                                                                                                                                                                                                                                                                                    2024-03-05

                                                                                                                                                                                                                                                                                                                                                    Space left on stone, expressed in units other than characters or lines (e.g. pages, cm)

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: space ; EpiDoc-specific + customization: space

                                                                                                                                                                                                                                                                                                                                                    A space should be used wherever there is an intentional space left on the support: i.e. a space that never contained text (vacat). A unit attribute should record the units of measurement in whatever form the editor requires (common values include "metre", "cm"), and a quantity attribute should record the number of such units measured.

                                                                                                                                                                                                                                                                                                                                                    A type attribute may be used in order to indicate the reason for the empty space; possible values may include hole, damage, decoration, indent, etc. For instance, if a hole existed in the support prior to the addition of the text, this would best be represented with the value "hole;" however, this value would be less applicable if the hole was made after the the addition of text. Similarly, if intentional space was left to avoid existing damage on the support, a type attribute with value "damage" should be used, but not if the support was damaged after text was added; in the latter instance, if text was affected, gap should be used instead.

                                                                                                                                                                                                                                                                                                                                                    Panciera 1991 XI.2; Sosin 2011: (vac.4.2cm)

                                                                                                                                                                                                                                                                                                                                                    <space extent="4.2unit="cm"/>

                                                                                                                                                                                                                                                                                                                                                    Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                    • Default (Panciera) style: ( vac. )

                                                                                                                                                                                                                                                                                                                                                    Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                    1. Scott Vanderbilt, author
                                                                                                                                                                                                                                                                                                                                                    2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                    3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                    4. Scott DiGiulio, author

                                                                                                                                                                                                                                                                                                                                                    EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                    Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                    \ No newline at end of file diff --git a/gl/dev/trans-verseline-pt-br.html b/gl/dev/trans-verseline-pt-br.html index 1018ed9bf..43863e6db 100644 --- a/gl/dev/trans-verseline-pt-br.html +++ b/gl/dev/trans-verseline-pt-br.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                    Linhas de Verso

                                                                                                                                                                                                                                                                                                                                                    2023-04-27

                                                                                                                                                                                                                                                                                                                                                    • TEI definition: lg ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                                      Linhas de Verso

                                                                                                                                                                                                                                                                                                                                                      2024-03-05

                                                                                                                                                                                                                                                                                                                                                      • TEI definition: lg ; EpiDoc-specific customization: lg
                                                                                                                                                                                                                                                                                                                                                      • TEI definition: l ; EpiDoc-specific - customization: l

                                                                                                                                                                                                                                                                                                                                                      O EpiDoc segue a prática TEI de marcar as quebras de linha no suporte (em vez de linhas de verso) usando o elemento vazio lb (line-break/quebra de linha) para marcar o ponto em que a linha quebra (ou inicia - veja Quebras de Linha). Além de marcar linhas epigráficas, o que é obrigatório, um editor pode escolher codificar grupos de versos usando os elementos lg (line-group/grupos de linha) e l (linha).

                                                                                                                                                                                                                                                                                                                                                      Dentro das linhas de verso, no entanto, o início de cada linha de texto no suporte ainda temque ser marcado com um lb. Em outras palavras, lg e l estão substituindo os ab, mas não os lb.

                                                                                                                                                                                                                                                                                                                                                      Os grupos de linha e os elementos de linha podem conter atributos que registrem métrica, execução, rima, etc.

                                                                                                                                                                                                                                                                                                                                                      Panciera 1991 ; Sosin 2011; ; :

                                                                                                                                                                                                                                                                                                                                                      <l>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>Quaesii multum quot <lb n="2"/>memoriae tradere
                                                                                                                                                                                                                                                                                                                                                      </l>

                                                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                      • London style:
                                                                                                                                                                                                                                                                                                                                                        Quaesii multum quot
                                                                                                                                                                                                                                                                                                                                                        memoriae tradere
                                                                                                                                                                                                                                                                                                                                                      (IRT: 918)
                                                                                                                                                                                                                                                                                                                                                      <lg>
                                                                                                                                                                                                                                                                                                                                                       <lb n="1"/>
                                                                                                                                                                                                                                                                                                                                                       <l>
                                                                                                                                                                                                                                                                                                                                                        <unclear reason="damage">τ</unclear>ῆς μεγάλης ἀ<lb n="2break="no"/>ρετῆς τοῦτον<lb n="3"/>μέγαν ἡγεμον<unclear reason="damage"></unclear>α</l>
                                                                                                                                                                                                                                                                                                                                                       <lb n="4"/>
                                                                                                                                                                                                                                                                                                                                                       <l>Ἑλλάδιον <lb n="5"/>
                                                                                                                                                                                                                                                                                                                                                        <supplied reason="lost">Κ</supplied>ᾶρες στῆ<supplied reason="lost">σα</supplied>ν<lb n="6"/>
                                                                                                                                                                                                                                                                                                                                                        <supplied reason="lost"></supplied>
                                                                                                                                                                                                                                                                                                                                                        <unclear reason="undefined">μ</unclear>ειβ<unclear reason="damage">ό</unclear>μ<supplied reason="lost">ενο</supplied>
                                                                                                                                                                                                                                                                                                                                                        <unclear reason="damage">ι</unclear>.</l>
                                                                                                                                                                                                                                                                                                                                                      </lg>

                                                                                                                                                                                                                                                                                                                                                      Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                      • London style:

                                                                                                                                                                                                                                                                                                                                                        τ̣ῆς μεγάλης ἀ-
                                                                                                                                                                                                                                                                                                                                                        ρετῆς τοῦτον
                                                                                                                                                                                                                                                                                                                                                        μέγαν ἡγεμονῆ̣α
                                                                                                                                                                                                                                                                                                                                                        Ἑλλάδιον
                                                                                                                                                                                                                                                                                                                                                        [Κ]ᾶρες στῆ[σα]ν
                                                                                                                                                                                                                                                                                                                                                        [ἀ]μ̣ειβό̣μ[ενο]ι̣.
                                                                                                                                                                                                                                                                                                                                                      (InsAph: 1.131)

                                                                                                                                                                                                                                                                                                                                                      See also:

                                                                                                                                                                                                                                                                                                                                                      Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                                                        Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                                                          Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                          1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                          2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                          3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                          EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                          Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                          \ No newline at end of file + customization: l

                                                                                                                                                                                                                                                                                                                                                        O EpiDoc segue a prática TEI de marcar as quebras de linha no suporte (em vez de linhas de verso) usando o elemento vazio lb (line-break/quebra de linha) para marcar o ponto em que a linha quebra (ou inicia - veja Quebras de Linha). Além de marcar linhas epigráficas, o que é obrigatório, um editor pode escolher codificar grupos de versos usando os elementos lg (line-group/grupos de linha) e l (linha).

                                                                                                                                                                                                                                                                                                                                                        Dentro das linhas de verso, no entanto, o início de cada linha de texto no suporte ainda temque ser marcado com um lb. Em outras palavras, lg e l estão substituindo os ab, mas não os lb.

                                                                                                                                                                                                                                                                                                                                                        Os grupos de linha e os elementos de linha podem conter atributos que registrem métrica, execução, rima, etc.

                                                                                                                                                                                                                                                                                                                                                        Panciera 1991 ; Sosin 2011; ; :

                                                                                                                                                                                                                                                                                                                                                        <l>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>Quaesii multum quot <lb n="2"/>memoriae tradere
                                                                                                                                                                                                                                                                                                                                                        </l>

                                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                        • London style:
                                                                                                                                                                                                                                                                                                                                                          Quaesii multum quot
                                                                                                                                                                                                                                                                                                                                                          memoriae tradere
                                                                                                                                                                                                                                                                                                                                                        (IRT: 918)
                                                                                                                                                                                                                                                                                                                                                        <lg>
                                                                                                                                                                                                                                                                                                                                                         <lb n="1"/>
                                                                                                                                                                                                                                                                                                                                                         <l>
                                                                                                                                                                                                                                                                                                                                                          <unclear reason="damage">τ</unclear>ῆς μεγάλης ἀ<lb n="2break="no"/>ρετῆς τοῦτον<lb n="3"/>μέγαν ἡγεμον<unclear reason="damage"></unclear>α</l>
                                                                                                                                                                                                                                                                                                                                                         <lb n="4"/>
                                                                                                                                                                                                                                                                                                                                                         <l>Ἑλλάδιον <lb n="5"/>
                                                                                                                                                                                                                                                                                                                                                          <supplied reason="lost">Κ</supplied>ᾶρες στῆ<supplied reason="lost">σα</supplied>ν<lb n="6"/>
                                                                                                                                                                                                                                                                                                                                                          <supplied reason="lost"></supplied>
                                                                                                                                                                                                                                                                                                                                                          <unclear reason="undefined">μ</unclear>ειβ<unclear reason="damage">ό</unclear>μ<supplied reason="lost">ενο</supplied>
                                                                                                                                                                                                                                                                                                                                                          <unclear reason="damage">ι</unclear>.</l>
                                                                                                                                                                                                                                                                                                                                                        </lg>

                                                                                                                                                                                                                                                                                                                                                        Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                        • London style:

                                                                                                                                                                                                                                                                                                                                                          τ̣ῆς μεγάλης ἀ-
                                                                                                                                                                                                                                                                                                                                                          ρετῆς τοῦτον
                                                                                                                                                                                                                                                                                                                                                          μέγαν ἡγεμονῆ̣α
                                                                                                                                                                                                                                                                                                                                                          Ἑλλάδιον
                                                                                                                                                                                                                                                                                                                                                          [Κ]ᾶρες στῆ[σα]ν
                                                                                                                                                                                                                                                                                                                                                          [ἀ]μ̣ειβό̣μ[ενο]ι̣.
                                                                                                                                                                                                                                                                                                                                                        (InsAph: 1.131)

                                                                                                                                                                                                                                                                                                                                                        See also:

                                                                                                                                                                                                                                                                                                                                                        Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                                                          Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                            1. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                            2. Charlotte Tupman, autor
                                                                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-verseline.html b/gl/dev/trans-verseline.html index d6d32cd48..7278e3b44 100644 --- a/gl/dev/trans-verseline.html +++ b/gl/dev/trans-verseline.html @@ -21,6 +21,6 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                            Verse Lines

                                                                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                                                                            • TEI definition: lg ; EpiDoc-specific +

                                                                                                                                                                                                                                                                                                                                                              Verse Lines

                                                                                                                                                                                                                                                                                                                                                              2024-03-05

                                                                                                                                                                                                                                                                                                                                                              • TEI definition: lg ; EpiDoc-specific customization: lg
                                                                                                                                                                                                                                                                                                                                                              • TEI definition: l ; EpiDoc-specific - customization: l
                                                                                                                                                                                                                                                                                                                                                              • TEI definition: metDecl

                                                                                                                                                                                                                                                                                                                                                              TEI practice is to mark line breaks on the support (as opposed to verse lines) using the lb (line-begins) empty element to mark the point at which the line breaks (or begins - see Line breaks.) In addition to marking epigraphic lines, which is obligatory, an editor may choose to tag verse groups and lines using the lg (line-group) and l (line) elements.

                                                                                                                                                                                                                                                                                                                                                              Within the verse lines, however, the start of each line of text on the support still needs to be marked with an lb. In other words, lg and l are replacing the containing ab, but not the lbs.

                                                                                                                                                                                                                                                                                                                                                              <lg>
                                                                                                                                                                                                                                                                                                                                                               <l>
                                                                                                                                                                                                                                                                                                                                                                <lb n="1"/>Quaesii multum quot <lb n="2"/>memoriae tradere</l>
                                                                                                                                                                                                                                                                                                                                                              </lg>

                                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                              • London style:

                                                                                                                                                                                                                                                                                                                                                                Quaesii multum quot
                                                                                                                                                                                                                                                                                                                                                                memoriae tradere
                                                                                                                                                                                                                                                                                                                                                              • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                                | Quaesii multum quot | memoriae tradere
                                                                                                                                                                                                                                                                                                                                                              (IRT: 918)
                                                                                                                                                                                                                                                                                                                                                              <lg>
                                                                                                                                                                                                                                                                                                                                                               <lb n="1"/>
                                                                                                                                                                                                                                                                                                                                                               <l>
                                                                                                                                                                                                                                                                                                                                                                <unclear reason="damage">τ</unclear>ῆς μεγάλης ἀ<lb n="2break="no"/>ρετῆς τοῦτον<lb n="3"/>μέγαν ἡγεμον<unclear reason="damage"></unclear>α
                                                                                                                                                                                                                                                                                                                                                               </l>
                                                                                                                                                                                                                                                                                                                                                               <lb n="4"/>
                                                                                                                                                                                                                                                                                                                                                               <l>Ἑλλάδιον <lb n="5"/>
                                                                                                                                                                                                                                                                                                                                                                <supplied reason="lost">Κ</supplied>ᾶρες στῆ<supplied reason="lost">σα</supplied>ν<lb n="6"/>
                                                                                                                                                                                                                                                                                                                                                                <supplied reason="lost"></supplied>
                                                                                                                                                                                                                                                                                                                                                                <unclear reason="undefined">μ</unclear>ειβ<unclear reason="damage">ό</unclear>μ<supplied reason="lost">ενο</supplied>
                                                                                                                                                                                                                                                                                                                                                                <unclear reason="damage">ι</unclear>.
                                                                                                                                                                                                                                                                                                                                                               </l>
                                                                                                                                                                                                                                                                                                                                                              </lg>

                                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                              • London style:

                                                                                                                                                                                                                                                                                                                                                                τ̣ῆς μεγάλης ἀ-
                                                                                                                                                                                                                                                                                                                                                                ρετῆς τοῦτον
                                                                                                                                                                                                                                                                                                                                                                μέγαν ἡγεμονῆ̣α
                                                                                                                                                                                                                                                                                                                                                                Ἑλλάδιον
                                                                                                                                                                                                                                                                                                                                                                [Κ]ᾶρες στῆ[σα]ν
                                                                                                                                                                                                                                                                                                                                                                [ἀ]μ̣ειβό̣μ[ενο]ι̣.
                                                                                                                                                                                                                                                                                                                                                              • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                                τ̣ῆς μεγάλης ἀ|ρετῆς τοῦτον | μέγαν ἡγεμονῆ̣α |
                                                                                                                                                                                                                                                                                                                                                                Ἑλλάδιον | [Κ]ᾶρες στῆ[σα]ν | [ἀ]μ̣ειβό̣μ[ενο]ι̣.
                                                                                                                                                                                                                                                                                                                                                              (InsAph: 1.131)

                                                                                                                                                                                                                                                                                                                                                              The verse line-group may contain attributes recording number of group (e.g. n with a value of "1", "2", "a", "b", etc.) and conventional metrical structure by means of either a standard term for the metrical unit (e.g. met with value "elegiac couplet"; or "iambic trimeters") or a representation for the metrical pattern (e.g. for the iambic trimeter met="±+|-+|±+|-+|±+|-±"). In verse systems where rhyme exists, an attribute rhyme may be added to specify the rhyme scheme applicable to a group of verse lines.

                                                                                                                                                                                                                                                                                                                                                              The rhythm of a verse line, both conventional and realised, may be represented in the met, and real attributes respectively, by a sequence of alternating plus signs (+) and minus signs (-). The plus sign constitutes a long (in quantitative meter) or stressed (in accentuating meter) syllable and the minus sign stands for a short (quantitative) or unstressed (accentuating) syllable.

                                                                                                                                                                                                                                                                                                                                                              The verse’s feet may be indicated with a vertical bar (|) inside the met and real attributes. There are two possibilities of encoding caesurae and diaeresis (the specific kind of caesura which occurs on a foot boundary): (1) they could be inserted in the real attribute with a slash (/) for caesura and a double vertical bar (||) for the dieresis; (2) alternatively (or additionally) pauses could be represented within the text using the TEI empty element <caesura> (see Metrical Elements).

                                                                                                                                                                                                                                                                                                                                                              <lg met="#dactylic.elegaic">
                                                                                                                                                                                                                                                                                                                                                               <l met="#dactylic.hexameter"
                                                                                                                                                                                                                                                                                                                                                                real="++|+/+|+/--|+/+|+--|+-">

                                                                                                                                                                                                                                                                                                                                                                <lb/>Caelestis mul<lb break="no"/>sa propria<lb/> placabitur ara</l>
                                                                                                                                                                                                                                                                                                                                                               <l met="#dactylic.pentameter"
                                                                                                                                                                                                                                                                                                                                                                real="++|+--|+||+--|+--|-">

                                                                                                                                                                                                                                                                                                                                                                <lb/>hac divis aliis <lb/> tura merumq(ue) <lb/> damus</l>
                                                                                                                                                                                                                                                                                                                                                              </lg>

                                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                                                                Caelestis mul-
                                                                                                                                                                                                                                                                                                                                                                sa propria
                                                                                                                                                                                                                                                                                                                                                                placabitur ara
                                                                                                                                                                                                                                                                                                                                                                hac divis aliis
                                                                                                                                                                                                                                                                                                                                                                tura merumq(ue)
                                                                                                                                                                                                                                                                                                                                                                damus
                                                                                                                                                                                                                                                                                                                                                              • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                                | Caelestis mul|sa propria | placabitur ara
                                                                                                                                                                                                                                                                                                                                                                | hac divis aliis | tura merumq(ue) | damus

                                                                                                                                                                                                                                                                                                                                                              The verse line elements may contain attributes recording number of line (e.g. n with a value of "1", "2", etc.); conventional metrical structure by means of either a standard term for the metrical unit (e.g. met with value "hexameter"; met with value "pentameter") or a representation for the metrical pattern (e.g. for the hexameter met with value "+--|+--|+--|+--|+--|+±"); realization of metrical structure (e.g. real with value "-+|-+|-+|-+|++|-+", for iambic trimeter; real with value "+--|++|+--|+--|+--|+-" for hexameter; real with value "+--|++|+|+--|+--|+" for pentameter).

                                                                                                                                                                                                                                                                                                                                                              When using a met and a real, the notation used should be documented by a <metDecl> element within the encodingDesc of the associated header.

                                                                                                                                                                                                                                                                                                                                                              When a verse line is fragmentary and cannot be restored, the metrical values or pattern of the lacuna is marked using a seg element with an attribute met (see Lost Characters, Metre Known/Reconstructed), while the metrical values or pattern of the extant portion of the verse line may be marked using a seg element with an attribute real.

                                                                                                                                                                                                                                                                                                                                                              <lg n="amet="elegiac couplet">
                                                                                                                                                                                                                                                                                                                                                               <l n="1met="hexameter"
                                                                                                                                                                                                                                                                                                                                                                real="+--|+--|+--|++|+--|+-">

                                                                                                                                                                                                                                                                                                                                                                <lb n="1"/>Δεύτερον εἰς λυκάβαντα
                                                                                                                                                                                                                                                                                                                                                               <lb n="2"/>καὶ ἰκοστόν με περῶσαν</l>
                                                                                                                                                                                                                                                                                                                                                               <l n="2met="pentameter"
                                                                                                                                                                                                                                                                                                                                                                real="+--|++|+|+--|+--|+">

                                                                                                                                                                                                                                                                                                                                                                <lb n="3"/>λυγρὸς ἀφ᾿ ἱμερτῶν εἷλε
                                                                                                                                                                                                                                                                                                                                                               <lb n="4"/>μόρος θαλάμων <space quantity="4unit="character"/>
                                                                                                                                                                                                                                                                                                                                                               </l>
                                                                                                                                                                                                                                                                                                                                                              </lg>
                                                                                                                                                                                                                                                                                                                                                              <lg n="bmet="elegiac couplet">
                                                                                                                                                                                                                                                                                                                                                               <l n="3met="hexameter"
                                                                                                                                                                                                                                                                                                                                                                real="+--|++|+--|+--|++|+-">

                                                                                                                                                                                                                                                                                                                                                                <lb n="5"/>ούδ᾿ ὅλον εἰς πλειῶνα γά<lb n="6break="no"/>μοις ἐπιγηθήσασαν·<space quantity="3unit="character"/>
                                                                                                                                                                                                                                                                                                                                                               </l>
                                                                                                                                                                                                                                                                                                                                                               <l n="4met="pentameter"
                                                                                                                                                                                                                                                                                                                                                                real="+--|++|+|+--|+--|-">

                                                                                                                                                                                                                                                                                                                                                                <lb n="7"/>ἤματι δ᾿ὧι παστὸν καὶ <space quantity="2unit="character"/>
                                                                                                                                                                                                                                                                                                                                                                <lb n="8"/>σποδίην ἔλαχον, <space quantity="5unit="character"/>
                                                                                                                                                                                                                                                                                                                                                               </l>
                                                                                                                                                                                                                                                                                                                                                              </lg>
                                                                                                                                                                                                                                                                                                                                                              <lg n="cmet="elegiac couplet">
                                                                                                                                                                                                                                                                                                                                                               <l n="5met="hexameter"
                                                                                                                                                                                                                                                                                                                                                                real="+--|+--|+--|+--|--|++">

                                                                                                                                                                                                                                                                                                                                                                <lb n="9"/> Στλακκίη αἰνοδάκρυτος·
                                                                                                                                                                                                                                                                                                                                                               <lb n="10"/>ἀμαυροτέρηι δ᾿ ὑπὸ λύπηι</l>
                                                                                                                                                                                                                                                                                                                                                               <l n="6met="pentameter"
                                                                                                                                                                                                                                                                                                                                                                real="++|++|+|+--|+--|+">

                                                                                                                                                                                                                                                                                                                                                                <lb n="11"/>θνήσκω τὴν μούνην σοι,
                                                                                                                                                                                                                                                                                                                                                               <lb n="12"/>πόσι, παρθεμένη <g type="leaf"></g>
                                                                                                                                                                                                                                                                                                                                                               </l>
                                                                                                                                                                                                                                                                                                                                                              </lg>

                                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                                                                Δεύτερον εἰς λυκάβαντα
                                                                                                                                                                                                                                                                                                                                                                καὶ ἰκοστόν με περῶσαν
                                                                                                                                                                                                                                                                                                                                                                λυγρὸς ἀφ᾿ ἱμερτῶν εἷλε
                                                                                                                                                                                                                                                                                                                                                                μόρος θαλάμων ( vac. 4)

                                                                                                                                                                                                                                                                                                                                                                ούδ᾿ ὅλον εἰς πλειῶνα γά-
                                                                                                                                                                                                                                                                                                                                                                μοις ἐπιγηθήσασαν·( vac. 3)
                                                                                                                                                                                                                                                                                                                                                                ἤματι δ᾿ὧι παστὸν καὶ ( vac. 2)
                                                                                                                                                                                                                                                                                                                                                                σποδίην ἔλαχον, ( vac. 5)

                                                                                                                                                                                                                                                                                                                                                                Στλακκίη αἰνοδάκρυτος·
                                                                                                                                                                                                                                                                                                                                                                ἀμαυροτέρηι δ᾿ ὑπὸ λύπηι
                                                                                                                                                                                                                                                                                                                                                                θνήσκω τὴν μούνην σοι,
                                                                                                                                                                                                                                                                                                                                                                πόσι, παρθεμένη ((leaf))
                                                                                                                                                                                                                                                                                                                                                              • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                                | Δεύτερον εἰς λυκάβαντα | καὶ ἰκοστόν με περῶσαν
                                                                                                                                                                                                                                                                                                                                                                    | λυγρὸς ἀφ᾿ ἱμερτῶν εἷλε | μόρος θαλάμων ( vac. 4)

                                                                                                                                                                                                                                                                                                                                                                | ούδ᾿ ὅλον εἰς πλειῶνα γά|μοις ἐπιγηθήσασαν·( vac. 3)
                                                                                                                                                                                                                                                                                                                                                                    | ἤματι δ᾿ὧι παστὸν καὶ ( vac. 2) | σποδίην ἔλαχον, ( vac. 5)

                                                                                                                                                                                                                                                                                                                                                                | Στλακκίη αἰνοδάκρυτος· | ἀμαυροτέρηι δ᾿ ὑπὸ λύπηι
                                                                                                                                                                                                                                                                                                                                                                    | θνήσκω τὴν μούνην σοι, | πόσι, παρθεμένη ((leaf))
                                                                                                                                                                                                                                                                                                                                                              (GVCyr: gvcyr007)
                                                                                                                                                                                                                                                                                                                                                              <l n="1met="hexameter">
                                                                                                                                                                                                                                                                                                                                                               <seg real="++|++|+">
                                                                                                                                                                                                                                                                                                                                                                <lb n="1rend="right-to-left"/>
                                                                                                                                                                                                                                                                                                                                                                <unclear>Κ</unclear>οίσōνος
                                                                                                                                                                                                                                                                                                                                                                 στάλα</seg>
                                                                                                                                                                                                                                                                                                                                                               <seg met="--|+--|+--|+±">
                                                                                                                                                                                                                                                                                                                                                                <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                                                                 unit="character"/>

                                                                                                                                                                                                                                                                                                                                                               </seg>
                                                                                                                                                                                                                                                                                                                                                              </l>

                                                                                                                                                                                                                                                                                                                                                              Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                              • Default (Panciera) style:
                                                                                                                                                                                                                                                                                                                                                                Κ̣οίσōνος στάλα [---]
                                                                                                                                                                                                                                                                                                                                                              • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                                Κ̣οίσōνος στάλα [ ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ± ]
                                                                                                                                                                                                                                                                                                                                                              (GVCyr: gvcyr001)

                                                                                                                                                                                                                                                                                                                                                              Panciera 1991 ; Sosin 2011; ; :

                                                                                                                                                                                                                                                                                                                                                              See also:

                                                                                                                                                                                                                                                                                                                                                              Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                                                              Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                                                              Other pages describing <metDecl>:

                                                                                                                                                                                                                                                                                                                                                              Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                              1. Alice Bencivenni, author
                                                                                                                                                                                                                                                                                                                                                              2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                              3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                              4. Gabriël de Klerk, author
                                                                                                                                                                                                                                                                                                                                                              5. Francesco Tecca, author
                                                                                                                                                                                                                                                                                                                                                              6. Chiara Cenati, author
                                                                                                                                                                                                                                                                                                                                                              7. Marta Fogagnolo, author

                                                                                                                                                                                                                                                                                                                                                              EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                              Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                              \ No newline at end of file + customization: l
                                                                                                                                                                                                                                                                                                                                                            • TEI definition: metDecl

                                                                                                                                                                                                                                                                                                                                                            TEI practice is to mark line breaks on the support (as opposed to verse lines) using the lb (line-begins) empty element to mark the point at which the line breaks (or begins - see Line breaks.) In addition to marking epigraphic lines, which is obligatory, an editor may choose to tag verse groups and lines using the lg (line-group) and l (line) elements.

                                                                                                                                                                                                                                                                                                                                                            Within the verse lines, however, the start of each line of text on the support still needs to be marked with an lb. In other words, lg and l are replacing the containing ab, but not the lbs.

                                                                                                                                                                                                                                                                                                                                                            <lg>
                                                                                                                                                                                                                                                                                                                                                             <l>
                                                                                                                                                                                                                                                                                                                                                              <lb n="1"/>Quaesii multum quot <lb n="2"/>memoriae tradere</l>
                                                                                                                                                                                                                                                                                                                                                            </lg>

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • London style:

                                                                                                                                                                                                                                                                                                                                                              Quaesii multum quot
                                                                                                                                                                                                                                                                                                                                                              memoriae tradere
                                                                                                                                                                                                                                                                                                                                                            • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                              | Quaesii multum quot | memoriae tradere
                                                                                                                                                                                                                                                                                                                                                            (IRT: 918)
                                                                                                                                                                                                                                                                                                                                                            <lg>
                                                                                                                                                                                                                                                                                                                                                             <lb n="1"/>
                                                                                                                                                                                                                                                                                                                                                             <l>
                                                                                                                                                                                                                                                                                                                                                              <unclear reason="damage">τ</unclear>ῆς μεγάλης ἀ<lb n="2break="no"/>ρετῆς τοῦτον<lb n="3"/>μέγαν ἡγεμον<unclear reason="damage"></unclear>α
                                                                                                                                                                                                                                                                                                                                                             </l>
                                                                                                                                                                                                                                                                                                                                                             <lb n="4"/>
                                                                                                                                                                                                                                                                                                                                                             <l>Ἑλλάδιον <lb n="5"/>
                                                                                                                                                                                                                                                                                                                                                              <supplied reason="lost">Κ</supplied>ᾶρες στῆ<supplied reason="lost">σα</supplied>ν<lb n="6"/>
                                                                                                                                                                                                                                                                                                                                                              <supplied reason="lost"></supplied>
                                                                                                                                                                                                                                                                                                                                                              <unclear reason="undefined">μ</unclear>ειβ<unclear reason="damage">ό</unclear>μ<supplied reason="lost">ενο</supplied>
                                                                                                                                                                                                                                                                                                                                                              <unclear reason="damage">ι</unclear>.
                                                                                                                                                                                                                                                                                                                                                             </l>
                                                                                                                                                                                                                                                                                                                                                            </lg>

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • London style:

                                                                                                                                                                                                                                                                                                                                                              τ̣ῆς μεγάλης ἀ-
                                                                                                                                                                                                                                                                                                                                                              ρετῆς τοῦτον
                                                                                                                                                                                                                                                                                                                                                              μέγαν ἡγεμονῆ̣α
                                                                                                                                                                                                                                                                                                                                                              Ἑλλάδιον
                                                                                                                                                                                                                                                                                                                                                              [Κ]ᾶρες στῆ[σα]ν
                                                                                                                                                                                                                                                                                                                                                              [ἀ]μ̣ειβό̣μ[ενο]ι̣.
                                                                                                                                                                                                                                                                                                                                                            • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                              τ̣ῆς μεγάλης ἀ|ρετῆς τοῦτον | μέγαν ἡγεμονῆ̣α |
                                                                                                                                                                                                                                                                                                                                                              Ἑλλάδιον | [Κ]ᾶρες στῆ[σα]ν | [ἀ]μ̣ειβό̣μ[ενο]ι̣.
                                                                                                                                                                                                                                                                                                                                                            (InsAph: 1.131)

                                                                                                                                                                                                                                                                                                                                                            The verse line-group may contain attributes recording number of group (e.g. n with a value of "1", "2", "a", "b", etc.) and conventional metrical structure by means of either a standard term for the metrical unit (e.g. met with value "elegiac couplet"; or "iambic trimeters") or a representation for the metrical pattern (e.g. for the iambic trimeter met="±+|-+|±+|-+|±+|-±"). In verse systems where rhyme exists, an attribute rhyme may be added to specify the rhyme scheme applicable to a group of verse lines.

                                                                                                                                                                                                                                                                                                                                                            The rhythm of a verse line, both conventional and realised, may be represented in the met, and real attributes respectively, by a sequence of alternating plus signs (+) and minus signs (-). The plus sign constitutes a long (in quantitative meter) or stressed (in accentuating meter) syllable and the minus sign stands for a short (quantitative) or unstressed (accentuating) syllable.

                                                                                                                                                                                                                                                                                                                                                            The verse’s feet may be indicated with a vertical bar (|) inside the met and real attributes. There are two possibilities of encoding caesurae and diaeresis (the specific kind of caesura which occurs on a foot boundary): (1) they could be inserted in the real attribute with a slash (/) for caesura and a double vertical bar (||) for the dieresis; (2) alternatively (or additionally) pauses could be represented within the text using the TEI empty element <caesura> (see Metrical Elements).

                                                                                                                                                                                                                                                                                                                                                            <lg met="#dactylic.elegaic">
                                                                                                                                                                                                                                                                                                                                                             <l met="#dactylic.hexameter"
                                                                                                                                                                                                                                                                                                                                                              real="++|+/+|+/--|+/+|+--|+-">

                                                                                                                                                                                                                                                                                                                                                              <lb/>Caelestis mul<lb break="no"/>sa propria<lb/> placabitur ara</l>
                                                                                                                                                                                                                                                                                                                                                             <l met="#dactylic.pentameter"
                                                                                                                                                                                                                                                                                                                                                              real="++|+--|+||+--|+--|-">

                                                                                                                                                                                                                                                                                                                                                              <lb/>hac divis aliis <lb/> tura merumq(ue) <lb/> damus</l>
                                                                                                                                                                                                                                                                                                                                                            </lg>

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                                                              Caelestis mul-
                                                                                                                                                                                                                                                                                                                                                              sa propria
                                                                                                                                                                                                                                                                                                                                                              placabitur ara
                                                                                                                                                                                                                                                                                                                                                              hac divis aliis
                                                                                                                                                                                                                                                                                                                                                              tura merumq(ue)
                                                                                                                                                                                                                                                                                                                                                              damus
                                                                                                                                                                                                                                                                                                                                                            • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                              | Caelestis mul|sa propria | placabitur ara
                                                                                                                                                                                                                                                                                                                                                              | hac divis aliis | tura merumq(ue) | damus

                                                                                                                                                                                                                                                                                                                                                            The verse line elements may contain attributes recording number of line (e.g. n with a value of "1", "2", etc.); conventional metrical structure by means of either a standard term for the metrical unit (e.g. met with value "hexameter"; met with value "pentameter") or a representation for the metrical pattern (e.g. for the hexameter met with value "+--|+--|+--|+--|+--|+±"); realization of metrical structure (e.g. real with value "-+|-+|-+|-+|++|-+", for iambic trimeter; real with value "+--|++|+--|+--|+--|+-" for hexameter; real with value "+--|++|+|+--|+--|+" for pentameter).

                                                                                                                                                                                                                                                                                                                                                            When using a met and a real, the notation used should be documented by a <metDecl> element within the encodingDesc of the associated header.

                                                                                                                                                                                                                                                                                                                                                            When a verse line is fragmentary and cannot be restored, the metrical values or pattern of the lacuna is marked using a seg element with an attribute met (see Lost Characters, Metre Known/Reconstructed), while the metrical values or pattern of the extant portion of the verse line may be marked using a seg element with an attribute real.

                                                                                                                                                                                                                                                                                                                                                            <lg n="amet="elegiac couplet">
                                                                                                                                                                                                                                                                                                                                                             <l n="1met="hexameter"
                                                                                                                                                                                                                                                                                                                                                              real="+--|+--|+--|++|+--|+-">

                                                                                                                                                                                                                                                                                                                                                              <lb n="1"/>Δεύτερον εἰς λυκάβαντα
                                                                                                                                                                                                                                                                                                                                                             <lb n="2"/>καὶ ἰκοστόν με περῶσαν</l>
                                                                                                                                                                                                                                                                                                                                                             <l n="2met="pentameter"
                                                                                                                                                                                                                                                                                                                                                              real="+--|++|+|+--|+--|+">

                                                                                                                                                                                                                                                                                                                                                              <lb n="3"/>λυγρὸς ἀφ᾿ ἱμερτῶν εἷλε
                                                                                                                                                                                                                                                                                                                                                             <lb n="4"/>μόρος θαλάμων <space quantity="4unit="character"/>
                                                                                                                                                                                                                                                                                                                                                             </l>
                                                                                                                                                                                                                                                                                                                                                            </lg>
                                                                                                                                                                                                                                                                                                                                                            <lg n="bmet="elegiac couplet">
                                                                                                                                                                                                                                                                                                                                                             <l n="3met="hexameter"
                                                                                                                                                                                                                                                                                                                                                              real="+--|++|+--|+--|++|+-">

                                                                                                                                                                                                                                                                                                                                                              <lb n="5"/>ούδ᾿ ὅλον εἰς πλειῶνα γά<lb n="6break="no"/>μοις ἐπιγηθήσασαν·<space quantity="3unit="character"/>
                                                                                                                                                                                                                                                                                                                                                             </l>
                                                                                                                                                                                                                                                                                                                                                             <l n="4met="pentameter"
                                                                                                                                                                                                                                                                                                                                                              real="+--|++|+|+--|+--|-">

                                                                                                                                                                                                                                                                                                                                                              <lb n="7"/>ἤματι δ᾿ὧι παστὸν καὶ <space quantity="2unit="character"/>
                                                                                                                                                                                                                                                                                                                                                              <lb n="8"/>σποδίην ἔλαχον, <space quantity="5unit="character"/>
                                                                                                                                                                                                                                                                                                                                                             </l>
                                                                                                                                                                                                                                                                                                                                                            </lg>
                                                                                                                                                                                                                                                                                                                                                            <lg n="cmet="elegiac couplet">
                                                                                                                                                                                                                                                                                                                                                             <l n="5met="hexameter"
                                                                                                                                                                                                                                                                                                                                                              real="+--|+--|+--|+--|--|++">

                                                                                                                                                                                                                                                                                                                                                              <lb n="9"/> Στλακκίη αἰνοδάκρυτος·
                                                                                                                                                                                                                                                                                                                                                             <lb n="10"/>ἀμαυροτέρηι δ᾿ ὑπὸ λύπηι</l>
                                                                                                                                                                                                                                                                                                                                                             <l n="6met="pentameter"
                                                                                                                                                                                                                                                                                                                                                              real="++|++|+|+--|+--|+">

                                                                                                                                                                                                                                                                                                                                                              <lb n="11"/>θνήσκω τὴν μούνην σοι,
                                                                                                                                                                                                                                                                                                                                                             <lb n="12"/>πόσι, παρθεμένη <g type="leaf"></g>
                                                                                                                                                                                                                                                                                                                                                             </l>
                                                                                                                                                                                                                                                                                                                                                            </lg>

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style:

                                                                                                                                                                                                                                                                                                                                                              Δεύτερον εἰς λυκάβαντα
                                                                                                                                                                                                                                                                                                                                                              καὶ ἰκοστόν με περῶσαν
                                                                                                                                                                                                                                                                                                                                                              λυγρὸς ἀφ᾿ ἱμερτῶν εἷλε
                                                                                                                                                                                                                                                                                                                                                              μόρος θαλάμων ( vac. 4)

                                                                                                                                                                                                                                                                                                                                                              ούδ᾿ ὅλον εἰς πλειῶνα γά-
                                                                                                                                                                                                                                                                                                                                                              μοις ἐπιγηθήσασαν·( vac. 3)
                                                                                                                                                                                                                                                                                                                                                              ἤματι δ᾿ὧι παστὸν καὶ ( vac. 2)
                                                                                                                                                                                                                                                                                                                                                              σποδίην ἔλαχον, ( vac. 5)

                                                                                                                                                                                                                                                                                                                                                              Στλακκίη αἰνοδάκρυτος·
                                                                                                                                                                                                                                                                                                                                                              ἀμαυροτέρηι δ᾿ ὑπὸ λύπηι
                                                                                                                                                                                                                                                                                                                                                              θνήσκω τὴν μούνην σοι,
                                                                                                                                                                                                                                                                                                                                                              πόσι, παρθεμένη ((leaf))
                                                                                                                                                                                                                                                                                                                                                            • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                              | Δεύτερον εἰς λυκάβαντα | καὶ ἰκοστόν με περῶσαν
                                                                                                                                                                                                                                                                                                                                                                  | λυγρὸς ἀφ᾿ ἱμερτῶν εἷλε | μόρος θαλάμων ( vac. 4)

                                                                                                                                                                                                                                                                                                                                                              | ούδ᾿ ὅλον εἰς πλειῶνα γά|μοις ἐπιγηθήσασαν·( vac. 3)
                                                                                                                                                                                                                                                                                                                                                                  | ἤματι δ᾿ὧι παστὸν καὶ ( vac. 2) | σποδίην ἔλαχον, ( vac. 5)

                                                                                                                                                                                                                                                                                                                                                              | Στλακκίη αἰνοδάκρυτος· | ἀμαυροτέρηι δ᾿ ὑπὸ λύπηι
                                                                                                                                                                                                                                                                                                                                                                  | θνήσκω τὴν μούνην σοι, | πόσι, παρθεμένη ((leaf))
                                                                                                                                                                                                                                                                                                                                                            (GVCyr: gvcyr007)
                                                                                                                                                                                                                                                                                                                                                            <l n="1met="hexameter">
                                                                                                                                                                                                                                                                                                                                                             <seg real="++|++|+">
                                                                                                                                                                                                                                                                                                                                                              <lb n="1rend="right-to-left"/>
                                                                                                                                                                                                                                                                                                                                                              <unclear>Κ</unclear>οίσōνος
                                                                                                                                                                                                                                                                                                                                                               στάλα</seg>
                                                                                                                                                                                                                                                                                                                                                             <seg met="--|+--|+--|+±">
                                                                                                                                                                                                                                                                                                                                                              <gap reason="lostextent="unknown"
                                                                                                                                                                                                                                                                                                                                                               unit="character"/>

                                                                                                                                                                                                                                                                                                                                                             </seg>
                                                                                                                                                                                                                                                                                                                                                            </l>

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style:
                                                                                                                                                                                                                                                                                                                                                              Κ̣οίσōνος στάλα [---]
                                                                                                                                                                                                                                                                                                                                                            • verse parameter on:

                                                                                                                                                                                                                                                                                                                                                              Κ̣οίσōνος στάλα [ ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ˘  ˘  |  ˉ  ± ]
                                                                                                                                                                                                                                                                                                                                                            (GVCyr: gvcyr001)

                                                                                                                                                                                                                                                                                                                                                            Panciera 1991 ; Sosin 2011; ; :

                                                                                                                                                                                                                                                                                                                                                            See also:

                                                                                                                                                                                                                                                                                                                                                            Other pages describing <lg>:

                                                                                                                                                                                                                                                                                                                                                            Other pages describing <l>:

                                                                                                                                                                                                                                                                                                                                                            Other pages describing <metDecl>:

                                                                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                            1. Alice Bencivenni, author
                                                                                                                                                                                                                                                                                                                                                            2. Gabriel Bodard, author
                                                                                                                                                                                                                                                                                                                                                            3. Charlotte Tupman, author
                                                                                                                                                                                                                                                                                                                                                            4. Gabriël de Klerk, author
                                                                                                                                                                                                                                                                                                                                                            5. Francesco Tecca, author
                                                                                                                                                                                                                                                                                                                                                            6. Chiara Cenati, author
                                                                                                                                                                                                                                                                                                                                                            7. Marta Fogagnolo, author

                                                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-whitespace-pt-br.html b/gl/dev/trans-whitespace-pt-br.html index 9eda21004..cf1680928 100644 --- a/gl/dev/trans-whitespace-pt-br.html +++ b/gl/dev/trans-whitespace-pt-br.html @@ -21,14 +21,14 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                            Gerenciando Espaço em Branco em Transcrições

                                                                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                                                                            • TEI definition: expan ; EpiDoc-specific - customization: expan

                                                                                                                                                                                                                                                                                                                                                            Em transcrições diplomáticas e editadas, o tratamento padrão do Epidoc para lidar com o espaço em branco pode não produzir os resultados desejados. Problemas ocorrem em diversas ocasiões, a mais comum sendo espaços que aparecem antes e depois de um elemento de frase. O XML trata espaço em branco de forma diferente quando ele aparece dentro de um elemento definido para conter apenas subelementos e nenhum texto livre, e elementos cuja definição permite uma mistura de texto com outros elementos. No primeiro caso, o espaço em branco em torno dos elementos contidos será ignorado. No segundo caso, espaços e retornos serão tratados como texto, e aparecerão formatados na saída como espaço único. Isto se complica devido à forma com que os editores, como o oXygen XML lidam com marcação de linhas - linhas marcadas para aumentar a legibilidade não têm espaços ou caracteres linefeed as separando, só parecem ter.

                                                                                                                                                                                                                                                                                                                                                            Nos exemplos abaixo, expan recebe os subelementos abbr e ex e também algum texto livre. No segundo caso, espaços antes ou depois dos subelementos aparecem no resultado final.

                                                                                                                                                                                                                                                                                                                                                            +

                                                                                                                                                                                                                                                                                                                                                            Gerenciando Espaço em Branco em Transcrições

                                                                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                                                                            • TEI definition: expan ; EpiDoc-specific + customization: expan

                                                                                                                                                                                                                                                                                                                                                            Em transcrições diplomáticas e editadas, o tratamento padrão do Epidoc para lidar com o espaço em branco pode não produzir os resultados desejados. Problemas ocorrem em diversas ocasiões, a mais comum sendo espaços que aparecem antes e depois de um elemento de frase. O XML trata espaço em branco de forma diferente quando ele aparece dentro de um elemento definido para conter apenas subelementos e nenhum texto livre, e elementos cuja definição permite uma mistura de texto com outros elementos. No primeiro caso, o espaço em branco em torno dos elementos contidos será ignorado. No segundo caso, espaços e retornos serão tratados como texto, e aparecerão formatados na saída como espaço único. Isto se complica devido à forma com que os editores, como o oXygen XML lidam com marcação de linhas - linhas marcadas para aumentar a legibilidade não têm espaços ou caracteres linefeed as separando, só parecem ter.

                                                                                                                                                                                                                                                                                                                                                            Nos exemplos abaixo, expan recebe os subelementos abbr e ex e também algum texto livre. No segundo caso, espaços antes ou depois dos subelementos aparecem no resultado final.

                                                                                                                                                                                                                                                                                                                                                                    <expan><abbr>Aug</abbr><ex>ustus</ex></expan> -    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug(ustus)
                                                                                                                                                                                                                                                                                                                                                            +    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug(ustus)
                                                                                                                                                                                                                                                                                                                                                                    <expan>             <abbr>Aug</abbr>             <ex>ustus</ex>         </expan> -    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug (ustus)

                                                                                                                                                                                                                                                                                                                                                            O exemploaseguir não terá espaços em torno de qualquer das partes da abreviação. Entretanto, se houver line feeds dentro do expan eles serão mantidos.

                                                                                                                                                                                                                                                                                                                                                            +    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug (ustus)

                                                                                                                                                                                                                                                                                                                                                            O exemploaseguir não terá espaços em torno de qualquer das partes da abreviação. Entretanto, se houver line feeds dentro do expan eles serão mantidos.

                                                                                                                                                                                                                                                                                                                                                                    <expan>Καρ<ex>ανίδι</ex></expan> -    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Duke Databank style: Καρ(ανίδι)
                                                                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.1.154)

                                                                                                                                                                                                                                                                                                                                                            Se aparecerem, em um output formatado pelo Epidoc, espaços em branco onde estes não deveriam estar, a primeira coisa a fazer é verificar os arquivos fonte no XML para procurar espaços ou linefeeds que tenhamsido inseridos durante o processodecodificação, muitas vezes para melhorar a leitura.

                                                                                                                                                                                                                                                                                                                                                            Em alguns casos, por exemplo quando se codifica inscrições em hebraico ou arábico que usam um sistema de escrita da direita para a esquerda, é necessário usar line feeds antes das tags, para preservar a direcionalidade. Quando é importante preservar oespaço em branco exatamente como foi inserido, você deve configurar a propriedade <xsl:preserve-space> no início de seu arquivo de transformação xsl, e identificar os elementos para os quais isto se aplica. Então você pode gerencias espaço em branco explicitamente durante o processo de formatação.

                                                                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                            1. Elli Mylonas, autor
                                                                                                                                                                                                                                                                                                                                                            2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                            \ No newline at end of file +    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Duke Databank style: Καρ(ανίδι)
                                                                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.1.154)

                                                                                                                                                                                                                                                                                                                                                            Se aparecerem, em um output formatado pelo Epidoc, espaços em branco onde estes não deveriam estar, a primeira coisa a fazer é verificar os arquivos fonte no XML para procurar espaços ou linefeeds que tenhamsido inseridos durante o processodecodificação, muitas vezes para melhorar a leitura.

                                                                                                                                                                                                                                                                                                                                                            Em alguns casos, por exemplo quando se codifica inscrições em hebraico ou arábico que usam um sistema de escrita da direita para a esquerda, é necessário usar line feeds antes das tags, para preservar a direcionalidade. Quando é importante preservar oespaço em branco exatamente como foi inserido, você deve configurar a propriedade <xsl:preserve-space> no início de seu arquivo de transformação xsl, e identificar os elementos para os quais isto se aplica. Então você pode gerencias espaço em branco explicitamente durante o processo de formatação.

                                                                                                                                                                                                                                                                                                                                                            Responsabilidade por esta seção

                                                                                                                                                                                                                                                                                                                                                            1. Elli Mylonas, autor
                                                                                                                                                                                                                                                                                                                                                            2. Gabriel Bodard, autor
                                                                                                                                                                                                                                                                                                                                                            3. Assunção Medeiros, traduzido para o Português por

                                                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                            \ No newline at end of file diff --git a/gl/dev/trans-whitespace.html b/gl/dev/trans-whitespace.html index 6e04dfc7d..d34c689ac 100644 --- a/gl/dev/trans-whitespace.html +++ b/gl/dev/trans-whitespace.html @@ -21,14 +21,14 @@ window.open("https://www.google.com/search?q=" + $("#searchBox").val() + "%20site%3A" + encodeURIComponent(url)); }); }); -

                                                                                                                                                                                                                                                                                                                                                            Managing Whitespace in Transcriptions

                                                                                                                                                                                                                                                                                                                                                            2023-04-27

                                                                                                                                                                                                                                                                                                                                                            • TEI definition: expan ; EpiDoc-specific - customization: expan

                                                                                                                                                                                                                                                                                                                                                            In diplomatic and edited transcriptions, default Epidoc whitespace handling may not always produce expected results. Problems arise in several situations, the most common of which is spaces that appear before or after a phrase-level element. XML treats whitespace differently when it occurs inside an element that is defined to contain only subelements and no free text, and elements whose definition allows a mixture of text and other elements. In the first case, whitespace around the contained elements will be ignored. In the second case, spaces and returns will be treated as actual text, and will appear in formatted output as a single space. This is complicated by the way that editors such as oXygen XML handle wrapping of lines - lines that are wrapped for readability do not have space or linefeed characters separating them, they just appear to.

                                                                                                                                                                                                                                                                                                                                                            In the examples below, expan takes subelements abbr and ex as well as free text. In the second case, spaces before or after the subelements result in spaces appearing in the output.

                                                                                                                                                                                                                                                                                                                                                            +

                                                                                                                                                                                                                                                                                                                                                            Managing Whitespace in Transcriptions

                                                                                                                                                                                                                                                                                                                                                            2024-03-05

                                                                                                                                                                                                                                                                                                                                                            • TEI definition: expan ; EpiDoc-specific + customization: expan

                                                                                                                                                                                                                                                                                                                                                            In diplomatic and edited transcriptions, default Epidoc whitespace handling may not always produce expected results. Problems arise in several situations, the most common of which is spaces that appear before or after a phrase-level element. XML treats whitespace differently when it occurs inside an element that is defined to contain only subelements and no free text, and elements whose definition allows a mixture of text and other elements. In the first case, whitespace around the contained elements will be ignored. In the second case, spaces and returns will be treated as actual text, and will appear in formatted output as a single space. This is complicated by the way that editors such as oXygen XML handle wrapping of lines - lines that are wrapped for readability do not have space or linefeed characters separating them, they just appear to.

                                                                                                                                                                                                                                                                                                                                                            In the examples below, expan takes subelements abbr and ex as well as free text. In the second case, spaces before or after the subelements result in spaces appearing in the output.

                                                                                                                                                                                                                                                                                                                                                                    <expan><abbr>Aug</abbr><ex>ustus</ex></expan> -    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug(ustus)
                                                                                                                                                                                                                                                                                                                                                            +    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug(ustus)
                                                                                                                                                                                                                                                                                                                                                                    <expan>             <abbr>Aug</abbr>             <ex>ustus</ex>         </expan> -    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug (ustus)

                                                                                                                                                                                                                                                                                                                                                            The following example will have no spaces around any of the parts of the abbreviation. However, if there were any line feeds inside expan they would be preserved.

                                                                                                                                                                                                                                                                                                                                                            +    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Default (Panciera) style: Aug (ustus)

                                                                                                                                                                                                                                                                                                                                                            The following example will have no spaces around any of the parts of the abbreviation. However, if there were any line feeds inside expan they would be preserved.

                                                                                                                                                                                                                                                                                                                                                                    <expan>Καρ<ex>ανίδι</ex></expan> -    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Duke Databank style: Καρ(ανίδι)
                                                                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.1.154)

                                                                                                                                                                                                                                                                                                                                                            If spaces appear in formatted Epidoc output where they don't belong, the first thing to do is to check the XML source files for spaces or linefeeds have been inserted during the encoding process, often for readability.

                                                                                                                                                                                                                                                                                                                                                            In some cases, for example when encoding inscriptions in Hebrew or Arabic that use a right-to-left writing system, it is necessary to use line feeds before tags, in order to preserve directionality. When preserving whitespace exactly as it is entered is important, you must set the <xsl:preserve-space> property at the beginning of your xsl transformation file and identify the elements to which this applies. Then, you can manage the whitespace explicitly during the formatting process.

                                                                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                            1. Elli Mylonas, author
                                                                                                                                                                                                                                                                                                                                                            2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                            Date: 2023-04-27

                                                                                                                                                                                                                                                                                                                                                            \ No newline at end of file +    

                                                                                                                                                                                                                                                                                                                                                            Transformation using the EpiDoc Reference stylesheets:

                                                                                                                                                                                                                                                                                                                                                            • Duke Databank style: Καρ(ανίδι)
                                                                                                                                                                                                                                                                                                                                                            (DDbDP: bgu.1.154)

                                                                                                                                                                                                                                                                                                                                                            If spaces appear in formatted Epidoc output where they don't belong, the first thing to do is to check the XML source files for spaces or linefeeds have been inserted during the encoding process, often for readability.

                                                                                                                                                                                                                                                                                                                                                            In some cases, for example when encoding inscriptions in Hebrew or Arabic that use a right-to-left writing system, it is necessary to use line feeds before tags, in order to preserve directionality. When preserving whitespace exactly as it is entered is important, you must set the <xsl:preserve-space> property at the beginning of your xsl transformation file and identify the elements to which this applies. Then, you can manage the whitespace explicitly during the formatting process.

                                                                                                                                                                                                                                                                                                                                                            Responsibility for this section

                                                                                                                                                                                                                                                                                                                                                            1. Elli Mylonas, author
                                                                                                                                                                                                                                                                                                                                                            2. Gabriel Bodard, author

                                                                                                                                                                                                                                                                                                                                                            EpiDoc version: post-9.5

                                                                                                                                                                                                                                                                                                                                                            Date: 2024-03-05

                                                                                                                                                                                                                                                                                                                                                            \ No newline at end of file